OctaneRender® 2026.2 for 3ds max® v26.5

[neonZorglub]

3ds Max version supported: 2013 to 2026.

Changes of the 26.5 version, from 26.04

• Updated to Octane 2026.2
• Fixed crash with some textures
• Added missing Image Tile Set texture
• Fixed issue with tyFlow particle ID - added 'Birth Base ID'
• Fixed issue with imager upsampler
• Fixed issue with materialX sub parameter expansion
• Fixed issues with VRay material
• Fixed issues with PhoenixFD VDB volumes
• Added textures and material descriptions in UI when available

There is an issue when you open old scenes pre 2026 Octane. Where RGB maps are automatically set to use Output type = color4

I just spent ages trying to figure out issues with normal maps not working correctly. It is because they need to be set to color3 not color4

Old scenes opened in Octane 2026 seem to have RBG maps output type set to color4 where as creating a new RGB node is set to color3 by default

Thanks

Hi tombyrom,
Thank you for reporting this issue.
I could reproduce it and will investigate.
Those RGB image textures output should indeed be set to color3.
Thanks

[Elvissuperstar007]

I use 2025 3dmax

[coilbook]

Can we get a similar sparkles shader? https://youtu.be/M8G0Pk4oxwk?si=W4C5ZwXF1RIbZULY

[Elvissuperstar007]

Sometimes crashes occur for no apparent reason when trying to run the render viewport, as in the previous build.
It doesn't give any errors, it just closes 3dmax 2025.

[Elvissuperstar007]

Can we get a similar sparkles shader? https://youtu.be/M8G0Pk4oxwk?si=W4C5ZwXF1RIbZULY

Octane has been able to do all this for a long time, all the textures and procedures exist

[remKa]

Can we get a similar sparkles shader? https://youtu.be/M8G0Pk4oxwk?si=W4C5ZwXF1RIbZULY

You can use the "flakes" texture inside the normal slot

This a super nice texture, it would be great to have other sorts of normal textures, i.e. for scratched surface

[Elvissuperstar007]

I just checked and couldn’t find it, but it was in Octane! I remember there was a procedural brushed metal with circular patterns. I clearly remember testing Octane procedurals about 7 years ago, and it was there.

[tombyrom]

Hi tombyrom,
Thank you for reporting this issue.
I could reproduce it and will investigate.
Those RGB image textures output should indeed be set to color3.
Thanks

Thanks - any idea what the other issue though? Some older scenes not created in v2026 will not render.

To confirm it is an issue with 2026, I reinstalled v2025.5 - 16.12.

v2025.5 - 16.12 - Scene renders in Octane RenderView just fine, no engine errors

2025 - renders

v26.5 latest - Exact same file, but won't render and has engine errors?

2026 does not render

EDIT:
I have managed to reduce the error down to a single bitmap texture for debugging (however multple textures cause the render to not start, however not all of them)

See attached scene, I copied out a material from an old scene and on a new scene applied it to a plane.

To reproduce
1. Open file and try to render, it should fail with error
2. Remove the oXtxImg texture from the roughness slot and re-render, it should work
3. It complains about no OCIO file, however even with an OCIO loaded it still produces the error just a slightly different one.
4. The main error is this - Failed to build OCIO input transform for "tx-oTxImg"

I have tried to clear all the caches in preferences. But there seems to be some setting that cannot be controlled at the material editor level that is causing issues in 2026

[coilbook]

Hi neonZorglub,

Can you look into tyflow and slow eval times? Over 100,000 ty instanced little particles as low res spheres and eval times are 2-3 min per frame. But they are supposed to be instances. Seems like octane runs out of vram when tyflwo particle count increases every frame
Thank you

Empty file name.
Empty file name.
CUDA error (2) on device 3: out of memory
-> failed to allocate device memory
device 3: failed to upload data texture 67 '0:__data40__'
CUDA error (2) on device 2: out of memory
-> failed to allocate device memory
device 2: failed to upload data texture 67 '0:__data40__'

[neonZorglub]

EDIT:
I have managed to reduce the error down to a single bitmap texture for debugging (however multple textures cause the render to not start, however not all of them)

See attached scene, I copied out a material from an old scene and on a new scene applied it to a plane.

To reproduce
1. Open file and try to render, it should fail with error
2. Remove the oXtxImg texture from the roughness slot and re-render, it should work
3. It complains about no OCIO file, however even with an OCIO loaded it still produces the error just a slightly different one.
4. The main error is this - Failed to build OCIO input transform for "tx-oTxImg"

I have tried to clear all the caches in preferences. But there seems to be some setting that cannot be controlled at the material editor level that is causing issues in 2026

Hi tombyrom,
Thanks a lot for the scene!
I was trying many ocio settings, not couldn't find the issue..
All ocio settings work fine from version 2025 to 2026 (Color space in textures, ocio settings in camera)..
>> Except for 'Non-color data' !
This is not related to loading older scenes. You can get the issue with a new scene, if you just set 'Non-Color data' for Color space in a texture..
To fix this for now, just set any other Color space (sRGB, etc..)
I'll investigate more and will try to have a fix soon..
Thank you.