Hi there. Rendering does not finish. The image is basically done, then it says "Displaying Pass" in the status bar on the bottom. And nothing ever happens. Have to quit C4D then.
Running Lastest build of C4D and Octane.
The same issue was filed earlier today, didn´t see it.
viewtopic.php?f=30&t=81689
Render Stuck at "Displaying Pass"
Moderators: ChrisHekman, aoktar
PM Sent and replied at on your other post. See your "messages".
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- jeremyshin
- Posts: 106
- Joined: Thu May 04, 2017 5:59 pm
What is the resolution of your render? I had a lot of this annoying problem while rendering images from 2K to 4K.
With latest C4D there are something which is causing a bug on our multi processing. I've added a small delay between the processes to avoid it. But it needs to be tested before a release
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Could this be the reason for extremly slow renderings as well? Frames that usually take 10 seconds take up to 2 hours. GPUs are under full load though. Sometimes a restart of the render but most of the times a restart of c4d fixes the problem. I didn't post it in the bug section because I was not able to reproduce it and it occured on several scenes and projects.aoktar wrote:With latest C4D there are something which is causing a bug on our multi processing. I've added a small delay between the processes to avoid it. But it needs to be tested before a release
6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068
Not sure, but there maybe a render error(check Console window for Octane logs) or low VRAM/RAM or having another Octane software is open. I see the behavior when standalone is rendering while C4D plugin is running.KeeWe wrote:Could this be the reason for extremly slow renderings as well? Frames that usually take 10 seconds take up to 2 hours. GPUs are under full load though. Sometimes a restart of the render but most of the times a restart of c4d fixes the problem. I didn't post it in the bug section because I was not able to reproduce it and it occured on several scenes and projects.aoktar wrote:With latest C4D there are something which is causing a bug on our multi processing. I've added a small delay between the processes to avoid it. But it needs to be tested before a release
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Nope, it comes completely out of the blue. Would the error still be logged if the render continues and can be manually aborted? Didn't think of having a look there since in theory the render started and continued... just painfully slow.aoktar wrote:Not sure, but there maybe a render error(check Console window for Octane logs) or low VRAM/RAM or having another Octane software is open. I see the behavior when standalone is rendering while C4D plugin is running.KeeWe wrote:Could this be the reason for extremly slow renderings as well? Frames that usually take 10 seconds take up to 2 hours. GPUs are under full load though. Sometimes a restart of the render but most of the times a restart of c4d fixes the problem. I didn't post it in the bug section because I was not able to reproduce it and it occured on several scenes and projects.aoktar wrote:With latest C4D there are something which is causing a bug on our multi processing. I've added a small delay between the processes to avoid it. But it needs to be tested before a release
VRAM could be an issue but der should be enough ooc memory left.
Anyway, just wanted to share it as an info for you.

6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068