OctaneRender® 2026.2 for 3ds max® v26.7 - 3dsMax 2027 support

[paride4331]

I lost the overview a bit here in the threads.

I'm still running 3dsmax 2024 because of all the lagging reports with newer versions. So also on Octane 2025.5- 16.12.
Reading here all the posts it seems its a bit dangerous for updating to latest version? Especially if I render out of core with really heavy scenes? I'm not working with particles and clouds like others here.

Hi mbetke,
My recommendation would be to move to a newer version of 3ds Max, v2026 should work perfectly fine, or v2027 if you specifically need it, and then install OctaneRender 2026.2 on that setup, rather than using it with 3ds Max 2024. I’d also suggest running a few tests first to identify any possible compatibility or stability issues.Regarding the Nvidia Studio drivers, after extensive testing I eventually decided to roll back to version 591.86. The newer releases didn’t show any clear or critical issuesa te moment, it seems to me, but in my experience 591.86 currently feels the most solid and dependable driver version for OctaneRender.
Regards
Paride

[mbetke]

I made upgrade to this version and also updated to current VRay and Corona renderer. I don't have license for them and never use them but as far as I know they are needed for material conversion.

Now I have problems that the material is unsupported. But it used to work for years before. This is the log for it:

Code: Select all

...{elapsed : 168.24}...................................................................................................................

[2026-05-28_17:51:27.00] Converting material slot #0 <Plast Cher> to an Octane material..
[2026-05-28_17:51:27.00] !! Failed to convert material <Plast Cher>, unknown class <
CoronaPhysicalMtl>, Class_ID(0x6912ab89, 0x87151720) sid=3072.. 
[2026-05-28_17:51:28.31] Slot #0 <Plast Cher> not an Octane material..

"Currently supported" seems to be reduced to only VRay Materials for some reason.

Any ideas?

[neonZorglub]

I made upgrade to this version and also updated to current VRay and Corona renderer. I don't have license for them and never use them but as far as I know they are needed for material conversion.

Now I have problems that the material is unsupported. But it used to work for years before. This is the log for it:

Code: Select all

...{elapsed : 168.24}...................................................................................................................

[2026-05-28_17:51:27.00] Converting material slot #0 <Plast Cher> to an Octane material..
[2026-05-28_17:51:27.00] !! Failed to convert material <Plast Cher>, unknown class <
CoronaPhysicalMtl>, Class_ID(0x6912ab89, 0x87151720) sid=3072.. 
[2026-05-28_17:51:28.31] Slot #0 <Plast Cher> not an Octane material..

"Currently supported" seems to be reduced to only VRay Materials for some reason.

Any ideas?

Hi mbetke,
Thank you for the report and the log.
I could reproduce the issue.
It's specially a problem with CoronaPhysicalMtl. The other corona materials and objects are converted correctly (eg CoronaLegacyMtl, CoronaLayeredMtl, CoronaLight,..).
There is a conversion process for CoronaPhysicalMtl, but unfortunately, it's not called when we do the normal conversion.
It is called when Octane Preferences / Material / 'On-the-fly Material Conversion' is enabled, and the conversion is done internally, so the material can be renderer by Octane.
So you could keep it unconverted for now. The next release will add the normal conversion .
I also noted that CoronaShadowCatcherMtl and, CoronaScannedMtl are not supported yet. I'll try to add those in a future release.
Thanks

[mbetke]

Thanks. I thoughts it's a problem on my side with the Corona Update I did. Glad it can be fixed!

I did some manual adjustments for now. Corona Materials are very shiny usually with a roughness set to 0.0 all the time, which makes it neccesary to adjust them all one by one after first conversion pass.

[neonZorglub]

Thanks. I thoughts it's a problem on my side with the Corona Update I did. Glad it can be fixed!

I did some manual adjustments for now. Corona Materials are very shiny usually with a roughness set to 0.0 all the time, which makes it neccesary to adjust them all one by one after first conversion pass.

Hi mbetke,
Thank you for the feedback on Corona Materials.
I'm adding a preference setting:
"Corona: Replace Glossiness 1.0"
"For CoronaLegacyMtl (CoronaMtl), if the glossiness is 1.0, the converter will use this value instead. Set -1 to keep the value 1.0. Octane Roughness is set as (1 - corona glossiness). To get the usual octane default 0.0632, use a glossiness of 0.9368"
Thanks

[remKa]

Hello,

Motion blur doesn't work with displacement, please see attached video and override motion blur in cameras is broken again :

[paride4331]

Hello,

Motion blur doesn't work with displacement, please see attached video and override motion blur in cameras is broken again :

Hi remKa,
I’m unable to reproduce the issue on my end, it seems to work fine here. Could you share an example scene that reproduces it?
Regards
Paride

[neonZorglub]

Hello,

Motion blur doesn't work with displacement, please see attached video and override motion blur in cameras is broken again :

Hi remKa,
I’m unable to reproduce the issue on my end, it seems to work fine here. Could you share an example scene that reproduces it?
Regards
Paride

01.jpg

Hi remKa,
I also couldn't reproduce the issue.
Check with the attached scene, maybe use a png instead of a tif for the displacement texture ?.. If you can send us a sample, we'll have a look.

MB_with_displacement05_mx24.zip

(538.21 KiB) Downloaded 1 time

For the override motion blur, in fact it works. The issue comes from the default values for Shutter time and Subframe end, that are incorrectly set to 0.5 and 1.0 when creating a new camera. Change those to around 100.0, and it should work. Those incorrect default values will be fixed in the next release.
Thanks

[remKa]

Hello,

No luck with a .png neither, please find my scene here : https://www.swisstransfer.com/d/db876f86-3fad-4b04-9fbc-a019f699f85e

[paride4331]

Hi remKa,
Try increasing the motion blur duration; it should work
Regards
Paride