Jump to content

Search the Community

Showing results for tags 'viewports'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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
    • 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


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


  • 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


Last Updated

  • Start


Filter by number of...


  • Start








Found 45 results

  1. fergus

    Grid Lines

    I find using the VW grid line bubble tool very cumbersome and objects often struggle to snap to the lines as well as if the gridlines were drawn just as lines. It is also very cumbersome to adjust, are their advantages to using it? Is there are quick way of transferring gridlines on plan to elevations or section viewports without drawing planes to transfer them to the viewport and then adding them within the annotation layer?
  2. It would make navigation of viewports much easier if they can be associated with the page that they are located on. An extra column in the navigation browser that gives the sheet name and number would be helpful.
  3. First of all sorry for my rubbish title, could think what to write!! So in VW2017 when editing your viewport crop you could see (in grey) what was outside of your crop, I find this useful. I have noticed however that in VW2018 this doest seem to happen? Is it a feature that just needs to be turned back on? I have (hopefully) attached two images to show what I mean. Thanks in advance.
  4. Hello Forum, I'm creating elevation views on my sheet layers from my models. I like to display using 'dashed hidden line' as a lot of my interiors have furniture with shelving inside etc. I know I can turn off classes for certain objects I don't want to display. Is there a way to 'hide' objects from appearing in the background as dashed hidden lines, it makes the elevations look messy and confusing. I guess I'm looking for an efficient way to achieve this, any help much appreciated, cheers (screenshots attached)
  5. Is it a known issue that hidden line sketch mode (I'm using Section viewports in this case), produces seriously unstable results? I've run into a few different ways it fails to draw the expected result: The most common issue is that it displays everything in the view, but sketch mode does not appear to be activated. In some cases, the line work initially displays in sketch mode, but then after drawing annotation in the viewport, sketch gets deactivated. To be clear, sketch is still checked off as the desired render option, but the viewport behaves as if it's been turned off. Other times, all of the lines "beyond cut plane" simply don't display at all. Silver lining here is that for whatever reason, this seems to reactivate sketch mode for the cut plane elements and the annotation. There's also cases where the model line work maintains sketch display, but the annotative layer displays without sketch. I've also gotten the reverse situation, where only the annotation was displaying in sketch! It's really all over the map. There does seem to be one way to control this situation (at least it's worked so far). I discovered that by setting the line style of objects beyond cut plane to "use original" in the advanced properties, I can stabilize the sketch render setting, and both model and annotation maintain the correct display. When this is overwritten with a single class, all bets are off. Unfortunately, using the original line style of each modeling object requires a lot more work than being able to quickly set all lines to the same weight. So this is an unfortunate work around to have to accept. Thanks, Matt
  6. It would be nice if one could modify/edit classes in multiple viewports simultaneously. Not just turn them on or off, but also override class attributes like textures etc.. This would speed up work if one is rendering different options for certain components, ie. cladding options, component colours. Also it would be great, if one could override the texture for all aspects of object (wall, roof directions) with one button click. So you don't have to click 5 times to make sure the texture is going to be overridden for all aspects object. Thanks
  7. It would be SO very useful and supportive if it were possible to organise Design Layers, Saved Views, Sheet Layers & Viewports to into sub-folders, showing up kind of 'grouped' in the Navigation Palette. --> Same as you can do with Classes, by simply adding a dash ' - ' in between the words. I have many highly complex VW files, and they are filled with a huge number of Design Layers, Saved Views, Sheet Layers & Viewports. Any input is much appreciated.
  8. There are two issues with viewports linked to cameras. The first is the limit of 196mm (35mm equivalent) of zoom (12.45 degree field). This is an artificially low limit that does not allow the previewing of long glass on video cameras (33X or up). The second is that in the OIP it would be great if you could change which camera a viewport is linked to. When you select the viewport on the sheet layer it should say Camera: <name> and you should be able to point it to a different camera.
  9. I actually have two frustrations. The first is that elements of my model are disappearing in openGL. It seems to have something to do with how much of the object is behind the camera. The second is that when I make a viewport from a view, the visibilities change. Polygon fills which are on the layer planes disappear, and the disappearing elements (mentioned above) become more of an issue. I have uploaded two screenshots one from the Design layer (green floor from the 2D Polygon on layer plane) and one from a viewport. (Notice the absence of the wall on the left.) A few notes: In order for the viewport to fit onto the sheet, the scale of the viewports is enormous (1:1500) Both origins are close to the model space I got the model to cooperate by splitting up the elements so that not much of the element is behind the camera. I feel that this is a workaround, not a solution, The elements also disappear in the design layer, but not as frequently.
  10. Cookie_NZ

    Viewport defaults

    Hi all, Is it possible to change the 'Advanced Viewport Properties' defaults for all new viewports in a file? I'd like to have 'Adjust Flipped Text' default to off if possible. Thanks!
  11. Hi all, I'd like to hear from anyone who has or is currently experiencing this issue in any version of Vectorworks. I've had two users report this, one on Mac, one on Windows, both in Vectorworks 2019 SP1: The first user said Sheet Layer Viewports weren't being affected by alterations to their Class visibility settings, but changing Class visibilities in Design Layers turned off those Classes in all Sheet Layer Viewports instead. The second user only described that: In Design Layer > change visibilities of Classes = Those same Classes get turned off in [all] Sheet Layer Viewports. Restarting the computer was confirmed as a remedy by the first user. Is there anyone else experiencing this? And if so can you please reply including: Vectorworks version and Service Pack Platform and operating system. Cheers! Jeremy
  12. I believe this should be considered a bug, or at min. not desirable behaviour. Page based symbols do not display correctly when Navigation Graphics is set to Best Compatibility. This may be is a result of my graphics card, but certain things should always show. - Create a page based symbol - when inserted into a section viewport it scales down based on the scale of the viewport it seems. - when a crop is applied to a viewport the symbol increases in size? If you print a PDF it displays correctly. Page Based Symbol.vwx
  13. Hi there, Any thoughts as to why my Windoor ID tags are not showing up correctly in elevation? For context the elevation is created using a section viewport placed onto a design layer that is the same scale as the model plan layers (1:100). Correct classes all appear to be on, and viewport is set to display planar objects. As you can see in the attached image the tag can be seen, but the actual ID number is missing. There is no trouble viewing the IDs in any plans. Thanks in advance.
  14. Previously my rendering attempts have been relatively basic; I set up a sheet layer viewport, and then use the settings for the viewport to control how the render looks. But I know there are Renderworks cameras. Previously when I've dabbled with these I've got confused and given up due to lack of time but this morning I decided to brace myself and try and get my head around what they are for. So, it seems they basically give you a greater range of controls over how your renders look ("camera effects" and so on). I have to create a camera and I have to create a viewport, and I have to link them. OK. Got it. Then I want to adjust the settings for that rendering. I've linked a camera to the viewport because that gives me greater control, via the camera settings. When I right-click on my viewport to edit the camera I get an object info pallette titled "Renderworks Camera". So, logically, everything that controls how my rendering looks is in now in here, instead of in the settings for the viewport, right? Wrong! In my camera settings I find a dropdown called "Render Mode". Aha! This is where I change from an OpenGL rendering to a Renderworks one. I choose a Renderworks mode. Nothing happens. Ok. Maybe I have to return to the viewport for it to take effect. I return to the viewport on the sheet layer. Nothing has happened. I try updating the viewport. Nothing. Maybe I thought I'd changed it but actually hadn't. I go back into the settings for the camera. Yes, I have changed the dropdown, and now the view, in this "edit camera" mode, is rendering in a Renderworks mode. Back to the viewport on the sheet layer. Viewport is still rendered in OpenGL. *time passes, some cursing* So I discover that what controls the render mode of the viewport is what's set in the viewport settings, not what's set in the camera settings. But some things in the camera OIP settings don't affect the viewport. For example if I go into "edit camera" and using the camera OIP: - Change to top/plan view, the view in the camera edit mode does change, but does not in the linked viewport, and has not been preserved next time you go into the camera edit mode - Change projection from perspective to orthogonal, view in camera edit mode does not change, does change in the linked viewport, and has changed next time you go into camera edit mode. - Use "activate camera" then "click to aim camera", view in camera edit mode does change, does change in the linked viewport, and has changed next time you go into camera edit mode. In other words the controls in that camera OIP are completely inconsistent in what they do. Some seem to control attributes of the camera object, some seem to control not the camera but what you see in edit mode, and of these, some take immediate effect and some don't Am I alone in finding this horribly confusing? Basic questions 1) Why have settings in the camera OIP that neither affect the camera itself or what you see during that "edit camera" session? 2) Why not just control all this stuff in settings for the viewport itself (fundamentally what's the point of the renderworks cameras at all?)
  15. nubourne

    Vanishing Elevation Viewports

    Hi, I hope all of this makes sense - I've been trying to troubleshoot this for hours. I have created a 3D model of a set. I use section viewports (that I have configured to be elevations) to create my front views of the walls. I am to the point where I am setting up my sheet layers and dimensioning. All has been fine - for the most part. I'm not sure at when in the workflow, but something changed. All of the elevations were on the sheet, and I had dimensioned everything. I went to work on the next sheet of elevations, and went back to the previous sheet to double check something, once I got back to that sheet, one of the viewports was missing a wall - dimensions where there as annotations, and a few stray shapes that I couldn't identify. Thinking this was strange, I go back to the original sheet (plan view) to see if I had unintentionally moved the viewport reference (section line?) and it's not there. Nowhere to be found - whether selecting all, or using the custom selection tool. I didn't save, quit the program and reopened to see if that would fix it. No go. Quit again and shut down the computer (not restart), then rebooted, opened VW - still had missing info. Every other viewport and its reference is fine. I tried to create a new viewport and nothing. The problem isn't resolved. Has anyone run into this before? Thanks.
  16. As a scenic designer, rarely do I have walls parallel or at 90 to the proscenium. So what is the best way to create a plate of elevations (front, section and plan views?) When creating a section I know I can do it from the top/plan view. Is there a way to rotate the view of the viewport other than entering degrees in the dialogue box? I tried set working plane, but that didn't work. But many times I might have walls at "random" angles - (52.36 or whatever). Seems like there must be a better way? Seems like this should be a basic function of VW - creating viewports from a 3D model, but this seems not to be addressed very well. thanks.,
  17. After a recent career move, I am back at working on VW2015 (MAC) after being on VW2018 previously. I am experiencing what I can only describe as a serious bug in viewport annotations for the first time. Text, linework, dimensions… annotated jump and shift position within the viewport, it can happen as easy as returning to the file the next day or moving the viewports around. The shifting is not always at unison; elements can go ‘all over the place’. This has caused tremendous strain to my performance to the level of a project successful completion being compromised. I have a hunch it could be related to rotated ‘view plan’ in design layers as well as copied annotations from one viewport to another retaining some sort of fixated origin point. But there seems not to be a single cause of the problem. I contacted our local representative but basically was told “bad luck” for using such an “old version” of the software. I have expressed my desire to upgrade within the company but I am afraid they will wait for VW2020 to do so. Any help / advice in solving this issue will be appreciated…
  18. I love saved views! Viewports are critical to anything but the smallest projects. How to make them better? My basic set of saved views are essentially copies of my basic sheet viewports. But as a project gets more complex the viewport settings change with new class/layers, overrides or whatever. So a common work step is to update those saved views to match. Why not have it automated? Aren't viewports really just saved views on a sheet? Sure you can get there, but many clicks and much time can be saved by having every viewport show in the saved view list and track with those changes! A sub list could be links to the annotations for those viewports. But that would only save time and frustration...
  19. My workflow is: I make changes to my model, I've set up several sheet layers, using cameras, to show the views I need, and I've set the render style for those. But I have to click and wait for each one to render before going onto the next one. Would be great to have some kind of batch render setting so I could set them all going without having to do them manually. (Have searched, couldn't find a duplicate - apologies if there is one!)
  20. Hi, 2018 keeps driving to a complete unusable halt in my sheet layers after introducing a 3rd or 4th viewport. My drawings are pretty light and are not too complex and only rendering in wireframe (to consider another rendering format is unthinkable) the program then becomes unusable with massive delays, jerky zoom and content disappearing when zoom is halted. The same file in 2017 works fine, is this a known issue with 2018? A quick check on the system shows CPU running @6% and RAM only @ 8gb of 16gb
  21. hi call me daft but is there anyway to see your viewport crop in the design layer after it is made? i thought this used to be a feature but can no longer make it work. currently in VW2017
  22. Hi all, just a quick helping hand being requested as I've deployed VWA 2018 onto our computers, but my own workstation is the only one upgraded to High Sierra on the Mac. The problem is when I copy a viewport from one sheet to another in the same file, it becomes a PDF! As such, I can no longer edit it as normal. Is this a bug, or did I mess up a setting that I can change back to stop this behavior? Thanks in advance for any guidance!
  23. I'd like an option to copy and paste objects from another file but without importing Classes. The information would come in as an object that behaves like a Viewport, with its own Class visibilities. The difference being that you wouldn't need to create a Workgroup Reference, nor import all the data from a Design Layer when creating a Design Layer Viewport (both of which I find eventually weigh a VW file down). When co-ordinating with engineer's drawings, for instance, I tend to copy and paste just the bits I need rather than creating a WGR and Viewport. The downside is it brings in their Classes. If they have a lot this can impact quite a bit on Class navigation.
  24. Does anybody have issue with creating a sectional viewport of U shape stair on to sheet? Please see attached image It looks good in 3d perspective or in plan but when a sectional viewport is created is starting to mess up .
  25. I'd like to be able to double-click into a Viewport with Hidden Line rendering and have an option to edit the lines. Including deleting, changing length and changing thickness. I'm happy for these changes to then be obliterated if I update the viewport, but it's meant just as a final touch-up workflow for those little niggly bits that are extremely hard to model out. For instance this request is motivated mostly by those pesky lines that show up where you have a wall meeting another wall parallel to it but that is already L-joined to another perpendicular wall.


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.