CarlJdP Posted January 25, 2016 Share Posted January 25, 2016 (edited) Hi all, I'm having trouble with extruding a 2d polygon along a nurbs curve. The 2d polygon is one of many to be extruded along this path, so it is slightly offset from the path, and thus I select the [fix profile] option. I noticed that if I deselect [fix profile] the crash does not occur.. Every time I run this command I get 'VW 2016 needs to close down' ? Does anyone else get the same crash as I do? Edited January 25, 2016 by CarlJdP Quote Link to comment
Kevin McAllister Posted January 25, 2016 Share Posted January 25, 2016 It crashes for me too. If I change the 2d polygon to a NURBS curve too I get an error message. If I switch the direction of the NURBS path it crashes again. Kevin Quote Link to comment
Benson Shaw Posted January 25, 2016 Share Posted January 25, 2016 (edited) The profile has a stacked vertex where the top of the bread loaf meets the overhang. Delete the extra vertex and the EAP works as expected. I hate it when those vertices stack up. -B Edited January 25, 2016 by Benson Shaw Quote Link to comment
AlanW Posted January 25, 2016 Share Posted January 25, 2016 (edited) Hi, File as was downloaded worked fine for me. Windows. VW2016. SP2 Edited January 25, 2016 by Alan Woodwell Quote Link to comment
Benson Shaw Posted January 26, 2016 Share Posted January 26, 2016 Whoa, Alan - it didn't crash for you? The file crashed for me when opened then EAP. Could this be a system config thang? My rig is OK - pro laptop, but nowhere near state of the art cpu/cores or memory. or Win/Mac? But CarlJdP is Win with Nvidia 780. Anyway, looks like there is a workaround on the Mac side. -B Quote Link to comment
CarlJdP Posted January 26, 2016 Author Share Posted January 26, 2016 @Benson Shaw Thank you, the stacked vertex explains it Would be nice though if Vectorworks could catch this exception. @JimW / @MarissaF Would be nice, with a lot of the tools, if the FAILED error message could state why the operation failed, or which objects caused it.. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 26, 2016 Vectorworks, Inc Employee Share Posted January 26, 2016 @Benson Shaw Thank you, the stacked vertex explains it Would be nice though if Vectorworks could catch this exception. @JimW / @MarissaF Would be nice, with a lot of the tools, if the FAILED error message could state why the operation failed, or which objects caused it.. Adding this thread to the existing request for more informative solid modeling error messages. Quote Link to comment
Kevin McAllister Posted January 26, 2016 Share Posted January 26, 2016 It would also be nice to add a wish for a way to find/delete coincident points. This is a leading cause of geometry issues in VW yet there's no way to easily repair this issue. Its easy enough in a situation like this (+- 10 points) if you know what you're looking for. But when you have 100s of points it can be a nightmare. Kevin Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 26, 2016 Vectorworks, Inc Employee Share Posted January 26, 2016 Simplify Polys should do this. Usually the Minimum Deviation mode is what you'd want to use, at any setting greater than 0 but larger than the smallest rounding precision unit in the document stacked vertices should be removed. Quote Link to comment
Kevin McAllister Posted January 26, 2016 Share Posted January 26, 2016 Thanks Jim. Great tip! Actually using the tooltips I discovered that a maximum deviation of 0 will remove collinear points which is a little simpler. (Often you need to only remove collinear points but not change a path's shape.) Kevin Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 26, 2016 Vectorworks, Inc Employee Share Posted January 26, 2016 I didn't know 0 would work! Ty, I'll make an article out of that actually for the kbase. Quote Link to comment
Benson Shaw Posted January 26, 2016 Share Posted January 26, 2016 But you still have to know that coincident vertices are the problem for failed EAP or other fail. Currently, the stack shows a slightly darker vertex marker. Could stack indication be enhanced with a different color or larger marker? -B Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted January 26, 2016 Vectorworks, Inc Employee Share Posted January 26, 2016 I would say a visual indicator would be a good wishlist item, I'll submit that. However, I would also say a pre-check might be in order so that an EAP could at the very least WARN a user about a stacked vertex, and ideally either fix it automatically or avoid it becoming an issue. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.