Cinema4D version 2021.1.1-R3 (Previous stable) 01.02.2022 Tweet

[aoktar]

Hi all,
This is the newest stable plugin build based on 2021.1.1 SDK. Any feedback will be much appreciated. Enjoy it!
This is the SDK matching Standalone 2021.1.1.

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.

2021.1.1-(R3) plugin revisions
- Fix: wrong results with MoGraph shader for some cases
- Added missing 'Look' parameter for image save dialog
- Fixed: removing the 'intersection material' from the 'clipping material' when 'remove unused materials' command is used
- Some fixes on "custom texture" nodes.
- Fix for wrong instance color with multi-instances when cloner's grid mode is sphere/cylinder.


2021.1.1-(R2) plugin revisions
- Added "Comment" node for node editor
- Minor fixes on AOV related parts
- Added Light Mixer node under render AOV outputs.



2021.1.1 plugin revisions
- Some minor fixes on AOV topics and added new crypto AOVs.
- Note that "user_instance_id" is causing a crash, will be fixed on next SDK.

2021.1.1 Renderer changes
Added Cryptomatte AOVs for mattes based on the render layer, user instance ID and geometry node name of an object.
Brought back the option "Emulate old volume behaviour" to the kernel nodes.
Overhauled the way how render work is distributed to local and remote GPUs: The main idea is to reassign already assigned but unfinished work to available GPU when there is no more unassigned work left. This avoids that net rendering may hang due to unfinished work, because some intermediate result got lost. It may also reduce the render time when the local GPUs are out of work but Octane is still waiting for one or more render nodes to finish and return their result.
And read for rest: Standalone 2021.1.1.

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-25)
https://render.otoy.com/customerdownloa ... R3-win.rar

WINDOWS SUBSCRIPTION(Studio) BUILD (R15-25)
https://render.otoy.com/customerdownloa ... R3-win.rar

WINDOWS DEMO BUILD (R15-25)
https://render.otoy.com/plugindownloads ... R2-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). 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..

[AaronWestwood]

Thanks Aoktar, literally submitted a ticket yesterday about the "old volume behavior" missing in 2021, so this came at a perfect time!!! You're so speedy

I did have a quick question. Messing around with the filmic OCIO and it comes with a bunch of different contrast curves. Rendering to PV is 1:1 as in the LV which is great, but saving an image from the LV it doesnt have the looks there. I can copy to clipboard just fine and it looks the same, but the save render dialogue has the looks missing. See image attached, is this something which could be included in the File > Save Render dialogue?

[Meet]

Is octane voronoi noise added in the current build?

[moebius]

Is it just me, or does the "Add Render AOVs" not work?

Bild_2021-12-22_101937.png (4.54 KiB) Viewed 10023 times

[aoktar]

Thanks Aoktar, literally submitted a ticket yesterday about the "old volume behavior" missing in 2021, so this came at a perfect time!!! You're so speedy

I did have a quick question. Messing around with the filmic OCIO and it comes with a bunch of different contrast curves. Rendering to PV is 1:1 as in the LV which is great, but saving an image from the LV it doesnt have the looks there. I can copy to clipboard just fine and it looks the same, but the save render dialogue has the looks missing. See image attached, is this something which could be included in the File > Save Render dialogue?

It's different on UI. I think you didn't to try to change the options. See this

Is octane voronoi noise added in the current build?

Is it just me, or does the "Add Render AOVs" not work?

Both will be added/fixed on a next build.

[AaronWestwood]

Thanks Aoktar, literally submitted a ticket yesterday about the "old volume behavior" missing in 2021, so this came at a perfect time!!! You're so speedy

I did have a quick question. Messing around with the filmic OCIO and it comes with a bunch of different contrast curves. Rendering to PV is 1:1 as in the LV which is great, but saving an image from the LV it doesnt have the looks there. I can copy to clipboard just fine and it looks the same, but the save render dialogue has the looks missing. See image attached, is this something which could be included in the File > Save Render dialogue?

It's different on UI. I think you didn't to try to change the options. See this

The attachment a2.jpg is no longer available

Hey Aoktar

Im not sure im following. Ive clicked through and tried every single possible setting, the "Looks" just arnt there in the LV render dialogue option like your screenshot shows..

Im not talking about the colourspace, but the looks.

As mentioned, PV and Clipboard work 100% fine....just the LV render dialogue has this missing...

[Kalua]

Thank you, Aoktar for the quick upgrade!
Is there a quick way to convert existing octane lights into octane toon lights?
Regards,

[aoktar]

Thank you, Aoktar for the quick upgrade!
Is there a quick way to convert existing octane lights into octane toon lights?
Regards,

No, you can write a python script

[aoktar]

Here's a short video to show new Notes node for node editor. Any feedback welcomes
https://www.youtube.com/watch?v=0hx6hN1i1iE

[AaronWestwood]

Thanks Aoktar, literally submitted a ticket yesterday about the "old volume behavior" missing in 2021, so this came at a perfect time!!! You're so speedy

I did have a quick question. Messing around with the filmic OCIO and it comes with a bunch of different contrast curves. Rendering to PV is 1:1 as in the LV which is great, but saving an image from the LV it doesnt have the looks there. I can copy to clipboard just fine and it looks the same, but the save render dialogue has the looks missing. See image attached, is this something which could be included in the File > Save Render dialogue?

It's different on UI. I think you didn't to try to change the options. See this

a2.jpg

Hey Aoktar

Im not sure im following. Ive clicked through and tried every single possible setting, the "Looks" just arnt there in the LV render dialogue option like your screenshot shows..

Im not talking about the colourspace, but the looks.

As mentioned, PV and Clipboard work 100% fine....just the LV render dialogue has this missing...

Happy new year all! Just thought to re-query this to see if its do-able?

AW