Update for Plugin 2023.1.3 and it's compatibility with the new Nvidia Studio Driver 560.81.

Result = Absolutely nothing. Stick with 552.22.

Unfortunately, Nvidia Studio 560.70 version doesn't solve the stability issue, please stay with 552.22!

ciao,
Beppe

Is OTOY contacted Nvidia about this issue ?
I ask because for Davinci Resolve 19.x and some nice AI features it requires newer drivers than 552.x so it's tricky to install ...

New v560.70 Studio Driver gives me the same issues.

Actually all drivers after 552.22 are causing C4d stability issues for me. Octane works fine with 552.22 but I'm getting issues with other software because of not updating the driver. (X-particles, After Effects)

Is anyone able to run Octane (2023.1.3 R3,4) C4d 2024.4, with a Studio Driver newer ...

All fixed,

I didn't realize that in the C4d viewport if you have "geometry only" selected under "Filter" it prevent LV updates.

Thanks

All of a sudden, in this particular scene none of the three cameras updates in the LV. All of the "update" switches are activated, however when I switch to a new clean scene (same LV) the new cameras all update fine.

Windows
3090ti
C4d 2024.4.0
Octane 2023.1 R4

Thanks

I'm working in the new Xparticles now and Im having more difficulty than usual with fire and smoke. I'm not entirely sure if its my grasp of the new VDB in 2020 Oct. or the new Explosia build from Xpart. I'm going to keep at it, if I have any revelations on 2020 octane with Xparticles 844 i'll share ...

If you stop the render every 30 frames or so, you can limp through it. Worst workaround ever.

This specific issue is pushing me away from Octane.

Please help!

I've seen this issue come up a few times in the C4d forum, but no solutions.

R20, V4.1-R2, Xparticles 4
Nvidia Quadro p5000 x 2 (16gb VRAM)
Windows 10 - Thread-ripper

Im having the exact same issue with motion blur and consistently increasing render times. Once you restart, it ...

This keeps me up an night, did you ever fine a solution?