Jump to content

Large polygons in VW9 - worse than VW 8!


Recommended Posts

I have this polygon, well, in fact a polyline, coming from somewhere else, with 32571 vertices. With VW 8.5.2, its behaviour is erratic. When converted to a polygon, a third wont be able to be filled. When I simplify it by deleting every second vertex, it becomes manageable.

However, with VW 9 nothing helps & nothing works. If I try to convert to a polygon, VW just dies. I guess this is progress - maybe junior users like myself don't just understand how things are.

Link to comment
  • Vectorworks, Inc Employee

quote:

Originally posted by petri_sakkinen:

I have this polygon, well, in fact a polyline, coming from somewhere else, with 32571 vertices. With VW 8.5.2, its behaviour is erratic. When converted to a polygon, a third wont be able to be filled. When I simplify it by deleting every second vertex, it becomes manageable.

However, with VW 9 nothing helps & nothing works. If I try to convert to a polygon, VW just dies. I guess this is progress - maybe junior users like myself don't just understand how things are.

Have you submitted it to bugsubmit@nemetschek.net? I don't see anything like this in the buglist. We can't fix it if we don't know it's broken. (If you have reported it, and it hasn't been properly recorded by us, my apologies.)

------------------

Andrew Bell

andrewb@nemetschek.net

I am not an official spokesperson for NNA

Link to comment

No, I haven't. With this web page set-up, that is an extra step entirely - can't just cc a message to bugsubmit.

Also, I am not sure what happens to emails sent to you guys: a couple of weeks ago I received a reply from tech support saying that they only handle questions which quote the serial number. Fair enough, no problem - except that the question was posted 18 months ago.

quote:

Originally posted by Andrew Bell@NNA:

Have you submitted it to bugsubmit@nemetschek.net? I don't see anything like this in the buglist. We can't fix it if we don't know it's broken. (If you have reported it, and it hasn't been properly recorded by us, my apologies.)


Link to comment

Thanks, John, but I solved the problem with my own simplification routine which does not crash. It is a quick & dirty one, just deletes every second polygon. The one that used minimum distance ceased to work with VW 8 and I haven't had the time to rewrite the part in question.

Of course, the problem & the poly were not really mine but rather those of a client. It is somewhat awkward (to say the least) that a design practice has to have a specialist consultant on stand-by for this kind of eventualities.

Link to comment

It's that horrifying very quick and dirty algorithm which inspired my minimum distance script. (It probably doesn't crash or do anything bad, but i was too lazy to test it carefully and thought it best to warn as a ward against evil.)

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...