-
Vram management in Octane
Hello,
Im after some advice, if any one is feeling generous…Recently I have been making projects with higher poly counts, such as large scale airports and high poly kitchen appliances. Quite quickly I come across problems with Vram, not enough Vram.
I go through striping models down as much as possible, use instancing as much as possible, reduce texture sizes (so they’ll be 512px or lower if not close for example) and use octane textures as much as I can rather than image textures.I’m wondering how others deal with such scenarios, for example, I had a cad model of a fridge freezer which i stripped down re topped as much as I could, but it still had 15m polys, then I had to fill it full of photoreal food! In the end it wouldn’t render locally and I had to send to render farm. Is there a ‘limit’ on how high a poly count octane can handle, are other renderers more or less capable (i really dont want to move from octane even for single projects!)
I currently have my main PC which has an i9, 64gb ram and 2 x 3080 (10gb, but i can only seem to use 6gb), and a slave pc with 4 x 1080ti.
If anyone can offer advice or links to how to best control these problems or best practices, like would it be more efficient to combine models so they are high poly but less objects?
Any help much appreciated
Cheers
AKreplied 1 month, 2 weeks ago 2 Members · 3 Replies
-
3 Replies
-
Hi Andy,
With the use of Instances as much as possible, because it has a significant effect in reducing the file size, one of the methods used is to render the scene in pieces and assemble the renderings in Photoshop or other programs. If you have several shots, you could in each scene keep only the visible things on the camera and delete everything else. You could also use the Polygon Reduction tool, in addition to some tips related to lighting and materials such as:
- Check which material effects are computationally cheap vs costly as caustic or detailing displacement materials and use the cheap ones as much as possible if the costly ones are not significantly better.
- Simplify lighting complexity as much as possible and prevent emissive surfaces from being blocked too closely by other geometry.
- Consider faking volumetrics if possible and consider whether they’re worth it for the scene.
I hope this is useful to you.
-
Thank man yes very helpful,
On further research and testing, I have found that reducing parallel samples to lower, such as 4/8, this frees up alot of Vram. Also using the built in texture compression wisely you can free up more.
I guess its a case by case and trim the fat as much as you can, and buy bigger cards when you can!
Thank you
-
You’re welcome, Andy! thank you too for sharing with us what you’ve found.
Reply to this Discussion! Login or Sign Up