Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Forums: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020
Sub forum for plugin releases

Moderator: aoktar

Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby aoktar » Tue Apr 21, 2020 12:11 am

aoktar Tue Apr 21, 2020 12:11 am
Hi all,
This is the latest of the plugin with release candidate of 2020.1-RC4 SDK. This means that this release contains all features planned for the stable build once it is released but we may still go through more iterations to solve any issues as required. Please be aware this is still not a stable release so please do not use this for production purposes Any feedbacks are welcome for development and fixing the issues. Enjoy it!

This is the matching Standalone: OctaneRender™ 2020.1-RC4.

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.

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-RC4
- Fix for wrong display for some renderpasses with HDR linear/aces tonemap type, also tonemap parameter is a part of scene anymore
- R22 compatibility for R21 build

2020.1-RC4 Standalone fixes/changes that related to Renderer and plugin
Bugfixes:
- Fixed a few scenarios causing CUDA errors after some scene updates.
- Fixed an issue with recent NVIDIA drivers that would cause materials to not to be properly assigned to some instances when using RTX.
- Fixed object layer and material maps so they also work with the new light node types.
- Fixed some scenarios which would cause Octane to not to be able to reach any server due to invalid Windows proxy settings.
- Fixed crash happening during startup on OSX when a proxy is configured in the OS settings.
- Fixed case in which compilation of invalid meshes would result in an unhandled exception.
- Fixed CUDA error when layered materials would exceed the maximum number of layers allowed.
- Fixed CUDA error happening with some mediums with zero scattering values.
Improvements:
- Improved sampling of scattering media with saturated scatter and absorption spectra.
- Mitigated appearance of fireflies in mediums with a highly wavelength-dependent scattering radius.



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

WINDOWS SUBSCRIPTION(Studio) BUILD (R15-R21)
https://render.otoy.com/customerdownloa ... C4_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


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
Last edited by aoktar on Mon Apr 27, 2020 5:37 pm, edited 1 time in total.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
aoktar
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 15937
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby Kalua » Tue Apr 21, 2020 1:15 am

Kalua Tue Apr 21, 2020 1:15 am
Thanks, Aoktar!
Testing it now!
Cheers,
C4D 25.117 Octane 2022.1.2 R4, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 536.67
https://www.behance.net/PaperArchitect
Kalua
Licensed Customer
Licensed Customer
 
Posts: 481
Joined: Fri Oct 11, 2013 2:13 am
Location: Caribbean Sea

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby VVG » Tue Apr 21, 2020 7:25 am

VVG Tue Apr 21, 2020 7:25 am
Image
Win 10x64, AMD 1950x 16C/32T, RAM 32Gb, RTX 3060x3
Octane-for-C4D(R23.110)2021.x.x, Cycles4D, Centileo. Nvidia 472.47 STUDIO
VVG
Licensed Customer
Licensed Customer
 
Posts: 301
Joined: Sat May 07, 2016 2:34 pm

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby zoppo » Tue Apr 21, 2020 9:36 am

zoppo Tue Apr 21, 2020 9:36 am
This one has the same problem / bug as the 2019 version:

Setting an image texture to "Type: float" doesn't change the Vram usage.
C4D 2023 | Win10
User avatar
zoppo
Licensed Customer
Licensed Customer
 
Posts: 298
Joined: Wed Dec 09, 2015 10:37 am
Location: München

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby Kalua » Tue Apr 21, 2020 3:03 pm

Kalua Tue Apr 21, 2020 3:03 pm
zoppo wrote:This one has the same problem / bug as the 2019 version:

Setting an image texture to "Type: float" doesn't change the Vram usage.


Hi, zoppo
Where are you getting your Vram usage readings from? Live view window or the Octane Texture manager?
C4D 25.117 Octane 2022.1.2 R4, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 536.67
https://www.behance.net/PaperArchitect
Kalua
Licensed Customer
Licensed Customer
 
Posts: 481
Joined: Fri Oct 11, 2013 2:13 am
Location: Caribbean Sea

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby aoktar » Tue Apr 21, 2020 4:05 pm

aoktar Tue Apr 21, 2020 4:05 pm
zoppo wrote:This one has the same problem / bug as the 2019 version:
Setting an image texture to "Type: float" doesn't change the Vram usage.

Did you make all tests for every cases? You don't know back processes about the renderer and plugin for image storage and processing, even I don't know the renderer side. So I can't claim that's a bug or problem.
I made a quick test and it looks like working, do you wish to share a better info about problem and way to reproduce it?
Attachments

[ Play Quicktime file ] a1.mp4 [ 1.22 MiB | Viewed 12517 times ]

Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
aoktar
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 15937
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby frankmci » Tue Apr 21, 2020 8:21 pm

frankmci Tue Apr 21, 2020 8:21 pm
I'm back to testing 2020, and I'm delighted to see the new node grouping tools. These will be SO helpful.

I'd like to request that the background color of the node name field for the Group Node have better contrast with the text. As it is now, it's nearly impossible to read, and my eyes aren't what they used to be. (While I'm at it, the Displacement and DisplacementMixer node names could use better contrast, too.)

I also noticed that the name of the Group Nodes don't update, and are stuck on "NodeGraph", if you change the name in the Info window. To make it take effect, you have to use Right-Click>Edit>Rename.

Great work, Ahmet. I know you said a while ago that node grouping wasn't going to be easy to implement, but this seems to be working very nicely. Thanks!

Also, since the GroupNode can have multiple output pins (wonderful!) can each pin be labeled with the name of its hidden parent node?
Technical Director - C4D, Maya, AE, - Washington DC
frankmci
Licensed Customer
Licensed Customer
 
Posts: 814
Joined: Fri May 26, 2017 2:00 pm

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby zoppo » Tue Apr 21, 2020 9:38 pm

zoppo Tue Apr 21, 2020 9:38 pm
aoktar wrote:Did you make all tests for every cases? You don't know back processes about the renderer and plugin for image storage and processing, even I don't know the renderer side. So I can't claim that's a bug or problem.


I didn't, I don't, and why should I?

On the other hand I did show you pictures in the 2019-thread: Pick a texture > put it in an "image texture" node > look at the Octane Texture Mangager's Vram column.
Now change the (RGB) texture's type to float and, according to the Octane Texture Manager, nothing changes regarding the Vram.
"Works" in v2019 and v2020.

So either the "Float" setting has no effect, or the Texture Manager ignores it. I would call that a bug, even without knowing "back processes about the renderer and plugin for image storage and processing". If it's not the plugin not processing the setting, but the underlying Standalone, just pass it on to the Standalone guys, please.

@kalua - That's where ;)
C4D 2023 | Win10
User avatar
zoppo
Licensed Customer
Licensed Customer
 
Posts: 298
Joined: Wed Dec 09, 2015 10:37 am
Location: München

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby thanulee » Tue Apr 21, 2020 10:23 pm

thanulee Tue Apr 21, 2020 10:23 pm
Thanks for the update.
Is the autobump issue fixed? Seems like core issue probably.
I ve sent you a scene while ago in slack which was freezing the render at a certain frame. I figured out that eventually this was due to autobump.
If that doesnt ring a bell, i can resend scene private to support?

Let me know Ahmet, thanks a lot!
User avatar
thanulee
Licensed Customer
Licensed Customer
 
Posts: 709
Joined: Sat Dec 19, 2015 11:00 pm

Re: Cinema4D version 2020.1-RC4 (ReleaseCandidate) 21.04.2020

Postby aoktar » Wed Apr 22, 2020 1:14 am

aoktar Wed Apr 22, 2020 1:14 am
frankmci wrote:I'm back to testing 2020, and I'm delighted to see the new node grouping tools. These will be SO helpful.

I'd like to request that the background color of the node name field for the Group Node have better contrast with the text. As it is now, it's nearly impossible to read, and my eyes aren't what they used to be. (While I'm at it, the Displacement and DisplacementMixer node names could use better contrast, too.)

I also noticed that the name of the Group Nodes don't update, and are stuck on "NodeGraph", if you change the name in the Info window. To make it take effect, you have to use Right-Click>Edit>Rename.

Great work, Ahmet. I know you said a while ago that node grouping wasn't going to be easy to implement, but this seems to be working very nicely. Thanks!

Also, since the GroupNode can have multiple output pins (wonderful!) can each pin be labeled with the name of its hidden parent node?

This feature is partially implemented and had to stop working on for improving/fixing other issues. Even I forgot that, thanks for reminding this. I'll try to complete it in next releases.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
aoktar
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 15937
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Next

Return to Releases


Who is online

Users browsing this forum: Affari, wrapthereal66 and 5 guests

Thu Mar 28, 2024 10:33 am [ UTC ]