Just probing the consensus of what performance expectations should be with a pdf import in Rhino and possible ways of optimizing.
I have imported a pdf plan and have ~500k curves and a few other objects, but the main geo is the large number of curves.
Performance is very bad across the board, from navigating to snapping / smart tracking, to copy & pasting which acts basically like scanning / reading the entire file. The weird thing is that I have a second session open where I am building my model and this session is lightweight, no curves etc but even here copy & pasting is very slow.
I’ve ran purge on both sessions, and turned my display settings way down… anything else that I can do? Is this sluggishness normal?
With about 500k curves, I’d say, yes, this is normal.
As long as all of these are visible in a viewport, things will be slow.
If you zoom into areas where less curves are visible, things should be fine again, so either trying to hide geometry that doesn’t need to be visible or working in smaller areas of the model would speed things up.
Also, non-solid hatches and linetypes from a PDF file will be read as individual lines. Replacing these with Rhino hatches would also help.
Finally, it’s possible that curves that appear to be a single curve are split up into multiple individual curves. Joining these into one curve helps reducing the number of objects in the scene and will speed things up.
-wim
Indeed, all hatches came in as geometry.
But this thread came after optimizing the scene file the best I could… so I have already delete unnecessary geometry (hatches etc), purged everything I could etc. But the truth is that if I want to keep most of the plan with the layers and most of the relevant geometry the scene file is unbearably slow… it is workable, but slow.
Thank you @wim