VRAM and black frames on render

[ChrisPettit]

HI. Having a terrible problem with frames rendering completely black out of the Octane Renderer for C4D. I appears to not properly load all the geometry before it either shuts off and stops rendering or times out (I'm using the time limit feature with the Pathtracing module
I have a scene that involves a lot of geometry and textures that builds over time (each rendered scene is getting more and more complex). Suddenly I appear to have reached the limit of my ability to get all that geometry pushed into Octane before it times out. At first I thought I'd just raise the time limit simply to allow only the first frame to load all the geometry. But then it times out at the original time anyway even though I raised it. So them I cleared it, it still timed out, weird.

So then I copied and pasted all the geometry and textures into a whole new scene, but it simply wont load the geometry into the renderer before it just gives up and fails. But at no time has the renderer given and indication that available VRAM is low


I have 2 good Nvidia cards (Titan X and 980 GTX) and don't appear to be exceeding available VRAM. But the bottom line is it stops attempting to render before the geometry gets loaded entirely. Could this be a VRAM issue, or is there simply a limit to how much geometry and textures Octane can take before it goes buggy? Also, does Octane leverage both cards VRAM in conjunction with each other? In my case that would be 12GB + 4GB for a total of 16GB. Or does it limit it to the larger of the 2 cards?

I tryed this type of a project before with a client using Octane before I bought the new machine and the Titan card, and assumed that the only limitation was how much VRAM I have. Now I'm not so sure

Thanks in advance for any input.

[aoktar]

Hi,
Do you know geometry limits on Octane? Do you see some Cuda errors on Octane Log window or Console window?

[ChrisPettit]

After you mentioned it, I just ran a new search and found references to polygon limits, I had tried to understand that before but didn't realize it was related to polygon count. Thanks! Octane 3 gets rid of this problem yes?

Much more alarming however is the thread that indicates that the limiting factor for VRAM is the SMALLEST of of my 2 cards not the largest. So if I render out using both my cards, am I limited to the 4GB contained on the 980 or the 12GB on the Titan? If so, am I better off only using the larger of the 2?

Thanks again Aoktar for all your help!

[aoktar]

After you mentioned it, I just ran a new search and found references to polygon limits, I had tried to understand that before but didn't realize it was related to polygon count. Thanks! Octane 3 gets rid of this problem yes?

Much more alarming however is the thread that indicates that the limiting factor for VRAM is the SMALLEST of of my 2 cards not the largest. So if I render out using both my cards, am I limited to the 4GB contained on the 980 or the 12GB on the Titan? If so, am I better off only using the larger of the 2?

Thanks again Aoktar for all your help!

Hi,
If you're using latest versions of plugin, total triangle limit is around 19Millions. We are hoping the Otoy guys will rid this limitations with some revisions on 3.0 codes.
Also you are limited to Vram of lowest one. If you'll stick with these two cards, plug your monitor to 12gb card. Because OS and other softwares can spend some vram from desktop gpu. Check also out-of-core parameters for using system ram for textures.

See this topic: viewtopic.php?f=33&t=51679