Reshape Tool Bug VW2017

[JJe]

When using the reshape tool, the data points are moved as expected, but the vector lines in between do not display in the new location. Anyone else having this problem?

[Art V]

Yes I have the same bug, it can be solved for now by changing the display setting in VW2017 from Best performace to Good performance and compatible. Please do a bug submit, as that will give tech support the necessary information in helping to track the cause of this.

If you do another operaton on the object, e.g. a fillet, then it gets properly displayed and then using the reshape tool works ok for that object. At least it does that with me.

Edited September 22, 2016 by Art V

[PVA - Jim]

Confirmed, submitted as a bug. VB-136242

[JJe]

Thanks Art V for the workaround, reducing the quality of the display setting seems to work for me too.

Thank you JimW for submitting the bug report.

[mat8iou]

Running Vectorworks Architecture 2017 64 Bit (Build 327801) on Yosemite, on a 2013 21.5" Imac.

 

If I use the reshape command on a simple rectangle it works fine. If I use it on anything more complex, it moves the handles and a ghosted outline, but the rest of the shape remains in the original position. even if I deselect and reselect the shape, the shape shows the shape outline in one place and the handles on the ends of each segment in a different place (see screenshot).

 

It is the same on other machines in the office that are running Yosemite.

 

We've tried to replicate it on the one machine that runs El Capitan, and can't, which suggests that it may be a problem linked to the OS version.

 

Has anyone else experienced this?

 

 

[Art V]

Yes, it is a known issue.

 

One way to solve it for now is to set your display setting in the VW preferences from Best Performance to Good performance and compatible.

 

For more posts on this see this topic:

https://forum.vectorworks.net/index.php?/topic/45360-reshape-tool-bug-vw2017/

Edited September 30, 2016 by Art V

[mat8iou]

On 30/09/2016 at 11:33 AM, Art V said:

Yes, it is a known issue.

 

 

Great. Thanks for the info - and the solution.