Octane 2025.4 for Cinema4D - v1.7.2

Sub forum for plugin releases

Moderators: ChrisHekman, aoktar

Post Reply
bruce.chai
OctaneRender Team
Posts: 83
Joined: Thu Oct 19, 2023 8:26 pm

Hi all,

To learn more about the new features and improvements of OctaneRender 2025.4, please check out the 2025.4 release post

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

2025.4-v1.7.2 plugin revisions

Changes:
  • Added support for MacOS Tahoe
  • Added Quality settings for the Intel Denoiser in the Imager (Octane Camera tag)
  • Added (deprecated) label to old Geometry Engine options in the Main Tab
  • Thin Wall now works correctly in the Sub-Materials
  • Fixed an issue with very large node-trees in the material editor
  • Safe Frame opacity now works again at 100%
  • Fixed gap after the Voxel option in the Octane Object Tag
  • Universal material section labels fixed


Downloads:
WINDOWS STUDIO+ 2025.4-v1.7.2 (R21-R2026)
Installer: https://render.otoy.com/customerdownloads/plugins/c5/ef/58/e4/OctaneRender_Studio%2B_2025.4_for_Cinema4D_v1.7.2.exe
Archive: https://render.otoy.com/customerdownloads/plugins/b7/29/83/89/OctaneRender_Studio%2B_2025.4_for_Cinema4D_v1.7.2_Bundle.zip

Mac OSX Prime 2025.4-v1.7.2
https://render.otoy.com/octane_eula_only_downloads/9b/5e/32/1e/OctaneRender_Prime_2025.4_for_Cinema4D_v1.7.2.zip

WINDOWS Demo 2025.4-v1.7.2 (R21-R2026)
Installer: https://render.otoy.com/plugindownloads/2f/89/01/e4/OctaneRender_Demo_2025.4_for_Cinema4D_v1.7.2.exe
Archive: https://render.otoy.com/plugindownloads/eb/a8/e2/da/OctaneRender_Demo_2025.4_for_Cinema4D_v1.7.2_Bundle.zip




Support
Some important notes about these builds:

The minimum NVIDIA driver version that is required by this version is 528. You can launch Octane with an older driver version, but it will fail to render and it will produce an error message in the log.

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.4.0, R2025.0.2, R2026.0). 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..
Tim0042
Licensed Customer
Posts: 39
Joined: Fri Sep 06, 2019 8:57 pm
Location: Hamburg

Thank you for the new version! (Also thumbs up for the continued use of Trello!)

One question regarding the update - 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?

I hope my question makes sense : )
martinzip
Licensed Customer
Posts: 65
Joined: Mon Feb 09, 2015 4:36 pm

Hey Chris, thanks for your great work!
Octane is super stagle on my macbook pro M3!
I have some trouble with the motionblur of a helicopter rotor. In Octane 2022 (on my old mac Pro) it works fine with one sample in the octane global render settings...
In Octane 2025.4 1.7.2 it looks quite wrong.
Here with one sample, two samples and 8 samples.

I miss the blur between the samples... all have camera settings 0,02 sec for shuttertime...Every rotor blade has a motionblur tag...
Please help I am in the middle of production.

Kind regards
Martin
Attachments
Mblur_smpl8_Main_0475.jpg
Mblur_smpl2_Main_0469.jpg
Mblur_smpl1_Main_0468.jpg
User avatar
bepeg4d
Octane Guru
Posts: 10434
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

Hi Martin,

Please set the "Time sampling per frame" at 4 in Render Settings/OctaneRender/Main tab and report back, thanks:
IMG_6066.jpeg
ciao,
Beppe
martinzip
Licensed Customer
Posts: 65
Joined: Mon Feb 09, 2015 4:36 pm

Ciao Beppe

Timesampling per frame 4 does not change anything, there is no blur between the samples of movement...
See attached picture.
Attachments
Mblur_smpl4_sh_time 0,03s.jpg
martinzip
Licensed Customer
Posts: 65
Joined: Mon Feb 09, 2015 4:36 pm

Hey Beppe

found the solution!!! I animated the rotor with automatic curve continuation!
I thought maybe a key at the end could help... so it does!
But sure its a small bug when c4d continuing a keyframe animation the motionblur is not working correctly!
Here the same rendering with 8 timesamples...it looks perfect...with 4samples it is not perfectly round.. but much better than before

Thanks Beppe for your help.
Maybe this is something the developper can have a look at...

Kind regards from cologne
Martin
Attachments
Mblur_smpl4_Main_0472.jpg
Mblur_smpl8_Main_0471.jpg
Post Reply

Return to “Releases”