Otoy® is proud to announce the availability of a new OctaneRender™ for Maya®
The world's fastest and most feature-rich unbiased render engine that integrates completely into Autodesk® Maya®.
Maya® Version Requirements
This release will work with Maya® Versions 2020, 2022, 2023, 2024 and 2025 64-bit on Windows and Linux systems. Maya 2024 and 2025 on macOS (ARM only).
Important: if using macOS, we strongly recommend that you update to version 13.3. Prior to 13.3, there is an OS related issue that causes a render failure consistently if you render for long periods of time.
Hello,
I just updated from version 2023.1.1-22.10.
I understand that there are changes in color management, which is why the gamma of "imagetexture" is originally set to 1 instead of 2.2.
But to get a correct result, I have to manually set the gamma to 2.2 or manually connect an sRGB Ocio color space in each imagetexture. This doesn't make the work easier.
Is there a global setting to manage the color management of "imagetexture"? I couldn't find any information in the Maya documentation.
Especially since all the gammas in my old scenes are changed from 2.2 to 1, and the strange thing is that gammas other than 2.2 remain unchanged.
It doesn't make sense to change only the 2.2 gammas. If the management is different, they should all change proportionally, right?
All the assets in my pipeline have to be manually edited, it's a huge amount of work.
The default value of Maya-node's plug in a new created node - is Maya's "thing" that I'm not sure could be changed on-the-fly when Maya with the plugin is already running and all Octane node-types are already registered in the scene. Current default value for that plug is 1.0 in Standalone, this is why it is the same as in Standalone in Maya.
Regarding your old scenes you'd want to open in this version-branch - I can guess what's happening with only 2.2 plugs. Maya stores plugs' values in a weird way: only the non-default values get saved in the scene file, Maya ignores all the plugs with default values in them when saving a scene file. So if Maya loads a plug value from a scene file that has no value stored for that plug - it sets the current default value to it. Otherwise it sets the value stored in the scene file. And there is no way in the API to know the real previous value of that plug during Maya scene load process...
The big difference between Maya and Standalone - Maya doesn't have such thing as "internal nodes". Standalone just creates an internal sRGB OCIO node inside each new image texture node. But Maya can't do that, its new node just has a plug to which you could connect either already existing OCIO node, or create a new one and connect it.
It could maybe technically possible in Maya's API (not even sure so far) to connect this plug to something during creation of a new image node, but this would open a whole can of worms: what exactly node you'd want to auto-connect, which one from possibly a hundred of already existing in a scene, or create a new one for each new image texture node no matter how many of exactly the same nodes already exist in the scene... The most robust way is leave this decision to the artist who creates the node: they know for sure which one from hundred of already existing nodes they want to connect to that plug, or if they need to create a new one... As I mentioned - no such issue in Standalone, it is easier there because it has the internal nodes feature, and it just safely sets the internal default node which gets automatically destroyed as soon as an artist connects any other node to this plug...
So I see the solution to that would be just change the default for image textures' gamma plug from 1.0 back to 2.2. This will not be the same as in Standalone, but this will solve the difference in render result of a new default image texture node, and loading of older scenes' 2.2 plugs. Will fix that in next version, thank you for reporting this.
