Hi, my rhino file is too big. I want to reduce it. (it’s 60 Mb) It’s very hard to generate a rendering…
How can I do?
Please, it’s very urgent!
Thank you very much
I have edited the title and category so that it will be easier to find.
In the mean time, have you seen these topics
THANK YOU. I READ EVERYTHING AND I UNDERSTOOD THAT THE RESOLUTION IS USING _SAVEAS .
“Try _-SaveAs and check SaveSmall=Yes and SavePlugInData=No”
BUT i’m not sure that “SavePlugInData=No” doesn’t delete anything…?
It does not save any plugin data. This means that plug-ins may stop working. Any geometry in the file, however, is preserved.
1 Like
Hi michtat - if rendering is the problem, then you’ll probably want to control the render meshes better - see:
http://wiki.mcneel.com/rhino/meshfaq
Also, if there are many repeated elements in the file, it may help to use blocks :
http://wiki.mcneel.com/rhino/usingblocks
-Pascal
1 Like
HI,
I had something related to solids being made from a bad surface that had hundreds of points.
Because of this, I had a lot of solids which had this surface.
The file was in about 200 MB !
But then I applied the “ShrinkTrimmedSrf” to the solids.
Indeed if on a later stage you wish to untrim… that will be of no use…
But… Now I have less than 50 MB for that file.
T.
Hello, my file is unworkable right now, and shot up from around 100mb or less to 1,140 mb. Please help. I am using cad blocks and hatches. However, I am also using that in another file taking up much less space. When I did SelBadObjects, 2 come up, but even after deleting those, the file is still slow; I also need both of those bad objects. Any suggestions?
Hello - please run the SystemInfo command in Rhino and copy/paste the results here.
-Pascal
Rhino 7 SR18 2022-4-26 (Rhino 7, 7.18.22116.07001, Git hash:master @ 87bfab984a3c0622bb859cff8b5d16be7462b1b0)
License type: Educational, build 2022-04-26
License details: Cloud Zoo
Windows 10.0.22000 SR0.0 or greater (Physical RAM: 16Gb)
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Hybrid graphics configuration.
Primary display: Intel(R) UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 3-18-2022 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro T1000 (NVidia) Memory: 4GB, Driver date: 4-20-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 512.59
> Integrated accelerated graphics device (shares primary device ports)
- Video pass-through to primary display device
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 3.3 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 3.3
Shading Language: 3.30 NVIDIA via Cg compiler
Driver Date: 4-20-2022
Driver Version: 30.0.15.1259
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.18.22116.7001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RPC.rhp “RPC”
C:\Program Files\Rhino 7\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.18.22116.7001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.18.22116.7001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.18.22116.7001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.18.22116.7001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
Hello-
FindLargestObjects.py (4.2 KB)
Here’s a script that might be of some use - if the problem lies in geometry, which it may not - (e.g. you coud have many large textures in the file - please check for that)
To use the Python script use RunPythonScript, or a macro:
_-RunPythonScript "Full path to py file inside double-quotes"
-Pascal
1 Like
What I got was: 7,967.6719k and 9,180 polygons. Not really sure what this means or what to do with it.
That is not immense - it should have selected the object - what is it?
-Pascal
it appears to be a window shade, do I just delete it then?
a window shade that came with a cad block I downloaded from the internet
Hello- I doubt this is the culprit here unless you have a lot of them - what happens if you SaveSmall your file? Does it become more manageable as a file on disk? If so, please zip it and upload here
to my attention. Please include a link back to this topic in your comments.
Are there a lot of materials and textures in the file?
-Pascal
yes there are a lot of materials and cad blocks. I am not sure what textures are. I have saved small and the size has decreased to around 700mb. It is better, but still very slow. I will upload it to the website.
It is asking me for your email address
I uploaded it with your name instead of your email
Hi Danna -
As Pascal noted, none of the objects in the file are excessively big.
It’s just the sheer number of it. There are 71483 objects in your file.
In Rhino, each individual object will carry a significant number of bits of information like its layer, color, … That will be the same for just a simple plane or a very detailed polysurface. When you run into display performance issues, the first thing to do is to try to reduce the amount of objects in the scene. You should see that, in your file, when you hide a lot of objects, the display performance should be good.
While in most cases, it might be somewhat complicated to reduce the amount of objects and still be able to work meaningfully in the file, in your case it should be more straight forward.
You have over 60 000 single surfaces in your scene. Joining these into polysurfaces should greatly reduce the number of objects:
On top of that, most of these polysurface objects are repeated several times in the scene. These could be turned into blocks.
Other than that, I’d use UngroupAll to get rid of the grouping of objects that makes it hard to see what’s really going on in the file.
-wim
Would I be able to make blocks quickly? Do I then have to copy it over every time again? Idk how that works. Also, to join into a polysurface, do I just use join command?
- Thanks