OTOY Forums

This is the OctaneRender_Studio+_2026_3_for_3dsmax_v26.9 version, without rendering details, polygons, or algorithm processing in the viewport.

Thanks OR team.

Hi Pelana001_1,
I think it's just a matter of perspective and lighting.
Regards
Paride

HI paride4331, thanks for answer, very kind, I'll using the version OctaneRender® 2026.3 for 3ds max® v26.9 and I don't have issues.

neonZorglub wrote: Wed Jul 08, 2026 9:41 pm

coilbook wrote: Wed Jul 08, 2026 5:00 pm This is 2026.4 version

Thanks ! Fixed typo in the post title.

Hi neonZorglub,
Do you know why slaves crash when vram usage is over their vram limit instead of using out of core RAM?

coilbook wrote: Wed Jul 29, 2026 1:20 am

neonZorglub wrote: Wed Jul 08, 2026 9:41 pm

coilbook wrote: Wed Jul 08, 2026 5:00 pm This is 2026.4 version

Thanks ! Fixed typo in the post title.

Hi neonZorglub,
Do you know why slaves crash when vram usage is over their vram limit instead of using out of core RAM?

Hi coilbook,
Did you set the Out-of-Core setting on the node during its setup?
Regards
Paride

The orthographic camera is broken.

The bug does exist after all; it doesn't happen every time, but it shows up in 70% of cases.

Elvissuperstar007 wrote: Mon Aug 03, 2026 5:17 pm The orthographic camera is broken.

Hi Elvissuperstar007,
Thanks. I've submitted my report to the developers. As a temporary workaround, switch to a different 3ds Max viewport and then switch back to the Octane Camera viewport. This causes the render to resume progressing. However, if the Ortho option is turned off and then back on, the issue reappears, and you'll need to repeat the same workaround.
Regards
Paride

paride4331 wrote: Wed Jul 29, 2026 1:31 pm

coilbook wrote: Wed Jul 29, 2026 1:20 am

neonZorglub wrote: Wed Jul 08, 2026 9:41 pm
Thanks ! Fixed typo in the post title.

Hi neonZorglub,
Do you know why slaves crash when vram usage is over their vram limit instead of using out of core RAM?

Hi coilbook,
Did you set the Out-of-Core setting on the node during its setup?
Regards
Paride

Hi Paride, yes I did. 16 gb per slave. Not sure if maybe all mesh cannot fit vram maybe. Most textures are procedural. Thank you.

Hi coilbook,
16 GB o-o-c limit could be the bottleneck. If the scene exceeds the available VRAM by more than those 16 GB, Octane may still run out of memory and crash instead of using more system RAM. Also, some data may still need to fit in VRAM, so large or complex meshes, displacement, subdivision, volumes, hair, etc. could be the actual cause. Since most textures are procedural, I’d look at the geometry and check the VRAM/o-o-c usage in the Octane log right before the crash.
Regards
Paride