Octane 2025.4 for Cinema4D - v1.7.2

[dasmodular]

Have you tried using an Octane Object tag on those items?

No, I haven't, but I just tried it: Even if I directly apply an Octane Object Tag to these instances and deactivate motion blur, I still get motion blur on these parts.

[dasmodular]

@dasmodular:

Have you tried to disable the Camera motion blur in the Octane camera Tag?

ciao,
Beppe

No, I haven't tried that, because the camera is also moving.
I just tested it and it makes no difference.

The current solution was to leave "Time sampling per frame" at 1.

I'm trying to reduce the project file to isolate the problem.

[Tim0042]

When scaling a project, would it be possible to have the Bump Height in materials be scaled automatically as well? For example, if I CTRL+D scale the project from 1 to 10, could we multiply the Bump Height in all Materials by 10? This might prevent them from changing their appearance in that regard.

Maybe the reverse could work for Density within a Medium Node, so if the scene becomes 10 times larger, divide the Density by 10 to compensate?

Also, using this chance to pull up my question from last month again, as it also has to do with materials : )

The material compatibility mode includes "2025.4" as an option, so the Octane version we just jumped to. What is this used for?

I understand switching to legacy behavior when opening older projects / matching old materials (so the "2022.1" option makes sense), but is choosing "2025.4" just the same as leaving the field blank?
I kiiiinda think it has to, because once I choose something, I cannot return to the blank state - not even with "reset to default". However, the material thumbnail does refresh (if not necessarily change).

The Texture Projection Node also has a compatibility mode, but its default is not a blank field but instead "Latest (2025.1)". Maybe these different behaviors could be aligned?

[DinoMuhic]

When scaling a project, would it be possible to have the Bump Height in materials be scaled automatically as well? For example, if I CTRL+D scale the project from 1 to 10, could we multiply the Bump Height in all Materials by 10? This might prevent them from changing their appearance in that regard.

Maybe the reverse could work for Density within a Medium Node, so if the scene becomes 10 times larger, divide the Density by 10 to compensate?

Also, using this chance to pull up my question from last month again, as it also has to do with materials : )

The material compatibility mode includes "2025.4" as an option, so the Octane version we just jumped to. What is this used for?

I understand switching to legacy behavior when opening older projects / matching old materials (so the "2022.1" option makes sense), but is choosing "2025.4" just the same as leaving the field blank?
I kiiiinda think it has to, because once I choose something, I cannot return to the blank state - not even with "reset to default". However, the material thumbnail does refresh (if not necessarily change).

The Texture Projection Node also has a compatibility mode, but its default is not a blank field but instead "Latest (2025.1)". Maybe these different behaviors could be aligned?

Yeah blank means basically no compatibility mode or latest.

[desire]

Hello!
Why LiveViewer doen't stop render after changing the layout at this version with cinema 2026.0.0 (and may be 1.7.1)?
Octane just continues to render in the background (there is no LiveViewer window opened at that moment).
Now it is necessary to stop rendering via LiveViewer and switch layout after that.
I found it out by a chance, I've been working in UVedit layout for quite a long time, when having noticed that the system has warmed and noised up - I open LiveViewer, and everything has been rendering there all this time...

[Powel2097]

I noticed since the last 2 updates that when working in Cinema in the viewport / Camera view, then switching to 2x2 view, to f.e. move an object from the top perspective, the live viewer isn´t updating.
I have to switch back to fullscreen Camera view for it to make changes.

[markitecture]

Hey,

Been trying to get octane to render using my m4 macbook pro for the last few days, I've installed prime 2026 and the latest c4d plugin but am still getting the "no gpu selected" error that had been plagueing the tahoe updated macbooks since oct.

Any resolution at all to this yet?

[bepeg4d]

Hey,

Been trying to get octane to render using my m4 macbook pro for the last few days, I've installed prime 2026 and the latest c4d plugin but am still getting the "no gpu selected" error that had been plagueing the tahoe updated macbooks since oct.

Any resolution at all to this yet?

Hi,

Ok, please open c4d 2026, then go to c4d menu Extensions/Console/, (Shift+F10), then select "OctaneRender" on the left, and share a complete screenshot of the panel, or copy paste the OctaneRender console output in your answer, thanks.

ciao,
Beppe