Jump to content

Search the Community

Showing results for tags 'reference'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted / Issues Resolved
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • ConnectCAD
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
    • Hardware
  • Customization
    • Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • Workflows
    • How To
    • FAQs

Categories

  • Marionette - Objects
  • Marionette - Networks
  • Marionette - Nodes
  • Marionette - Menu Commands

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Occupation


Homepage


Hobbies


Location


Skype

Found 12 results

  1. From the perspective of creating and maintaining drawings standards: Is there a way to have a class in one document and have it referenced in another document, then make a change in the class attributes and have it change in the referenced document. (as you might with a symbol) Also is there a way to rename a class and have it be renamed in the other referenced documents.
  2. PROBLEM: Vectorworks can't properly locate referenced DWG onto a model PROCESS: We reference DWG files created by our consultants (as is normal for any architects workflow) - First, we make sure all files have the same (0,0,) point - Then, we import these DWGs as design layers in a VWX file, so we can append class names for better organisation. - Finally, we Reference this VWX file and put them in our Project File. MANEFESTATION: On one terminal (where were did the imports), the file is in the correct location. However, in the shared project file, other terminals open this file and the position is wrong. [See enclosed screenshots] Also, if there was permission issue, causing us to re-save this project file, we also lose the correctly referenced location. This is frustrating and wonder if others have experienced similar issues.
  3. I have accidentally created two separate references to the same file, 'gmv symb lighting v2019.vwx' They are both up-to-date as a 'path to relative document'. Unfortunately, I don't recall the exact steps I took to find myself in this position. I believe one was created as an absolute reference. Knowing this, what steps can I take to reconcile the two? Thanks.
  4. For some reason I cannot reference external file via viewport on a design layer. "source" is greyed out. Any ideas.
  5. I have not often used dvlp refs to external file but wanted to report. In at least one file, Vwx crashes a second or two into a slvp update if a dvlp ref is out of date. Is that usual? Seems like it should refuse to start the slvp update and warn about the out of date ref? -B
  6. Hello! I'm having some troubles with one of my files, a few days ago I couldn't open it anymore. Now I can open it, it seems to be fixed, but anytime I try to update my reference (with is on the office server), vectorworks shut down. Do you have any idea how to solve this?! Thanks for the help, best regards.
  7. Currently Vectorworks does not have an option to fully import referenced files afterwards and break the reference in one go (e.g. similar to the bind option for references in AutoCAD and compatibles). It would be nice to have a bind option that would allow us to fully import a referenced file afterwards through the organizer and remove the reference after successful import. Especially with multiple references this can be convenient.
  8. Since the introduction of Project Sharing in VW2016 and many other features in VW, it seems like the company has made a decision of steering users to single file workflows. With that said, we haven't found a way yet to consolidate our complex and memory intensive referenced file workflow into a single file system...at least not practically. I'm curious to what credit VW gives to differing workflows when developing tools or looking at the big picture. While I love the idea of doing everything in one file, we face two large hurdles to practically implement this practice on some of our larger sites. These roadblocks are: File Size - Our work is often broken out into 3 different segments (layout/grading, planting, and irrigation); thus, we have created a separate file for each. We have created a referenced file workflow that combines each of the various files together to generate our documents (schematic, design development, construction document). On large projects it is not uncommon for any one file to top out at 1+ GB, and individually, this already puts a strain on our machines. I cannot imagine combining our files together will result in smaller or more manageable file sizes, so we really haven't even considered it. Layer Management - With our multiple files, each with their respective design and sheet layers, it is also equally hard to imagine combining all of this organization into one file without a better way to organize it. Take our irrigation files alone. Our practice is to put each individual irrigation design zone/station into its own respective design layer. We do this for a myriad of reasons, but mainly, it is just easier to track and document complex systems. That said, it isn't unheard of that some of our irrigation files will contain almost 100 design layers! Similarly, we have worked on projects that have 20 irrigation sheets, 20 hardscape/grading sheets, 20 detail sheets, and 20 planting sheets. If I put all of that information together in one file, there is no way to organize it. I imagine a simple hierarchical or folder system similar to how classes currently sort would help this exponentially. The main reason I bring this topic up is that I have noticed that many of the new features VW has pushed in the past few years are solely intended to function in a single file workflow, but immediately run into difficulties when using a referenced file approach that we currently employ. Take the new Titleblocks for example, or even the old Sheet Borders...how do I use the same titleblock in 3-4 different files while keeping the Project specific data constant and maintaining individual control of the Sheet specific data? Referenced symbol? Referenced Titleblock Style? This works great in theory, but you quickly realize that the Project based data, when changed in one referenced file, does not transfer to other referenced files. I would love to hear more about peoples experiences/struggles with their single file or referenced file workflows. How is it working for you? Cumbersome? Have it all worked out? What else needs to be done to make this practical?
  9. Now that VW supports multiple views / windows / open files at once it would be nice to have a way to force referenced design-layer view ports to update in real- or near-real-time. As it is now, when I make a change in referenced file (say, moving the height of a fence panel,) in order to see the change in the other file with the DLVP in it, in the main file I have to do: Tools --> Organization..., then select the "References" tab, then select the referenced file, then click "Update", after which the changes propagate from the master file to the DLVP. It'd be nice to have a check-box in a DLVP for "Auto-update this viewport whenever the referenced design layer changes." Is there any work around for this? Editing the workspace doesn't work as it doesn't allow for auto-navigation within the "Organization..." modal dialog box, nor for assigning a shortcut to the "Update" button in that dialog box. EDIT: this should be posted in General -- moderators, please consider moving it. Thanks.
  10. I have a 3D model from which I have generated a series of section viewports on sheet layers. Is it possible for me to reference these sheet layer viewports into the design layer of another file? (I know I could do this if I'd generated design layer sections, but I will potentially update the model so I'd like to keep the link.) I have a Landmark 2014 licence.
  11. I created my survey site model in one file and a building in a second file. From the Survey file, I attached the building file as a reference file. But Now , how do I translate and rotate the imported layer so that to register in the exact location over the site model? I see the reference layer , but it is placed way out of place.
  12. Hi -- I am referencing Part "P" into Assembly "A" I have classes / layers in "P" that I want to hide / show in different viewports in "A". How do I go about this ? When I go to the "Layers" or "Classes" visabilites in the Viewport dialogue box - I don't see the referenced layers / classes. Only the local ones. I don't want to control from the referenced viewport object of "P" - as I don't want it to be for ALL viewports in "A". Hope this makes sense Thanks!

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...