Cinema 4D version 2018.1-RC6.1 (Test version)

[aoktar]

Hi All,

This is the first test release of the plugin which is based on 2018.1-RC6 SDK and matches OctaneRender Standalone 2018.1-RC6.

As with all experimental releases, please do not use this for production purposes. It will expire in 60 days

New features
To learn more about the new features and improvements of OctaneRender 2018.1, please check out the 2018.1 release post, but this a quick list of the main new features that have been added:

NV Link support on RTX 2080 and RTX 2080 Ti
Cryptomatte. It's working with new EXR(Octane) format type. In this type you cannot use render masks but you will not need to use with Crypto mattes.
Vertex Attributes in the mesh objects. It's used for vertexmap and vertexcolor emulation.
New "Color Vertex Attribute" and "Float Vertex Attribute" nodes to retrieve the vertex attributes in the shaders.
Way less Volume Render Noise. New option in the kernels to disable this feature if the matching of the Octane v4 volumes is needed.
Direct Levelset surface rendering. New option in the Octane volumetrics custom object plugin to configure the OpenVDB rendering to work with SDFs and assign their Octane material nodes.
Scatter depth limiting (i.e. fast fog rendering)
Overall 5% faster than V4 stable (about 315 OB vs 298 OB in our tests)


To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also, make sure you use a driver of version 387 or higher and if you are working on Mac OS that has a CUDA driver installed that supports at least CUDA 9.1.

IN ANY CRASH CASE PLEASE DO THESE!!!
If you see CUDA errors follow 1,2,3,4.
1- 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...


Change list
Having all fixes/improvements of 4.02.1-R3 since 2018.1-RC1 and also SDK 2018.1-RC4 features

Changes of 2018.1-RC6.1
- Reverted back to R20.028 sdk from R20.057
- Fix for InstanceColor id interactivity problems with render instance and multi-instances
- Extended 3rd party support with connection functions

Changes of 2018.1-RC6
- Fix: Possible memory leak on usage of "Use denoised beauty pass" parameter.
- Added: motion blur support for multi-instances in cloners.
- Fix: Node previews work without having render session.

Changes of V4.02.1-R3
- Fix: brdf type in octane materials come from old scenes.
- Fix: Missing parts for saved blend material in livedb.

Changes of V4.02.1-R2
- single file for each render layer with Octane-EXR type. It's well on exr compression.
- fix: search function of livedb manager
- fix: Brdf change issue with V1/V2 materials on V4. viewtopic.php?f=85&t=70622#p356762
- small fixes over 4.02.1

Changes of V4.02
- Better log outputs
- Missing light render passes(directs/indirects)
- Several minor fixes in plugin and core side(See standalone topic)
- Bugfix: crash on exportORBX command if you don't have LiveViewer on startup layout
- extended connection api for 3rd parties
- commandline/nogui support on -exportORBX commandline parameter
- UDIM(Image Tiles texture) support
- HDRLS connection bridge
- Missing DeMain pass in Octane-EXR option

Changes of 2018.1-RC1.1
- Icon for vectron
- Fix: Interactive performance problem with many objects
- Preview problems of octane materials
- Fix: Wrong brdf list with specular/universal materials

Changes of V4.01.1-R1
- Better display performance in LiveViewer
- Fix: Only displaying the vram stats for gpu0
- Minor speed improvement on scene preparation in animation rendering
- Fix: Show in Picture Viewer command
- Fix: Missing clones order in Scatter object with CSV mode
- Fix: Missing default value in Triplanar's coordinate space

Changes of V4.00-R1
Fix: Texture tangent and some info passes in render settings
- Planetary environment.
- Orbx proxy object.
- Fix: Unrecognized channel names in vdb file. viewtopic.php?f=30&t=69481#p350342
- No need to activate denoiser from SettingsWindow or cameraImager for getting denoising passes working in Picture Viewer
- Fix: Missing network render option for Studio builds.
- Fix: Wrong swap for objects/lights in Picture Viewer rendering when you have visibility animations.
- Fix: Extra beauty/denoising passes with RenderLayerMasks

Changes of V4.00
Fix: instanceID problem geometry objects
Fix: A crash case in motion blur
Fix: Several core fixes for Cuda crashes
- Manual revisions for V4 features


WINDOWS REGULAR BUILD (R15-R20)
https://render.otoy.com/customerdownloa ... .1-win.rar

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

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

OSX SUBSCRIPTION(Studio) BUILD (R15-R20)
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). 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.
-Updated Nvidia drivers at least 388.xx, recommended 417.22 or 419.17 (one of most recent with Cuda 9.1) and be carreful with latest drivers which can cause cuda errors. Avoids to use 418.81.
-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

ORBX EXAMPLE VIDEO
https://vimeo.com/302046063

Node sliders
https://vimeo.com/268974364

Viewport rendering mode
https://vimeo.com/265747658
https://vimeo.com/265294205

[Kalua]

Hi, Aoktar
Thanks for the release. I'm feeling this release less stable than others: C4D freezes and closes without wrinting bug report whatsoever: In previous releases I would experience this when rendering under very heavy scenes loads.
In RC6 this behavior has become more erratic: modeling operations or simple GPU AI device assignment "check/uncheck" causes C4D to freeze and close with no bug or crash warning/report.
One more question: Why doens't C4D remember my checked/unchecked GPU AI devices "Use for denoising" configuration? I must reconfig these checks every time I start C4D...
Cheers,

[anklove]

Got a alot of random bugs on this build.
For example octane became super-sensitive to resizing LV window, i got about 10 crashes for 1 day. Also it randomly swithes materials between each other, disables textures and messes materials with other ways and the only thing that cures that is close project and open it again.

[aoktar]

What's your C4d versions and Octane license type? And driver? Do you have any bugreport?
And what kind of scene do you have? Having Motion blur?

[anklove]

What's your C4d versions and Octane license type? And driver? Do you have any bugreport?
And what kind of scene do you have? Having Motion blur?

I have 18.057 C4d, permanent licence, 24.21.13.9907 driver. Dont have bugreport.
Also i found another bug: when im trying to get render region from LV it always puts 0% as top and bottom border.

All of these bugs appeared only in RC6.

[aoktar]

What's your C4d versions and Octane license type? And driver? Do you have any bugreport?
And what kind of scene do you have? Having Motion blur?

I have 18.057 C4d, permanent licence, 24.21.13.9907 driver. Dont have bugreport.
Also i found another bug: when im trying to get render region from LV it always puts 0% as top and bottom border.

All of these bugs appeared only in RC6.

Send some screenshot from the moment of crash. And also keep visible the console window.

[y81r]

Hello Ahmet, I have a weird one.
When copy an object with a standard c4d material command + c, command + v, a new material is automatically duplicated.
this is not a normal cinema behavior.
If Octane is not installed as a plugin that does not happen.

MacOS 10.13.6
c4d r20.057
Octane 2018.1-RC6 and Octane 2018.1-RC4
No other plugins or scripts installed.

Maybe someone can confirm that.

Thank you!


Edit:

By the way, this does not happen if you ever had an Octane material on an object in a scene.
Error path:
1. create a fresh new c4d scene
2. create a cube
3. Create a c4d material
4. copy, paste with keyboard in object manager

see the bug in the texture manager

[aoktar]

Hello Ahmet, I have a weird one.
When copy an object with a standard c4d material command + c, command + v, a new material is automatically duplicated.
this is not a normal cinema behavior.
If Octane is not installed as a plugin that does not happen.

MacOS 10.13.6
c4d r20.057
Octane 2018.1-RC6 and Octane 2018.1-RC4
No other plugins or scripts installed.

Maybe someone can confirm that.

Thank you!

Maybe you're in a specific case! Did you try with different scenes?

[y81r]

Hello Ahmet, I have a weird one.
When copy an object with a standard c4d material command + c, command + v, a new material is automatically duplicated.
this is not a normal cinema behavior.
If Octane is not installed as a plugin that does not happen.

MacOS 10.13.6
c4d r20.057
Octane 2018.1-RC6 and Octane 2018.1-RC4
No other plugins or scripts installed.

Maybe someone can confirm that.

Thank you!

Maybe you're in a specific case! Did you try with different scenes?

I edit my Post...

By the way, this does not happen if you ever had an Octane material on an object in a scene.

Error path:
1. create a fresh new c4d scene
2. create a cube
3. Create a c4d material
3.1 add c4d Material to the cube
4. copy, paste with keyboard in object manager

see the bug in the texture manager

EDIT: forget to tell that the material has to be assigned to the cube

[divasoft]

Why doens't C4D remember my checked/unchecked GPU AI devices "Use for denoising" configuration? I must reconfig these checks every time I start C4D...
Cheers,

YEs! This is my constant headache.