Cinema4D version 2020.1.3-R2 (Obsolete stable) 24.06.2020

[divasoft]

Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

It seems to render fine for me, even on an old GTX 1070 with 8 gigs of VRAM. Are you working with some tight memory limitations? The C4D UI does get a little sluggish with that many particles, but the rendering doesn't seem to be a problem. If you turn down you Parallel Samples you can get a bit more headroom, memory wise, with a small hit on render speed. Here's frame 20 of your example scene:

Try to run the render several times, changing something in the scene, try to render the animation and you will understand what I'm talking about. Octane can start once or twice, but with a full-fledged workflow with similar scenes, I have to restart cinema every 5 minutes.

[jayroth2020]

Have you reported this using help at otoy dot com? if not, please do and will get it into the system for formal testing and try and sort it out for you.

[frankmci]

Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

It seems to render fine for me, even on an old GTX 1070 with 8 gigs of VRAM. Are you working with some tight memory limitations? The C4D UI does get a little sluggish with that many particles, but the rendering doesn't seem to be a problem. If you turn down you Parallel Samples you can get a bit more headroom, memory wise, with a small hit on render speed. Here's frame 20 of your example scene:

Try to run the render several times, changing something in the scene, try to render the animation and you will understand what I'm talking about. Octane can start once or twice, but with a full-fledged workflow with similar scenes, I have to restart cinema every 5 minutes.

I just spent 15 or 20 minutes goofing off with your scene, adding elements, merging it with other projects, trying different kernels and render settings, etc. and while it's definitely very sluggish, and it is clearly stressing the system, it never crashed. I also rendered out the full sequence with some extra geegaws with no problem. Perhaps there's a weak link in your chain somewhere, some questionable error correcting RAM? A component overheating? I notice that C4D is using 40+ gigs of RAM while rendering this pretty simple scene, so there's an awful lot of number crunching going on here. I'm certainly not an Otoy tech, but it doesn't seem to be specifically an Octane problem, at least based on the example you have provided.

[divasoft]

I just spent 15 or 20 minutes goofing off with your scene, adding elements, merging it with other projects, trying different kernels and render settings, etc. and while it's definitely very sluggish, and it is clearly stressing the system, it never crashed. I also rendered out the full sequence with some extra geegaws with no problem. Perhaps there's a weak link in your chain somewhere, some questionable error correcting RAM? A component overheating? I notice that C4D is using 40+ gigs of RAM while rendering this pretty simple scene, so there's an awful lot of number crunching going on here. I'm certainly not an Otoy tech, but it doesn't seem to be specifically an Octane problem, at least based on the example you have provided.

I have 64 gigabytes of RAM and my video cards do not overheat. I don’t understand why I should sit and wonder what the problem is, getting excuses from the developers instead of real help. Look, Ahmet did not even try to find out what the problem is.
In addition, I want to say that I get the same errors on completely different systems. This is about a dozen different configurations at my work and home.

[divasoft]

Have you reported this using help at otoy dot com? if not, please do and will get it into the system for formal testing and try and sort it out for you.

Tell me why you need to write there about crush, what I wrote here is not enough? I thought you have internal communications between developers, as the guys from the redshift team have.

[frankmci]

I just spent 15 or 20 minutes goofing off with your scene, adding elements, merging it with other projects, trying different kernels and render settings, etc. and while it's definitely very sluggish, and it is clearly stressing the system, it never crashed. I also rendered out the full sequence with some extra geegaws with no problem. Perhaps there's a weak link in your chain somewhere, some questionable error correcting RAM? A component overheating? I notice that C4D is using 40+ gigs of RAM while rendering this pretty simple scene, so there's an awful lot of number crunching going on here. I'm certainly not an Otoy tech, but it doesn't seem to be specifically an Octane problem, at least based on the example you have provided.

I have 64 gigabytes of RAM and my video cards do not overheat. I don’t understand why I should sit and wonder what the problem is, getting excuses from the developers instead of real help. Look, Ahmet did not even try to find out what the problem is.
In addition, I want to say that I get the same errors on completely different systems. This is about a dozen different configurations at my work and home.

Well, I was trying to be helpful, but that clearly was a mistake. Good luck.

[divasoft]

My previous results were obtained with version 2020.1. And on the 13th frame and all the frames after it, the octane constantly fails. I updated to the last version and the octane was able to work a little longer. now crash occurs on frame 19. Ahmet, can you say something useful or help something?

[aoktar]

My previous results were obtained with version 2020.1. And on the 13th frame and all the frames after it, the octane constantly fails. I updated to the last version and the octane was able to work a little longer. now crash occurs on frame 19. Ahmet, can you say something useful or help something?

Probably about RTX core. As I said your problems are not about my side. So what can you do?
You can directly ask to support email for contributing the whole team or send me your scene to me.
But what can I do if it's not happening on me and a core issue? Just pass it to core team and pray for that they can check and reproduce the issue. For my opinions there's some limitations or problems in core for a lot of scattered geometries.

[jayroth2020]

Thank you for submitting your report, Divasoft. As you know, the file is in the testing suite. We will keep you informed with our results.

Thank you!

[jayroth2020]

As Ahmet mentioned, disabling RTX allowed this scene to render successfully. The dev team will review the results, but for situations like this in the future, try disabling the RTX option.