Tweet
Im using an supported rendering colourspace scene-linear DCI-P3 D65 (not sure why its an option). I found, that in combination with AdobeRGB display device, and Untonemapped view transform meant my backplates looked correct, and I could match easily in cg with no mismatches. Im sure my workflow is incorrect, but I get the results I need. I also found in a recent full cg job that some shaders like a gold I made looked much better than it did in ACES. (Aces had a secondary bounce that was more orange, and my current setup looked far more like the gold I wanted). Now this is all fine, since it works, and it looks how I like, but the input colorspace always changes itself back to ACES, despite my efforts to set it to what I want. I know this menu is tied to the maya color prefs, so they change when the VFB settings change, but it never remembers it, and everytime I need to open a scene, I have to go change the input colourspace. If Im stressed, or its late, or Im multi tasking, sometimes I forget and my renders (and gols) comes out looking wrong.
Is this intended behaviour, that no matter how often you change the input colourspace, to something other than aces, it always switches itself back upon scene re-open? Or do I need to change it in maya prefs for it to save to the scene, rather than changing it via the VFB? Ive attached a screen grab of the settings I like to use, and that work for me.
Is this intended behaviour, that no matter how often you change the input colourspace, to something other than aces, it always switches itself back upon scene re-open? Or do I need to change it in maya prefs for it to save to the scene, rather than changing it via the VFB? Ive attached a screen grab of the settings I like to use, and that work for me.
Attached Files
Comment