Page 18 of 18
Re: OctaneRender™ 2.1 for LightWave™ - Daily builds
Posted: Mon Dec 29, 2014 11:46 pm
by Lewis
Hi!
Can somene confirm me did we lost ability to see motion blur at octane IPR or that never worked at IPR? I find it strange that i can't see motion blur at 2.16.0 content scene called "octane_benchmark_FOV_motion_blur.lws" at IPR ? It works only when rendered (F9/F10) but not at IPR ?
Re: OctaneRender™ 2.1 for LightWave™ - Daily builds
Posted: Tue Dec 30, 2014 4:49 am
by abstrax
happymilk wrote:Hi Juanjo.
Good release (as ever)
I think I found a bug:
the new polygon side texture node don't work when i apply a bump node in the material
This happen in the mix material mode and in the mix texture mode

Thanks for the report. The polyside material should work in the mix material, but I can confirm that it doesn't work in material channels when bump mapping/normal mapping is used. We will try to fix it as soon as possible.
Re: OctaneRender™ 2.1 for LightWave™ - Daily builds
Posted: Tue Dec 30, 2014 9:27 am
by juanjgon
Lewis wrote:Hi!
Can somene confirm me did we lost ability to see motion blur at octane IPR or that never worked at IPR? I find it strange that i can't see motion blur at 2.16.0 content scene called "octane_benchmark_FOV_motion_blur.lws" at IPR ? It works only when rendered (F9/F10) but not at IPR ?
Yes, the IPR motion blur currently doesn't support the camera FOV enveloped parameter. It is a limitation because in the Octane IPR I need to use the camera FOV to support the IPR zoom, so it has it's own not motion blurred FOV parameter.
The camera FOV motion blur is only available in the final F9/F10 rendering.
-Juanjo
Re: OctaneRender™ 2.1 for LightWave™ - Daily builds
Posted: Tue Dec 30, 2014 9:30 am
by Lewis
Thanks Juanjo, i figured it out last night after side by side comparison to check what's the difference since i thought it's Octane option that was turned on when it was actually "E" buttona t FOV on LW camera

.