Octane 2026.3 for Cinema4D - v1.9.3

Sub forum for plugin releases

Moderators: ChrisHekman, aoktar

ChrisHekman
OctaneRender Team
Posts: 1138
Joined: Wed Jan 18, 2017 3:09 pm

Hi all,

This is a hotfix release for 1.9.1 with OctaneRender 2026.3.

The main changes in this build are the new Material Link node, Octane 2026.3 and splitting the Octane settings between Scene Settings and Plugin Settings.
The split was done because certain settings were not stored in the scene but did change how the scene looks and is rendered. This could cause different results on different machines.


Note:
Downgrading from this version and previous version (1.9.0 / 1.8.5) to an older version (1.8.4 and lower) of the plugin is likely to break the colorspace on texture image nodes.
You can use this python script to fix the issue after downgrading.
download/file.php?id=96735


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

2026.3 - 1.9.3 plugin revisions
  • Fixed bit depth dropdown menu in OctaneRender PV settings
  • Added Gradient node colorspace version conversion
  • Fixed imager crash
  • Fixed OCIO related renderfailure
  • Fixed popup issues during startup with C4D-2023 and earlier versions
  • Fixed solomode crash
2026.3 - 1.9.1 plugin revisions
  • Updated to Octane 2026.3
  • Added a Material Link node for cleaner material linking. Can be used on Composite and Mix materials
  • Added support for Cinema 4D OCIO settings in Cinema 4D 2026
  • Live viewer can now we resized much smaller
  • Split Octane Plugin Settings into:
    • Plugin Settings – Global plugin-wide settings shared across all scenes
    • Scene Settings – Stored per scene within the Cinema 4D file
  • Color and Float attributes now support values up to 10 instead of 2
  • Added a Node Editor button to Null Materials
  • HDR textures now import with the correct color space
  • Disabled unnecessary node previews
  • Attribute strings are now preserved when switching Attribute nodes from Float to Color
  • Improved Shift/Ctrl selection behavior in the Node Editor
  • Added Vector4 input support for OSL Shader nodes
  • Added a Clear/Delete button to the Rest Position Tag
  • Material Layers and Rounded Edges pins are now enabled by default
  • Typed-in values are now preserved in the Adjust Contrast (SDR Only) AOV
  • Fixed the Select Sub Nodes command in the Node Editor View menu
  • Fixed various minor OSL loading issues
  • Plugin now handles activation failures more gracefully
  • Added a Clamp pin to the Displacement node
  • Added I/O type information to Baking Texture and Image Tile nodes
  • Added additional Chinese translations
  • Fixed a performance regression affecting Cloners
  • Bug reports are now checked before logs are cleared
  • Aligned logging checkboxes for improved UI consistency
  • Fixed adding Render AOV layer parameters for Texture AOVs
  • Improved color conversion for:
    • XNoise
    • XColor
    • XGradient
    • XColorizer
    • Gradient nodes
    • Octane Volume Ramp
    • Tex Composite
    • AOV Light Mixer nodes
    • AOV Adjust White Balance
    • ToonRamp
Downloads:
WINDOWS STUDIO+ 2026.3 - 1.9.3 (R21-R2026)
Installer
Archive
Installer Chinese
Archive Chinese

MacOS Prime 2026.3 - 1.9.3 (R21-R2026)
Archive

WINDOWS DEMO 2026.3- 1.9.3 (R21-R2026)
Installer
Archive

2026.3 - Nodes
OctaneRender Studio+ 2026.3 Node for Windows (installer)
OctaneRender Studio+ 2026.3 Node for Windows (ZIP archive)
OctaneRender Studio+ 2026.3 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..
User avatar
UON.Visuals
Licensed Customer
Posts: 28
Joined: Mon Sep 05, 2016 12:28 am

Network rendering isn't working on any of my nodes, what does this mean?
Screenshot 2026-05-23 213230.jpg
Screenshot 2026-05-23 213230.jpg (12.82 KiB) Viewed 755 times
Screenshot 2026-05-23 212642.jpg
Secretwoodsrl
Licensed Customer
Posts: 16
Joined: Fri Feb 08, 2019 2:03 pm

I'm struggling to get OCIO working with other config file / environment variable.
I don't have any error, the plugin just ignore to use the view that I choose.
I see them all in the menu, but in the live viewer nothing changes.
I tried with the imager and also with the AOV node system.

It's only working by flagging "Use Cinema4D Config file", but it's a bit annoying because I have to modify every old scene that I open.
I'm using C4D 2024.
User avatar
bepeg4d
Octane Guru
Posts: 10575
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

UON.Visuals wrote: Sun May 24, 2026 4:33 am Network rendering isn't working on any of my nodes, what does this mean?

Screenshot 2026-05-23 213230.jpg
Screenshot 2026-05-23 212642.jpg
Do you Vectron objects in your scene?
Vectron is giving those error messages on Render-Nodes 2026.3.
It has been already reported to core devs and should be fixed for next Octane core update.

ciao,
Beppe
User avatar
UON.Visuals
Licensed Customer
Posts: 28
Joined: Mon Sep 05, 2016 12:28 am

Yep it's a vectron scene, I'll wait for the next version then!
Secretwoodsrl
Licensed Customer
Posts: 16
Joined: Fri Feb 08, 2019 2:03 pm

Secretwoodsrl wrote: Mon May 25, 2026 7:22 am I'm struggling to get OCIO working with other config file / environment variable.
I don't have any error, the plugin just ignore to use the view that I choose.
I see them all in the menu, but in the live viewer nothing changes.
I tried with the imager and also with the AOV node system.

It's only working by flagging "Use Cinema4D Config file", but it's a bit annoying because I have to modify every old scene that I open.
I'm using C4D 2024.
Update:
I found that the problem was the OCIO file I was using (Aces 1.2).
I don't know if there was an update in the core of Octane or in the plugin side, but now config files that use newer versions of OCIO works as excepted and even better than before.
ChrisHekman
OctaneRender Team
Posts: 1138
Joined: Wed Jan 18, 2017 3:09 pm

Secretwoodsrl wrote: Tue May 26, 2026 9:07 am
Secretwoodsrl wrote: Mon May 25, 2026 7:22 am I'm struggling to get OCIO working with other config file / environment variable.
I don't have any error, the plugin just ignore to use the view that I choose.
I see them all in the menu, but in the live viewer nothing changes.
I tried with the imager and also with the AOV node system.

It's only working by flagging "Use Cinema4D Config file", but it's a bit annoying because I have to modify every old scene that I open.
I'm using C4D 2024.
Update:
I found that the problem was the OCIO file I was using (Aces 1.2).
I don't know if there was an update in the core of Octane or in the plugin side, but now config files that use newer versions of OCIO works as excepted and even better than before.
That last line is good to hear.
I have forwarded the issue with older OCIO files to the Octane team
Tim0042
Licensed Customer
Posts: 54
Joined: Fri Sep 06, 2019 8:57 pm
Location: Hamburg

Tested the update and my scene from 1.9.0 has now kept its look in this new version, so this solves the issues I mentioned in the last thread. Thanks! : )
Tim0042
Licensed Customer
Posts: 54
Joined: Fri Sep 06, 2019 8:57 pm
Location: Hamburg

Setting the Live Viewer to "sRGB: ACES 1.0 SDR-video" does not seem to affect how Output AOVs are displayed in the LV, creating a color/gamma mismatch between them and the Main pass. They only match if I set the LV back to "None". Is this expected behavior?

As a workaround, I can temporarily apply a conversion in the layer stack of the Output AOV group - but having to remember to delete or disable this node before every final export to avoid double-tonemapping the EXR is a bit cumbersome and risky. Is there a better way to preview Output AOVs with the project's View Transform active?
User avatar
bepeg4d
Octane Guru
Posts: 10575
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

Tim0042 wrote: Thu May 28, 2026 9:47 am Setting the Live Viewer to "sRGB: ACES 1.0 SDR-video" does not seem to affect how Output AOVs are displayed in the LV, creating a color/gamma mismatch between them and the Main pass. They only match if I set the LV back to "None". Is this expected behavior?

As a workaround, I can temporarily apply a conversion in the layer stack of the Output AOV group - but having to remember to delete or disable this node before every final export to avoid double-tonemapping the EXR is a bit cumbersome and risky. Is there a better way to preview Output AOVs with the project's View Transform active?
Sorry, I cannot reproduce the issue.
Output AOVs are untonemapped, so you need to apply the same color conversion with layers, to obtain the same result you have in Main pass, and Live View color dropdown menu shouldn't have any effect on Output AOVs :roll:

Could you share an example scene that shows the issue?

ciao,
Beppe
Post Reply

Return to “Releases”