Jump to content

Search the Community

Showing results for tags 'bug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
    • News You Need
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment
    • Vision and Previsualization
    • Braceworks
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • 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
    • Terms of Service and Community Guidelines

Calendars

  • Community Calendar

Categories

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

Categories

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

Location


Skype

Found 45 results

  1. Viewport Rendering Artifacts

    We're seeing our elevation viewports display all kinds of inconsistent rendering behavior. It appears that a portion of the viewport is rendering over the top of another portion of the view. Re-rendering the viewport will sometimes correct the issue, sometimes the artifact will move somewhere else, and sometimes it will remain. Usually if I re-render enough times I can get a clean view. This started out as an occasional bug, but is increasing in frequency. Attached are the same viewport (rendered twice). You can see the artifact in the upper left.
  2. If a drawing label is in a VP annotations, you can renumber it - and if there is a conflict - VW will give you a prompt with the option to renumber. If the drawing label is not in a VP - and you try to renumber - and there is a conflict - it will just not work - and will revert back to the original number. This seems like a bug - you should be able to renumber drawing labels.
  3. Hi I noticed another bug in 2018 SP 3 on windows 10. If you use the eyedropper tool to copy the properties of one dimension to another, it does not carry the witness line override settings. does anyone have this issue as well? OSX ?
  4. Sometimes, connections between nodes are not retained when I move the nodes around. It looks as if the nodes were never connected in the first place, even though I snapped an output to an acceptable input. The attached PDF shows nodes from a shared resource on the forum; I've also attached the VWX file. The string input nodes are not connected to anything, but they have wires running to floating circles. I made sure that all classes and layers are visible, so I'm certain that there aren't any hidden nodes. The wires can be unsnapped from the mysterious circles, and reconnected to a proper node. This issue occurs when I copy+paste portions of a marionette network for re-use in another marionette network, or when I relocate portions of a marionette network. The issue reappears, even after connecting to the correct node. marionette_issue_nodes-not-connecting.pdf ODBC_v2017_v2018.vwx
  5. We have been experimenting with Project Sharing and are having some difficulties. On this particular project, a team member with Admin access to the file made changes to the Plant Definition and 2D symbol for a few of the plant resources in the file. He also moved them around and and added a few here and there...save and commit... When I open the file and refresh (I'm also an Admin), I can see that the Plants have been added and moved around, but the Definition does not change...the plants still appear at the same size, spacing, etc. as I had them prior to his changes, and the 2D symbol changes don't appear either? This is odd and only one of several abnormalities experienced with Project Sharing. We are in some desperate need of education regarding Best Practices for Project Sharing and would welcome any input. Thanks.
  6. Wall assembly glitch

    Good morning, Ran into quite an annoying bug this morning when trying to assemble a curved curtain wall. Process - first i created a curved polyline to be the shape of my wall then used the tool distribute along path in order for me to segment my wall into workable corners afterwards i followed the contours of the intersections between my lines and curved profile. After assembly the wall, I noticed I cannot modify all the walls height at the same, and more importantly, when i reselect the walls - i cannot edit them anymore, as if a glitch happened. I'm uploading a file for your review. Let me know if you can recreate the bug. Note - you have to do it from scratch. If i close the file and reopen it, it doesn't reproduce the error anymore. I've reproduced this already on two machines. Note 2 - If you try to modify the walls - it will show that it is a wall, but as if its stuck on a command. If you press ctrl-5, it resets the tool. very strange. Note 3 - even after the quick fix, i notice the problem translates to other tools. In my opinion this could be a memory leak. This bug is w/ Vectorworks 2018 SP 2. I haven't tried with others. Sincerely, Sam Wall Glitch.vwx
  7. Workspace in 2018 - Keeps resetting

    In VW2018 we have been having issues with our custom workspaces resetting upon each open. A few of us prefer to stack our Basic and Landmark toolbars on the left side of the screen, 2 tool columns wide each. Upon open in 2018, these tool sets completely collapse every time, no matter how the workspace is saved. Only been an issue in 2018, never before.
  8. We have a new issue, never encountered prior to VW2018. Currently we are having difficulty with Plant plug-in object visibilities...I've attached 2 screenshot videos (no narration, sorry) that show what we are encountering, but I will do my best to explain. We have (8) different classes we use to control the internal visibilities of our Plant objects. Currently, these classes are not responding to simple on/off/gray controls unless you go into each plant individually, after changing the visibilities, and then exiting the plant. Then and only then do they look correct. To make things worse, this error is compounded by the fact that as soon as one database worksheet plant schedule is recalculated, all of the active visibilities and buggy visibilities revert to a pre-altered state. I know this isn't the most clear description and I hope the screen captures do it more justice. Ultimately we need this fixed ASAP. This is a bad bug that affects our ability to produce any documents. Plant_Symbol_VW2018_Bugs.mp4 VW2018 Plant Bug 2.mp4
  9. Does anyone else run into accidently undocking palettes and not being able to re-dock them without restarting VW? It also seems way easier to inadvertently undock a palette than in previous releases.
  10. Running VW 2018 SP1 on Mac. We have a few fonts (specifically DIN) that we use for our drawings that are becoming distorted when exported to PDF. The characters become squished to look tall and narrow with lots of space between each letter. This is occurring in all text including titleblocks as well as drawing labels. Changing to a system font seems to fix this (tested with Helvetica). Unfortunately our title block was really designed around the DIN font, so changing the font would require a complete redesign of our titleblock. The problem can be fixed by checking the "rasterize text" option in the export to PDF window, but this is really not ideal. The font was working perfectly for us in VW 2017 and prior. Anybody else with font issues in 2018? Any possible solutions?
  11. Hoist Insertion Tool Snapping is Offset

    When trying to snap a motor via the red insertion guides to a beam in a drawing (see the vertical light blue line in the photo) even when my cursor snaps to the light blue beam (as pictured) the red insertion square does not line up with the beam, it's offset slightly to the left. So the hoist always inserts slightly off the beam. Is this a bug?
  12. I have a number of extrude along paths that are only visible in my sheet layer viewports, and not visible in the design layers. This makes editing them or deleting them impossible. Any ideas?
  13. I was trying out using my multi-monitor set up with the new MultiView. If you create a floating pane, the class and Layer visibility drop-down in the OIP does not drop down.
  14. Section Viewport Bug

    Good Day, 1) When creating a section viewport of a DLVP the objects not inside a symbol do not 'cut' and render with the selected 2D attributes. See the attached VW file and PDF. 2) When making changes to the layer with the objects, the changes are not reflected when updating the section VP unless you toggle on and off layers. DLVP Section Rendering Bug.vwx DLVP Section Rendering Bug.pdf
  15. Space Labels Multiple Bug?

    Hi All, We're having a pretty serious problem with the space label tool right now, and I'm not sure if this is just affecting us or widespread. Basically, we set up multiple space label tags (in order to be read at difference scales - some show more or less information than others). For some reason the 'allow multiple space labels' box in advanced settings seems to keeps unticking itself. See vid below.. Any ideas?? Thanks, A
  16. When using the Existing Tree tool, somehow empty folders are created in the resource manager. Every edit, move, copy, tweak, etc. in an existing tree tool results in the creation of an empty resource manager folder. I am currently working on a project with 150+ existing tree tools and this resulted in the creation of over 200 empty folders?
  17. I have created a texture that represents a mesh with 25mm square holes. I have also created a hatch to go with the texture. I would like to be able to show the mesh in a variety of render styles including hidden and dashed hidden lines. Although textures and surface hatches are meant to lineup I can't make this one line up in any way without offsetting the surface hatch which is not the point of the lineup window in the surface hatch section of the texture. I have included my drawing and wondered if the forum hive could take a look and tell me what I am doing wrong! Is it the hatch that is wrong or the way that I have the Hatch Alignment settings? Or does the surface hatch alignment feature not work? Thanks Mesh.vwx
  18. Another one of those, try, try again until you succeed posts. I posted this awhile ago and included a video, to no avail or answer yet. When using the new irrigation tools, once a pipe is drawn and components are added to it, there is no way to rotate the graphic symbol other than to a true north. What is interesting is that the OIP will show a rotation angle even though the graphic symbol doesn't rotate. You can see the video for a better explanation (sorry, no voice over). https://screencast-o-matic.com/watch/cDX33GQh5g This is really annoying because we almost never get so lucky to work in a true north orientation and our best practice has always been to relate system components and their rotation to the line on which they are placed. It just adds graphic clarity. This problem is also true of any tags or labels that are created from an irrigation object. They cannot be rotated so as to appear horizontal on a sheet layer viewport. This is common practice and I don't understand why the usability hasn't been integrated. We have largely avoided the entire irrigation suite, and this problem is a large reason why. Fix please!
  19. I have asked this question before and don't know if I ever got a response. so why not try again. When using the CREATE OBJECTS FROM SHAPES... command to convert any basic object into something else (doesn't matter what), there is a conversion of any accurately drafted arc and radius information from a point on arc mode to a bezier mode. See the attached image for comparison. This is a frustrating phenomena/bug for the many reasons noted, but most importantly for the loss in fidelity. Once an original object is converted, there is no way to restore the original arc fidelity. I have requested a fix for this before and feel that this should be dealt with ASAP.
  20. Undo History Grouped Bug

    Hi, I have my undo history set to 'Grouping All View Changes', which works well for the most part. However, in certain files this setting appears not to work properly.. if I navigate using shift+mouse scroll wheel (horizontal) or alt+mouse scroll wheel (vertical), it does not group these changes. What this essentially means is that I can't use this method of navigation without making my undo history useless! Again - this only seems to happen in certain files. Any idea what could be causing this? Perhaps I have some other setting enabled in the file which is overriding the group changes selection? Thanks!
  21. Hey Everybody (long time listener, first time caller), We've been using referenced viewports as for light plots with small changes between shows with quick turnarounds. It has worked fine for the past couple of years, and right at 2017 SP3 we started getting label legends that stacked all of the containers on the fixture. Ironically, the information pertaining to the container stayed in place. Anyone have any thoughts as to why this would happen? I'm pretty sure it's a SP3 problem, but I know SP3 added some features, I was curious if it added something that might cause this, or do we have to go back to SP2?
  22. Hi, We have been attempting to use the new data visualization tool, which clearly has the power to become very useful. However we are having some difficulties. Firstly, even using this tool in a basic way seems to cause extreme slowdown. Secondly (and more critically for us currently), the display for some areas seems to be buggy and 'stuck' on an incorrect hatch colour. Please take a look at the video below which shows the issues. The beginning of the video shows how quickly our systems handle navigation on a normal sheet without data visualization turned on. The second sheet shown is using simple data visualization to show space objects with various coloured hatches applied. You can see how much more slowly this sheet refreshes as zoomed or panned, which is infuriating to work with. But the area which is coming up as as a black hatch at most zoom levels is the most problematic. This type of issue has cropped up on a couple of our drawings, and is still present on pdf's if printed at this scale.
  23. Seems that in VW17, if you mirror a callout while in a rotated top/plan view, the mirror changes shape and position. In VW16, when I mirrored a callout in rotated top/plan the mirror would nehave exactly as if I had mirrored it in top/plan - that is to say, it would be oriented 90 degrees (or whatever angled I had mirrored it to) to the original. The only workaround I found so far is to change to top/plan and then mirror the callout. This results in a callout that is rotated incorrectly, but is at least the same shape. From there you just have to rotated it back to match the original. I did a quick search and didn't come up with any posts about this already, but im surprised nobody has flagged this one yet. I have been able to replicate the bug in new files and on multiple PC and Mac machines.
  24. After doing several viewport FQR updates. The screens and any texture that is assigned glow, seems to do this weird inverted thing color thing. This has happened in multiple files, fresh ones, and older ones. Anyone else run in to this? Is it a bug? Restarting VW fixes the problem for a handful more renders. Vectorworks 2017 SP2. Machine spec's in the screen shot below.
  25. Fixture Mode - Bug

    Noticed that my lighting fixtures (spotlight - theatrical symbols - all custom) keep disappearing when I zoom. I thought maybe there was a scale discrepancy, but after checking that and checking to make sure that my class and layer options are all correct, I started futzing with the Fixture Mode dropdown. When I am able to select the fixtures, even if their fixture mode is already set to none, if I grab that dropdown menu and set them to none again, suddenly they don't disappear. This is true across the board, no matter what symbol or what fixture mode. Setting them to none makes them all stay. Edit: Day 2 - I have to do this once every time I open the file. And it seems that syncing with Lightwright also makes me have to do this again. Running VW2017 2012 Macbook Pro OS X El Capitan VW 10.11.6 2.6 GHZ Intel Core i7 16 GB 1600 MHz DDR3 Ram NVIDIA GeForce GT 650M 1024 MB

 

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