Hello,
I just updated to Cinema 4D 2023.2, so not sure if this is the issue or not.
Cinema - 2023.2
Octane - 2022.1-R6
I have been using the same scene with success and without issues for the past month, and have never ran into this issue. Everything looks fine in the picture viewer, but it fails to save the file and C4D crashes. In the picture viewer, when the crash happens there is the following copy is in the bottom. Displaying Denoised reflection indirect pass 1/2.
I have copied the whole scene to a new file, and did not have success with that either.
Attached is a screen grab of the console and Octane Log, Octane crash report, simplified scene with the same crash on the denoising.
Failure to save file & crash when exporting to PV
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
- Attachments
-
- Display_OT3B.zip
- (1.37 MiB) Downloaded 125 times
-
- c4doctanelog.txt
- (4.11 KiB) Downloaded 98 times
Last edited by twik25 on Thu Mar 30, 2023 7:04 pm, edited 1 time in total.
Okay, after some more tests... here is what I have found. It is isolated to Denoising, when rendering the file to picture viewer. This crash only happens in 2023.2.
2023.2
All GPUs - Crash
Single GPU - Works on all 4
Any combination of GPUS (1&2, 1&3, 1&4, ect.) - Crash
2023.1
All GPUs - Works
R26
All GPUs - Works
R21.207
All GPUs - Works
2023.2
All GPUs - Crash
Single GPU - Works on all 4
Any combination of GPUS (1&2, 1&3, 1&4, ect.) - Crash
2023.1
All GPUs - Works
R26
All GPUs - Works
R21.207
All GPUs - Works
Hi,
from the log, both c4doctane Win 10 and Nvidia driver are not updated.
Now we are at 2022.1-R10.
You also have a mix of Quadro and GeForce GPUs
Are you using Quadro or GeForce drivers?
ciao,
Beppe
from the log, both c4doctane Win 10 and Nvidia driver are not updated.
Now we are at 2022.1-R10.
You also have a mix of Quadro and GeForce GPUs

Are you using Quadro or GeForce drivers?
ciao,
Beppe
Hi Beppe,
Thanks for responding. I have stayed on older drivers because:
1. They have been working without issue.
2. I do not have the issues while running Adobe software that have been reported.
3. The requirements are "NVIDIA Studio driver with version at least 456.38 on Windows" which I have.
The 1080s are running Geforce drivers, and the A5000's are running Quadro drivers. Again, working fine without issues.
So to be crystal clear, I currently have Cinema 4D R21, R26, R2023.1, and R2023.2 on my machine. With C4D 2023.2 - Octane crashes during the file saving process when using denoising with more than 1 GPU activated (Quadro or Geforce - doesn't matter).
And you are suggesting that it is a GPU mixmatch, GPU driver or windows driver error instead of a just released software update (Cinema 4D) running a plugin that was not specifically updated along with it?
I will install 2022.1-R10 on the C4D 2023.2 and see if that fixes it.
Thanks,
Tim
Thanks for responding. I have stayed on older drivers because:
1. They have been working without issue.
2. I do not have the issues while running Adobe software that have been reported.
3. The requirements are "NVIDIA Studio driver with version at least 456.38 on Windows" which I have.
The 1080s are running Geforce drivers, and the A5000's are running Quadro drivers. Again, working fine without issues.
So to be crystal clear, I currently have Cinema 4D R21, R26, R2023.1, and R2023.2 on my machine. With C4D 2023.2 - Octane crashes during the file saving process when using denoising with more than 1 GPU activated (Quadro or Geforce - doesn't matter).
And you are suggesting that it is a GPU mixmatch, GPU driver or windows driver error instead of a just released software update (Cinema 4D) running a plugin that was not specifically updated along with it?
I will install 2022.1-R10 on the C4D 2023.2 and see if that fixes it.
Thanks,
Tim
Okay, after doing a lot of testing... This appears to only happen when "Show Passes" is enabled. With this unchecked, it renders fine but it doesn't save the denoised beauty pass apparently (It does save the other denoised passes). Please see attached video. After I try canceling the render. C4D locks up and is unusable, and I have to end task in the Windows Task Manager.
I saw Ahmet uploaded Cinema4D version 2022.1.1. I tried this version and the issue was still there.
Please let me know if I can be of further assistance troubleshooting this issue. As of now, I am back on C4D 2023.1.
Thanks,
Tim
I saw Ahmet uploaded Cinema4D version 2022.1.1. I tried this version and the issue was still there.
Please let me know if I can be of further assistance troubleshooting this issue. As of now, I am back on C4D 2023.1.
Thanks,
Tim
- Attachments
-
- jXq8gymSON.mp4
- (16.05 MiB) Downloaded 2431 times
Also crashing here. The image renders in picture viewer, denoise runs then crashes. Often when this happens it is accompanied by the system graphics locking up for 10 seconds (cant move the mouse) and then 2500x
"CUDA error (702) on device 0: the launch timed out and was terminated
-> failed to deallocate device memory"
Rendering to render queue works fine
geforce 3090
driver 531.41 studio
c4d r26.107
octane 2022.1.1 R2
Will update to R3 shortly but dont see any denoiser fixes in release notes
"CUDA error (702) on device 0: the launch timed out and was terminated
-> failed to deallocate device memory"
Rendering to render queue works fine
geforce 3090
driver 531.41 studio
c4d r26.107
octane 2022.1.1 R2
Will update to R3 shortly but dont see any denoiser fixes in release notes
- kasperrubin
- Posts: 5
- Joined: Fri May 18, 2018 3:56 am
If anyone still has this issue I found that you also must disable Multilayer file, then you get out the denoised beauty.