Here is the a quick step list:
- Download the OpenColoIO config for ACES 1.1 from this link:
- github.com/colour-science/OpenColorIO-Configs/tree/feature/aces-1.1-config
- Unzip and place the config in your user folder or on a server location.
- Set a system variable for OCIO to this path to use it for all applications that supports it and don’t have an option in the preferences to set the path manually.
- Or start Blender with the variable set only for Blender.
- On the Mac I use Automator to create an App called “Blender_ACES”. In this app I use a shell script to set the variable and start Blender.
- For Windows I use a simple .bat file.
- I didn’t find an easier and way.
- Happy Blending…
- Oh, the color chart you can find here:
- github.com/colour-science/colour-nuke/tree/master/colour_nuke/resources/images
I updated the page and added some more images and explanations what happens when you (in this case me) forget to start Blender in ACES but having already a .blend file that contains ACEScg images. This real accident happened with tests in MAYA some years back on a cloud render farm where the OCIO environment was just ignored.