Jump to content

Recommended Posts

This bug should be resolved with Vision 2019 SP2. The issue was that we thought the file was temporary and so we cleaned it up when we shouldn't have. If you are running SP2 and still experiencing this issue, please provide the files you are working with a steps to reproduce the issue, if at all possible. This will help us resolve the issue as quickly as we can.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

 

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.

×