Has anyone else had issues with DR and gamma? Ever since upgrading to 2.40.04 (EDU) for Max 2014 I’ve had gamma issues with my nodes with the new workflow. If I set my main machine up the way the new workflow should work (Mode: Color mapping only (no gamma)) and use the sRGB button in the VFB my node buckets are a different lightness. If, however, I go back to my old workflow (No sRGB, ‘Mode: Color Mapping and Gamma’, etc.), the problem goes away and the nodes render the same as everything. So it’s not a file permissions thing, it’s related to gamma. It even happens in a blank scene with just a vray sun.
My suspicion is that it’s rogue config or dll files from VRay 2.40.03 or something that I made work for 2014 before the latest version was out, but I’m not really sure. I’ve uninstalled that copy but I did get a warning that ‘not all files were removed’ but I think that’s just one folder that is, in fact, empty anyway. Has anyone had a similar experience?
I made few tests with the same setup as yours, but everything works fine.
Could you try to uninstall V-Ray and delete all left over files or folders from the plugins, then install it again?
Also make sure that you are using the same build 2.40.04 Edu on all of your slaves.
No, that didn’t solve it. I even deleted my Appdata folder for Max 2014 on my nodes. The only thing that seems to solve it to have VRay handle gamma, very odd. Interestingly enough my old workflow yields slightly brighter results than the new and the nodes work everytime. I guess I will switch to the old workflow for now just so my nodes work.
Old workflow (still works, yields slightly brighter results):
Max Gamma @ 2.2
VRay @ 2.2
Save the file @ 1.0
VRay Gamma @ 2.2 and have it control gamma
sRGB button off
New workflow (breaks nodes, yields darker results):
Max @ 2.2
VRay @ 2.2
Save file to default gamma (no override)
Tell VRay to affect color mapping only (no gamma)
sRGB button on
I ‘solved’ what was causing it. If I change my burn value from .25 back to 1.0 in Color Mapping rollout the problem goes away, regardless of whether I let VRay handle gamma or no. This is good news although I like to be able to tweak the BV.
Any thoughts? This doesn’t seem to relate to me or my system. All the nodes are affected and it’s in any scene I try.
Unfortunately we are not able to reproduce the issue in our environment - everything works correctly even with Burn Value 0.25.
Would it be possible to attach a sample scene with the wrong-setup , and another one that is works correctly.
Any screen-shots or videos of the issue will be very helpful in order to solve the issue more effectively.
Ok, that’s really weird. I will try and get a scene and some screenshots ASAP and pm you with a link. My suspicion is the scene will work fine on your system, though, since it happens even with a brand new scene on mine. I guess I could try nuking my 3dsmax.ini file on all systems.
Please send the link support@chaosgroup.com , do not send it to PM because we are not monitoring PM messages.
Include a link this thread in the email - because we have a lot of requests and it is difficult to track from where every scene come from.
Was this ever resolved? I’m hvaing the same issue on a new render node. The burn & gamma values seems to be different on this single node compared to all the others.
Can you attach one image to see what you are getting?
Do you get this difference only on specific scene rendered?
Make sure that the new machine OS regional settings are identical to the other ones.