Page 4 of 7
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Thu Feb 26, 2026 11:56 am
by neonZorglub
Hi Elvissuperstar007,
Thank you for the scene.
I tried repeating viewport rendering, closing viewport, changing some parameters, re-opening viewport, many times, but could not reproduce the crash..
What kind of editing do you usually do ? (eg material parameters ?, camera ? render settings parameters, ... ? )
I'll try to test more in a similar way as your workflow, and maybe make a script to keep those tests running for several hours..
Also, if you have several GPUs, could you try to work with only 1 for a day, and switch to another GPU on the next day ? (just in case that's a crash related to gpu / driver ..)
Thanks
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Thu Feb 26, 2026 1:57 pm
by Elvissuperstar007
Well, it didn't crash right away. I had to work with the real-time material settings, and it would work fine for 20-30 minutes and then close 3ds Max. This didn't happen with the Octane 2025 version.
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Thu Feb 26, 2026 4:36 pm
by paride4331
Hi coilbook,
It should be something like this, more or less, and then it can be adjusted as needed.
Regards
Paride
- 01ge.zip
- (255.36 KiB) Downloaded 21 times
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Thu Feb 26, 2026 4:51 pm
by ramone163
Starting with the 2025 versions, there is a problem with VDB files. The parameters, viewport and timeline have started lagging. In version 2024, everything works smoothly.
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Fri Feb 27, 2026 3:58 pm
by paride4331
ramone163 wrote: Thu Feb 26, 2026 4:51 pm
Starting with the 2025 versions, there is a problem with VDB files. The parameters, viewport and timeline have started lagging. In version 2024, everything works smoothly.
Hi ramone163,
I’ve run several tests with versions from v2024 onward, and it seems there’s an issue with reading and writing .vdb cache files in v2026. I’m submitting my report to the development team.
Regards
Paride
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Fri Feb 27, 2026 5:59 pm
by coilbook
paride4331 wrote: Thu Feb 26, 2026 4:36 pm
Hi coilbook,
It should be something like this, more or less, and then it can be adjusted as needed.
Regards
Paride
00.jpg
01ge.zip
Thank you!
Anyway to get better vram usage. Parallels samples from 16 to 32 use like 2 gb of vram, AI light uses like 3-4 gb of vram. That's a lot of wasted vram. So half of 12 GB of precious vram gets used by octane for technical purposes only.
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Fri Feb 27, 2026 7:09 pm
by ramone163
paride4331 wrote: Fri Feb 27, 2026 3:58 pm
ramone163 wrote: Thu Feb 26, 2026 4:51 pm
Starting with the 2025 versions, there is a problem with VDB files. The parameters, viewport and timeline have started lagging. In version 2024, everything works smoothly.
Hi ramone163,
I’ve run several tests with versions from v2024 onward, and it seems there’s an issue with reading and writing .vdb cache files in v2026. I’m submitting my report to the development team.
Regards
Paride
Thank you
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Mon Mar 02, 2026 8:47 am
by Elvissuperstar007
Try rendering for about 10 minutes while changing materials on the model in real time. All materials are present in the Material Editor.
Close the Octane Interactive viewport.
Hide the group of light sources and enable one light that is currently turned off.
Go to the 3ds Max Environment settings and change the light color from gray to pure white.
Try to start the interactive viewport again — 3ds Max will close without any error message.
This happens every time. At the same time, 3ds Max does not crash if I render while changing materials. However, as soon as I change the environment, disable the main light, or enable a previously disabled one, it crashes immediately — but only when launching the Octane interactive viewport. If I restart 3ds Max and adjust these parameters before rendering, everything works fine and it renders normally.
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Tue Mar 03, 2026 12:09 pm
by paride4331
Elvissuperstar007 wrote: Mon Mar 02, 2026 8:47 am
Try rendering for about 10 minutes while changing materials on the model in real time. All materials are present in the Material Editor.
Close the Octane Interactive viewport.
Hide the group of light sources and enable one light that is currently turned off.
Go to the 3ds Max Environment settings and change the light color from gray to pure white.
Try to start the interactive viewport again — 3ds Max will close without any error message.
This happens every time. At the same time, 3ds Max does not crash if I render while changing materials. However, as soon as I change the environment, disable the main light, or enable a previously disabled one, it crashes immediately — but only when launching the Octane interactive viewport. If I restart 3ds Max and adjust these parameters before rendering, everything works fine and it renders normally.
Hi Elvissuperstar007,
I can’t reproduce the issue on my side. Maybe I’m missing something, or there’s a specific step I’m not taking. Could you clarify the exact sequence of actions?
Regards
Paride
- test.mp4
- (12.39 MiB) Downloaded 23 times
Re: OctaneRender® 2026.2 for 3ds max® v26.5
Posted: Tue Mar 03, 2026 12:27 pm
by paride4331
coilbook wrote: Fri Feb 27, 2026 5:59 pm
paride4331 wrote: Thu Feb 26, 2026 4:36 pm
Hi coilbook,
It should be something like this, more or less, and then it can be adjusted as needed.
Regards
Paride
00.jpg
01ge.zip
Thank you!
Anyway to get better vram usage. Parallels samples from 16 to 32 use like 2 gb of vram, AI light uses like 3-4 gb of vram. That's a lot of wasted vram. So half of 12 GB of precious vram gets used by octane for technical purposes only.
Hi coilbook,
Could you provide some information about the type and number of light sources in the scene?
Regards
Paride