![]() |
[fixed] Bug or TOUGH CASE with Booleans ... - Printable Version +- Wings 3D Development Forum (https://www.wings3d.com/forum) +-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1) +--- Forum: Bug Reports (https://www.wings3d.com/forum/forumdisplay.php?fid=12) +--- Thread: [fixed] Bug or TOUGH CASE with Booleans ... (/showthread.php?tid=2723) Pages:
1
2
|
RE: Bug or TOUGH CASE with Booleans ... - ggaliens - 02-03-2019 If you watch the video, you can see exactly how I made it. I bet you GESTALT vision can also just SENSE / see when the smooth has been pressed enough time. I just smoothed the knot and the geodome a couple times each. Just have my video up next to you wings screen and press smooth until there looks to be a resolution match. I just tried with each smooth 3 times. It failed. Now I will try easier ... just smooth each TWICE. Still a fail With a message about coplanar faces. Wings 2.2.2 I try to take the coplanar faces warning for what it really says ... so I then do a crumple 1% to probably ensure zero or almost zero coplanar faces. Then it works. What is the easiest way for me to share a file with you these days ? Here is a share. Try to subtract knot from geodome https://drive.google.com/open?id=1t2DbgZxe-TQlDwEh6sDD-Vs5GDymWAFj RE: Bug or TOUGH CASE with Booleans ... - micheus - 02-04-2019 Yeah, if the objects are in default size and location, sure I could to try reproduce it. It was just hard to notice that using a smartphone. ![]() You may know that's not easy to debug objects with this amount of faces. I crash Wings3D many times until get something with the minimum amount of faces that still can cause the crash and then send to dgud. That was the reason I thought to use the original would be better. ![]() Google drive is ok for sharing files. Thanks. RE: Bug or TOUGH CASE with Booleans ... - dgud - 02-09-2019 If you cleanup (body/Cleanup) the "support" object, boolean works fine. You have 3 pairs of vertexes in exactly the same place which causes problems in the calculations. I don't know how to solve problems with "bad" models in the code either. A crash is not a good user message it gives no clue about what is bad, on the other hand I don't want to write lots of code to figure out what is wrong with the input either. EDIT: Ok I solved the problem for this model, since the problematic area was not involved in the boolean operation the problem could be fixed, but if you tried a boolean op on the bottom face it will continue to crash. (02-01-2019, 08:03 PM)Ravo Wrote: A guaranteed failure in boolean: RE: [fixed] Bug or TOUGH CASE with Booleans ... - digitaldavinci - 01-16-2020 I just ran into the Coplanar faces message. Not sure about these and how to find them. RE: [fixed] Bug or TOUGH CASE with Booleans ... - dgud - 01-16-2020 You can not have parallel faces when doing boolean, move the offending faces sligthly. |