Octane 2026.5 for Cinema4D - 2.0.0

[ChrisHekman]

Hi all,

This is our first 2.0.0 release! For the last year an a half we have been working on getting the C4D plugin into better shape.
We worked on stability and usability and worked on filling in many of the gaps in existing features.
Additionally we have worked on refactoring and building new sysems to facilitate faster and more stable development of new features.
We will be releasing these new features in the upcomming 2.x.x builds.
For this build we are starting with Realtime Rendering, Texture Manager Refactor, and Gaussian Splat rendering in the C4D viewport.
Furthermore the build has a new look as we have improved the icons of the LV and many of the Octane scene Objects and Tags.

In the upcomming builds we will releasing improvements and features such as:
Multiple Render Settings(RenderTargets), Improved Picture Viewer Export Settings, C4D Nodegraph support

This build contains OctaneRender 2026.5

To see what the future holds, check out our Trello!
https://trello.com/b/1HYU24R0/octanec4d


2026.5 - 2.0.0 Plugin Changes

• Upgraded to OctaneRender 2026.5
• Realtime mode in Live Viewer (Windows C4D 2026 only)
  This feature shares the octane render results as a GPU texture with C4D resulting in a smoother and faster LV
  Will be extended with realtime denoising in Octane 2027 giving realtime noisefree results in the LV
  For Multi-GPU setups it is required to have both C4D and Octane use the same GPU for the render results
• Gaussian splat viewport rendering (C4D 2026 only)
• Icons update for Live Viewer
• Icons update for Objects and Tags
• Texture Manager Refactor
• Liquid velocity vector support
• Gaussian splat loading by plugin
• SPZ format support for Gaussian Splats
• Added Gaussian log type
• Voronoi Fracture fragments now each get their own instance ID
• NRC Online Training and SPP options on Photon, Direct, and Pathtracing kernels

Fixes

• Fixed anisotropic pins not appearing on material layer nodes
• Fixed error in the log if a Volume Fog object is created
• Fixed Color picker live update issue
• Fixed issue with chinese color space names
• Removed outdated slider types
• Fixed MaterialX UI bug in attribute viewer (Happened on latest versions of C4D 2026)
• Fixed Texture manager mac crash
• Fixed projection node compatibility issues in older scenes. This fixes issues with upgrading to latest plugin version
• Fixed first mesh UV set missing its UVW tag name
• Fixed removed UVW tags leaving their UV set on the Octane mesh
• Fixed image texture output type when switching between RGB, grayscale and alpha images
• Fixed crash in deleteSubApiNodes when a node had no object link
• Fixed warnings/error messages for simulated camera
• Fixed issue with certain OCIO files
• Fixed importance sampling issue

Downloads:
WINDOWS STUDIO+ 2026.5 - 2.0.0 (R21-R2026)
Installer
Archive
Installer Chinese
Archive Chinese

MacOS Prime 2026.5 - 2.0.0 (R21-R2026)
Archive

WINDOWS DEMO 2026.5 - 2.0.0 (R21-R2026)
Installer
Archive

2026.5 - Nodes
OctaneRender Studio+ 2026.5 Node for Windows (installer)
OctaneRender Studio+ 2026.5 Node for Windows (ZIP archive)
OctaneRender Studio+ 2026.5 Node for Linux




Support
Some important notes about these builds:

The minimum NVIDIA driver version required is R535 (R572 for GeForce RTX50 series).

Open Image Denoise is supported on CUDA compute model 7 and later, we fallback to the CPU version on machine with older models.


IN ANY CRASH CASE PLEASE DO THESE!!!
If you see CUDA errors follow 1,2,3,4.
1- Use NVIDIA STUDIO drivers, not Game Ready versions. If you have stability issues try different drivers, some of them could cause instability issues. Make a clean install while doing this to be sure previous files completely removed.
2- Check GPU frequency. Overclocking would cause instability issues
3- Check PSU. Insufficient power output would cause instability issues
4- Check the free amount of GPU's VRAM and system's RAM while working. Low VRAM will/may cause CUDA errors. Be aware of some generator objects will have different triangle count in Picture Viewer than Live Viewer. It’s like “editor/render” parameter. Just try to use the same value. Also try to optimize your scene for polygon count, even use smaller images. Try to use Octane texture nodes rather than using C4D texture/shaders.
Alternatively, use V4 and Out-of-core(OOC) function. Increase RAM for OOC and It should not exceed physical RAM amount. Check TDR value and increase if it's necessary.
5- If you see C4D crashes without CUDA errors, then send us bugreport.zip, screen-shots and video capture to show process and crash moment. Also please send us a sample scene in a format of C4D or ORBX to let us investigate and test it. Alternatively, try to delete/hide some objects/materials until crash gone away. If you find what's causing crashes, send us a sample scene to let us for investigating and bring a fix or solution.
Thanks for helping the development by your feedbacks! It’s impossible to quickly catch every case without user feedbacks! It’s the same procedure as other companies do like Maxon/etc...



Please note the macOS build will only work correctly on macOS 14.5 and newer, and only on Apple Silicon.

Requirements:
-You'll need to update your Cinema 4D to latest versions(R21.115, S22.118, R23.110, R24.111, R25.117, R26.107, R2023.2, R2024.5.1, R2025.3.3, R2026.1.2). Otherwise, the plugin will not work and not appear in menus.
-Internet connection for activation, be sure that C4D and Octane will not be blocked by the firewall and any antivirus software.
-Nvidia drivers at least Nvidia Studio Drivers(minimum 528) and be careful with latest Game Ready drivers which can cause cuda errors. Stay with stable one for you.


ONLINE HELP MANUAL
Use embedded help buttons from Octane nodes and windows
or from link: https://docs.otoy.com/cinema4d/OctaneRenderforCinema4D.html


Archive Installation
First, remove all octane related stuff from plugins and the main folder of Cinema4D.

Extract all files to Cinema4D\plugins\c4dOctane directory.
Also, download manual.zip and extract to c4dOctane directory if it's not available in place.

There are a few files for each one is for different Cinema4D version. Remove all except the file is for your version.
Ex. if you have Cinema4D R2023, keep only "c4dOctane-R2023.xdl64" and delete c4dOctane-R26.xdl64, c4dOctane-R25.xdl64, c4dOctane-R24.xdl64, c4dOctane-R23.xdl64, etc..

[twik25]

I might be missing something, but I can not get the lighting (real-time) view to work. I have tried installing standalone to match. I have 2 A5000's, but one 1 A5000 card active in both c4D and standalone. I'm using Windows, and C4D 2026.4. I hit the lighting button and it is black. I have tried with a completly new scene with nothing in it, same results. I can see the progress bar moving, it is just not showing anything. Nvidia driver version 580.

[ChrisHekman]

I might be missing something, but I can not get the lighting (real-time) view to work. I have tried installing standalone to match. I have 2 A5000's, but one 1 A5000 card active in both c4D and standalone. I'm using Windows, and C4D 2026.4. I hit the lighting button and it is black. I have tried with a completly new scene with nothing in it, same results. I can see the progress bar moving, it is just not showing anything. Nvidia driver version 580.

There are issues with multi-gpu atm. Usually it gets fixed when switching the active Octane gpu while the plugin is running. We are investigating a fix for the multi-gpu issue.

[J.C]

I might be missing something, but I can not get the lighting (real-time) view to work. I have tried installing standalone to match. I have 2 A5000's, but one 1 A5000 card active in both c4D and standalone. I'm using Windows, and C4D 2026.4. I hit the lighting button and it is black. I have tried with a completly new scene with nothing in it, same results. I can see the progress bar moving, it is just not showing anything. Nvidia driver version 580.

As far as I remember in some release notes, when RT feature was introduced, multiple GPUs are not supported with RT enabled along with some other limitations.

[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. : )

[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 OFF

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.

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:

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:

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 (8.38 KiB) Viewed 1569 times

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.

With Motion Blur disabled, the particle distribution looks normal.

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.

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

[ChrisHekman]

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

[ChrisHekman]

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

[ChrisHekman]

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?