display gamma in RT

[Subburb]

There was an issue for example, when the user has chosen 2.2 display gamma in the 3ds Max preferences, but is using the V-Ray VFB to render with 2.2 gamma in the "Color mapping" section of V-Ray. In that case, the ActiveShade view ended up being gamma-corrected twice, which is now fixed.

Vlado, can you confirm that point ? so if user have SP5 + RT 1.5SP1 this issue is corrected ?

I've some solidrocks beta testers wich seems to have double gamma when using max display gamma 2.2 + Vray gamma 2.2...

[Subburb]

just an idea : an additionnal option named "don't affect gamma" would be useful (near the don't affect colors) to separate the gamma thing from Colormapping, to help users to find their way...
Actually if you check this option (don't affect colors), you're forced to be into Linear color mapping. With this additionnal option, users should bake or not gamma into final image, using desired color mapping.

[Subburb]

Hmmm i'm using Vray SP5 and fresh max2009 VrayRT demo (x64). The 2010 RT demo just crash when i launch setup.

Here's the result : RT windows seem to remains in double gamma....

[danieljhatton]

Here is my two penneth. You can see I am using the Reinhard burn reduction which does work well with the 'Don't affect Colours (Adaptation)' set up, this then naturally does not cross over to RT. Is it currently impossible to match this method in VFB to Max without reverting to Adaptation RGB option which produces bad results with some HDR lighting methods? One would assume the RT would just match VFB?

[danieljhatton]

I was thinking. In the next Service Pack of Vray RT would a tick box option 'Match Vray Frame Buffer' be an option? It would be a very usable solution would'nt it. Unticked would match the Studio Max Frame Buffer. This way, the Reinhard method can work, and anyone using the default adaptation method can leave it ticked or un-ticked and will get the results they normally have now anyway. Jees, just thought, you would'nt even need a tick box at all. Even better.

Also. When a copy of Vray VFB is made, why does a Max FB copy appear and not a Vray VFB copy? It seem to me that all these issues are here because the Vray VFB shares a relationship with the Max FB? Am I right?

[vlado]

It seems to me in the screenshot, that it is not the gamma that is different between the images, but something else (looks mostly like the sunlight is different). Would it be possible to get me the scene for this to vlado@chaosgroup.com ?

Best regards,
Vlado

[danieljhatton]

It seems to me in the screenshot, that it is not the gamma that is different between the images, but something else (looks mostly like the sunlight is different). Would it be possible to get me the scene for this to vlado@chaosgroup.com ?

Best regards,
Vlado

Sorry I messed up my input gamma with the materials, so here is another using the correct set-up. Still want it?

Also I am using a compensation curve in VFB! Maybe another thing effecting things.

[vlado]

Yes, the VFB curve can definitely cause the results to be different.

Best regards,
Vlado

[RockinAkin]

Another scenario was using the sRGB button in the V-Ray VFB; V-Ray RT now checks this and applies the respective correction to the ActiveShade view as well.

Hi Vlado,

Sorry to bring up this old post - but I just found something that MIGHT be considered a bug. (certainly confused me for a little bit)
If you launch VRayRT active shade BEFORE opening the VRay VFB and checking the sRGB button, the activeshade window will not be affected once the button is checked. You have to restart active shade to make the button affect active shade.

Maybe would be nice if it RT monitored the state of the sRGB button in real-time.

Thanks.