Jump to content

Search the Community

Showing results for tags 'bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Announcements
    • News You Need
    • Job Board
  • Feedback
    • Roadmap
    • 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


  • 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



About Me






  1. Hi all, I can't seem to find anyone else with this issue, so I've had to resort to posting it myself in search of a fix. For some reason my textures show up white on 3D objects and symbols as if they are generic white solids, even when a texture has been applied previously. The files often open with the textures there but once I begin editing they soon disappear, or the file opens with all objects displaying as white objects with no textures. What is weird with this and different to a lot of other issues I've seen others having is that the objects seem to lose all surface UV's altogether, not displaying in the render window as having any texture at all, and I am unable to apply any texture back onto the object. This also means that when importing to twinmotion or publishing other viewports that the textures appear white as if no texture has been applied. I am using Vectorworks 2022 and I have ensured that the software is up to date, that my graphics card settings are correct, and I have even tried reinstalling vectorworks altogether and still getting this issue. I work in a small team who also use Vectorworks that have not experienced this problem, in fact if I send the files that I have been using to their machines they all work fine, even though I have a brand new PC! I've also opened up past projects which didn't have this bug originally and now the same issue occurs, so by now i definitely think this is a software issue or bug rather than an issue with my machine. Any advice on this subject would be highly appreciated. I did have a quick fix by turning the 'Use textures' on and off from within shaded options.. but now this option often appears greyed out and I am unable to get around this without restarting vectorworks multiple times until it decides to work. Please help!! EDIT: This issue seemingly occurs after loading a file back up, I spent all day in a project yesterday without any issues until I opened the file back up again today to find my textures missing. Vectorworks Design Suite 2022 - [SF 40131 Burfield Academy.vwx] 2021-11-19 13-45-05.mp4
  2. In Vw2022, on the 'Help > Install Partner Products' it does not show my installed Partner Products -- which is how I ended up with WinDoor being installed twice, along with two 'Tools > Partner Products' menus. I'm running the current Vw2022 SP1.1. Thank you. Bug reported.
  3. Any others having the same issue? Bug submitted today, happens on Mac and windows here. Environment Vectorworks Version : v2022 SP1.1 (619242) Vectorworks Product : Design Suite, Renderworks Operating System : Mac OS 11.6 iMac, 27-inch Mid 2015 3.3 Ghz Quad-Core Intel Core i5 16 GB 1867 MHz DDR3 AMD Radeon R9 M290 2 GB Bug Title Curtain wall Bottom Offset fails to extend the wall below 0 from 0 and freezes the application. Bug Description Editing an existing curtain wall to have a bottom offset below ‘0’ to be a negative number fails to generate and freezes the application when the bottom offset is at 0. If the Bottom offset is a positive number, then going below 0 the wall will generate. It only occurs when the bottom offset is set at 0 to start. Steps to Reproduce 1. Open a blank file, draw a standard wall, or a curtain wall from the start. 2. Change the standard wall type to a curtain wall. 3. The bottom bounds should be set to layer elevation. 3. Edit the bottom offset of the wall to be a negative number below 0. 4. Application freezes, requiring a force quit. What is the expected (correct) behavior? That the wall will move in the desired direction without freezing. What is the current (bug) behavior? The application freezes.
  4. When placing motors (or hoists) in VW2020, the X and Y values will not update to a given origin on a drawing. As an example, if you have 2 different hoist origins and you toggle back and forth between them, the motors will not change their X/Y values.
  5. I want to preface `this rant/feature request/bug report` as coming from a long standing user, professor, industry professional, and enthusiast. I'm not really looking for a workaround or a third party tool: I want Vectorworks to natively fix the following issues. I also develop a piece of software that uses the XML Data Exchange so I have a fairly deep knowledge of how Vectorworks functions. These are core issues in the program. MVR does address several of these issues indirectly, but the export and import of raw data is a critical part of many workflows and it should either be depreciated or fixed. File -> Import -> Lighting Device Data Data Import needs to import Position/Rotation data when a fixture is created and the field is included in Data Exchange or via the Import. Currently the tool creates "Orphans" for anything it can't match and ignores Position X/Y/Z. This fails in metric or imperial with the format of `#.##m` or `#.##'`. I suspect this is because anything that is "unmatched" is set as an orphan and the position is ignored. This makes moving data from another program into Vectorworks. As a side note I believe this behavior is present in the Data Exchange workflow as well, because when I add a light and provide `PosX/Y/Z` data via the XML it also appears as an orphan without the correct position. The identifier should also be allowed in mappings a second time as Vectorworks disposes of it if it doesn't match a UUID. As such I can't synchronize another drawing to Vectorworks UUIDs by doing an import, export to sync up the UUID, and then reimporting to try to correct position information. Workflow example: I use my software to examine dimensions offset from zero and correct minor errors like x:=`15'-6.23"` and correct it to x:=`15'-6"` Workflow Example: Export data from Capture 2020 or lower into Vectorworks I suspect there are other fields that are ignored/suppressed and that logic should be audited Data Exchange Seems to suffer from the same issues which is not surprising Spotlight Data Exchange (Feature Request) This API should be documented and exposed. It is a simple XML exchange and I was able to reverse engineer it in a couple of hours, but it would be nice to have some documentation on how Vectorworks processes the files. Excel Import/Export (Feature Request) Given the fact Excel exchange is now standard in the architectural modules I would like to see lighting device data exchanged via Excel in Spotlight as well. We used to have this with the "Editable Worksheet" back in Vectorworks 12 (not 2012)--I can't remember exactly when it was eliminated but that was a huge blow to productivity. It seems like we're basically there again, and, I suspect implementing this would address my concerns above. In Conclusion Can I make all of the above work? Yes, but (as I discovered while teaching a class on lighting design) these tools behave inconsistently and in a clunky manner with no easy solutions. It would be nice to see 10 or 20 developer hours spent cleaning up these scripts and I would be happy to volunteer my time to explain--in detail--the issues to a developer if they don't understand the industry enough to make an adequate feature request. I realize the vast majority of my posts on this forum come across as crotchety at best, but that is because I come here when I have a problem I can not solve on my own. I really miss the basic export/import functionality from Vectorworks as it was a good way to teach how the software thinks, how data works, and why some tools are preferable to others. The database has always been the strength of Vectorworks and this has eroded in recent years. For someone like me who has their own database and workflow for production this amounts to being hamstrung in my workflow. My students prefer to visualize in Capture and draft in Vectorworks, but for the first time I can remember several of them have opted to create paperwork and plots in Capture rather than use Vectorworks at all and this is a major contributing factor, hence my post. -Daniel B. Chapman
  6. I have a problem where the object info palette does not update when I select an object. Sometimes it just starts happening randomly or sometimes it's like that when I first open the file. Often, but not always, it can be cured by repeatedly right clicking on an object until it responds and starts showing the correct info. Also, when you have something selected, it sometimes doesn't update when you change the size of something in the drawing, which can lead to problems if you then try the +5mm trick in the width or height fields as it adds 5mm to the old values not the new ones and then resets the object in the drawing to the wrong size.
  7. Hi everyone, I'm experiencing an annoying bug which makes impossible for me to use v2021. I'm working with 2D/3D symbols for windows with custom database attached in the ressources manager, in order to makes .ifc exports. After I opened my v2020 file to Vectorworks 2021, I noticed that when I deleted a class, re-assigning the elements to another class, the database of my 2D/3D windows symbols disappeared after freezing a few seconds. I made 2 videos on macOS and on windows10, to show this behaviour, which are attached to this post. Does anybody know why this happened ? Or does anybody already meat this issue ? Meanwhile, I'm stuck under v2020… Thanks in advance for your feedback, with kind regards, GatRed GR-201219.mp4 GR-201222.mp4
  8. After i use the "walkthrough tool with gamer mode" my mouse cursor disappears. The mouse goes OUT of the Vectorworks window while in walkthrough mode. (Which is annoying as i use hot corners and constantly showing my desktop turning right.... These bugs are with us since 2019...any date when these will be fixed?
  9. Please help. The dimension text disappears if the decimal precision's changed in the 'Document settings / Units / Dimensions' dialogue box. It doesn't just disappear, VW can no longer dimension - even if it is changed back. Can this be looked at as a priority.
  10. Hi, i have a pointcloud as an "environment" but when i want to make a renderworks render of my project the pointcloud just renders in front of everything. (Even when it is "cut out", on sheet layers too.) Check the pictures attached. OpenGL shows the pointcloud good. Is this a bug or a feature? (It does this in VW 2020 and in 2021...latest sp.)
  11. I'm showing distances between speakers created with the speaker tool in a view port with the dimension tool. Once I create a dimension, half the speakers just disappear. I have to change some parameter that will re-create the autohybrid in order for a speaker to reappear. I tried updating the viewport, and that does not help.
  12. Hello, Small post just to mention a bug (or at least a weird behavior) while using the railing tool ("Barrière" in French). This issue occurs randomly. The first three railings can be created as expected and then suddenly the fourth one will go crazy. See picture bellow.
  13. Redefine Saved View NOT obeying Restore Options, specifically Render Mode and Options ex. OpenGL - No Edges Vectorworks Designer 2020 SP3.1 macOS Mojave 10.14.6 Model Name: MacBook Pro Model Identifier: MacBookPro15,1 Processor Name: Intel Core i9 Processor Speed: 2.9 GHz Number of Processors: 1 Total Number of Cores: 6 L2 Cache (per Core): 256 KB L3 Cache: 12 MB Hyper-Threading Technology: Enabled Memory: 32 GB BUG-Saved View-Redefine-Render Mode and Options.vwx
  14. 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?
  15. I'm going through Remarkable Renderworks and have encountered some strange behavior. I noticed a similar issue when going through the other Renderworks tutorials and feel educated enough now to understand what's going on that leads to unexpected behaviors. I'm posting in the Rendering forum in case this is a use error, not a bug. Though, pretty sure this is a bug. Also posting this for posterity for other folks going through Render tutorials and getting weird results. Here's the exercise file: https://www.dropbox.com/s/giixw4jb98wva5g/exercise-36.vwx?dl=0 I have my camera selected and active with an F-Stop of 1.4. In wireframe I click "Click to Set Focus Distance" and I select the vase in the foreground. My intention is to have a shallow DOF, focused on the foreground vase. I'm using the cropped perspective view as per the tutorial: When I click the vase, the Focus Distance reads out as 19'8.982" when in fact it should read 3'4.139" I know this because: When using the "Set Focus Distance" from the camera view and it goes to that high wrong number and I switch to Final Quality, I get the wrong results, obviously: When using the "Set Focus Distance" from the Top/Plan view I get an entirely different number of 4'10.096" - shouldn't this number always be the same or close to the same? In all instances I'm clicking the front of the blue vase. Here are the results I get when selecting the Focus Distance from Top/Plan: When I manually put in the correct Focus Distance, I get the expected behavior - though the brightness is definitely incorrect. A change in focus distance should not change the brightness of a scene if all of the other settings remain the same... When I did it a second time, the focus and the brightness of the image were correct. Why's that? Because if you change the settings of a camera, sometimes you have to toggle its activation on and off in the Viz palette... This works as a solution to other render bugs by the way. If you find your renders aren't updating to from fast to final for some reason this appears to be a work-around for that bug too. Do any Vectorworks employees read this stuff? It's a little disheartening to find so many RW issues and not a peep from the Devs.
  16. For anyone else who hasn't figured this out yet: I've noticed that the File Name in project data (for Title Blocks) doesn't always refresh or populate properly. If you go into Title Block Border Settings --> Project Data and then cycle the "Include file path in File Name" button, it will refresh and show the proper name. Seeing this as a problem in all files... so I imagine this is a bug?
  17. We are running into an issue where data tags placed in viewport annotations continually lose their connection to the data and sometimes even shift locations to way outside of the original viewport bounds. Obviously this is a problem if we are trying to use them to annotate viewports in complex construction document sets because we shouldn't have to constantly re-spend the time associating the data tags with their objects or move them around. This is likely similar to the issue stated under this thread.
  18. When we save and commit on a project sharing file, many of us are experiencing a visual thing where multiple viewports ghost in. It seems to be a memory issue but it is strange that it seems to be tied to project sharing and saving and committing.
  19. In VW2019 and now in VW2020, after the new creation of Plant Styles, there is a problem with the way the Plant Tool operates... Upon picking a precisely defined Plant Style to use with the Plant Tool, the tool does not have the ability to place the plants using the Style Definition for Spread, Height, or Spacing. This means that when plants are placed using the tool, they automatically are placed using a custom Spread, Height, or Spacing. This may or may not match the Style Definition, but that is a mere coincidence. The only way to make a plant placement respond to the Style Definition for Spread, Height and Spacing is by first placing plants and then by going into the Advanced Plant Settings, Size Tab, and switching from Custom Spread, Custom Height, and Custom Spacing to Use Plant Style. This is a SEVERE regression and a problem with current workflows. Instead please allow for the ability in the Plant Tool Preferences to utilize the Plant Definitions Spread, Height, and Spacing as a DEFAULT. @Bryan G.@Tony Kostreski @Eric Gilbey, PLA @Vladislav Stanev
  20. I am trying to update a 2D Path Plugin object from v2017 to v2019 (plugin worked fine in v2017) and I am running into a weird issue. If you move the object from location 1 to location 2, it still has a memory of the original location of the path at location 1 even though nothing shows up there. When try too add/clip surface to edit the 2D path object, it looks at the location 1 for the joins and moves the 2D path back to the original location plus or minus the add/clip surfaces. It works correctly when I double click into the path object to change the shape through vertex tools but that is by FAR a slower method of our workflow. Definately a bug or maybe a method I can use to reset path geometry to the new locations? Thanks for any insights! See below for pics. You can see it ignores the new location and bases the new shape of the object off the old location.
  21. I just installed Vw2020, and the Message Center (up by my logged-in User Account Name) says that I have 4 messages. (At least I *think* it's a 4, it's such a small font size it's almost impossible to read. Update: It's definitely a '4', when I started Vw2020 this morning I paid attention to the Message Center icon and noticed that it was flashing *4* repeatedly at me.). I click on the icon and it says 'No News to Display', including a scroll bar for no reason since there's nothing to display. Am I missing something in Vw2020? [UPDATE: I thought it might have been my DNS Ad-blocker that was getting in the way of Messages getting through, so I turned that off: Nope, still no messages in Vw2020. So I opened up Vw2018 and Vw2019 to see how the Message Center works there, and it works fine in both of them -- I even see messages about Vw2020.] VSS-92287
  22. Why, when using the extremely useful Publish Saved view to DWG option in the Publish settings is the option Export as flattened 2D graphics not available? This is extremely annoying and destroys the productivity of this functionality if ALL of the options traditionally associated with DWG exports are not available from the publish command.
  23. While I had Vw2020 open, I used the macOS Finder to change the name of one file in my User Favorites folder and Vw did not like this, although I didn't know until I tried to quit Vw (eventually I had to Force-Quit). Apparently Vw had been putting dozens of error messages in the background unbeknownst to me, as there were no error sounds and the error messages were all happening behind the VW application so I had no idea. Other than Vw acting very strangely, as I could select objects and nothing would show as selected on the OIP, I couldn't move objects, etc. These dozens of error messages were all stacked one on top of the other. I pulled them apart to see the sheer depth of the non-notifications. An error message like this should never be sent to the background. VSS-92498
  24. In previous versions of Vw, I could set all attributes to be 'By Class' on the Attributes Palette by selecting the palette's Utility Menu and selecting 'Make All Attributes by Class'. This no longer seems to work Vw2020, as when I select 'Make All Attributes by Class' none of the attributes change until I draw an object -- then the palette changes to the Class attributes. Then if I switch to a new Class, the attributes palette doesn't update to show the attributes of the now current Class. Something seems seriously broken. EDIT: it seems to be working correctly now, so I think it was directly caused by what I reported in this other thread:
  25. No matter what I do, symbols are exported as individual geometry. Anyone else?
  • Create New...