Page 6 of 8
Re: Cinema4D version 2025.1 Build 0104
Posted: Tue Apr 29, 2025 7:50 am
by iDani
Hello,
there is a problem with the cinema 4d display tag on MAC and PC. If i animate a Display tag from 0-100% visibility for instance, cinema 4d Octane is crashing every time. I am on latest versions for all applications.
cheers Daniel
Re: Cinema4D version 2025.1 Build 0104
Posted: Tue Apr 29, 2025 12:01 pm
by DinoMuhic
iDani wrote: Tue Apr 29, 2025 7:50 am
Hello,
there is a problem with the cinema 4d display tag on MAC and PC. If i animate a Display tag from 0-100% visibility for instance, cinema 4d Octane is crashing every time. I am on latest versions for all applications.
cheers Daniel
I can not replicate this in a simple scene. Can you send an example scene please?
But in general, it is advised to use the Visibility slider inside the Octane Object tag for this and not the display tag, which is only partly supported.
Re: Cinema4D version 2025.1 Build 0104
Posted: Tue Apr 29, 2025 12:09 pm
by DinoMuhic
19Nik90 wrote: Thu Apr 24, 2025 1:40 pm
Hi, I've encountered this problem, I don't know if its a bug or something related to me....
When I need to render an image sequence using takes, the render get stuck at the second frame, and the only solution is to force Cinema 4D to quit.
I've noticed that this happen only if the "Render AOV Manager" is enable, to save a Render pass file. If "Render AOV Manager" is disable, the image sequence gets rendered.
This happen to me on a big project with plenty of materials, so I've created a simple scene to trying to recreate the error, I've attached the scene.
I'm on the latest Octane and Cinema 4D versions.
Thank you
Hi,
Thanks for the file, I was able to reproduce this and filed it as a bug to be fixed for the next release.
Re: Cinema4D version 2025.1 Build 0104
Posted: Tue Apr 29, 2025 12:18 pm
by 19Nik90
DinoMuhic wrote: Tue Apr 29, 2025 12:09 pm
19Nik90 wrote: Thu Apr 24, 2025 1:40 pm
Hi, I've encountered this problem, I don't know if its a bug or something related to me....
When I need to render an image sequence using takes, the render get stuck at the second frame, and the only solution is to force Cinema 4D to quit.
I've noticed that this happen only if the "Render AOV Manager" is enable, to save a Render pass file. If "Render AOV Manager" is disable, the image sequence gets rendered.
This happen to me on a big project with plenty of materials, so I've created a simple scene to trying to recreate the error, I've attached the scene.
I'm on the latest Octane and Cinema 4D versions.
Thank you
Hi,
Thanks for the file, I was able to reproduce this and filed it as a bug to be fixed for the next release.
Perfect! Thank you very much.
Re: Cinema4D version 2025.1 Build 0104
Posted: Wed Apr 30, 2025 3:53 am
by astrofalcon
Wanted to mention that Standard Volume Medium is causing C4D to crash in this build.
Re: Cinema4D version 2025.1 Build 0104
Posted: Wed Apr 30, 2025 9:09 am
by bepeg4d
desire wrote: Thu Apr 24, 2025 11:43 pm
bepeg4d wrote: Wed Apr 23, 2025 8:38 am
Thanks for sharing the scene.
Light Masking is working as expected, but there is an issue with Live View update, so please go to "room_02" Octane Object Tag, Main tab, and enable the "Force update" option:
IMG_4780.jpeg
ciao,
Beppe
Hello, thank you for your answer!
Did the same as your instruction with no effect. Still get a wierd result to PV while "as expected" work of light masking at LV. Please see screenshot.
And you say nothing for a second question, unfortunately.
Here it is
"a few versions ago the ability to add alpha channel to a beauty pass while saving PSD through Render AOV manager is gone. Why so? Could you fix it please?"
Thank you.
2025-04-25_02-40-22.png
Hi,
if you create a new Render Setting from scratch, everything works as expected:
ciao,
Beppe
Re: Cinema4D version 2025.1 Build 0104
Posted: Wed Apr 30, 2025 11:56 am
by ChrisHekman
astrofalcon wrote: Wed Apr 30, 2025 3:53 am
Wanted to mention that Standard Volume Medium is causing C4D to crash in this build.
Yes this was an issue with octane 2025.1, this is fixed in the next build. The current workaround would be to add a " " (space) in the transparent channel name.
Re: Cinema4D version 2025.1 Build 0104
Posted: Wed Apr 30, 2025 2:11 pm
by astrofalcon
ChrisHekman wrote: Wed Apr 30, 2025 11:56 am
astrofalcon wrote: Wed Apr 30, 2025 3:53 am
Wanted to mention that Standard Volume Medium is causing C4D to crash in this build.
Yes this was an issue with octane 2025.1, this is fixed in the next build. The current workaround would be to add a " " (space) in the transparent channel name.
Appreciate the quick response! Glad to hear there is a temp workaround! Thanks for all of the fantastic updates in the latest C4D plugin BTW!!
Re: Cinema4D version 2025.1 Build 0104
Posted: Wed Apr 30, 2025 5:30 pm
by desire
bepeg4d wrote: Wed Apr 30, 2025 9:09 am
Hi,
if you create a new Render Setting from scratch, everything works as expected:
IMG_4858.jpeg
ciao,
Beppe
Hello!
Can't say it was obvious))) but I got it, thanks for the reply!
Re: Cinema4D version 2025.1 Build 0104
Posted: Sat May 03, 2025 5:44 pm
by Delizade
After using Octane for two months over the course of a year, almost every critical move has ended in a crash or bug in this period.
Today, we needed pyro, so we added a sphere and applied an Octane tag to the pyro output after activating the Live Viewer, plugin crashed.
I don’t know what’s going on, but due to issues caused by Octane throughout this production process, I’ve lost a total of 5–6 full working days. We can also add today’s final two-hour struggle with pyro issue to that.