Page 2 of 4
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Thu Jul 17, 2025 7:56 am
by bepeg4d
Hi Daniel,
Thanks for sharing the scene, now the issue is more clear.
What is not working is the "Use denoised beauty pass" option in Render Settings/OctaneRender/Main tab, if you save your results via C4D Save option:
While if you disable C4D Save option, and save your results via Render Settings/OctaneRender/Render AOV Manager tab, and enable the "Denoised beauty" option, everything is working as expected:
You don't need to create any AOVs, and if "Save beauty" option is disabled, only the denoised result will be saved.
Please always save your results from Render Settings/OctaneRender/Render AOV Manager tab, this also ensures to use the correct OctaneRender format for PNGs and EXRs.
It is planned to revisit this section in one of the next updates, to make it more obvious, and less confusing.
ciao,
Beppe
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Thu Jul 17, 2025 8:40 am
by iDani
Hi Beppe,
thank you for your reply and investigating the issue.
I will use the previous version for now. It works just like before.
And the version is also very stable. Except for the well-known problem with breaking off when rendering on the Mac after about 600 frames.
thank you very much
cheers Daniel
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Fri Jul 18, 2025 6:18 pm
by Kalua
bepeg4d wrote: Thu Jul 17, 2025 7:56 am
Hi Daniel,
Thanks for sharing the scene, now the issue is more clear.
What is not working is the "Use denoised beauty pass" option in Render Settings/OctaneRender/Main tab, if you save your results via C4D Save option:
IMG_5440.jpeg
While if you disable C4D Save option, and save your results via Render Settings/OctaneRender/Render AOV Manager tab, and enable the "Denoised beauty" option, everything is working as expected:
IMG_5442.jpeg
You don't need to create any AOVs, and if "Save beauty" option is disabled, only the denoised result will be saved.
Please always save your results from Render Settings/OctaneRender/Render AOV Manager tab, this also ensures to use the correct OctaneRender format for PNGs and EXRs.
It is planned to revisit this section in one of the next updates, to make it more obvious, and less confusing.
ciao,
Beppe
Thanks for sharing this.
Used to be simpler.
Will give a try in another time.
I also rolled back for now.
Thanks.
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Mon Jul 28, 2025 3:21 am
by tim_grove
Hi, have the bugs related to chaos nodes from V1.5 been solved yet?
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Fri Aug 01, 2025 6:33 am
by divasoft
Hey guys, looks like Octane can’t see the colors from the nested cloner. Putting the cloner under a Fracture doesn’t help either. Could you fix this and maybe release a hotfix?
RS gives the correct result
Or maybe there is another way to solve this problem?
Scene
https://disk.yandex.ru/d/aX8Fw0Q7Ep-Zpw
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Thu Aug 07, 2025 1:59 am
by tim_grove
tim_grove wrote: Mon Jul 28, 2025 3:21 am
Hi, have the bugs related to chaos nodes from V1.5 been solved yet?
Anyone? I've checked about 7 changelogs between the standalone and C4D releases and can't find any information on what's happening or when it will be fixed.
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Thu Aug 07, 2025 7:49 am
by bepeg4d
tim_grove wrote: Thu Aug 07, 2025 1:59 am
tim_grove wrote: Mon Jul 28, 2025 3:21 am
Hi, have the bugs related to chaos nodes from V1.5 been solved yet?
Anyone? I've checked about 7 changelogs between the standalone and C4D releases and can't find any information on what's happening or when it will be fixed.
Hi Tim,
About Chaos texture, sorry, do you mind to share a scene with me via PM?
ciao,
Beppe
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Thu Aug 14, 2025 2:00 am
by protokol
Just checking, is particle motion blur broken again?
Specifically - x-particles. I'm getting some super weird results. Super basic scene just rendering the default particle emitter. It will render random amounts of frames and then stop. You can see in the screenshot attached the particle system is still going but it randomly decides to stop rendering them.
Memory leak
Posted: Sun Aug 17, 2025 1:21 am
by UON.Visuals
Not sure if this has been fixed yet, I am still on 2025.1 becuse of the issue with half my render nodes crashing
I have a super simple scene but it uses an animated texture made of 4500 EXR images. For some reason, rendering the scene fills up my ram over time until C4D crashes or freezes. Shouldn't it just be reading each EXR image one at a time as each frame is rendered?
The ram stays full even if I stop the render and then open up a blank scene in Live Viewer
If this is already fixed in 2025.2.1 that's awesome, but I still can't use it. Will the render node issue be fixed on next release?
Re: Cinema4D version 2025.2.1 - v1.6.1 Hotfix
Posted: Mon Aug 18, 2025 7:57 am
by bepeg4d
protokol wrote: Thu Aug 14, 2025 2:00 am
Just checking, is particle motion blur broken again?
Specifically - x-particles. I'm getting some super weird results. Super basic scene just rendering the default particle emitter. It will render random amounts of frames and then stop. You can see in the screenshot attached the particle system is still going but it randomly decides to stop rendering them.
Hi,
Ok, confirmed, thanks for the report.
Thankfully, this is happening only in Live View, Picture Viewer is not affected:
And if you reload the scene in Live View, the particles are loaded correctly at that frame:
ciao,
Beppe