Page 1 of 1

Octane lights invisible in render viewport due to incorrect float values when opening older scenes

Posted: Fri May 08, 2026 2:54 pm
by SeanB3D
Hello!

Lights appear to be the correct size in 3ds Max's viewport, but clicking on an Octane Light ('Geo Type: Disk' in this instance) will reveal both X & Y floats are set to 0.
This wouldn't usually be a big deal but in this case it has caused all lights in those older scenes to be invisible in the render as well.
I also noticed that entering a new value, hitting enter seems to keep the floats at 0 when you click back on them again to check their parameters. Making a new light also seems to have this same issue, so I think the issue goes deeper than just older scenes.

I think this bug was marked as resolved in Octane Plugin for 3ds Max - 2026.1 - 26.3, but it has re-appeared in version 2026.2 - 26.7
The scenes I'm moving from were created in 3ds Max 2024 & Octane 2023.1.3, opening them in 3ds Max 2026.3.2 and 2026.2 - 26.7 should reproduce this issue.
OctaneLights_3dsMax2026_Octane2026.2-26.7.jpg
Everything else in older scenes seems to work great now, with only a few adjustments made, but in order for my team to move across to later versions we would need this resolved!
Thanks in advance!

Re: Octane lights invisible in render viewport due to incorrect float values when opening older scenes

Posted: Mon May 11, 2026 7:52 am
by paride4331
Hi SeanB3D,
Here’s definitely something strange happening with all the Octane lights, the parameters are entered correctly, but once the lights are reselected, they show zero instead of the actual assigned values..
I sent my report to developers.
Regards
Paride

Re: Octane lights invisible in render viewport due to incorrect float values when opening older scenes

Posted: Mon May 11, 2026 2:43 pm
by SeanB3D
Thanks very much!