Cinema4D version 2020.1.3-R2 (Obsolete stable) 24.06.2020 Tweet

[aoktar]

Hi all,
This is the Cinema 4D plugin with latest production ready version 2020.1.2 SDK. Any feedbacks are welcome for development and fixing the issues. Enjoy it!

This is the matching Standalone: OctaneRender™ 2020.1.3.

Make sure to use a NVIDIA Studio driver with version at least 435.80 for Windows or 435.12 for Linux to enable support for RTX hardware acceleration. There are no OSX drivers that currently support RTX.


New functionality in node editor


New intuitive workflow for nodes


How to make great looking, fast and fully procedural large clouds in five minutes.

C4D noises(osl implementation) in action, recorded in early stage of development



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. Do 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...


Changes of 2020.1.3-R2 plugin
- Fix: Reverted to material engine of R7 to avoid several input problems for OSL nodes
- Small improvements on node search window
- Added a few missing parameters for universal camera

Changes of 2020.1.3 plugin
- Fix: missing image inputs to osl scripts
- Fix: non-functional parameter "use thin film layer"
- Activated the volume spotlight hardness parameter
- Fix: VDB loading problems
- Fix: missing shift parameter for universal camera
- Ability to (de)activate the "OSL scripting mode" per C4D Noise/Gradient nodes

Changes of 2020.1.2 plugin
- Fix: Compare mode for 8bit-tonemapped buffers
- Fix: missing displacement in composite material from livedb
- Internal changes for universal camera and volume spot light


Note that R21 builds are compatible with S22 and you can use R21 builds in S22, some known issues are available

WINDOWS ENTERPRISE BUILD (R15-R21)
https://render.otoy.com/customerdownloa ... R2_win.rar

WINDOWS SUBSCRIPTION(Studio) BUILD (R15-R21)
https://render.otoy.com/customerdownloa ... R2_win.rar

OSX ENTERPRISE BUILD (R15-R21)
https://render.otoy.com/customerdownloa ... Macosx.zip

OSX SUBSCRIPTION(Studio) BUILD (R15-R21)
https://render.otoy.com/customerdownloa ... Macosx.zip

R15 resources(just for R15 users)

Requirements:
-You'll need to update your Cinema 4D to latest versions(R16.050, R17.053, R18.057, R19.053, R20.057, R21.115). 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 435.80) and be careful with latest Game Ready drivers which can cause cuda errors. Stay with stable one for you.
-Cuda 9.1 driver for OSX.



ONLINE HELP MANUAL
Use embedded help buttons from Octane nodes and windows

To use OFFLINE version of manual from plugin
Download following package and extract to Cinema4D/plugins/c4doctane/manual
https://render.otoy.com/plugindownloads ... p-html.zip

V3 SAMPLE SCENES SET(make a request if you need any specific sample)
https://render.otoy.com/plugindownloads ... scenes.rar

See this topic for some partial samples: viewtopic.php?f=85&t=53989

CINEMA 4D TUTORIALS SECTION: viewforum.php?f=87

CHANGE LOG: https://docs.otoy.com/#60Change%20log


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..

Cinema 4D Release 15: c4dOctane-r15.cdl64 or c4doctane_R15_demo.dylib
Cinema 4D Release 16: c4dOctane-r16.cdl64 or c4doctane_R16_demo.dylib
Cinema 4D Release 17: c4dOctane-r17.cdl64 or c4doctane_R17_demo.dylib
Cinema 4D Release 18: c4dOctane-r18.cdl64 or c4doctane_R18_demo.dylib
Cinema 4D Release 19: c4dOctane-r19.cdl64 or c4doctane_R19_demo.dylib
Cinema 4D Release 20: c4dOctane-r20.xdl64 or c4doctane_R20_demo.xlib
Cinema 4D Release 21: c4dOctane-r21.xdl64 or c4doctane_R21_demo.xlib

[eyeonestudio]

Thanks for the quick update. VDB is OK.
BTW. What is Volume spotlight "Hardness" parameter?

[bepeg4d]

Hi,
the Hardness parameter controls the inner radius of the spotlight cone, to control the softness/sharpness of the spotlight circle.
ciao Beppe

[eyeonestudio]

Hi,
the Hardness parameter controls the inner radius of the spotlight cone, to control the softness/sharpness of the spotlight circle.
ciao Beppe

Thank you for the explanation.

[divasoft]

Hi. A month has passed, I suppose you have not checked that particle scene. Try this one, you don’t need to simulate long hours, just wait 10 minutes to simulate 50 frames. I hope this is not too long for you. Nevertheless, it would not be bad if you looked at why octane constantly crashes during the final render in random times.
It is NECESSARY to test octane on complex scenes, because it is only on them that deep errors appear. In the meantime, I have to restart cinema every 3-5 frames.
I sent you a scene in PM.

Upd: on frame 32 a permanent error. Further it does not render at all.

[stefanmathez]

OMG Aoktar you are a legend!

I spend half a day yesterday trying to understand why VDB wasn't loading!!

Thank you so much!

toomuchlag

[aoktar]

Hi. A month has passed, I suppose you have not checked that particle scene. Try this one, you don’t need to simulate long hours, just wait 10 minutes to simulate 50 frames. I hope this is not too long for you. Nevertheless, it would not be bad if you looked at why octane constantly crashes during the final render in random times.
It is NECESSARY to test octane on complex scenes, because it is only on them that deep errors appear. In the meantime, I have to restart cinema every 3-5 frames.
I sent you a scene in PM.

Upd: on frame 32 a permanent error. Further it does not render at all.

This is more acceptable scene to work on. Had no possibility to work on your previous scenes because of work-load on many critical parts.

[divasoft]

Hi. A month has passed, I suppose you have not checked that particle scene. Try this one, you don’t need to simulate long hours, just wait 10 minutes to simulate 50 frames. I hope this is not too long for you. Nevertheless, it would not be bad if you looked at why octane constantly crashes during the final render in random times.
It is NECESSARY to test octane on complex scenes, because it is only on them that deep errors appear. In the meantime, I have to restart cinema every 3-5 frames.
I sent you a scene in PM.

Upd: on frame 32 a permanent error. Further it does not render at all.

This is more acceptable scene to work on. Had no possibility to work on your previous scenes because of work-load on many critical parts.

Thanks for your work. Please pay attention to this problem. I really love octane, but I can’t use it because of these problems.

[aoktar]

Thanks for your work. Please pay attention to this problem. I really love octane, but I can’t use it because of these problems.

There's a problem with odvbmesher under Generators object. It's rendering if you move it to another location. Because it's not using ip system under Generators.

[divasoft]

Thanks for your work. Please pay attention to this problem. I really love octane, but I can’t use it because of these problems.

There's a problem with odvbmesher under Generators object. It's rendering if you move it to another location. Because it's not using ip system under Generators.

I do not quite understand you. If I move an OVDBobject outside the XPsystem, will the crashes stop?