Render sits on Exporting Materials / 3gb VRAM? I have 15.

[richieblac]

Hello, I recently purchased V3 and this is my first ever foray into Octane and a third-party renderer.

GPU's are a Titan X 12gb and a GTX 780 3gb.

I began by fiddling with some of the stock models in C4D with a simple HDRI and floor. The Live Viewer is working great.

However, when I go for a render in Picture Viewer, it sits in Exporting Materials.... The longest I waited was over 10 minutes but at that point I figured something has to be wrong.

When I try out a test with only Octane materials, the render follows through immediately.

Is this normal behaviour?

Also, when I have my GTX 780 enabled, Octane says there is only 3gb VRAM available, seemingly ignoring the Titan X. Is this normal?

Thanks for your answers!

-Rich

[tukor]

Hi there.
First of all im a total noob, so better wait to other one to answer you

But if you want to know what i think, this is it:

I dont think Octane is getting 15ram from your because Octane only takes into account the lower card. So thats why its using 3gb.
Thats because each card has to get the scene into its memory, so the 3gb card cant take more than 3gb.. so the total usage is 3gb.
Their mems does not stack.
You better let the titan be used for Octane with priority = maxium (dont worry i have a 980ti with 6gb and still havent found its limit), and the 780 for the display so you get a smooth viewport while the Titan is rendering.

The other thing, its something i have not used (y try to use all octane material, without c4d standard mats).
But i think it maybe has something to do with the texture sizes that octane uses for converting the standard mats to octane (i think it bakes the image).
I dont know how to fix it, but i know there are some options for it.

Edit: take a look at: octane settings-c4d shaders and see if something there is useful.
And dont worry. You will LOVE Octane.

[aoktar]

Hi,

First thing to know LV != PV. Yes it display same results but having some differences under the hood. I have explained in manual as much as possible.

LV works with viewport data. So triangle counts can be different than Picture Viewer. Because for example, subdivisions. LV is using the result with affected by "Editor" parameter but Picture viewer accounts "Render" parameter. Try to make all this parameters same. I suppose that's about this.

Second there may be some problems if you use other type materials or textures not Octane. Also play with all parameters on some test scenes to see how works. Settings, kernels, imagers, etc...

And Octane has to use same amount VRAM on each gpus.

[richieblac]

tuker: I already love it! I was playing with the demo for a week before I decided to pull the trigger and buy. I expect and accept differences with a third-party renderer, and specific behaviours when interacting with the host. Just trying to come to grips with what they all are! Actually my Titan X runs warm on low/medium priority, assuming because it's also driving my 3 displays. I've set up a custom fan speed curve though, and the temps are acceptable after that. I would still like it to drive my displays for other applications, so perhaps this is a situation where if I'm in a particularly demanding project, I'll move the displays over just for that.

aoktar: Thanks for your response! I will just keep on tweaking with settings in small scenes and see what does what. But I will also simply get used to setting up/transferring to Octane materials when I import someone's model that uses C4D mats. I think with the VRAM issue, what I will do is have both cards enabled for general use, until the 3gb is threatened to be full, then I will just disable the 780.

[aoktar]

Always best to check vram usages and triangles without going blindfolded. And read some part of manual about different triangle counts for LV vs. PV. Use same subdivision, etc. for "Editor" and "Render" parameters.
Don't forget to enable out-of-core for textures if you need.