no way. I got me a 16"pen-display - my iPad (iOS10.3.3) is too old to work with the new M1Mac.instead of a mouse.
I'm still puzzled that we can't find the culprit of your issue. Maybe Console.app can help to diagnose. Open Cheetah3d aside Console, filter for Cheetah3d relevant entries and start torturering and check if there are any records appearing when beachball is turning for instance. A crash could be helpful also not wanted, but I think Martin can benefit from this kind of reports.Oh, I certainly didn't take it that way and I like this approach to modeling this object as well - clean and simple. I would not have thought to start with a cylinder and thanks for including the file.
Okay sounds good, I could definitely report it if it happens again.I'm still puzzled that we can't find the culprit of your issue. Maybe Console.app can help to diagnose. Open Cheetah3d aside Console, filter for Cheetah3d relevant entries and start torturering and check if there are any records appearing when beachball is turning for instance. A crash could be helpful also not wanted, but I think Martin can benefit from this kind of reports.
Whoa that's interesting I think I arrived at the same solution as well. I've started optimizing all the points and that seems to have helped solve the problem (well that and not having as many Chrome tabs open). Thanks for looking into and attempting to replicate the problem. Glad to know it's not just my hardware problem.I can replicate MMounteer´s problem (Intel iMac 27 on Big Sur). There is no crash but a long (possibly infinite?) beachball and the fan kicks in. I am then executing a forced quit.
It seems as if the orphaned points (existing in 3 of the 4 objects) are causing - or, at least, contributing - to this problem. Once optimised, this behaves without any problems.
Honestly I'd leave this browser.well that and not having as many Chrome tabs open