Open AlexeyAdamitsky opened 1 year ago
To solve your issue you have to add "Non-Color" option by adding it in to the config.ocio file. Open it as a note or TextEdit if you're using mac.
Under the colorspaces line add:
!
This option is from the default config.ocio file after adding that restart Blender and it should work correctly. Good luck.
Thanks for the suggestion. It's a solution for sure. But it's not a great one because it'll essentially create a duplicate or RAW color space role but called differently. The best approach would be for the addon developer to support color space roles and not just the names. Because names can vary but roles are more permanent and future-proof for OCIO changes in Blender.
DeepBump (v4) doesn't work if you run a different color management config. In my case I'm using AgX config from EaryChow.
I'm getting this error:
I'm not sure if this is possible, but it would be great if you could use color roles instead of explicit "Non-Color" color setting. This way what color config a users uses won't matter as long as the config is properly setup.