Cinema4D version 2025.1 Build 0104

Sub forum for plugin releases

Moderators: ChrisHekman, aoktar

Post Reply
ChrisHekman
OctaneRender Team
Posts: 1053
Joined: Wed Jan 18, 2017 3:09 pm

Hi all,

Here is the Octane 2025.1 Stable release for Cinema4d.
This build contains the major features of 2025 such as Rest positions, Decals, Vectron Displacement and the Realistic Lens Camera.
Additionally we took time to restructure and streamline UI, focus on plugin stability, added icons, and added missing commands for many objects that the plugin provides.

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

2025.1-0104 plugin revisions

Changes:
  • Decal Support: Decal Object and Decal Texture node
  • Rest Positions as a Tag
  • Realistic Lens Camera added to the Octane Camera
  • Vectron Displacement added as Scene Object
  • Vectron Domain Transform added as Scene Object
  • Copying nodes in node editor now copies keyframe animations
  • Camera Mask render pass added
  • Dither fo 8 - bit display(SDR only) AOV added
  • New pin on NT_OUTPUT_AOV_LAYER_BLEND_TEXTURE node
  • Additional Metallic type option to Metallic Material added
  • Compatibility mode for texture environment rotation
  • Step Increase pin on volume / medium nodes
  • Refactored Vectron UI
  • Vectron Icons
  • Create commands for Vectron objects
  • Refactored AOV selection popup menu
  • Node creation button for many texture typed pins
  • Changed “Parallel Samples” and “Max Tile Samples” default values and ranges for kernels
  • Create Commands for Octane Lights that did not have them yet
  • Icons for ORBX Loader and octane lights
  • Clamp pin option on Composite Texture node
Fixes:
  • Fixed freeze that could happen during viewport rendering
  • Old standard materials work again
  • Fixed 2 vectron crashes
  • Fixed step size for certain pins sliders
  • Fixed issue where node commander could create the wrong node
  • Fixed issue where certain nodes would not show up in the node list on the left side of the material editor
  • Added “Max Tile Samples” setting to photon kernel
  • Image Exporter “premultiplied alpha” now defaults to “none”
  • Fixed Range node pin sliders
  • Copied nodes no longer retain connections to non - copied nodes

Downloads:
WINDOWS STUDIO+ 2025.1-0104 (R21-R2025)
Installer: https://render.otoy.com/customerdownloa ... 4Setup.exe
Archive: https://render.otoy.com/customerdownloa ... 4Setup.zip

Mac OSX Prime
Archive: https://render.otoy.com/plugindownloads ... ld0104.zip




Support
Some important notes about these builds:

The minimum NVIDIA driver version that is required by this version is 522. 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. On macOS, only the CPU version is supported.


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). 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 522) 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/OctaneRe ... ema4D.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..
Last edited by ChrisHekman on Wed May 14, 2025 9:52 am, edited 2 times in total.
User avatar
UON.Visuals
Licensed Customer
Posts: 19
Joined: Mon Sep 05, 2016 12:28 am

Amazing, thank you! I'll try it out right now.
FxDesign
Licensed Customer
Posts: 110
Joined: Wed Apr 24, 2013 10:47 am
Contact:

Hello,

I don't know if I'm using it correctly, but there is a bug/strange behavior with the rest tag as you can see in this video:

When I move an object inside a vdb mesher, the mesh disappear
Attachments
Cinema_4D_4hf2Q8Ci1s.mp4
(8.71 MiB) Downloaded 78 times
Tim_Twisted
Licensed Customer
Posts: 39
Joined: Mon Apr 23, 2018 1:31 pm

Thanks Chris, looking forward to using the new Real Lenses. Are there also plans to further expand the lens flare post options since the lenses got this much attention?
DinoMuhic
OctaneRender Team
Posts: 191
Joined: Wed Mar 25, 2015 10:24 pm

FxDesign wrote: Thu Apr 10, 2025 7:57 am Hello,

I don't know if I'm using it correctly, but there is a bug/strange behavior with the rest tag as you can see in this video:

When I move an object inside a vdb mesher, the mesh disappear
Hi,

Thanks for the video.

Can you reproduce this with a baked/cached volume builder? Or even better with a baked-out alembic?

The rest position tag only stores vertex color data into itself when you activate it, which should not be enough to let the mesh vanish, so my feeling is there is a deeper issue here.
FxDesign
Licensed Customer
Posts: 110
Joined: Wed Apr 24, 2013 10:47 am
Contact:

it's working better when cached, but after the last keyframe of a moving object, the mesh disappear again
Martange
Licensed Customer
Posts: 23
Joined: Thu Jan 21, 2016 4:21 pm

Hi and thanks for this incredible update !

I have a major problem with vectron displacement though... As I move the camera, I can see the vectron bounding box behind it and the displacement is clearly lackind details overall (except on some sections). Changing the bounding box size doesn't help...

Am I doing anything wrong ? I have attached my scene to this post as well as a video showing the issue.
Attachments
Screenshot 2025-04-10 130029.png
Screenshot 2025-04-10 130005.png
Untitled video.mp4
(57.6 MiB) Downloaded 46 times
ChrisHekman
OctaneRender Team
Posts: 1053
Joined: Wed Jan 18, 2017 3:09 pm

Martange wrote: Thu Apr 10, 2025 11:12 am Hi and thanks for this incredible update !

I have a major problem with vectron displacement though... As I move the camera, I can see the vectron bounding box behind it and the displacement is clearly lackind details overall (except on some sections). Changing the bounding box size doesn't help...

Am I doing anything wrong ? I have attached my scene to this post as well as a video showing the issue.
That is odd, i would not expect displacement to somehow to be view dependent. Could you send us your C4D scene?
Martange
Licensed Customer
Posts: 23
Joined: Thu Jan 21, 2016 4:21 pm

Of course, here it is

EDIT : I think it has to do with the "box" projection of the noise I use instead of the vectron bounding box...
Attachments
VECTRON DISPLACE 2.zip
(105.85 KiB) Downloaded 27 times
User avatar
cjadams
Licensed Customer
Posts: 239
Joined: Sun Oct 18, 2015 2:27 pm

Thank you very much! - The Trello is a very very very great thing! - It was one of the things the REDSHIFT folks did and feels like good will! - It really makes customers feel so much better to see the ideas and the progress. CONGRATS!

2 Things:
- I noticed that the Mac build for 104 seems to not be linked above.. but DOES seem to be in the otoy downloads so there is that..

- ALSO is there an updated Render node for this 104 build …or do we just keep using 2025.1 render node?
Post Reply

Return to “Releases”