Octane vs iRay (Image Series rendering in DAZ)

dennis.d.t2972686

Hi All,

When I start a GPU-based iRAY Image Series render in DAZ, I can never be 100% sure than the next frame render is going to stay GPU-based and not switch over to CPU-based rendering (yes, I'm using the latest NVIDIA drivers and yes, the texture size is pretty much the same as in the initial frame). It's really a 50/50.... Is Octane any more consistent in this regard than iRay? 

 

 

 

DustRider

Not an issue with Octane, it supports out of core memory (can use system RAM as well as GPU memory), but you will most likely need to modify/optimise your shaders to make them look like they do with Iray.

Leonides02

DustRider said:

Not an issue with Octane, it supports out of core memory (can use system RAM as well as GPU memory), but you will most likely need to modify/optimise your shaders to make them look like they do with Iray.

Octane is a mess with DAZ. I recommend against it unless you're willing to put in hours adjusting the materials.

TheKD

I had that problem when I used win10, even sometimes just doing one render would drop in the middle to cpu for no apparent reason.

As for octane, I was a bit dissapointed. Everyone I talks to who uses octane as their goto were always telling me that it's so much faster than iray. In the few days I took testing it, iray was faster. The materials came over looking OK, but I only tried it on one scene, containing one G8F character. Could have just been a lucky pick, I haven't had time to mess with it again since. The one consistant issue I was having was my geograph kept vanishing on me in the octane render, and I had to keep stopping the render, and readding it when I noticed the gaping hole came back.

One weird issue I had on one scene I was just messing about, not rendering a normal scene that I would for production, the geometry was in the wrong place. I had a girl sitting on a chair in the viewport and in iray render. But in octane, the chair was moved five feet away. I only seen it happen once, but that was a real head scratcher lol.

marble

TheKD said:

I had that problem when I used win10, even sometimes just doing one render would drop in the middle to cpu for no apparent reason.

As for octane, I was a bit dissapointed. Everyone I talks to who uses octane as their goto were always telling me that it's so much faster than iray. In the few days I took testing it, iray was faster. The materials came over looking OK, but I only tried it on one scene, containing one G8F character. Could have just been a lucky pick, I haven't had time to mess with it again since. The one consistant issue I was having was my geograph kept vanishing on me in the octane render, and I had to keep stopping the render, and readding it when I noticed the gaping hole came back.

One weird issue I had on one scene I was just messing about, not rendering a normal scene that I would for production, the geometry was in the wrong place. I had a girl sitting on a chair in the viewport and in iray render. But in octane, the chair was moved five feet away. I only seen it happen once, but that was a real head scratcher lol.

Agreed. As we discussed in the other thread - I had that strange object move behaviour too. Some comments on the Otoy forum suggested that they made it free because it is a such a mess though why they would want to showcase a faulty plugin is beyond me.

EDIT: It seems that DAZ Support are addressing the frame 2 fallback issue in the forthcoming beta version but that, for me, is only one of the probelms with 4.12 and IRay. It will be welcome though, if they fix that at least.

dennis.d.t2972686

Thank you. This is very helpful. 

Marble, I'm still using 4.10 and discovered some time ago that disabling "Optix Prime Acceleration" really helps with the fallback issue.

marble

dtinc88 said:

Thank you. This is very helpful. 

Marble, I'm still using 4.10 and discovered some time ago that disabling "Optix Prime Acceleration" really helps with the fallback issue.

Oh yes. I have few problems with 4.11 but serious problems with 4.12 (GR or beta).