Tweet
Hey there!
I'm kinda surprise there's no topic asking for a full ACES workflow with vray and 3ds max.
They are still used in big companies such as ILM to provide large environments, so the ACES workflow should clearly come up to life in an easy way.
The best solution would be to implement ACES CTL (Color Transform Language). More explanations here:
https://acescentral.com/t/colour-art...ng-aces/520/60
It would give a better accuracy and faster render.
Also you could update vrayOCIO with some features:
-> Activate/Deactivate VRAYOCIO map, for testing purpose only. The only way to do it it's to rename the in and out by something the config.ocio doesn't find.
-> Clarifying the sRGB colorspace environment variable (1, 2)
-> Clarifying the "colorspace type" parameter of a vrayhdri in the manual.
-> Clarifying the tag looked for by vray for the vrayocio "from basemap file name", like you did on the <UDIM>, <UVTAG> part. Add the possibility to add our own rules (check the "rule conditions" of the screenshot above).
-> Automatisation of all the steps needed to set up the aces workflow
Again the best choice would be more ACES CTL than OCIO, no doubt about it.
Thank you!
I'm kinda surprise there's no topic asking for a full ACES workflow with vray and 3ds max.
They are still used in big companies such as ILM to provide large environments, so the ACES workflow should clearly come up to life in an easy way.
The best solution would be to implement ACES CTL (Color Transform Language). More explanations here:
https://acescentral.com/t/colour-art...ng-aces/520/60
It would give a better accuracy and faster render.
Also you could update vrayOCIO with some features:
-> Activate/Deactivate VRAYOCIO map, for testing purpose only. The only way to do it it's to rename the in and out by something the config.ocio doesn't find.
-> Clarifying the sRGB colorspace environment variable (1, 2)
-> Clarifying the "colorspace type" parameter of a vrayhdri in the manual.
-> Clarifying the tag looked for by vray for the vrayocio "from basemap file name", like you did on the <UDIM>, <UVTAG> part. Add the possibility to add our own rules (check the "rule conditions" of the screenshot above).
-> Automatisation of all the steps needed to set up the aces workflow
Again the best choice would be more ACES CTL than OCIO, no doubt about it.
Thank you!
Comment