Search the Community
Showing results for tags 'viewports'.
Found 54 results
ADDED: Scroll down to see a video of this issue in action I have a number of booms in my plot. These are shown on my lighting plot layer with viewports created by the Create Plot and Model Views tool. I have the definition and model layers for all of the booms hidden. This setup correctly shows the boom in plan view with instrument symbols. When I pan around the document however (holding down [Space] and dragging with the mouse), the viewports boom viewports all suddenly show the 3D model of their respective booms, including the full width of the pipe and the 3D mesh for the instrument model. If I change the visibility of any non-active layer, the viewports pop back to the (correct) plan view, even if the layer whose visibility I changed has nothing to do with booms (such as my softgoods layer). Toggling the active layer's visibility does not fix the rendering. I assume that this is a bug of some form? If not, what am I doing to cause this behaviour? Edit: I can cause a similar behaviour as well: If I edit the definition layer for one of the booms, then hit the Previous View button to go back, all my default layers get shown (such as lighting, softgoods, venue, notes), however only the selected layer (lighting) is shown on screen. If I toggle the visibility of any other layer, all of the missing layers snap back into being shown.
Hi I have a structural model, and I've done section viewports in a plan view, to be rendered as hidden line. I have 3d conversion set to low for speed, and they have a depth set (not infinate) I render the section, and it looks lovely... when I go to annotate it, on entering the viewport it displays as hidden line, with tonnes of unnecesary extra lines making redraw very slow and difficult to annotate. When you exit, you need to update the viewprt and then it displays as expected. Previous versions of VW always allowed you to annotate the hidden line render, and not go to wireframe.... anyone else with this issue? PC, Win 8.1, Nvidia graphics Cheers
I am currently working on a multi unit development. Currently there are 12 individual units (~100m² each). Each file has its on VW file. There is also one VW file which has a referenced VP for each of these units. This "master" file is ~550mb and is quite sluggish and prone to crashing. Soon will be adding another ~20 units for the next stage and I am concerned that the file will become unusable. Is this the correct approach? I think my comp specs are above recommended? The units aren't particularly complex, simple monopitch roofs, two cladding types. Any help would be greatly appreciated.
I am new to using Viewports. I have modeled an object on a design layer and have now begun building viewports on sheet layers. When i attempt to dimension objects in the viewports (after first double clicking the viewport to edit annotations) i encounter the following problems; 1. If i want to show the angle of something, i find i first have to draw two lines over the objects and then use the angle tool to get the angle of those 2 lines. 2. Similarly, if i want to use the radius tool on a curved piece of geometry, i have to find it's center, and draw a circle out to it, use the radius tool on the circle, disassociate the dimension from the circle and delete the cir cle so that it doesn't show up in my drafting. 3. anything curved seems to be a real problem for viewports, displaying it properly, (increasing the 3d conversion resolution in Vectorworks preferences) and as i said above dimension-ing it, finding it's center. So is this the way these things are supposed to work? or am i really missing something? I've been using V-Works for about 9 years now, having started with V-Works10 / moving up to 2009 / 2011 and now a big jump to 2016. I work in the entertainment industry, drafting scenery for movies and TV, not alot of standard doors or windows, lots of curvy sci-fi things, typically i am building the objects myself, but now I have to draft them for others, love the idea of viewports, but feel i am missing something as relates to dimesioning and displaying them efficiently. Thanks for reading this. Paul