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
OctaneRender™ for LightWave™ 1.5 beta - build 1.31.2
Moderator: 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
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.
I also tested standalone 1.32 and it is also giving odd but different results.
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
-
BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
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 ?
19 x NVIDIA GTX http://www.borisgoreta.com
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.
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.
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Yes, perhaps there are some issues with normals. Can you show me a screen grab with this problems, or a way to reproduce them?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 ?
-Juanjo
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
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
win 8.2 / 64 / systemmem 27Gb / gtx 750Ti & asus stricks Gtx 780 6Gb
To export a scene you need to have the IPR working. Export functions save the current scene loaded in the IPR.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
-Juanjo