OTOY Forums

Hello friends,

I am using a linear workflow and want to save an OpenEXR Untonemapped file with the 3dsmax octane plugin, and i am getting a corrupt image...(see attached image)

the problem comes out when i use the "use tone mapping" option in the camera imager (3dsmax)
when i use octane standalone version, the EXR Untonemapped file comes out ok.
what is wrong?
im using a linear response by the way.

thx for your time,
hope you can help me with this, i dont want to be exporting the file to the standalone for saving the final render...

PD:
Im not really sure how to get the EXR Untonemapped version in 3dsmax, there is not an option like in the standalone

Same here with all releases I tested since 2.0

Saving an untonemapped open-EXR ist totally broken in Octane.
Often it causes my Photoshop CS5 to crash, wenn changing mode to 16 or 8 bit.
Seems octane 3dsmax is uncapable of producing working 32bit EXR files.
I have posted this twice and gave up ... nobody cares.

Im using exr all the time, and it works OK. One thing is spooky though: as when you use linear wf in max and vray for example. You typicaly whant tu load and save output in gamma 2.2 but If you do that in octane/max you end up with a negative gamma, you havet to add a gamma of something like, more than 4. IF you use default, gamma 1, you havet to add a gamma 2.2 curve to it..

I'm having the same problem here !!
and when I turn the tone mapping off, seems the gamma correction starts working just in 1.0 and the 2.2 from the camera stop working, and when I save this file in 3d full float, I can see some black dots, I think is the same problem, and I haven't find anything here teaching how correct this.
Thanks guys !!

Lightfarm wrote:I'm having the same problem here !!
and when I turn the tone mapping off, seems the gamma correction starts working just in 1.0 and the 2.2 from the camera stop working, and when I save this file in 3d full float, I can see some black dots, I think is the same problem, and I haven't find anything here teaching how correct this.
Thanks guys !!

I think it´s a good thing the gamma curve is not baked, and that it´s better to work linear as long as possible Just use a LUT for the gamma, in Fusion or Nuke in example.
don´t know how it works in PS though.
As for the black dots, I haven´t seen it here.

I checked how it worked for me in PS. It works OK as long as I set the prefs in max to not gamma correct (or maybe just set Gamma to 1).
If I load it in to my PS collor profile it will come in as gamma 1. If I use the embedded profile or discard the profile, it will come in correct, with a gamma 2.2 curve applied. The problem that occurs when you add a gamma profile from max is that it somehow get´s negative. and so. very dark. PS also crashed everytime I tried to do changes to the image so I guess it also corrupts by the max-gamma saving.

hope this helps, and pleas confirm the max gamma thing

/Daniel

Thank you, I will try this and I tell you soon, but the black dots it is a really problem. in this image is just a few dead black pixels, but in other images there is a lot of them, and the only way to remove them is rendering with the normal 3dsMax frame buffer.I think those black dots shouldn't be there in the Octane frame buffer as well, right?