Page 2 of 4

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Thu Jun 05, 2025 11:45 am
by J.C
Render AOV nodes still rearrange itself and all material and AOV nodes still have red outlines.

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Thu Jun 05, 2025 8:14 pm
by LFedit
I just updated to octane 2025.2 with the hot fix and my scene that was rendering correctly in octane 2023, is not rendering with an alpha channel, even though nothing changed and the alpha is being shown in the live viewer. any thoughts on fixing this?

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Thu Jun 05, 2025 8:27 pm
by LFedit
DinoMFX informed it it's a current limitation. Here's a workaround he sent me:

"you can just create another Output AOV with a Render AOV layer set to Beauty as a pass and that one will have alpha, also all other passes except the default beauty will have alpha"

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Sat Jun 07, 2025 10:16 pm
by desire
Hello!
Trying to utilize octane Field texture with custom shape for a masking purpose of mixing textures and get weird results.
Scene look changes dramatically. For custom shapes I turned off any visibility options but got huge influence over colors and shadows.
And render time increases a lot - from 50s without Fields custom shapes to 1m30s with Fields custom shapes

scene look versus
scene look versus
octane object tag options
octane object tag options

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Tue Jun 10, 2025 12:23 pm
by y81r
Analytic Lights with Post FX cause Cuda error 700 problems in larger scenes
Find Octane Log attached

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Wed Jun 11, 2025 8:42 am
by bepeg4d
y81r wrote: Tue Jun 10, 2025 12:23 pm Analytic Lights with Post FX cause Cuda error 700 problems in larger scenes
Find Octane Log attached
Hi,

Please try to export the scene in .orbx format to Standalone 2025.2, and check if you have the same behavior, thanks.

ciao,
Beppe

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Fri Jun 13, 2025 10:37 pm
by Hoffguy
Migrated 2024 to 2025. We use deadline and the Octane Export Log no longer shows in deadline logs, making all of our error checking no longer function. Any idea if the flagging or reporting or something changed between versions?

I've done some additional testing and the export log is absent from commandline.exe as well





2024
Image

2025
Image

Commandline.exe 2025
Image

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Mon Jun 16, 2025 9:09 am
by WDH
Hi, do we have a plan to clean up our render settings like https://developers.maxon.net/docs/cpp/2025_2_0a/classcinema_1_1_base_video_post.html#a610cf30456b13b5424797d73cfa63644?

I mean the standard videopost that Octane not ues.

that would be a lot easy to modify octane vp.
Snipaste_2025-06-16_17-00-29.png

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Mon Jun 16, 2025 10:14 am
by ChrisHekman
Hoffguy wrote: Fri Jun 13, 2025 10:37 pm Migrated 2024 to 2025. We use deadline and the Octane Export Log no longer shows in deadline logs, making all of our error checking no longer function. Any idea if the flagging or reporting or something changed between versions?

I've done some additional testing and the export log is absent from commandline.exe as well





2024
Image

2025
Image

Commandline.exe 2025
Image
Thanks for the report. I refactored the logging because it was a mess and was using depricated fucntions and to give it its own category in the console window. But it seems a side-effect was that it no longer outputs to stdout.
I have added this back in and should be in the next build

Re: Cinema4D version 2025.2 - v1.5.1

Posted: Tue Jun 17, 2025 5:57 pm
by Hoffguy
ChrisHekman wrote: Mon Jun 16, 2025 10:14 am
Hoffguy wrote: Fri Jun 13, 2025 10:37 pm Migrated 2024 to 2025. We use deadline and the Octane Export Log no longer shows in deadline logs, making all of our error checking no longer function. Any idea if the flagging or reporting or something changed between versions?

I've done some additional testing and the export log is absent from commandline.exe as well
Thanks for the report. I refactored the logging because it was a mess and was using depricated fucntions and to give it its own category in the console window. But it seems a side-effect was that it no longer outputs to stdout.
I have added this back in and should be in the next build

Thank you Chris!