Page 6 of 34

Re: Version 2.11.1 - RC1

Posted: Tue Oct 14, 2014 11:52 am
by aoktar
Rickky wrote:Camera response curve is broken in R16. Forget it, it works :D
But I notice that the Id mat with the new render passes is very noisy.
Is it the octane core ?
yes, not a plugin behaviour

Re: Version 2.11.1 - RC1

Posted: Wed Oct 15, 2014 5:36 pm
by smessing
Hi Aoktar-

I just updated to 2.11 and I am now getting random flashing colors as I move the camera around in the octane viewer. This is happening in r15 and r16. I tried updating to the new nvidia 344.11 driver and the issue is still happening. I am running 3 Titans on windows 7.

Have you seen this issue?

Thanks
-Steve

Re: Version 2.11.1 - RC1

Posted: Wed Oct 15, 2014 5:45 pm
by aoktar
smessing wrote:Hi Aoktar-

I just updated to 2.11 and I am now getting random flashing colors as I move the camera around in the octane viewer. This is happening in r15 and r16. I tried updating to the new nvidia 344.11 driver and the issue is still happening. I am running 3 Titans on windows 7.

Have you seen this issue?

Thanks
-Steve
Hi Steve,
just uncheck COHERENT parameter in kernels. This parameter makes faster and cleaner rendering, but flashes in first samples.

Re: Version 2.11.1 - RC1

Posted: Wed Oct 15, 2014 5:47 pm
by smessing
Got it. Thanks!

Also, any plans to integrate the new R16 reflectance setting so that they render in octane? It's sometimes nice to be able to render glossy shaders using the standard c4d materials. I currently can't figure out how to do this.

Thanks,
-S

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 5:30 am
by zackyd
I am experiencing delays when I am changing material settings, that I was not in previous versions. Is this due to a material preview?

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 11:23 am
by aoktar
zackyd wrote:I am experiencing delays when I am changing material settings, that I was not in previous versions. Is this due to a material preview?
yes most probably, material previews+opengl previews. Have you got big images?

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 11:24 am
by aoktar
smessing wrote:Got it. Thanks!

Also, any plans to integrate the new R16 reflectance setting so that they render in octane? It's sometimes nice to be able to render glossy shaders using the standard c4d materials. I currently can't figure out how to do this.

Thanks,
-S
yes, but we can support one specular layer

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 2:20 pm
by Augustronic
Hello Aoktar,

I'm handling several issues with the final render settings.

1) The geometry often isn't complete. The scene is heavy and single object are mising if I use "Resend Only Updated Objects" (maybe full motion blur is on, too). (At the moment it's working...)

2) "Send All Scene Data" is not available when using "Full motion blur".

3) Rendering passes and selecting "Resend Only Updated Objects" renders the the first frame with the set Path Tracing render setting of "Octane Settings". After the rendering of the passes it switches to Direct Lighting at the second frame and continues with Direct Lighting. My workaround is to use the "Overwrite Kernel Settings" and set my Path Tracing render settings there.

But anyhow, Octane v2.11.1 is the first build that's able to render this scene now!!

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 2:28 pm
by Augustronic
P.S.: It looks like Octane can't properly update X-Particles Skinner objects...

Re: Version 2.11.1 - RC1

Posted: Thu Oct 16, 2014 2:35 pm
by Weirdpictures
Hey Aoktar,

great build, working actually very stable on OSX Yosemite and GTX Titans. One thing we noticed in a render yesterday is that Coherent render produces flickering animations in some cases. It works amazing for stills and maybe exterior animations, but in interior area light scenarios the final rendered frames are flickering in an animation. When we render the frames without the coherent mode the animation and renders are fine and play without any flicker as usual.

I don't think that it's a bug but rather a limitation of this new algorithm to be aware of.

Otherwise plugin works pretty stable for us.

Thanks for all the hard work.