Help! Working with massive model Tweet

[fauntail]

Hi all,

I'm new here. I'm working with a 25 million poly model in c4d and its not rendering at all in the live viewer. I need to light it and work with it somehow but I can't even render it in live viewer. I've been combing through the forums and online, but I'm under a deadline and panicking a little bit. Can anyone recommend a way to

(a) reduce the polycount so it will render?
(b) create a proxy in c4d or octane?
(c) shed any light on how to manage a situation like this using C4d?

Also, I seem to be getting a render failure dialogue.


Thank you for even reading this.

Cheers,

F

[aoktar]

You need some VRAM to render bigger meshes. How much is yours?

[zoppo]

Use smaller textures and use render instances if possible.

[GIOLETS]

I can suggest my workflow:

1) first try to understand if the problem caused by the mesh or by the textures.
You can give a look to the Octane Log when you launch the render uin Picutre Viewer.
Yuo'll see something like that:

Device:0 TotMem:11Gb rtData:284Mb film:11Mb geo:4.417Gb node:130Kb tex:5.454Gb unavailable:559Mb temperature:38

In this case I have 4,4Gb of geometry (mesh) and 5.4Gb of texutre. So knowing how much VRAM I have on my GPU I can understand where is the problem.

2) the "out of core" option can help you sending all the textures data amount to the RAM of your PC and freeing the VRAM of your GPU for the mesh.

3) the suggestions from yhe other users are also crucial: try to use render instances if possible, and try to lower the resolution of your textures

[frankmci]

By my rough rule of thumb, 25m polys should take about 5 gigs of VRAM. If you have significantly less than that, yes, you'll need to reduce your polys.

The other suggestions of out-of-core, instancing, etc can make a big difference.

Also, you might want to break up the shot into different element passes and then composite. Does it lend itself to foreground/background? Subject/environment?

In a pinch, might dynamic level of detail be a solution? It can slow Octane down a bit with loading/unloading geometry but shouldn't add more than a few seconds per frame now and then.

As Giolets said, the Log can tell you a lot... if you can find it. It's stashed out of the way in Octane Settings/Settings/Other at the bottom of the tab. I always leave it to Log Output: All. I'd love to be able to stick that button in a more convenient toolbar.