I have big problems with gamma and VFB+ and tons of questions I would like from the developer to be answered :- )
Not sure how to iniciate dialogue with him.
I'll try to write some notes for you from my experience.
Some of them from head:
With Vray it's super clear: You use gamma 1.0 in framebuffer with ticked sRGB. VFB+ also let's you do this. All is equal.
In Corona, this is somehow done automatically for you...so although Corona framebuffer stores image internally in gamma 1.0 also, and displays it in 2.2, the VFB+ displays it in 2.2 directly as well, so no need to tick sRGB there.
Which is a problem, because if I render with Corona on RebusFarm, I cannot bring the openExr back into VFB+, which is of course 1.0 back into VFB+ without it looking wrong. I have to tick sRGB, which makes it look different then it looked originally ! I have no idea what is happening there and why.
No matter what combination of Gamma I use (3dsMax, VFB+), the direct transfer button into Photoshop ALWAYS, double-gamma shit. ALWAYS. I tried every single combination.
I can only export stuff correctly from VFB+ using gamma 2.2 (like 16bit Tiff). So I loose the linear option, but I haven't been using linear post-production in long time, it became additional step I am glad to skip.
I believe all these issues are somehow connected with how VFB+ takes information from Corona. I cannot replicate this behavior by manually loading images into VFB+. I would like to maybe hear from the developer on what is going on here.
« Last Edit: 2016-02-01, 18:56:27 by Juraj_Talcik »
Logged
Please follow my new
Instagram for latest projects, tips&tricks, short video tutorials and free models
Behance Probably best updated portfolio of my work
lysfaere.com Please check the new stuff!