Octane 2026.2 for Cinema4D - v1.8.4

[ChrisHekman]

Hi all,

This is a hotfix build for 1.8.3 due to a colorspace bug on textures that creeped in last minute.

This is a plugin release for OctaneRender 2026.2.
For this release we continued our focus on stability and quality.
Notably most colors from Octane materials, Redshift and legacy C4D materials should now be in the correct color space.
And colorpickers in C4D should now match with the Live Viewer when the LV is set to the sRGB colorspace.

Additionally we now support the Chinese version of OctaneRender.
Due to legacy issues the plugin itself is a mixed translation for now, and a lot of text will still be in English.


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

2026.2 - v1.8.4 plugin revisions

• Fixed colorspace issues on Octane texture nodes. (Image Texture, Instanced Textures, Tile textures, MaterialX Textures
• Added version conversion for texture nodes
• Added Linear sRGB colorspace option to texture nodes

2026.2 - v1.8.3 plugin revisions

• Color space handling has been corrected across the plugin for C4D 2024/2025/2026.
• MaterialX import support added (available in the Live Viewer dropdown next to Import ORBX).
• Updated to Octane 2026.2.
• Added Chinese version of the plugin. The translation is not complete yet and will be mixed with English. We will continuously improve the translation.
• GUI inputs for Octane nodes are now displayed in sRGB and match the Live Viewer when the LV is set to sRGB color space.
• The Live Viewer (when set to sRGB) now matches C4D and Redshift when the OCIO view tonemap is set to un-tone-mapped.
• Redshift materials now transfer color values to Octane in the correct color space.
• Legacy Standard materials now transfer color values to Octane in the correct color space.
• Object Layer Color in the Octane Object Tag now has its own dedicated UI matching Octane Standalone.
• Removed support for the legacy linear workflow.
• The plugin now consistently stores color information in linear sRGB.
• Sending a picked color to the Octane Physical Camera Tag is now supported.
• Fixed distorted UVW issues.
• Fixed a crash caused by accessing pixel data outside of the Live Viewer image.
• Added support for User Data tags on child objects.
• Refactored Kernel settings — the UI now matches the Octane Standalone layout.
• Added Radiance Cache to the Photon Kernel.
• Added compatibility mode to the Universal Camera.
• Added compatibility mode to PBR Materials.

Downloads:
WINDOWS STUDIO+ 2026.2 - v1.8.4 (R21-R2026)
Installer
Archive
Installer Chinese
Archive Chinese

MacOS Prime 2026.2 - v1.8.4 (R21-R2026)
Archive

WINDOWS DEMO 2026.2 - v1.8.4 (R21-R2026)
Installer
Archive

2026.2 - Nodes
OctaneRender Studio+ 2026.2 Node for Windows (installer)
OctaneRender Studio+ 2026.2 Node for Windows (ZIP archive)
OctaneRender Studio+ 2026.2 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..

[19Nik90]

Hello, I'm not sure how to handle the right color space.

The new version of Cinema 4D apply by default the ACEScg color space in the project setting, and if I activate the octane ACES tone mapping togle in the "Tone mapping" tab, it is like the program is appling a double ACEScg and the colors are complitely wrong.

To keep everything like before i need to set Cinema 4D color space to Legacy (Linear sRGB).

Can you please explaing how to handle this?

Thank you

Nicola

[ChrisHekman]

Hello, I'm not sure how to handle the right color space.

The new version of Cinema 4D apply by default the ACEScg color space in the project setting, and if I activate the octane ACES tone mapping togle in the "Tone mapping" tab, it is like the program is appling a double ACEScg and the colors are complitely wrong.

To keep everything like before i need to set Cinema 4D color space to Legacy (Linear sRGB).

Can you please explaing how to handle this?

Thank you

Nicola

I assume you are looking at the picture viewer? We are currently working on a solution for that.
In the meantime you can set the view transform to raw. That will show you the results in the selected colorspace in the OctaneRender PV Render Settings.
Ofcourse going to the legacy color space still works aswel.

[Anlv]

I have updated to v1.8.4, but I cannot find the "version conversion" button mentioned in the release notes ("Added version conversion for texture nodes"). Could you please provide a screenshot?

[ChrisHekman]

I have updated to v1.8.4, but I cannot find the "version conversion" button mentioned in the release notes ("Added version conversion for texture nodes"). Could you please provide a screenshot?

It is automatic when loading in older scenes.

[19Nik90]

Hello, I'm not sure how to handle the right color space.

The new version of Cinema 4D apply by default the ACEScg color space in the project setting, and if I activate the octane ACES tone mapping togle in the "Tone mapping" tab, it is like the program is appling a double ACEScg and the colors are complitely wrong.

To keep everything like before i need to set Cinema 4D color space to Legacy (Linear sRGB).

Can you please explaing how to handle this?

Thank you

Nicola

I assume you are looking at the picture viewer? We are currently working on a solution for that.
In the meantime you can set the view transform to raw. That will show you the results in the selected colorspace in the OctaneRender PV Render Settings.
Ofcourse going to the legacy color space still works aswel.

RawPictureViewer.png

Hi,

No, I'm not talking about the picture viewer, this happen in the viewport rendering.

But now I've noticed that this only happen in the Viewport rendering and not in the octane live viewer.

To recap:
-When C4D is set to ACEScg color space and octane ACES tone mapping is on, the colors in the viewport rendering are wrong or distorted.
-When C4D is set to legacy color space and octane ACES tone mapping is on, the colors in the viewport renderng looks right as seen in the octane live viewer.

Thank you

[ChrisHekman]

Hello, I'm not sure how to handle the right color space.

The new version of Cinema 4D apply by default the ACEScg color space in the project setting, and if I activate the octane ACES tone mapping togle in the "Tone mapping" tab, it is like the program is appling a double ACEScg and the colors are complitely wrong.

To keep everything like before i need to set Cinema 4D color space to Legacy (Linear sRGB).

Can you please explaing how to handle this?

Thank you

Nicola

I assume you are looking at the picture viewer? We are currently working on a solution for that.
In the meantime you can set the view transform to raw. That will show you the results in the selected colorspace in the OctaneRender PV Render Settings.
Ofcourse going to the legacy color space still works aswel.

RawPictureViewer.png

Hi,

No, I'm not talking about the picture viewer, this happen in the viewport rendering.

But now I've noticed that this only happen in the Viewport rendering and not in the octane live viewer.

To recap:
-When C4D is set to ACEScg color space and octane ACES tone mapping is on, the colors in the viewport rendering are wrong or distorted.
-When C4D is set to legacy color space and octane ACES tone mapping is on, the colors in the viewport renderng looks right as seen in the octane live viewer.

Thank you

Yea color management is a bit tricky in C4D. Lets go over the expected behavior from top to bottom with the default OCIO settings in 2026

The Render Space at the top is the internal colorspace that C4D uses to store color information and do its calculations.
In C4D2026 this defaults to ACEScg, and previously in linear sRGB. Octane stores its colors as Linear sRGB and does its calculations using spectral rendering.

The Display Space is the colorspace the render results will be stored in. sRGB by default in C4D 2026. However you also will not see this colorspace by default.

Which leads us to the most important colorspace, the View Transform (Project). This is what the C4D viewport will be displayed in. It defaults to ACES 1.0 SDR-video.
This is what you actualy see in C4D at default.
When set to Raw, you will see the "Render Space", which will be ACEScg. <- This should match Octane LV when set to ACEScg
When set to Un-tone-mapped, you will see the "Display Space", which will be sRGB. <- This should match Octane LV when set to sRGB
When set to ACES 1.0 SDR-video it will be that colorspace. To make Octane LV match you need to load the same OCIO file as C4D and select it in the settings and LV

Now that being said. You will still see differences in colors between Octane and C4D. This is because lighting intensity and material light response will differ between Octane and C4D, and you will need to get them right.

[19Nik90]

I assume you are looking at the picture viewer? We are currently working on a solution for that.
In the meantime you can set the view transform to raw. That will show you the results in the selected colorspace in the OctaneRender PV Render Settings.
Ofcourse going to the legacy color space still works aswel.

RawPictureViewer.png

Hi,

No, I'm not talking about the picture viewer, this happen in the viewport rendering.

But now I've noticed that this only happen in the Viewport rendering and not in the octane live viewer.

To recap:
-When C4D is set to ACEScg color space and octane ACES tone mapping is on, the colors in the viewport rendering are wrong or distorted.
-When C4D is set to legacy color space and octane ACES tone mapping is on, the colors in the viewport renderng looks right as seen in the octane live viewer.

Thank you

Yea color management is a bit tricky in C4D. Lets go over the expected behavior from top to bottom with the default OCIO settings in 2026
ColorManagement.png

The Render Space at the top is the internal colorspace that C4D uses to store color information and do its calculations.
In C4D2026 this defaults to ACEScg, and previously in linear sRGB. Octane stores its colors as Linear sRGB and does its calculations using spectral rendering.

The Display Space is the colorspace the render results will be stored in. sRGB by default in C4D 2026. However you also will not see this colorspace by default.

Which leads us to the most important colorspace, the View Transform (Project). This is what the C4D viewport will be displayed in. It defaults to ACES 1.0 SDR-video.
This is what you actualy see in C4D at default.
When set to Raw, you will see the "Render Space", which will be ACEScg. <- This should match Octane LV when set to ACEScg
When set to Un-tone-mapped, you will see the "Display Space", which will be sRGB. <- This should match Octane LV when set to sRGB
When set to ACES 1.0 SDR-video it will be that colorspace. To make Octane LV match you need to load the same OCIO file as C4D and select it in the settings and LV

Now that being said. You will still see differences in colors between Octane and C4D. This is because lighting intensity and material light response will differ between Octane and C4D, and you will need to get them right.

Thank you so much! Everything is much clearer now.

[Anlv]

Starting from version 1.8.3, has the float texture node been removed?

[desire]

Starting from version 1.8.3, has the float texture node been removed?

It's just renamed. Placed at blue group at the top in node editor