Page 2 of 10
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 2:10 pm
by gabrielefx
Bug:
some weird behaviors with lights toggle on-off visible on-off
Scene created with Octane for Max 2.01 and opened with 2.03
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 2:12 pm
by gabrielefx
HHbomb wrote:Hi gabrielefx, I have opened your scene and no problem if I enable the lights.
you have Max 2014 or Max Design 2014?
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 2:22 pm
by gabrielefx
gabrielefx wrote:HHbomb wrote:Hi gabrielefx, I have opened your scene and no problem if I enable the lights.
you have Max 2014 or Max Design 2014?
Edit:
I found the bug cause
If I open mylights scene and I select the camera01 and I hit render (Octane frame buffer) The scene doesn't start.
If I select one ies and I turn it on immediately the render starts.
During the render if I turn off the ies light the render continue normally.
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 2:38 pm
by MistAjuliax
HI guys,
So i've made a simple test in 3ds max 2015. The differences i noticed for the same scene in 2.04 version are:
a laggy 100%cpu load when octane opens the viewport or loads the render in production mode when in 2.03 there no significant cpu load.
a significant increase using of vram, it takes a little longer to render, and much more to load the render.
octane for max 2.03 vram used : 0.021gb , no cpu load , hair&fur material parameters , no dynamics, production render takes 42secs
octane for max 2.04 vram used : 0.176gb , 100%cpu load , octane material( which means that you can load an image texture) , dynamics works when you check "live" in dynamics hair&fur parameters. production render takes 1min17
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 2:46 pm
by merid888
thank you karba, thank you
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 3:16 pm
by gabrielefx
MistAjuliax wrote:HI guys,
So i've made a simple test in 3ds max 2015. The differences i noticed for the same scene in 2.04 version are:
a laggy 100%cpu load when octane opens the viewport or loads the render in production mode when in 2.03 there no significant cpu load.
a significant increase using of vram, it takes a little longer to render, and much more to load the render.
octane for max 2.03 vram used : 0.021gb , no cpu load , hair&fur material parameters , no dynamics, production render takes 42secs
octane for max 2.04 vram used : 0.176gb , 100%cpu load , octane material( which means that you can load an image texture) , dynamics works when you check "live" in dynamics hair&fur parameters. production render takes 1min17
laggy when opens the material editor too.
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 3:47 pm
by HHbomb
I installed 2.04 for testing.(just plugin)
I wanted to revert to 2.07a but now net render don't works anymore, slaves pc are "invalid slaves"...
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 5:41 pm
by MistAjuliax
MistAjuliax wrote:HI guys,
So i've made a simple test in 3ds max 2015. The differences i noticed for the same scene in 2.04 version are:
a laggy 100%cpu load when octane opens the viewport or loads the render in production mode when in 2.03 there no significant cpu load.
a significant increase using of vram, it takes a little longer to render, and much more to load the render.
octane for max 2.03 vram used : 0.021gb , no cpu load , hair&fur material parameters , no dynamics, production render takes 42secs
octane for max 2.04 vram used : 0.176gb , 100%cpu load , octane material( which means that you can load an image texture) , dynamics works when you check "live" in dynamics hair&fur parameters. production render takes 1min17
I forgot something, it's a hair&fur scene test.
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 5:48 pm
by mykola1985
It, would be nice to see a simple comparison picture of the new GI Clamp option... can't figure out the difference
Re: OctaneRender® for 3ds max® v2.04
Posted: Fri Jul 25, 2014 6:40 pm
by coilbook
after installing 2.04 this is how first frame always looks like in the animation sequence, unfinished