bepeg4d wrote: Mon Oct 06, 2025 8:50 am
Sorry, can you share the new scene?
The issue is not totally clear.

ciao,
Beppe

Sure, see attachment. Only difference is a cube with a default specular material. If you open this in Cinema 2026 the refraction inside the cube is way too bright, while 2025 looks normal.

Hi Bepe,

Thanks for the clarification. The original problem I had when the transmission layer is placed behind a simple specular material object still persists, even with the transmission type adjusted in 1.7.1. I thought this would be solved if the transmission was equal but it seems the problem ...

I noticed there are color (calculation) difference between Cinema4D 2025.2.1 & 2026.0.0.

My guess is this can probably be traced back to the new color management settings in C4D 2026, but as far as I can see they seem to be correct (legacy due to the file originating in 2025).

I'm not sure how to ...

The "Use denoised beauty pass" option in Render Settings -> OctaneRender still doesn't work.
I prefer not to use the Octane Render AOV Manager (most of the time) since C4D native saving system is more straightforward and it works better with C4D Render Queue.
The bug was introduced in v1.6.1 ...

Thanks for the reply and confirming what I already suspected.

Hi,

I'm looking for a solution regarding mapping UV size on splines. Currently UV's are scaled to the full length of the spline. I'm looking for a solution to set a specific length/value inside the Octane material so the UV will map to a specific length before it tiles, regardless of the length of ...

Sometimes it works to do a slight scale (0.999) on the selection of objects if they have a centered pivot, but these are all workarounds and not actual solutions unfortunately.

This problem occurs because of polygon faces of different objects being in the same exact place (but flipped). In CAD it's standard to draw objects without any space between objects, and because this value is exactly zero the ray epsilon doesn't make a difference (since it's dividing/multiplying 0 ...

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 ...

Please share the solution for others finding this topic instead of just saying Fixed it.