-
70 MB to editable 7 GB! Taking ages to load and save!
Hi,
So I made a scene full of construction rods, no shader has been applied. One was an original, the rest were instances. After I had the entire scene locked I had converted the entire scene to an editable mesh and deleted the original object since I didn’t need it anymore. My file is now become a 7 GB file from 70 MB.
Now when I load this file it takes ages, and when I save the file it takes even longer. Is there a way I can optimize the file? I can’t reduce poly count because it reduces the mesh and I need the detail.
Please help!
-
2 Replies
-
Without seeing the file or an image of the scene, its hard to advise.
Could you use primitive cylinders instead? You can keep these “low” poly but have them render perfectly smooth.
Is there a reason you can’t use instances?
7gb is pretty big but if there are thousands of rods, those poly’s add up. Check the end caps – first do you really need them? Are there more polys than need to be on the cap – usually you can get away with a single ngon or radiating triangles with no divisions.
Could the rods farther from camera be of a lower rez?
You can increase your phong angle and reduce the geometry and the rods will still render smooth (to a point). -
Hi Steve,
Thanks for the response. By the time you replied I had already sorted my problem. The thing is that I was rendering about 150 metal beams reflecting high resolution hdri maps in HD. When my work files arrived in the render farm their servers were crashing. Initially I thought it was my instance files so I sent them editable files. Then I realized it was the work pace itself that was so heavy, so I split the beams into 5 different work files so they can be rendered layer by layer and I could add them together in compositing later.
Reply to this Discussion! Login or Sign Up