Page 3 of 6
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 1:00 pm
by funk
Juanjgon, BorisGoreta is right. It seems you have reversed the IPR EXR savers. In previous versions (1.20.6 and standalone) "Save EXR" gives you a HDR (not tonemapped) EXR, while "Save EXR Tone mapped" gives you a LDR tonemapped EXR.
In this version 1.31.2 its now in reverse. "Save EXR Tone mapped" is giving us a HDR EXR, while "Save EXR" is giving us a LDR EXR
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 1:07 pm
by juanjgon
funk wrote:Juanjgon, BorisGoreta is right. It seems you have reversed the IPR EXR savers. In previous versions (1.20.6 and standalone) "Save EXR" gives you a HDR (not tonemapped) EXR, while "Save EXR Tone mapped" gives you a LDR tonemapped EXR.
In this version 1.31.2 its now in reverse. "Save EXR Tone mapped" is giving us a HDR EXR, while "Save EXR" is giving us a LDR EXR
Ahhh ... yes, this could be the problem, I am going to check it. Thanks
-Juanjo
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 1:12 pm
by funk
Actually I did further tests and its not just simply reversed. There is more to this bug
I also tested standalone 1.32 and it is also giving odd but different results.
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 1:32 pm
by BorisGoreta
When the viewport is in wireframe mode IPR renderer sometimes gives uncorrect results, is this still the issue of LW not being able to provide correct poly data when in wireframe mode ?
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 1:37 pm
by funk
I posted a reply to the 1.32 RC about EXR saving.
http://render.otoy.com/forum/viewtopic. ... 81#p171281
It seems standalone 1.32 is now burning in exposure/fstop/iso plus doing some sort of gamma when saving untonemapped. Previous versions didnt do this. The lightwave plugin bug might stem from this although the standalone is not limiting the dynamic range the same way.
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 3:33 pm
by juanjgon
BorisGoreta wrote:When the viewport is in wireframe mode IPR renderer sometimes gives uncorrect results, is this still the issue of LW not being able to provide correct poly data when in wireframe mode ?
Yes, perhaps there are some issues with normals. Can you show me a screen grab with this problems, or a way to reproduce them?
-Juanjo
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 5:01 pm
by polytek
Juanjo,
I have a question about the export function from lightwave to the stand alone app, most off the time when i push the export button there is no respond at all, nothing seems to happen....am i missing something?
Poly
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 5:19 pm
by juanjgon
polytek wrote:Juanjo,
I have a question about the export function from lightwave to the stand alone app, most off the time when i push the export button there is no respond at all, nothing seems to happen....am i missing something?
Poly
To export a scene you need to have the IPR working. Export functions save the current scene loaded in the IPR.
-Juanjo
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 5:53 pm
by polytek
Yes i know, i have IPR working but even then the button dos not always work...
Poly
Re: OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Posted: Mon Feb 17, 2014 6:02 pm
by juanjgon
polytek wrote:Yes i know, i have IPR working but even then the button dos not always work...
Poly
Strange ... do you have the IPR in pause mode or something like that?
-Juanjo