Cinema 4D version 4.00 (obselete stable)

[atilak]

Hi Aoktar, I have to report a critical lowering of performance during work. The preview is extremely slow, it is as if it were jerky, even if the priority is set to Low. The scene that with the 3.8 version was very fast, with this version tends to slow down to the point of being unmanageable. The strange thing is that the GPU does not heat up at all, while the CPU seems to have excesses of overheating. Regarding rendering is certainly faster, about 2.5 times with my rtx 2080, I noticed that the first frame that is rendered takes a lot of time to be processed, the subsequent frames are very fast. (In the current scene, about 4min for the first frame and 12 seconds for the following frames) Unfortunately the project management is critical on my pc. I was forced to go back to 3.8 so as not to interrupt the work. Occasionally I also got sudden crashes but without having any special warnings in the log. Could it be due to a lack of support for the RTX 2080?
Thank's for your job.

win 10
i7 6700 4.00 GHz
32GB RAM
RTX 2080ti 11gb

Could you share a scene with us about this problem?

Yes, i upload the project and send you the link to private message. I tried the V4 on my laptop (mounts a 1060 gtx) and despite the scene is not optimized I can manage it better than with the desktop PC and the RTX 2080. I suppose it is the fault of some setup or incompatibility with RTX

[feathers632]

Now getting a lot of this: Started logging on 03.12.18 11:59:57

OctaneRender 4.00 RC7 (4000017)

CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to download symbol(stats data)
device 0: direct light kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to unload module
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to create link
device 0: failed to create OSL compile context:

device 0: failed to compile module 1
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to load symbol data to the device(kernel data)
device 0: picking failed

Have updated to a newer Nvidia driver 417.01 but the issue was present with previous driver. Windies 10.

Issue began last night when adding either more complexity to model or adding a chromatic aberration sphere to a camera. I have stopped my GPU overclock and will do further testing.

[isotope]

First, this is great and the AI denoiser is really amazing so thank you!

I am however having an issue that I did not encounter in V3.

I'm running Octane 4 Stable for Cinema 4D R20 on Windows 10. I've noticed since using version 4, when rendering using the Render Queue Cinema 4D will gradually use up all the system memory and eventually crash. This takes usually 4-8 hours for all memory to be allocated to Cinema 4D, depending on the project.

I am using the same scenes as I was previously with v3 where this was not an issue. Changing graphics card drivers doesn't resolve the issue either, so I think it's constrained to v4.

The only thing I can think of is perhaps Octane is having to convert v3 materials to v4 every frame, and that is what's causing this issue. Can you tell me if I can / need to convert a v3 Octane material to a v4 material, or if materials should just work normally without any extra steps?

Has anyone else encountered something similar?

Hardware:
1x RTX2080Ti
2xGTX 980Ti
64GB RAM

[aoktar]

First, this is great and the AI denoiser is really amazing so thank you!

I am however having an issue that I did not encounter in V3.

I'm running Octane 4 Stable for Cinema 4D R20 on Windows 10. I've noticed since using version 4, when rendering using the Render Queue Cinema 4D will gradually use up all the system memory and eventually crash. This takes usually 4-8 hours for all memory to be allocated to Cinema 4D, depending on the project.

I am using the same scenes as I was previously with v3 where this was not an issue. Changing graphics card drivers doesn't resolve the issue either, so I think it's constrained to v4.

The only thing I can think of is perhaps Octane is having to convert v3 materials to v4 every frame, and that is what's causing this issue. Can you tell me if I can / need to convert a v3 Octane material to a v4 material, or if materials should just work normally without any extra steps?

Has anyone else encountered something similar?

Hardware:
1x RTX2080Ti
2xGTX 980Ti
64GB RAM

There's not any conversions V3 to v4. Do you mean ram gets full after some rendering? After how much frames and what's resolution.? How many scenes in render queue?

[isotope]

First, this is great and the AI denoiser is really amazing so thank you!

I am however having an issue that I did not encounter in V3.

I'm running Octane 4 Stable for Cinema 4D R20 on Windows 10. I've noticed since using version 4, when rendering using the Render Queue Cinema 4D will gradually use up all the system memory and eventually crash. This takes usually 4-8 hours for all memory to be allocated to Cinema 4D, depending on the project.

I am using the same scenes as I was previously with v3 where this was not an issue. Changing graphics card drivers doesn't resolve the issue either, so I think it's constrained to v4.

The only thing I can think of is perhaps Octane is having to convert v3 materials to v4 every frame, and that is what's causing this issue. Can you tell me if I can / need to convert a v3 Octane material to a v4 material, or if materials should just work normally without any extra steps?

Has anyone else encountered something similar?

Hardware:
1x RTX2080Ti
2xGTX 980Ti
64GB RAM

There's not any conversions V3 to v4. Do you mean ram gets full after some rendering? After how much frames and what's resolution.? How many scenes in render queue?

Thanks for the reply Aoktar.

Yes the system memory gets full and then Cinema 4D will not respond. The GPUs will then not be used/ the render will stop. Happens after around 300-400 frames depending on the scene. On application quit, sometimes the memory will be released, but sometimes a restart of the system is required.

About 20 scenes in the queue and each scene is around 400-600 frames - so sometimes the render will finish a scene but crash later in the next scene. Each scene is set to 4096x4096px with a spherical camera and stereo enabled. All scenes have out-of-core enabled (4Gb and 512Mb).

Thanks

[aoktar]

Thanks for the reply Aoktar.

Yes the system memory gets full and then Cinema 4D will not respond. The GPUs will then not be used/ the render will stop. Happens after around 300-400 frames depending on the scene. On application quit, sometimes the memory will be released, but sometimes a restart of the system is required.

About 20 scenes in the queue and each scene is around 400-600 frames - so sometimes the render will finish a scene but crash later in the next scene. Each scene is set to 4096x4096px with a spherical camera and stereo enabled. All scenes have out-of-core enabled (4Gb and 512Mb).

Thanks

Understand! Do yo have similar problem without render queue? Can I get a sample scene to try?

[isotope]

Thanks for the reply Aoktar.

Yes the system memory gets full and then Cinema 4D will not respond. The GPUs will then not be used/ the render will stop. Happens after around 300-400 frames depending on the scene. On application quit, sometimes the memory will be released, but sometimes a restart of the system is required.

About 20 scenes in the queue and each scene is around 400-600 frames - so sometimes the render will finish a scene but crash later in the next scene. Each scene is set to 4096x4096px with a spherical camera and stereo enabled. All scenes have out-of-core enabled (4Gb and 512Mb).

Thanks

Understand! Do yo have similar problem without render queue? Can I get a sample scene to try?

I haven't tried it without the render queue and probably won't get to test that for a couple of days. I'm afraid I can't send any scenes as client wouldn't allow. I'll come back to you with picture viewer results. Thanks!

[Timelinedenmark]

Anyone else have problems with Network Render in Octane 4?
The render slave status is red in the PV, and it says "Data:0/0 Mb.".
No errors reported by the slaves.

[cirasa]

hi Aoktar,

last week we have upgraded Octane to V4 and since day one
we have encountered the same issue with render queue.

the RAM gets full and Cinema 4D not respond.
The scenes aren't particulary heavy so the first was rendered without problems,
but with the progression of render queue the system-RAM go full and Cinema4D can't refresh that for next files,
so the rendering will stop.

attached the screenshot of render queue.

thanks in advance for any usefull suggestion.

[aoktar]

hi Aoktar,

last week we have upgraded Octane to V4 and since day one
we have encountered the same issue with render queue.

the RAM gets full and Cinema 4D not respond.
The scenes aren't particulary heavy so the first was rendered without problems,
but with the progression of render queue the system-RAM go full and Cinema4D can't refresh that for next files,
so the rendering will stop.

attached the screenshot of render queue.

thanks in advance for any usefull suggestion.

Do you have animated sequence, octane objects as scatter or volume, etc?