This is the latest stable plugin build based on 2021.1.4 SDK. Any feedback will be much appreciated. Enjoy it!
This is the SDK matching Standalone 2021.1.4.
Make sure to use a NVIDIA Studio driver with version at least 456.38 on Windows. No driver updates are required for macOS 10.13 (CUDA).
This version supports the new NVIDIA Ampere architecture on Windows and Linux. Kepler cards with compute model lower than 3.5 are just supported on macOS.
Changes of 2021.1.4-(R4) plugin
- xpGroup object support
- R26 builds
Changes of 2021.1.4-(R3) plugin
- Missing AOV parameters of sub material
- Fix: a crash with Background object
Changes of 2021.1.4-(R2) plugin
- Better camera navigation in LV
- Fix: wrong color values with MoGraph colors on some cases like having nested multi cloners
Changes of 2021.1.4 plugin
- Fixed wrong AOV number in capture AOV
- Added new options for composite AOV layer node
Core changes since OctaneRender 2021.1.3:
- Added "Legacy blend mode" alpha operation and a "Force premultiply opacity" pin to the composite AOV layer node. These options allow you to reproduce the results seen in older scenes, before fixes were made in 2021.1.2.
- Reverted the cleanup of the resolution node. I.e. all resolutions we had in version 2020.2 and before are available again, plus the more modern resolutions we introduced in 2021.1.
- Small performance improvement for non-RTX ray-tracing.
- Improved startup times, especially on Linux.
- Map range output AOV node will now allow the output minimum value to be higher than the output maximum value.
- If an OctaneLive activation fails due to an interrupted Internet connection, we open a retry dialog and try again automatically after 20 seconds.
- Fixed authentication failures when more than 4 Octane processes try to authenticate on Linux. If a failure still occurs, we open a retry dialog and try again automatically after 4 seconds.
- Fixed incorrect rendering of materials that use a dirt texture as input of any of the channel manipulation textures (like Channel merger or Channel mapper).
- Fixed incorrect rendering of OSL textures that have an unconnected
_sdfinput. - Fixed black pixels on materials that emit and which have an opacity of 0 or a general visibility of 0.
- Fixed incorrect values in volume Z-depth front AOV.
- Fixed render hang when you use the baking camera is a scene with displacement triangles.
- Fixed auto bump which may cause artefacts on vertex displacement materials that projections other than UV mapping.
- Fixed copy and pasting a geometric primitive, where the first change of the primitive type of the copied geometric primitive was ignored.
- Fixed crash when you load the "fun with vectron" example scene.
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...
WINDOWS ENTERPRISE BUILD (R15-R26)
https://render.otoy.com/customerdownloa ... R4-win.rar
WINDOWS SUBSCRIPTION(Studio) BUILD (R15-R26)
https://render.otoy.com/customerdownloa ... R4-win.rar
WINDOWS DEMO BUILD (R15-R26)
https://render.otoy.com/plugindownloads ... R4-win.rar
Requirements:
-You'll need to update your Cinema 4D to latest versions(R16.050, R17.053, R18.057, R19.053, R20.057, R21.115, S22.118, R23.110, R24.111, R25.117, R26.013). 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 456.38) 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
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 R18.0, keep only "c4dOctane-r18.cdl64" and delete c4dOctane-r17.cdl64, c4dOctane-r16.cdl64, c4dOctane-r15.cdl64, etc..
