Jump to content

Hello Community!

This Saturday, May 30, from 9am – 12pm EDT we will be performing maintenance on the Vectorworks Community Board. During this time, the site will be unavailable.

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

Calendars

  • Community Calendar

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


About Me


Occupation


Homepage


Hobbies


Location


Skype

Found 69 results

  1. 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.
  2. 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?
  3. 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.
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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
  11. 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:
  12. No matter what I do, symbols are exported as individual geometry. Anyone else?
  13. I am trying to group together several similar items (each in a different class) into one group inside of a symbol. This group is intended to be in a parent class that would then control the visibility of the entire group. However, after grouping the items in the symbol and placing it the desired class, when I exit the symbol, the items come un-grouped. When I reenter the symbol edit, sure enough, they are all ungrouped. Any ideas?
  14. This is something all of us in our office has experienced, and started with VW 2018. VW 2019 is causing this bug to happen more frequently however and I haven't found any other questions on this. When we have multiple drawings open to copy certain elements from one to another, the bug seems to stop any other drawings functioning. After coping something, that drawing remains in full operation where we can continue working, however as soon as you go across to another open drawing to paste, it, you can't do anything! You can select tools etc. but nothing happens on the drawing itself. If you flick back to the drawing you've copied from, its remained active as if you were trying to paste, or any other function within this drawing. Its like it stops registering any other drawings open and no further changes can be made until we restart VW. Sometimes simply reopening all the drawings is enough. Please note this is often when just two-three drawings are open, we rarely have more than that open at one time. Any insights would be most helpful! Thanks
  15. This shape was originally created as a floor object. After deletion of the object, a 2D "ghost image" of it remains on Top/Plan view. Sometimes, the shape appear was a darkened shadow in OGL or wireframe modes. It shows up in our plans, but not in rendering or hidden line sections. This problem persists for over half a year after said geometry was deleted, and continues to stay despite many new versions re-created of the file as well as Vectorworks version update. It is affecting our modelling accuracy as the ghost image blocks the shapes we newly created, especially on Top/Plan view. How do we get rid of this bug for good?
  16. This one has been bothering me for a very long time! Since VW2018 was released, my saved workspace will not save entirely. Essentially I have a double stacked group of tools on the left side of the screen that I prefer. In VW2018, every time I open the software, it reverts back to a collapsed version of this sidebar configuration. This only happens in VW2018. It has never happened in prior versions, and it appears to be fixed in VW2019. If VW2019 wasn't riddled with bugs and we weren't pulling back from implementing it in our office, I wouldn't mind this persistent issue, but since it looks like 2018 will be my mainstay for quite some time, I am finally adding this bug to the list. I know this is a minor thing that doesn't really affect anything, but damn it is annoying. Annoying Workspace Collapse in VW2018.mp4
  17. Hello, I am testing out the Razer Blade Stealth. I opened a document I had created using my previous laptop with an Intel Graphics 520 Internal card - and found that on the blade I received a horrible graphics bug. Starting in a render view in OpenGL and then persisting in plan view or anything else... Is this an issue with some drivers on the Razer Blade Stealth?
  18. When trying to add a custom valve to the irrigation library, the software fails to recognize fractional sizes. For example, I have tried to create an 1-1/2" version of a valve made by Buckner Superior. When entering the data for size, regardless of whether you enter it as 1 1/2" or 1.5" the library changes that size back down to 1" upon accepting the settings. I have even tried duplicating an existing library instance of a 1 1/2" Rainbird valve, changing a couple of the settings, and then accepting the changes and it still down sizes the valve in the library? Here is a brief video of the problem, sorry for the lack of audio. @LanceF @Tony Kostreski @Eric Gilbey, RLA ASLA @Bryan G.
  19. Our workflow for irrigation in VW has ALWAYS been to separate each station into a unique design layer. This allows for greater control, visibility, and conflict detection. Since the creation of the irrigation tools, this workflow has been compromised. Irrigation components, mainly valves, will magically change design layers when connected to different features. Nothing in VW should ever change design layers unless by User Error or by choice. Additionally, when moving valves and other components between design layers, the will actually lose their connection status. I understand that irrigation networks are a unique feature in VW and the fact that they can connect through different design layers in the first place is a revelation, but that shouldn't compromise our ability to control it. The following is a simple screenshare showing the issue. FIX THIS!
  20. Bug Alert, This works with simple object for example draw a rectangle and make it a symbol, the same behaviour will persist. With a hybrid symbol, open "multiple views panes". Edit the 2D component of the symbol, the 2D objects disappear. Also happens when editing a symbol containing symbols, if a symbol is 2D only it will disappear when entering the root symbol with multiple views on. See Screen recording. Very frustrating behaviour!! Screen Symbol.mov
  21. We have had a nightmare scenario where in a push toward a deadline we noticed that ALL of the fonts and their formatting changed throughout several documents and their associated references. I have never seen anything like this before in our workflow and we have been using for a long time. Thoughts?
  22. Just encountered a new problem I haven't experienced before...I'm guessing it's because of VW2018! So...We have a utilities file where we have applied custom line-types to the different utilities. Because of our workflow, we reference this file into a BASE file that then get's referenced into all of our different design files. The viewports in the design files are rotated, and none of the utility linetypes appear. When you go to the design layer, they are visible in normal Top/Plan, but when you apply a rotated top/plan, they disappear! I just converted this particular project from 2017, where it worked just fine, to 2018 yesterday and only now am I experiencing this issue. We are experiencing similar issues on other 2018 files as well. Why does this always happen...stuff that works just fine somehow becomes broken in new versions. This is BAD!
  23. The whole program goes grey for about a full minute when changing from General to other settings in the Railing/Fence Settings dialog. Something needs to be optimized there.
  24. So...we've come across an annoying bug. We are using a reference viewport system to build separate Production files, containing all of our sheets for a given project. These files reference in a Design file as we call it where all of the live linework is housed. The reason for this is not for discussion, it is just a workflow we have found works best for a multi-user/large multiple drawing set projects. With this workflow comes a strange bug when referencing worksheets through referenced viewports....they shrink. We often have to build our smart database worksheets/legends in the Design file and then reference those into the Production file through viewport references, but when we do, the worksheets shrink in vertical dimensions. We noticed this because we often have to put a reference symbol over the top of the worksheet for items (this is because the =image function in VW needs some serious attention), and when the worksheet and symbols come through the reference, they are no longer aligned and often are off by a completely illegible amount, no longer aligning with their intended worksheet row.
  25. 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

 

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.

×
×
  • Create New...