Wings Triangulate problems.

[ggaliens]

I have a file that reliably crash/freezes on face triangulate.

All it takes to correct the behavior is to "tweak" each vertex a tiny amount ... scale uniform by 101%

Some small change seems enough to fix problem.

The file is called "hurts-so-good.wings" and is located

https://www.dropbox.com/s/d9fyetrotl1iz0...wings?dl=0

---

Just "looking" at the far end-cap of this shape seems to FREEZE wings3D.

I have tried 1.5.4 also. Same problem.

Save and reload does not WASH PROBLEM AWAY (I don't think).

---

It might be the act of hi-lite is querying some bad value.

[micheus]

I took a fast look on it. I noticed it seemed to not stop try to triangulate the non quad faces, since after 15min and 3.5GB of memory it hadn't stop to work.

The problem is happening only if we select the entire object of if we try to select (just a highlight) any edge in the bottom circle.
I did a loop cut close to it and removed that area and then I could triangulate without problem.
So, it seems to be a very specific problem. If it cannot be reproduced it doesn't worth spend time looking for a problem ("bug ?!")

[ggaliens]

Yes. You are right ... if we cannot re-produce ... we will forget about it.

So far ... cannot reproduce.

What bothered me about it though ... was that only a very tiny vertex jiggle would make the problem go away. And the ISSUE is not really with triangulate. That just uncovers a larger problem. Even if you "look" at the bad end cap (lets call it evil) ... the problem happens. FREEZE.

---

I can tell you that some edge collapse did happen to make this item. It was a proactive edge collapse ... to introduce some asymmetry to cylinder for unimportant reasons.

[micheus]

Probably something broke the WING data, in that area since after we get the first edge highlighted some process enter in an infinite loop - and eating memory.

So if you just remove [bksp] the edge pointed the problem go away:

[ggaliens]

I see what you did. But I had to do more then backspace.

I also had to delete the isolated vertices left over after backspace. Else I still had the problem.

I had thought about printing out We#we.es, We#we.fs and We#we.vs
and then look hard at tables ... but that's still a long problem maybe. YUK. Too much.

I agree ... we forget about this one for now.