Cinema4D version 2025.1 Build 0104

[bepeg4d]

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.

Hi,
Just few messages before your last post with workaround:
viewtopic.php?p=439038#p439038

ciao,
Beppe

[ChrisHekman]

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.

The pyro issue has been fixed and the fix will be part of next build comming early next week.

On the general stability issues. I have taken over this project for a couple of months now and a lot of issues have been fixed - sadly a few new ones have also been introduced like the pyro crash.
My goals for this project is not just to fix the issues however, but also to refactor the code in such a way that new bugs and crashes become much less frequent.
Additionally we are close to finishing our new automated testing system which should detect issues early on.
I am confident that within the next couple of months the Octane plugin will be much more stable, consistent and pleasant to use for users - while simultaniously much easier for the developers to maintain and expand.

[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

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.

Hi,
the Problem with the Octane Tag is that the Objects are still Visible in the Viewport. I use a loft of fade in and outs of objects. I built the scene with only Octane Tags and a little bit of xpresso to hide the objects in the viewport, but it is still crashing on every fade. I cant share the scene but it is a lot of cloners with instances. Hope the helps.

cheers Daniel

[foliumcr]

I've been building a large scene out with vectron objects acting primarily as the building blocks of the scene.

However, from a certain point, additional vectron objects (Box) when applied to my Composite Material renders out a completely black object. All other vectron objects under the same material stay the same - normal, but every vectron object past that point simply is black. The same happens for Vectron displacement.

Is there a limit to the number of vectron objects available?

[ChrisHekman]

I've been building a large scene out with vectron objects acting primarily as the building blocks of the scene.

However, from a certain point, additional vectron objects (Box) when applied to my Composite Material renders out a completely black object. All other vectron objects under the same material stay the same - normal, but every vectron object past that point simply is black. The same happens for Vectron displacement.

Is there a limit to the number of vectron objects available?

There shouldnt be a limit. Could you share the scene?

[DinoMuhic]

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

In my tests this happens even outside of the take as long as the Cryptomatte AOV is turned on in the render passes. Can you confirm?
Without the Cryptomatte AOV it works.
Definitely will try to get to the bottom of this before next release.

[19Nik90]

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

In my tests this happens even outside of the take as long as the Cryptomatte AOV is turned on in the render passes. Can you confirm?
Without the Cryptomatte AOV it works.
Definitely will try to get to the bottom of this before next release.

Yes I confirm, it happens even without takes.

Thank you

[foliumcr]

I've been building a large scene out with vectron objects acting primarily as the building blocks of the scene.

However, from a certain point, additional vectron objects (Box) when applied to my Composite Material renders out a completely black object. All other vectron objects under the same material stay the same - normal, but every vectron object past that point simply is black. The same happens for Vectron displacement.

Is there a limit to the number of vectron objects available?

There shouldnt be a limit. Could you share the scene?

I've shared the scene at https://limewire.com/d/L1nOg#CRcujcNjgJ
For me, even when isolated from the rest of the scene, the black vectron objects appear. Sometimes disabling vectron displacement fixes it, but sometimes a vectron box by itself has the issue.

[DinoMuhic]

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

In my tests this happens even outside of the take as long as the Cryptomatte AOV is turned on in the render passes. Can you confirm?
Without the Cryptomatte AOV it works.
Definitely will try to get to the bottom of this before next release.

Yes I confirm, it happens even without takes.

Thank you

The issue was identified and will be fixed in the next release of Octane Standalone, as it is a core bug.
To workaround this issue currently, the simplest way I found was to just have at least one more info pass in your AOV manager enabled.
For example a Object ID AOV or a Material ID AOV (those stay small and dont need any compute really).
Another way seems to be to enable Multilayer EXRs.

Sorry for the inconvenience and thanks for the report.

[DinoMuhic]

I've been building a large scene out with vectron objects acting primarily as the building blocks of the scene.

However, from a certain point, additional vectron objects (Box) when applied to my Composite Material renders out a completely black object. All other vectron objects under the same material stay the same - normal, but every vectron object past that point simply is black. The same happens for Vectron displacement.

Is there a limit to the number of vectron objects available?

There shouldnt be a limit. Could you share the scene?

I've shared the scene at https://limewire.com/d/L1nOg#CRcujcNjgJ
For me, even when isolated from the rest of the scene, the black vectron objects appear. Sometimes disabling vectron displacement fixes it, but sometimes a vectron box by itself has the issue.

Hi,
I opened your scene up and none of the vectron objects are black (all are textured). Is there anything specific we need to follow to get them to turn black or is it already happening for you in this scene when you open and render it in the LiveViewer?