OTOY Forums

sorry! Still have problems!

Now without ORBX but normal Objects.
After a few frames rendering stops everytime with error: Cannot get the Render Result of Pass ...
Sometimes its a Light-Pass, sometimes AO-Pass and so on

What can I do?

thanks MIke

That's really odd.
Could you please send me your scene? Delete any mesh, I just care about your exact scene settings.
Thanks!

well I killed every Blender and Octane progs and folders and installed everything new.
Hope it will work now!

regards
Mike

sorry, but I'm really p......!
Installed everything new and still Octaneserver stopps after 3 or 5 frames.
Starting Server 31.6 first then Octane 31.6
Tried with newest NVidia Drivers with no luck - so back to 32.0.15.9144

I have to render soon 6 Animations in 4K with 300 Frames each.
It will take years if I have to restart rendering every 3 frames ...

What the fuck can I do ?

Again, I'd like to take a look at your scene settings.
Just delete all of your objects and textures and send me the scene.
Of course being able to take a look at the whole scene would be better. You shouldn't be worried about NDAs, since we only use it for debug and sharing it with me would be absolutely "safe".

Hi Lino,

thanks for taking a look again!
Here is the blender scene without Product (about 180MB with)
Working with Win11, Octane Addon 31.6 and Server 31.6, 2 x 4090 with NVidia 5.9144
Blender Addons: Meshmashine, BoxCutter, Hardops Boltron, Lootools and Octane of course

Even after PC-reboot every Rendering stops after 3 or 5 frames with error: "Cannot connect to Octane Server: localhost 50051"
When I then look at the taskbar the Server is no more present

Nobody else having same problem? Just me?
Hope you get some important insight from that file

thanks
Mike

Thanks for sharing the scene, I really appreciate it.

Quick question: does this stripped version of the scene also produce the crash on your side, or does it render correctly?

I tested it here and was able to render the full sequence without any issues. I also tried adding some geometry and reusing one of the materials (KSB_Metall), and everything rendered correctly.

This suggests that the problem is not related to the scene itself or to the general render settings.

Also, I’m not aware of other users reporting similar issues, and I’m personally using the same Octane version on complex scenes without any problems.

Given that the Octane Server process disappears from the taskbar, this points more towards a local/system-specific issue (e.g. drivers, GPU stability, memory, or a specific asset/setup in the original scene).

Most likely, the issue is tied to something that is not present in the stripped version of the scene (specific assets, textures, geometry, or a particular setup).

If sharing the full scene is not possible due to NDA (which I completely understand), a possible alternative could be to:

• progressively reintroduce elements into the scene until the issue appears — that’s what I would do

• or try to isolate the problematic asset/material/setup

This way we might be able to narrow it down without exposing sensitive data.

Of course, having access to the full scene would make it much easier to identify the exact cause of the crash. It would only be used strictly for debugging purposes to help resolve the issue, and not stored or shared in any way.

Let me know if you’re able to identify any specific element that triggers the issue.

Hi Lino,

thanks much for your investigation!

I see, that it happens also with total different scenes and its always
the case, that the Octane Server suddenly stopps and dissapears.

So the question is, what causes Octane Server to crash every few seconds/minutes
and is there maybe a workaround to get this app stable?
I never had similar problems with C4D Octane.

I have a bunch of programs installed, so difficult to identify incompatibility with other software.
Which version of NVidia driver are you using?
Maybe I start here.

regards
Mike

Hi Mike,

If you’re able to reproduce the issue with a simpler scene that you can share, I’d be happy to test it on my side — that would make it much easier to verify whether it behaves differently here.

If the issue only occurs on your system (even with different scenes), we can reasonably rule out scene-related causes. The fact that the Octane Server process disappears suggests it’s crashing at system/driver level.

I’m currently using NVIDIA Studio drivers 595.79 and everything is stable on my side, so I would definitely start from there.

A few focused tests I would suggest:

1. Switch to Studio drivers (clean install)
You're on 5.9144 — I would strongly recommend moving to a recent Studio driver (e.g. 595.79) and doing a clean install.

2. Run with a single GPU
Since you're on 2×4090, disable one GPU and test again.
If the crash disappears, that’s a strong indicator of a multi-GPU / power / driver-related issue.

3. Check Windows Event Viewer right after a crash
Look for errors related to:

• nvlddmkm

• CUDA / GPU resets

• application crash logs

This can often tell exactly what’s failing.

4. Test with Octane Standalone (via ORBX export)
If possible, export the scene as an ORBX and try rendering it in Octane Standalone.

This helps isolate whether the issue is coming from:

• Blender integration

• or the Octane Server / system itself

At this point the issue is clearly external to the scene — something is killing the Octane Server process.

Let me know what happens with:

• Studio drivers

• single GPU test

• ORBX / Standalone test

These should already narrow it down significantly.

Hi LIno,

thanks very much for your help!

First of all: its rendering now more than 20 frames without interruption and it looks good so far!

I tried the latest NVidia (the 595.79 you mentioned) bevor, but only within the NVidia Setup which did not work.

I now did a clean install with DDU in safe mode and installed 595.79 again.
Then I disabled 1 GPU in Blender Prefs and tried rendering and OctanServer did not close for more than 10 frames.
Then I activated the second GPU again and its still rendering ...

For now it seams, that actually a conflict with old NVidia leftovers was the problem although all
other installed programs ran without problems the entire time.

So fingers crossed! I'll report when all renders done

Thanks again!
Mike