Hard Freeze / Crash on "Updating" & "Creating Geometry" with Heavy CAD Scene - C4D 2026 - Ryzen 9950X + Dual RTX 4090

[tegatwork]

EDIT : The problem seems to be solved, here is my process.
- I tried to erase all materials and it was working.
- So I brought them back and tried to remove the "round corner" option from all of them, still working
- Added round corner on my principal materials : still working
- added more : crash is back

So, it seems there are some limits to this awesome option (I'm using it a lot...)... Do you think it's a bug or a real technical limitation?

Hi everyone,

I am experiencing a critical, persistent issue with Octane in Cinema 4D that completely blocks my workflow. I am working on a high-end workstation but the engine either completely freezes my system or crashes to desktop upon rendering.

System Specs:

OS: Windows 11 (Latest updates)
Cinema 4D Version: 2026.2.0
Octane Version: OctaneRender For Cinema 4D 2026.3
CPU: AMD Ryzen 9 9950X (32 threads)
GPU: 2x NVIDIA RTX 4090
Drivers: NVIDIA Studio Driver version 596.36

The Problem:
I am working on a large mechanical scene imported from CAD (crane model). The hierarchy currently contains 10,784 visible objects (21,806 total objects), sitting at around 7.5 million visible polygons (10.9 million total). This count is expected to grow as I add the environment and more details.

The issue behaves completely randomly. Sometimes I randomly manage to get a single frame out successfully. But as soon as I make any modification in the scene (moving an object, editing geometry, tweaking the setup) and try to fire up the Live Viewer again or render to the Picture Viewer, it completely crashes or freezes. One of two things happens:

1. Indefinite Freeze: Cinema 4D hangs forever on "Updating" or "Creating Geometry". Looking at Windows Task Manager, C4D.exe drops down to 0% CPU usage. The execution thread completely dies in silence.
2. Crash to Desktop: C4D crashes suddenly. The BugReport always points to an issue with the Intel Denoiser module (`oidn`) trying to initialize during the `isGreyscalePass` evaluation.

Here is the call stack from my latest crash report:

```text
octane.dll: Octane::isGreyscalePass + 0x2458a0
octane.dll: Octane::isGreyscalePass + 0x2480a3
octane.dll: Octane::isGreyscalePass + 0x242be6
octane.dll: Octane::isGreyscalePass + 0xcc6e52
octane.dll: Octane::isGreyscalePass + 0xc9dcfb
octane.dll: Octane::isGreyscalePass + 0xcae380
octane.dll: Octane::isGreyscalePass + 0xcabc8a
octane.dll: Octane::isGreyscalePass + 0xcafff7
octane.dll: oidn_init_module_device_cuda_v20303 + 0x784107
octane.dll: oidn_init_module_device_cuda_v20303 + 0x7833f3
octane.dll: oidn_init_module_device_cuda_v20303 + 0x7762a4

```

Everything we have already tried:

Drivers: Made a full clean DDU uninstall and switched entirely to official NVIDIA Studio Drivers (v596.36).
TDR Registry Fix: Manually added and verified `TdrLevel = 3` and increased `TdrDelay` up to `60` (60 seconds) in `Registry\...\GraphicsDrivers`. It didn't prevent the crash or the 0% CPU freeze on the second render invocation.
Scene Isolation: Copied and pasted the geometry into a 100% fresh C4D project file to eliminate hidden scene corruption.
Settings: Disabled Motion Blur entirely, turned off native C4D shader baking, cleared Octane Texture Cache, and enabled Out-of-Core (OOC) memory.
Denoiser: Tried turning off the Denoiser in the Camera Tag and the Live Viewer, but the crash still triggers randomly on scene updates.

*Note: Exporting to ORBX / Standalone or collapsing everything destructively is not a viable option for me, as this asset is actively being built, rigged, and modified live inside Cinema 4D.*

Given the hardware layout (Ryzen 9950X + Dual 4090), it feels like a deadlock on the main thread during the bridge translation or a CUDA memory management crash when a live scene modification is parsed.

Is this a known issue with the OIDN library or high object counts in Octane 2026.3? Any help or insights from the team would be deeply appreciated.

Thanks in advance.

PS : @beppe you already tried to help me with an absolutely similar problem a few years ago (april 2023)... Upgraded rig, same problem....

[bepeg4d]

Hi,

Please write to help at otoy dot com asking for Beppe.

I need to see some logs and investigate more deeply.

ciao,
Beppe