OTOY Forums

Hi all,
This is the latest experimental plugin build based on experimental 2022.1-XB2 SDK. Any feedback will be much appreciated. Enjoy it!
This is the SDK matching OctaneRender® 2022.1 XB 2.

As with all experimental builds, we advise to not use this release for production purposes. We are trying to, but we can't guarantee that scenes saved with this version will be compatible in future releases. Please note that because of the active development, there are several limitations outlined below.

Make sure to use a NVIDIA Studio driver with version at least 456.38 on Windows.

2022.1-XB2-(R2) plugin revisions

• Fix: Volumebuilder works with Standard Volumes now.
• Fix: Some broken toon material parameters
• Colorkey and Adjustment nodes added
• Some visual fixes for nodes UI

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-26)
https://render.otoy.com/customerdownloa ... R2_win.rar

WINDOWS SUBSCRIPTION(Studio) BUILD (R15-26)
https://render.otoy.com/customerdownloa ... 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, R26.107). 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..

Octane initalizes now also Aov output is saveing again in this version
Thank you!

Hi Ahmet.
About the scatter. Maybe you don't need to invent and write new code? You can just take what the main development team has already done in standalone and just implement it, as you implement everything else in the integration. Because the standalone scatter works both fast and well.

y81r wrote:Octane initalizes now also Aov output is saveing again in this version
Thank you!

Enjoy it!

I click on the link to download the 2022.1-XB2 file and it states "I am not authorized to view that forum." My subscription is current and paid up through next year.

**Nevermind, I got in through my Downloads page in my account.**

divasoft wrote:Hi Ahmet.
About the scatter. Maybe you don't need to invent and write new code? You can just take what the main development team has already done in standalone and just implement it, as you implement everything else in the integration. Because the standalone scatter works both fast and well.

Maybe but I don't love to put my work to trash. You may understand me if you think that's one of the first scatters in the renderers with this capability. Also adding a mode for Octane scatter will cause to loose the some C4D features for scatter. As no viewport dummies/no mograph effectors/no vertexmaps/.... Anyway we'll check it!
And share your scene, our scatter should be fine in your case. I need to see what's your problem.

aoktar wrote:

divasoft wrote:Hi Ahmet.
About the scatter. Maybe you don't need to invent and write new code? You can just take what the main development team has already done in standalone and just implement it, as you implement everything else in the integration. Because the standalone scatter works both fast and well.

Maybe but I don't love to put my work to trash. You may understand me if you think that's one of the first scatters in the renderers with this capability. Also adding a mode for Octane scatter will cause to loose the some C4D features for scatter. As no viewport dummies/no mograph effectors/no vertexmaps/.... Anyway we'll check it!
And share your scene, our scatter should be fine in your case. I need to see what's your problem.

Yes, sure, your scatter is very good compared to others.
Scene example: https://disk.yandex.ru/d/nZzlUAgIQKaUGg

This build is still not compatible with latest NVidia Studio drivers 516.59 - connecting, reconnecting Image Texture nodes ( procedural ones too ) or changing Mix value in material node cause huge CPU delay compared to previous Studio drivers. Live Viewer is locked for 5-8 seconds. Even disabling nodes cause delays.

Attached video.

I think that this is caused by caching because reconecting last used node tree doesn't generate such freeze. I tried disabling caching in Nvidia driver and Octane settings without success.

When will OctaneRender 2022.1 XB 3 C4DPlugin be released?
I'm looking forward to brigade!

Apparently, an error is displayed when ACES tone mapping is activated.