[Shared Project Files Automatically Converts to 2019]

@Liene Cikanovica just to confirm, are you saying that you choose "Cancel" in the first dialog that appears (when you open the file in 2019), and VW still converts it to 2019 format? I'm not seeing this on my end so I just wanted to be sure I understand the issue. 

 

When the conversion occurs the 2018 file should get placed in its own folder (in the same directory as the original file) named "Old Version Vectorworks Files", so that you still have access to it. Are you not seeing the 2018 file get moved to this folder?

 

[Grey Classes/Layers in section Viewport]

@K MAC would you mind messaging me a copy of the file so we can take a closer look? Thanks!

[How to mask out hidden line in front of image props?]

@Christiaan I don't think there's any magical fix for this. This is just a suggestion but you could put a corresponding Bitmap in the viewport's Annotations, so that it overlaps the Image Prop.

 

-Extract the image from the prop texture

-Enter the viewport's annotations

-Import the image as a transparent Bitmap

-Move/resize it so that it overlaps the original prop

 

It's not ideal, but you'll still get the shadows cast by the original prop while getting rid of the unwanted lines.

 

Hope this helps,

 

Tim

[Line reshape: angle snaps not working]

@line-weight from my testing it looks like holding down Shift during a resize has always constrained the operation to the line's current angle (tested back to VW 2010). If you have the "Snap to Angle" constraint enabled you can snap to the 30/45/90 angles without pressing the Shift key, though.

 

If you're using the Reshape tool on a poly segment you'll get constrained to 30/45/90 angles while holding Shift, but the resize feature seems to work a bit differently than Reshape.

 

Hope this helps,

 

Tim

[Can i make a configurable 2d symbol ?]

@Sam Lee you could probably get away with just one symbol by using design layer Viewports and class visibilities, though the workflow is a bit unusual:

 

-Create one symbol that includes all the different variations for the downlight, and place the variations in their own classes within the symbol

-Place the symbol on its own design layer

-Create a design layer Viewport that shows only that layer

-Use the viewport's Class visibilities to control which of the downlight variations you want that instance to show

-Duplicate the viewport and change the visibilities as needed for other configurations

 

This seems to work pretty well in my testing, though it might not be for everyone. Other than that, the only way to really do this is with lots of different symbols (as Mark said).

[Structural Member Tool]

@mbft just a heads-up this should be fixed in SP2, so if you're still seeing problems please let us know.

[Glitchy when exporting as a PDF...]

@Jackson99 Good to hear! If you happen across it again please let us know. Thanks!

[DWG export marked as educational version]

@lgoodkind I looked through our database of known bugs and didn't see anything along these lines, so we definitely need to look into this. Would you mind messaging me a copy of one of the VW files where you're seeing the problem? Thanks for your help!

[Electrical & Plumbing going missing in symbols]

@Jim Smith much thanks, Jim. I do see the problem with the Bitmap (in the Notes-Stamp class) not showing in the VP and I've submitted a bug report to our engineers.

 

I wasn't able to duplicate the other issue (where the "EX RM 1" symbol wasn't showing in the VP), but since the problem resolved itself I'm guessing it was related to graphics caching (always tricky to troubleshoot).

 

We'll definitely keep a close eye on this, and if you see the problem again please let us know. For future reference though you can often fix graphics issues like this just by deleting the object (in this case the viewport) and then Undoing the delete.

 

Thanks again!

[Electrical & Plumbing going missing in symbols]

@Jim Smith would you mind messaging me a copy of the file so we can take a closer look? I did some tests with a setup similar to what you described but didn't see any problems, so there might be something more specific that's causing the problem. Thanks for your help!

[Glitchy when exporting as a PDF...]

@Jackson99 would you mind messaging me a copy of the file so we can take a closer look? Thanks for your help!

[Plant Component details disappear]

@BJRobinson would you mind messaging me a copy of the file so we can take a closer look? I did a quick test using the same Plant and didn't see the problem, so there might be something specific here that's triggering it. Thanks for your help!

[VW19 SP2 dramatic slow down...]

@bjoerka if you could message me that file I'd like to take a closer look. In my experience operations done prior to the Purge (for example deleting a bunch of things) can cause it to take longer, but it shouldn't take nearly this long. Thanks again for your help!

[VW19 SP2 dramatic slow down...]

@bjoerka Much thanks, I was able to duplicate the problem and I've logged a bug report for our engineers to take a look.

[VW19 SP2 dramatic slow down...]

@nahekul Thanks again. I was able to reproduce your slowdown and I've logged a bug report so our engineers can take a closer look.

[Editing Symbol/Plug-in objects]

@skeyshubber Plugin symbols can only contain the plugin object itself, so the only way to get it back to a plugin is to remove those 3 lines. Unfortunately any custom details you want to add would have to be added as separate objects, outside of the Railing/Fence.

 

The issue is that tools like the Railing/Fence are really only using the settings of the plugin object in the symbol, not its geometry. So when you add other geometry to the symbol, the tool has no way to know how to place it in relation to everything else. It's possible we could find a solution for this in the future but for now your best bet is probably to make completely separate objects.

 

Tim

[VW19 SP2 dramatic slow down...]

@ericjhberg @Henry Santos @nahekul @bjoerka if you're able to message me one of the files that seems slower, it would be much-appreciated. This doesn't seem to be a general problem all users are seeing, so it might be something specific to your files.

 

Also, if you're on Mac and are experiencing a slowdown, there's a really easy way to generate a log that helps our engineers diagnose the problem:

 

-Launch the Activity Monitor (in Applications/Utilities)

-While the slowdown is occurring in VW, highlight the Vectorworks 2019 app in the Activity Monitor and choose "Sample Process" from the pull-down menu at the top

-This will generate a text file that you can save and upload

 

Thanks for your help!

 

Tim

 

 

[Editing Symbol/Plug-in objects]

@skeyshubber when you edited the 3D Component of your Railing/Fence symbol did you add any new objects? That would cause the symbol to no longer be eligible as a plugin object.

 

If that's the case, you should just be able to edit the 3D Component again and delete any objects that were added. The symbol should automatically return to a plugin when you exit (at least it does in the few tests I tried).

 

Hope this helps,

 

Tim

[Front/side views of 2d components not available for angles that are not orthogonal to the drawing coordinate system?]

@Will Hi Will, I wasn't able to figure out why this particular symbol is having problems, but if I re-create it the problem goes away. I've submitted a bug report for our engineers to take a look, but if there's any more info you can offer on how the symbol was created it might give us a better clue. Thanks for your help!

[VW 2019 Unresponsive When Editing VP Annotations MM Dims]

@Bruce Kieffer would you mind sending me a message with a copy of the file so we can investigate? In the past I've noticed a delay of a few seconds when entering VP annotations for the first time, but it always goes away after that. I'm thinking there might be something about your dim standard or file setup that's causing this same delay to last much longer. Thanks for your help!

[VW 2019 crashes when viewing worksheets]

@skeyshubber would you mind sending me a private message with the file so we can investigate on our end? Thanks for your help!

[2019 SP1 is FUBAR]

@MartinFahrer would you mind sending me a private message with the last four digits of your serial number, so I can look-up your crashes in our Analytics site? 

 

I'm also looking into the keyboard shortcut problems you mentioned. It doesn't seem like other users are reporting this so it's kind of a mystery, but I'll contact the engineers responsible for keyboard input and let you know what I find. Can you just let me know your operating system, type of computer, and type of keyboard so I can pass it along?

 

Thanks for your help,

 

Tim - QA

[2019 SP1 is FUBAR]

@WEAREBVR Would you mind messaging me copies of the VW files where you're seeing these problems, so we can take a closer look? I tried some Bitmap tracing myself and didn't see any crashes, so it probably depends on the specific Bitmap. Web View export also seems to be working with other files so there must be something specific there, too. We really appreciate the help!

 

Tim - QA

[EAP/TEXTURE MAPPING ODDITY]

@bc Ahh yes that explains it. There was a bug in VW 2017 that caused only "Plane" to be available for EAP texture mapping (fixed in 2018).

 

As a workaround you can convert the EAP to a Generic Solid (using Modify/Convert/Convert to Generic Solids) which brings back all the mapping options including "Auto-Align Plane". 

 

Sorry for the inconvenience!

[EAP/TEXTURE MAPPING ODDITY]

@bc you should be able to fix this by changing the Map Type to "Auto-Align Plane" in the Render tab of the OIP. I'm guessing you currently have it set to "Perimeter"?

 

Hope this helps!