5/16/2023 0 Comments New in maya 2022![]() ![]() My CM rules config, xml file: deafultACES_new. You still need to create a few custom CM file rules, but it’s easier to use ACEScg than before.ĭon’t forget, the order is matter in the rules priority list!Īfter you created the rules save with the Export CM Pref button. Find your serial number on the Serial Numbers tab of the same popup. If you have ACEScg, linear files, use: ACEScg.For every math related data file you have to use: Rawįor example: Roughness, Metalness, Normal, Bump, Displace etc.For every directly color related, LINEAR and non-ACEScg file you have to use: scene-linear Rec.709-sRGBįor example: hdri files (hdr, exr) used in skydomes, and textured are lights etc. ![]() ![]() (in the old method this was the Utility – sRGB – Texture)įor example: usually tif, png, jpg formats and Color, Albedo, Base Color, SSS Color etc. For every directly color related, NON-linear and non-ACEScg file you have to use: sRGB.Similar color space names but different “content”, basically you have to apply almost the same conventions as before. The naming convention actually is not correct (strictly), but at least easier to use for every artist. In Maya 2022 the new and default color management settings are almost perfect (in most and general cases), but you still need a few tweaks to get the correct results.īecause the default Rendering space is now ACEScg, Autodesk choosed a simple and easy to use naming convention for it’s own config.ocio file and color transform files. Which is a nice addition for those who don’t want to use the default tone-mapped version (the rendering space of course is still ACEScg, so the view transform expecting that). The biggest change (through the config.ocio) file is now you can use an ACEScg based non-tone-mapped (sRGB) view transform. Actually Maya 2022.2 (and above), because there was a few changes in the OCIO config file and a few additional features are also added to Maya. ![]()
0 Comments
Leave a Reply. |