Jump to content

Search the Community

Showing results for tags 'referencing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

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

Calendars

  • Training Events
  • Coffee Breaks
  • Essentials Seminars
  • Webinars
  • Community Groups

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


Occupation


Homepage


Hobbies


Location


Skype

Found 13 results

  1. Is there a way to reference viewports or sheets from another project? I have to put together a report dealing with issues from the main project and would like to include drawings from the main project. Sections and details for example. I don't want to include all the geometry from the main project, so using design layer viewports is not an option. Thanks, Rudy Beuc
  2. Current behaviour… you can reference using layer import or you can reference using design layer viewport while you can create a design layer viewport from a referenced layer you cannot create a ‘referenced’ design layer viewport at the same time as using layer import referencing both methods have been around since 2009? both have been independent isn’t it about time the two co-existed? then we can do what Revit and autoCAD do
  3. Hi All! I'm currently working with two files referenced inside a third. The design layer AND classes structure is coordinated between the three so that we can model and design at will. Thing is that we are using the option for the referenced viewports to use the "host" classes visibilities, but each referenced file is split into several viewports each placed on the corresponding design layer so that when we layout in the host file, we see what we want... Thing is that I'd like to "collapse" the two guest files into a single one, and "try" the project sharing way instead of the referencing and here comes my problem. When I "break" the reference and tell VW to import the file, the design layers are imported with a new-name instead of importing the objects inside the existing design layers (which would have been just logic for me)... So... is there a way in which I can "paste" together two different models of two different buildings that have the same design-layers, floors, reference levels, etc. and MAINTAIN all this very important information structures? Thanks all in advance!!!
  4. Hallo All! I'm currently involved in a rather big project with several buildings that together make a block. We are thinking of splitting it into several files and federating them together in a master file, and I wonder if there is already a concrete workflow for this as, after my first attempts, I've hit some thick walls and I don't know if I'm doing something wrong. Let me explain... I make a file with all the correct storeys with the corresponding design layers attached to the correct reference heights. I open a new empty file with the same design layers and reference heights and reference the 1st file (is that right?). 1st problem is that the "reference object" is in the DL where I placed it and I can't control the reference visibility from the main file (yes from the object Layervisibility)... BUT I can configurate the reference so that it uses the same classes visibility as the host file. Is it possible to do something similar with the layers? My solution is to copy the reference in each design layer and adjust the reference layer visibility accordingly (i.e. copy the reference from GF to 1stF and turn off GF). This is painstaking! I get a "legoed" result. 2-3-4 references on top of each other... it "looks" right but it is horrible... you understand the problem as when I make a section of the frankensteined building, it must cut through several references and VW becomes crazy! Is there a correct way to do what I want to? Next question would be how to proceed when the references have different reference heights, but first things first... Thanks in advance!!!
  5. Hi, we have an issue with a number of our sheet files where at irregular intervals our title blocks lose all of their data (apart form sheet number and sheet name) and revert back to the default values. We have a titleblock style saved in our project library, with the associated record format, and this style is then referenced in to our various sheet drawings. Periodically all the information resets itself, which is an absolute nightmare as we usually just notice it as we are preparing to issue a set of drawings with it associated other stresses 😉 We had the same issue on VW 2019, have recently updated to VW 2021 but are getting the same behaviour. Has anyone else seen similar issues?
  6. This has happened to a few of us all working on separate drawings now - our drawing information sometimes seems to transport itself way way off grid, with no particular pattern as to why? Can anyone shed any light on this? In terms of our workflow, all of our drawings are set up initially using design layer viewport referencing, to reference in information such as topographic survey, architects / engineers layouts etc, from separate Vectorworks files. All of these referenced layers are set to 'Centre first import, align all subsequent imports' when initially importing into their own files from DWG. Once all of these design layer viewports are referenced (and sense checked that they are in the correct place and suitably stacking on top of each other,) we are then choosing to centre drawing on internal origin, before we begin adding our own information. We then use the design layer referenced viewports as a base to work from to inform our own design, which we draw on a separate layer(s) but in the same position, often snapping etc to the referenced layers and turning things on and off. Sheet layers are created with annotations etc, using both our own layers and the referenced layers. The file can be used for days or weeks working correctly. But then, suddenly we will notice that a sheet layer is only showing annotations and any referenced layers, with none of our own drawing information. The design layer references all remain in their original position, but our drawn information is appearing anywhere up to 250,000km away, and requires to be moved back into place. Is there a reason for this / something we can fix in our workflow to avoid? Or is this a bug of some sort?
  7. Hi all, Does anyone have an idea why referenced DWG viewport classes turn off after updating the file link? The classes in the linked file have not changed, only the contents have been revised. This happens with project sharing, at least. After updating the link the DWG disappears, there is only a small red rectangle at the insertion point (usually origin) representing the viewport. Selecting this reveals in the OIP that all classes have turned off by themselves. If I turn the classes on and update the project file, the classes will still be off for other users (of course, since class visibility is a user setting). However, this affects sheet layer viewports as well since the referenced dwg viewport class control occurs at the DL viewport, not on a sheet layer. Therefore, updating a DWG link will cause any dwg information to disappear in all related sheet layer viewports as well.
  8. We are having difficulties Referencing Symbols from Project Sharing file to Elevations / Sections sheet files, mainly the Level symbols, and grid lines symbol. Things that we use in both Elevations, plans and sections at all scales. We have a project sharing file, with multiple users for one bldg only (10 stories, 256 apartments), which is working fine. we than have separate vectorworks sheet files for plans / elevations / sections, which generate all the sheets as above. Referencing in the main Working file. but we can't get in the grid line symbols nor the level symbols, as we get an error message saying that the Working file cannot be referenced in (only the Project file), which we know... but the symbol is inside the project file, and not reachable from within the resource browser. is there a way around this somehow? kind regards anton
  9. ....I've added a drawing reference and then going to 'create a design layer viewport' to display the required reference file information, but 'select source' command is inactive...I must be missing something: any ideas?!
  10. Can you please consider as a matter of urgency for back referencing to be added to the Drawing Label sheet number when using auto coordination. This is a basic feature that is missing. So on linked viewports & on section viewports etc it shows where the detail or section is coming from. Our major competitors all have this. It is really important for an efficient workflow.
  11. Hi, I am having trouble with elements of my building model not appearing at the right height within a referenced file. We have a particular file set up within the office where the model is located within one file and then referenced into another file to create drawing sheets. The main model file is set up using stories within the design layers. When the file is then referenced the second file is unable to locate some stories (but not all). I have manually introduced stories to the second file to match, but this still doesn't work. Can anyone help?
  12. Hi there. I'm having a persistent issue with my viewports in sheet layers I have set up. The files are set up as follows; DESIGN FILE: SECTIONS PLOT FILE: SECTIONS The design file contains the drawn information and the plot file contains the sheet layer (plot sheet) with the design file referenced into it. I will set up my plot file correctly with my viewports referencing the relevant layers and it will appear to work for some time. After coming back to the file after a couple of day, the referenced information will of appeared to move miles out of location, meaning I need to either redefine my crop extents and drag the information back onto the sheet or simply redo the viewports from scratch. The design file isn't moving location. This can happen again and again, despite however many times I set up the viewports and don't alter the design file. Does anyone have any idea what may be causing this to happen? I've only noticed it since updating to vectorworks 2017 and converting my drawing files to 2017. I have the 2 service packs installed as well. Any help would be much appreciated. Regards. Sam
  13. Is there a way to use a referenced drawing in black & white only? I want to bring in the architect's backgrounds into my drawings as a reference, then annotate viewports with my own information (position of light fixtures etc.). To make my own drawings clearer, I want to set the architectural drawings to black and white only, then annotate them with my information (position and shape of light fixtures & circuit references) in a colour, so that this information stands out on screen (but still gives me the option to print everything in black & white) However, if I set a viewport to black and white (in the Advanced settings), then all annotations are automatically black and white, too. If I go back to the referenced drawing, and set the document preferences to black & white, then this seems to affect the on-screen display of that file only, as when I then reference or update the drawing into my file, all of the class/layer colour information faithfully returns & I am back to where I started. This is maddening me; surely there must be a simple way to display the referenced drawing in black and white, without manually editing the architect's file to set all layers & classes to black and white & I am just missing it?
×
×
  • Create New...