I am working in a file that contains about 400 block instances containing 119 block defintions, which partly are nested. Usually I never experienced trouble working this way, but this file in particular is very very slow.
When I explode all block down to their bottom, I get 20000 objects. It seems a lot, but it
s acutally no problem to work with.
I found a similar isssue here (outside this forum).
Working in wireframe mode is quite okay when working in with the blocks, but I just wonder where this comes from?
Aren’t he blocks there to make the models lighter?
And what strategies would make sense to avoid a laggy model?
This is one of the most annoying problems nowadays in the program. Blocks are really common in drawings and still haven’t found a solution. I usually edit them individually in another file of Rhino, an empty file.
Edit.: if i set the Antialiasing option in the OpenGL tab to “None” the problem solves
blocks are generally a problem, since eh version 7 i think, i am not sure why nobody reported this here but there are many complaints about it. it has become unusable on a bit older computers (and probably just heats up the faster ones unnecessarily) to the point where you have to explode blocks or hide them away to be able to navigate at least. there are several topics regarding this issue on discourse.