![autodesk flame color management autodesk flame color management](https://damassets.autodesk.net/content/dam/autodesk/www/products/responsive-imagery/responsive-lockups-banners/2019/formit-pro-2018-lockup-1200x132.png)
Warning: file: C:/Program Files/Autodesk/Maya2022/scripts/startup/l line 262: Color space "ACES - ACES2065-1" in node ":file10" is not defined in the selected transform collection. Warning: file: C:/Program Files/Autodesk/Maya2022/scripts/startup/l line 262: Color space "ACES - ACES2065-1" in node ":file9" is not defined in the selected transform collection. Warning: file: C:/Program Files/Autodesk/Maya2022/scripts/startup/l line 262: Color space "Output - sRGB" in node ":file7" is not defined in the selected transform collection. I was able to simply change the path file and save the scene, but when opening it back up, the settings look fine but I still receive some warnings. Here's a screenshot:īut when opening my scene, I get that warning message I mentioned and the settings changed back to the old broken ones, with the 1.0.3 OCIO. When opening Maya, everything looks fine. I did found something a little weird though. I hope this helps others who come across this. Affected color spaces will not be applied." Again, thank you for helping. It says "There is one missing color space used in the scene that is not defined in the selected transform collection. There's still one popup though, which I do not really know what it means.
![autodesk flame color management autodesk flame color management](https://i.ytimg.com/vi/qvGKgWwk5gM/maxresdefault.jpg)
Now that section is no longer grayed out and I can set it to the path you specified. I was somehow able to delete that OCIO environment variable I created by changing its path to Maya's default config, then after, it allowed me to delete it. I just want to double-check that when Maya 2022 is using its default OCIO v2 config, that opening a Maya 2022 does not produce color management errors by default. when its fully unset, when you go into your main Preferences/Color Management, you should see this path (and it shouldn't be greyed out) : The fact that you get errors when opening a Maya 2022 scene makes sense if the OCIO env var is set and pointing to aces_1.0.3\config.ocio, because that config probably doesn't contain the expected color spaces.ĭo you think you can unset the OCIO env var completely so that it uses the default installed config? i.e. That config is in C:\Program Files\Autodesk\Maya2022\resources\OCIO-configs\Maya-legacy
![autodesk flame color management autodesk flame color management](https://i.ytimg.com/vi/e5aWrvjfH-Q/maxresdefault.jpg)
Maya 2022 also has a "legacy" config file meant for compatibility, so that scenes from older versions like 2020 still load and look the same.
#Autodesk flame color management install#
So if the OCIO env var is not set anywhere by the user or system, Maya 2022 will load from that default install location and any scenes created in 2022 with its default color spaces will load without errors. But by default, Maya 2022 includes OCIO v2 and an OCIO v2 config file in it's default install location here: C:\Program Files\Autodesk\Maya2022\resources\OCIO-configs\Maya2022-default Shows that you have a custom OCIO v 1.0 config file set.
![autodesk flame color management autodesk flame color management](https://keycodeeducation.com/wp-content/uploads/2019/11/Flame.png)
#Autodesk flame color management driver#
Arnold Rendering Issue - Output driver 1 for AOV "RGBA" is null 2.