Cinema4D version 2023.1-[R7] (Obsolete stable) 25.11.2023

[aoktar]

This scenefile (See attached file) instant-crashes the moment I start the render, if camera motion blur is on.

I've tested it in both C4D V2023 and C4D V2024 using Octane 2023.1-[R1], Octane 2023.1-[R2] and the older Octane 2022.1.1-[R4] - it's all the same thing.

I'm using X-particles in the scene as well, but completely removing this makes no difference. It still crashes instantly, taking C4D down with it.

Link to file: https://we.tl/t-IlUHReYpWA

Also, on a side note, for this same project but in a different project file I've noticed that camera motion blur if the camera is following a spline using the "align to spline" tag is completely messed up, I really can't explain what is happening other than everything becomes one big blurry mess. EDIT: This seems to only happen if the spline being used for the "align to spline" tag is generated using the tracer object.

It's now crashing here, but data preparation of particle motion blur that's taking much time. I'd advice to make your snow effect with a smaller emitter and less particles.

[DetNyeSort]

It's now crashing here, but data preparation of particle motion blur that's taking much time. I'd advice to make your snow effect with a smaller emitter and less particles.

Well as I said, even completely deleting the particles from the scene still results in a crash on my end, only when I enable motion blur in the camera tag.



this is the message that I'm getting, clicking OK just closes C4D entirely.

I've also attached the bugreport that C4D saved

[aoktar]

It's now crashing here, but data preparation of particle motion blur that's taking much time. I'd advice to make your snow effect with a smaller emitter and less particles.

Well as I said, even completely deleting the particles from the scene still results in a crash on my end, only when I enable motion blur in the camera tag.



this is the message that I'm getting, clicking OK just closes C4D entirely.

I've also attached the bugreport that C4D saved

I meant that's not crashing. Typo here. Tried with windows version.

[DetNyeSort]

I meant that's not crashing. Typo here. Tried with windows version.

I think I've figured out the cause of the crash. The camera is currently being animated using a couple of GSG+ Signal tags (For handheld -like motion) these tags were on the camera itself, moving these tags away from the camera on onto a parent null seems to prevent the crash, even with the snow particles present in the scene.

If you don't know, GSG Signal animates parameters without keyframes, I think Cinema 4D sees it as an expression, so maybe this is a bug with expressions controlling the camera + motion blur?

[aoktar]

I meant that's not crashing. Typo here. Tried with windows version.

I think I've figured out the cause of the crash. The camera is currently being animated using a couple of GSG+ Signal tags (For handheld -like motion) these tags were on the camera itself, moving these tags away from the camera on onto a parent null seems to prevent the crash, even with the snow particles present in the scene.

If you don't know, GSG Signal animates parameters without keyframes, I think Cinema 4D sees it as an expression, so maybe this is a bug with expressions controlling the camera + motion blur?

To able to produce motion blur for camera, the used tag should be defined and threaded in the plugin. I don't have the plugin and never did anything for that.

[SSmolak]

So where is that mysterious Octane Cache folder ? I still think that it doesn't work. There is no any caching or it is always empty - C:\Users\USER\AppData\Local\OctaneRender\cache ?

[aoktar]

So where is that mysterious Octane Cache folder ? I still think that it doesn't work. There is no any caching or it is always empty - C:\Users\USER\AppData\Local\OctaneRender\cache ?

There are not any myst. folder. Caching is like holding the sent images in to the Octane side(RAM/VRAM) for next usages. I don't think you tried it under several tests, just talking about a specific case. There may be a different problem, like out out room.
Send e-mail to support, if you still want a help!

[aoktar]

Updated the build to R4 now with some fixes. Enjoy it!

[Tim_Twisted]

Hi Ahmet,

Quick question regarding a possible bug with the post fog; When I change the resolution to do a final high quality render, the fog does not scale with the resolution and thus changes in appearance. This is also visible when using the live viewer. Is this a bug or am I missing a setting? I thought the scale with film checkbox would help but I don't see a difference. Is it possible to link these values, so the resolution does not make a difference?


C4D test file uploaded here: https://we.tl/t-Gw6ZOKgFtL (The extra volume medium does not make a difference)

[aoktar]

Hi Ahmet,

Quick question regarding a possible bug with the post fog; When I change the resolution to do a final high quality render, the fog does not scale with the resolution and thus changes in appearance. This is also visible when using the live viewer. Is this a bug or am I missing a setting? I thought the scale with film checkbox would help but I don't see a difference. Is it possible to link these values, so the resolution does not make a difference?


C4D test file uploaded here: https://we.tl/t-Gw6ZOKgFtL (The extra volume medium does not make a difference)

Appearance is changing with resolution in case. I don't know is there something missing on my side, I'll talk to core team. But you can make last tweaks at full res with canvas scale<1.0. It's not a good idea, I know.