OctaneRender for Maya 2025.2.1-24.7 [STABLE]

[JimStar]

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 2022, 2023, 2024, 2025 and 2026 64-bit on Windows and Linux systems. Maya 2024, 2025 and 2026 on macOS (ARM only).

Octane for Maya masterclass:
https://www.youtube.com/watch?v=fANBzifhSow&list=PLTqdDmFtprFkzaBM7cmp8ZipQCNupDD0H


Changelog and the installers for Octane Standalone are here:
OctaneRender Standalone

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.

Changes since version 24.6:

• Implemented Maya 2026 support.
• Integrated the 2025.2.1 rendering engine.
• The file-names of plugin installers are now in unified format across all Otoy DCC.

Maya 2026 support is in process, going to be implemented in upcoming versions...


=================================
Subscription Studio+ Downloads
=================================

OctaneRender for Maya Studio+ [Windows](Link)

OctaneRender for Maya Studio+ [Linux](Link)


=================================
Prime Downloads
=================================

OctaneRender for Maya Prime [MacOS](Link)


=================================
DEMO Downloads
=================================

OctaneRender for Maya DEMO [Windows](Link)

OctaneRender for Maya DEMO [Linux](Link)

[Jozvex]

Hello, this might be a me problem but I've just installed this version and Maya 2026 can't find any of the AE templates for Octane's camera. I get this:

createNode camera;
// cameraShape1
// Error: line 1343: setParent: Object 'octSampPerFrameOctColumnAe' not found.
// Error: line 1405: Object 'octAnimDataOctAnimatorData' not found.
// Error: line 1343: setParent: Object 'octCamTypeOctColumnAe' not found.
// Error: line 1448: Object 'octFStopApertureSelectionOctFStopAperture' not found.
// Error: line 1343: setParent: Object 'octFStopOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octApertureOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octApertureEdgeOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octDistortionOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octPerspCorrOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octFocalDepthOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octAutoFocusOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octPixelAspectOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octApertureAspectOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octBokehRotOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octBokehRoundOctColumnAe' not found.
// Error: line 1343: setParent: Object 'octBokehSideCntOctColumnAe' not found.


I haven't done any further testing beyond this yet, so I'm not sure if others are not working. Thanks!

[JimStar]

Jozvex
I've just double-checked, and I can't reproduce this. The 24.7 plugin works without problems on my Maya 2026 installation. No errors generated for cameras, and the Octane rollout in camera's AE shows correctly and generates no error messages...
It's maybe something wrong with your Maya or plugin installations, or with Maya user-preferences maybe corrupted, or the scene itself, etc... Maybe reset Maya's user-preferences could help...

[Jozvex]

Hello!

I reinstalled Maya 2026 and now it works fine, so I guess something was messed up.

[itsallgoode9]

was something done regarding the texture gammas importing at 1.0 (i havne't updated in a while so couldve been done an earlier version updates) ? I think now if you open an old scene everything goes to 2.2, even if you HAD set it to 1.0.

[JimStar]

Currently the default values for Maya gamma plugs are back to 2.2, to make very old scenes open with proper values.
Because there is a problem with how Autodesk saves plug values in Maya scenes: if the value is default at the time of saving a scene, Maya does not write the value to the scene file at all. So it is always back to currently-set default whenever the scene is opened later. Thus there is no way for the plugin to do an on-the-fly conversion because the plugin does not know if the plug value was read from a scene file or it was just set as a current default and was intended to be like that or not...
So the best way would be just running some simple MEL script to set all the gamma plugs to a desired value if needed...

[itsallgoode9]

are you kidding me. not all values are 2.2 and not all value are 1 (hell, I have some set arbitraily inbetween from time to time), so a blanket number for a mel script isn't a solution.

I have a hard time believing this is a maya issue because the only thing that has changed for me, which caused this issue, is me updating my octane plugin. Older plugin, everything defaulted to 1 (which is broken). updated plugin everything is now 2.2 (which is broken). Maya version is the same either way. if this was a maya version issue, the issue would've alway been there, which it wasn't. I just opened a scene that I made a week ago and now all of my values are 2.2 even if I had changed them to 1. By your explination, that should've been saved as 1, since i changed it from the default value of 2.2.

If it truly is a maya issue (which i don't believe) then octane needs to save the gamma values regardless of maya. Imagine having a scene with hundreds of textures and all of a sudden needing to manually go through and check/change hundreds of gamma values--that's nowhere near realistic or acceptable.

[JimStar]

Maya saves all values that are not default. So if at the time of saving the default is 1.0 and your set value is 1.0 - it will not be saved in the scene file, and when reading the scene it will be set to the current default (if current default is 2.2 it will be set to 2.2). But if during saving your value is say 1.1 - it will be saved by Maya, and restored as 1.1 no matter what the current default is during reading the scene file...

[JimStar]

You can easily check that this is how Maya works: just open your saved .ma scene file with a text editor and search for some texture name that had a default value of gamma when you saved it. You will not see a line for that texture where Maya saves the "gamma" plug value. But you will see these "gamma" lines for any textures that have non-default values of gamma...

This is how Maya works for any nodes, even its own nodes, not just Octane's ones.

[JimStar]

I think I can implement a setting for Octane, that will allow you to choose what default you want for gamma value in textures. That should workaround this Maya's issue.
Just wait for the upcoming 24.8 version, should be ready soon...