Cinema4D version 2022.1.1-R6 (Obsolete stable) 08.07.2023

[aoktar]

It will either crash while you're clicking around on the timeline, or selecting a different gradient in the octane material node, or when rendering to picture viewer or in the render queue (it never renders more than 1 frame before crashing)

To add a data point, I was not able to crash the scene by manipulating anything in the UI, and the live viewer worked fine, however I did find that it would freeze after batch rendering a single frame, regardless of how I messed with the render settings our output. Here is the log.

I noticed that sometimes a File Explorer window would also freeze at the same time (but not all File Explorer windows), so it may be a higher order crash involving the video driver or some kind of VRAM corruption.

This is on Windows 11, C4d 2023.1.3, Octane 2022.1.1_R2, NVIDIA RTX4090, Studio Driver 31.0.15.2802

I advice to use latest C4D(2023.2) and latest driver. Older driver was causing interesting stability issues on me for example.

[frankmci]

I advice to use latest C4D(2023.2) and latest driver. Older driver was causing interesting stability issues on me for example.

Thanks, Ahmet. I was just trying to be helpful with some more info, but I also hadn't realized C4D 2023.2 was out. I'm setting up a new machine as I type, so I'll update everything and give it another shot.

[Tim0042]

Hi everyone! I'm currently struggling a bit with a motion blur issue, in connection with xParticles and its OpenVDB Mesher. This might be a bug - or I might be missing something? Some of the vertices seem to suffer some odd displacement instead of getting blurred.

The octane tag on the mesher is set to Vertex speed and the x, y and z vertex maps generated by xparticles are plugged in. The particles are cached but the mesher itself is not (to make sure velocity info is generated on the fly and is available).

I'm currently on C4D 2023.2.0, Octane 2022.1.1-R2, xParticles 1492 and NVIDIA Studio Driver 531.41 - so these should all be up to date. I'm encountering the same issue when rolling Octane back to 2021.1.6-R7. I haven't tested older versions of xParticles and C4D, though I do remember it working without issue at some point in the past with the method described above ("at some point" is not helpful, I know, sry!)

I've attached my project file (it didn't let me upload a c4d, but the zip will hopefully work; I can't include the hdri texture, but any will do, of course)

Again, sorry if I'm just missing something - and thanks for looking into it : )

//EDIT: Ah, small addition - the screenshots are from the live viewer, but the issue appears via proper picture viewer rendering as well.

[Tim0042]

Hmmmm, taking a closer look at the speed vertex maps itself - I think there might already be some less than ideal input from xParticles (spots with abrupt changes in velocity). It can be alleviated a bit by blurring the maps in the OpenVDBMesher Tag Options, though it's not ideal.

Still, this may be a case where there is nothing to be done on the Octane side of things? I'm not sure. =/

[aoktar]

Hmmmm, taking a closer look at the speed vertex maps itself - I think there might already be some less than ideal input from xParticles (spots with abrupt changes in velocity). It can be alleviated a bit by blurring the maps in the OpenVDBMesher Tag Options, though it's not ideal.

Still, this may be a case where there is nothing to be done on the Octane side of things? I'm not sure. =/

You need to be sure these maps are providing correct and excepted values for Octane side. Correct axis and direction for vectors are required.

[frankmci]

I advice to use latest C4D(2023.2) and latest driver. Older driver was causing interesting stability issues on me for example.

Thanks, Ahmet. I was just trying to be helpful with some more info, but I also hadn't realized C4D 2023.2 was out. I'm setting up a new machine as I type, so I'll update everything and give it another shot.

That did the trick, Ahmet. All working fine on this new machine with everything brand-spanking-new. I can't get this example scene to lock up through gradient manipulation, timeline jumping, scrubbing, playing, and rendering image sequences runs smoothly with no lockups.

[Kalua]

Thanks, Aoktar!
Overall working great here.
One question: I see Universal Camera now has a "Keep up-right" function, which is very nice. However I see it behaves differently than Thinlens Perspective control in regards to the camera vertical movement which seems to be inverted.
Please refer to .gif
Is it supposed to be like his?
Regards,

[aoktar]

Thanks, Aoktar!
Overall working great here.
One question: I see Universal Camera now has a "Keep up-right" function, which is very nice. However I see it behaves differently than Thinlens Perspective control in regards to the camera vertical movement which seems to be inverted.
Please refer to .gif
Is it supposed to be like his?
Regards,

Hi Kalua! I don't write the Core, so I don't know what's supposed to be.

[UON.Visuals]

I was hoping with the instance color stuff worked in this might fix a serious bug that crashes Cinema 4D consistently:

For 6 years, over several versions of octane (4.0 to 2022.1.1), Cinema 4D (r17 to 2023) , different windows installations and different computers, this bug has always stuck around and it drives me absolutely crazy.

When I use a blend cloner that clones cloners with their own shaders, when I use an octane material to color the child objects using a gradient to map them, it hangs or crashes Cinema 4D spectacularly. It is impossible to generate a log because Cinema 4D either quits too fast or just hangs forever.

I made a simple example project that replicates this behavior, anyone can download it here if they'd like to try it:
https://drive.google.com/file/d/12Q8zme ... sp=sharing

It will either crash while you're clicking around on the timeline, or selecting a different gradient in the octane material node, or when rendering to picture viewer or in the render queue (it never renders more than 1 frame before crashing)
Please fix this I would be so grateful, there are so many things I want to use blended cloners for but this has been stopping me ever since I started using Octane
(I imagine finding the cause of this bug will also fix other crashes when I use cloners and shaders for materials)

It's working here. I'll test it more! BUT I'd love that to see more a calmer feedback. I don't see any post of you about it earlier for example. We cannot know the issues without user reports.

Sorry haha I've been fighting this bug for years, I did message you directly about it back in 2019 and 2020 but figured it was my system software/hardware!

After updating to C4D 2023.2 and the latest studio drivers, IT'S FINALLY GONE I JUST RENDERED MULTIPLE FRAMES EVERYTHING WORKS PERFECT!!
THANK YOU SO MUCH! Time to dig up all the projects I abandoned!

[UON.Visuals]

I spoke too soon!

I updated the Octane plugin to 2022.1.1 R2 and the bug came back, with C4D freezing with a "mat checkAndUpdate STARTED" message on the bottom of the window.

I went back to Octane 2022.1 [R10] and no crash

Then installed 2022.1.1, same freezing "mat checkAndUpdate STARTED" every time

So I reinstalled 2022.1 [R10], hit the render button, rendered a ton of frames no problem.

So something that changed between 2022.1 [R10] and 2022.1.1 has brought this bug back, might help in pinpointing what's causing it!

Update:
I have more information that'll help!
https://drive.google.com/file/d/1365pa6 ... sp=sharing
This scene right here freezes octane/c4d (even 2022.1 [R10]) as soon as I hit render to picture and it renders 1 frame. If I open the file but change the child cloners to "render instance" instead of just instances, then hit render, I can render multiple frames. If I then switch the child cloners back to plain instances, then I can render multiple frames with those.

So this bug happens when the file is rendered right away upon opening, but if I switch the cloners to render instances, render, then switch them back the bug disappears. I've done this sequence 3 times now with the same results, I think that should help!

Any idea what else could be causing the "mat checkAndUpdate STARTED" freezing? Because I get it with other scenes at random times that I can't reproduce