No Im not here to solve it anymore, just looking for sympathy…
Bad objects maybe?
What does your Rhino SystemInfo look like?
Thanks, thats possible… can I send you the model by any chance?
Hi Daniel - if this is in the same model that it jumped to 700 seconds, did any of these change?
- file tolerance
- Views being 2d-ed
- Stuff being 2d-ed
Feel free to ssend the model to tech@mcneel.com, with a link back here in your comments…
-Pascal
1 Like
thanks, I’ve sent it just now. I’ve tried changing file tolerance after the file started to slow down from 0.001 to 1 - but it didn’t change the behavior (still sluggish overall). Views and objects should have been the same, the camera I mentioned in the email (02112-04) is much further away from the origin in comparison to other views, but it’s quite difficult to bring it closer without changing the view, so I was hoping to test other ideas first…
Yep, I see the one block, just by itself, takes a long time…
-Pascal
Could it be caused by too many nested blocks? Switching to a “flat” object “hierarchy” is possible if that would boost performance
@pascal @John_Brock thank you for your help - I might have called you too soon, Rhino went back to the previous 10-seconds performance after restarting Windows.
For completeness, I did restart it previously, as well, but a major update kicked in, so perhaps a second restart was what was needed.
Hi Daniel - thanks for the update - - I am still poking at the block you pointed out in your note - that file by itself is giving Make2d fits, here.
-Pascal
1 Like
Thank you, yes, Make2d on the “ILB.3dm” did cause Rhino to crash a few times without any error or the crash report window.