View Full Version : Chamfer Bug

10-31-2013, 04:42 PM
It's a bit hair pulling :)

10-31-2013, 11:05 PM
Ugh, that's nasty, I gather by your mentioning it today that this behavior's with release 11.6? Have you checked whether the other "new tools" have similar behavior when multiple morphs are present?

11-01-2013, 12:17 PM
I use 11.5.1 for daily work, so it has been there all along, though I just noticed it in the past weeks. I admit after I heard LW11.6 was going golden I slapped my forehead and ran to fogbugz, with tests done in build 2717.

Haven't check similar behavior with other new tools that make new geometry. Maybe in the weekend.


11-05-2013, 06:41 PM
I'm having 2 types of experience.
In 11.5.1, 'base' doesn't go crazy with FogBugz attached object until I use it on Morph1. Then it also goes crazy on 'base'. Bug takes place while the modifier operator is active.
In 11.6 build latest build, it goes cray either on 'base' or Morph1, right off the bat. Bug takes place after the operator is dropped.

Anyways, same issue with Thicken, Slice and EditEdges (right click to Add Edge Loop).

vid on 11.6 build 2723: http://screencast.com/t/w2gLyW55WA

I wonder if this really went by un-noticed by everyone all this time... Either people don't use the new tools that much, or do new topology after morphs, or I don't know...


11-05-2013, 10:11 PM
haven't used LightWave 11.5/6 that much (no special reason, it's better than ever) :]

but as for your comment > new topology after morphs...
nope, i hardly ever do that.

11-05-2013, 10:55 PM
Thanks for the report, we'll investigate it.

11-06-2013, 03:31 AM
Cool James.
Just a last additional info, UV maps entry seems to also snap to the first UV in the list after committing. So, it could be happening for every Vmap.