Octane 2026.5 for Cinema4D - 2.0.0

[Tim0042]

Hey, just to make sure it doesn't get lost I wanted to add my request regarding updated support for the Insydium plugin here as well.

The issue is basically this:

• The new nxEmitter is not recognized by the Octane Object Tag, so particles can't easily be rendered as geometry like before.
• The same likely applies to the Instance Color node that expects an emitter as source but doesn't know the new one. (Could not test this, as particles don't render yet.)

Sorry for the repeat, the thread basically became outdated an hour after I posted it. : )

We are looking into this

Perfect, thank you! : ) This is quite a notable update in terms of features, so I'm really curious to see how these simulations look in Octane.

[lhy2495724656]

OctaneRender 2026.5 for Cinema 4D - Plugin 2.0.0 Feedback

Hello OTOY team,

I tested OctaneRender 2026.5 / Cinema 4D Plugin 2.0.0 and found several issues, mainly related to the new Toggle GPU Texture Viewer, plus one particle Camera Motion Blur problem.

Issue A - Live Viewer looks blurry with GPU Texture Viewer OFF01_GPU_Texture_Viewer_OFF_Blurry_Live_Viewer.png

When Toggle GPU Texture Viewer is disabled, the traditional Live Viewer image looks noticeably blurry.

When I enable GPU Texture Viewer, the image becomes much sharper.
02_GPU_Texture_Viewer_ON_Clear_Live_Viewer.png
I would expect both display modes to show the render at comparable sharpness when the render resolution and viewer zoom are equivalent.


Issue B - Show In Picture Viewer does not work

With Toggle GPU Texture Viewer enabled:
03_GPU_Texture_Viewer_Show_In_Picture_Viewer_Not_Working.png
1. Right-click the Live Viewer image.
2. Choose Show In Picture Viewer.

Nothing happens.

This command works as expected in the traditional viewer workflow.


Issue C - Copy to Clipboard does not work

With Toggle GPU Texture Viewer enabled:
04_GPU_Texture_Viewer_Copy_To_Clipboard_Not_Working.png
1. Open the Live Viewer File menu.
2. Choose Copy to Clipboard.

The current render image is not copied to the clipboard.


Issue D - Shift+R crashes the Octane plugin

With Toggle GPU Texture Viewer enabled:

1. Open Octane Live Viewer.
2. Press Shift+R to render to the Cinema 4D Picture Viewer.

Cinema 4D shows this error:

The plugin c4doctane-2026.xdl64 has crashed.
05_GPU_Texture_Viewer_ON_Shift_R_Picture_Viewer_Crash.png
This happens consistently for me.


Issue E - Center snapping while panning is missing

In the previous Live Viewer, when I dragged or panned the rendered image, it could snap back to the center of the viewer.

With Toggle GPU Texture Viewer enabled, this center-snapping behavior is gone.

I would like the previous panning behavior to remain available in the GPU Texture Viewer.


Issue F - Render resolution and viewer zoom behave differently

With Toggle GPU Texture Viewer enabled, changing the render resolution or render scale also changes how the image is automatically fitted or scaled inside the Live Viewer.

This behaves differently from the previous viewer.

I would prefer the render resolution and the viewer zoom or framing to remain independently controllable.


Issue G - DeMain disappears in GPU Texture Viewer mode

With GPU Texture Viewer disabled, the pass bar includes DeMain, Denoised Main.

With GPU Texture Viewer enabled, DeMain is no longer available in the pass list.

I would like to keep access to the normal DeMain pass in GPU Texture Viewer mode.


Issue H - Camera Motion Blur produces abnormal particle streaks

In a particle scene, enabling:

Octane Camera > Motion Blur > Enable

causes the particles to produce extremely long radial streaks and smearing.
07_Camera_Motion_Blur_ON_Abnormal_Radial_Streaks.png
With Motion Blur disabled, the particle distribution looks normal.
06_Camera_Motion_Blur_OFF_Particles.png
I used the same type of particle setup in Plugin 1.9.4, where the motion blur behaved normally.

In 2.0.0, the abnormal streaking is very easy to reproduce.

Thank you.

Thank you for the thorough review. I have already fixed a few of these issues, and will fix them all and hopefully release a hotfix build this week.
The only exception is the DeMain pass issues. That is an Octane limitation. Denoise does not work in realtime mode. Realtime mode has it's own realtime denoising starting from Octane 2027.1 Alpha 3

Thanks for the clarification.
That makes sense regarding DeMain and the realtime-mode limitation.
I’ll test the hotfix build when it is released and check the other issues again.
Thanks for fixing these so quickly.

[lhy2495724656]

I noticed one small UI inconsistency in OctaneRender 2026.5 / Cinema 4D Plugin 2.0.0.
In the Live Viewer Objects menu, the Octane Camera entry still appears to use the old camera icon design.

Snipaste_2026-10-08_10-42-17.png (43.67 KiB) Viewed 678 times

Since Plugin 2.0.0 introduced the new icon style for Objects and Tags, the Octane Camera icon now looks inconsistent with the rest of the updated UI.
It seems this icon may simply have been missed during the icon update.

[J.C]

It's not possible to add more layers in effects input of an AOV Blend node. You can only add one effect now while in Standalone there can be multiple layers.

Could you provide a screenshot of what it is specifically which node doesnt work?

It's not possible to add Effects layer node to existing node graph:

The Effects layer node automatically appear only when adding ADV node.

[Tim0042]

I'm currently fighting one of these cases where the LV constantly restarts a rendering, making it frustrating (a bit of a dice roll) to preview render some scenes.

From what I can tell, this particular case seems to be related to the combination of Vertex Maps on skin deformed geometry? Noticed it on a larger project, but recreated the issue in a basic scene:

(This is an animated gif, but only seems to play when opening it in a new window. In any case, the C4D file is attached as a zip)

Basically, this is a sphere with a skin deformer and some joint weights, there is a Vertex Map Tag using a Spherical Field, and the Vertex Map is used in a Comp Material to mix a purple and a blue material. Also applied an SDS, so it is closer to a production-like setup.

The constant restarts don't happen on every single render attempt, but rotating the cam a bit with nothing selected should trigger them. Disabling "Check Geometry Updates" in the LV seems to prevent the issue from happening, but this is not really an option for animated scenes.

I regularly use vertex maps for blending between materials (just didn't manage to pinpoint the issue before), so any improvement here would help me a ton. : )

[bepeg4d]

Hi,

It seems related to Bone/Skin, if you disable/re enable the Skin object it stops to blink, can you confirm?

ciao,
Beppe

[Tim0042]

Hi,

It seems related to Bone/Skin, if you disable/re enable the Skin object it stops to blink, can you confirm?

ciao,
Beppe

Hey, thank you for checking! And yep, so it seems like deformers in general might be a factor? Disabling Skin stops the restarts, but adding e.g. a Displacer with a generic noise or a Bend deformer with a bit of strength brings it back. In the Bend deformer test the blinking did calm down eventually, whereas with Skin I've had cases where it never does unless I interact with the LV again in some way. So maybe its most noticable for Skin?

Removing the Vertex Map Tag seems to stop this as well, same for removing the Material tag with the mat that references the Vertex Map.

However, keeping everything and only removing the reference to the Vertex Map from within the material did not do the trick. Which I find confusing. But this is a bit tricky to test because sometimes it only shows up after moving the camera, sometimes resetting the render data helps,... Not sure. =/

[Seggy]

I'm running Cinema 2026.3.4 and this Octane plug-in (OR Prime 2026.5 for C4D 2.0.0) on a Mac Mini 2023 (Apple M2, 8Gb memory, Golden Gate 27.0.1) and I get an error trying to use the Octane plugin "There is no GPU device which is selected..."

Under the Plugin Settings, the Apple M2 (10 GPU cores) is not ticked. Ticking it just gets it unticked next time you go in.
Cannot see anything in any log files about what it going on. This machine should be "supported" (macOS build will only work correctly on macOS 14.5 and newer, and only on Apple Silicon) but I guess something is amiss. My suspicions is the 8Gb of standard memory onboard is not enough for C4D and Octane perhaps?

Octane X Prime 2026.5 runs just fine though (for reference).

Cheers,
Simon.

[bepeg4d]

@Tim0042
We are looking into it.

@Seggy
This is expected, macOS 27 Golden Gate is not supported yet.
We need to wait for upcoming OctaneRender 2026.6 version.

ciao,
Beppe