Cinema 4D version 2018.1-RC4 (Test version) Tweet

[aoktar]

Hi All,

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

As with all experimental releases, please do not use this for production purposes. 2018.1 XB2 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 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 (R16-R20)
https://render.otoy.com/customerdownloa ... C4-win.rar

WINDOWS SUBSCRIPTION(Studio) BUILD (R16-R20)
https://render.otoy.com/customerdownloa ... C4-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). 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(most recent like 39x.x) with Cuda 9.1 - change driver versions if you have much trouble with the current driver


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

[niestudio]

Thank you for your continued amazing work, Ahmet!!

[shaddam]

Amazing work as always ! works great with my 2080, doesn't seem to like my GTX 970 though, in either standalone or C4D - Error returned = There is no cuda device which is selected.
Win 10 1803
Driver 417.71

Ta.

[Singular1974]

Amazing work as always ! works great with my 2080, doesn't seem to like my GTX 970 though, in either standalone or C4D - Error returned = There is no cuda device which is selected.
Win 10 1803
Driver 417.71

Ta.

Same exact problem.

[abstrax]

Amazing work as always ! works great with my 2080, doesn't seem to like my GTX 970 though, in either standalone or C4D - Error returned = There is no cuda device which is selected.
Win 10 1803
Driver 417.71

Ta.

Sorry, it's not really clear what you mean. Are you saying that you can't select the 970 in the dialog? What happens when you do and is there an error message in the log?

[shaddam]

Amazing work as always ! works great with my 2080, doesn't seem to like my GTX 970 though, in either standalone or C4D - Error returned = There is no cuda device which is selected.
Win 10 1803
Driver 417.71

Ta.

Sorry, it's not really clear what you mean. Are you saying that you can't select the 970 in the dialog? What happens when you do and is there an error message in the log?

Apologies for not being clear,

In standalone - The 970 is deselected by default upon opening, when going into the preferences and attempting to press the check box to enable the 970 a Red X appears for a second over the checkbox indicating that it cannot be enabled

In Cinema 4D ( R18 ) - The 970 again is deselected upon opening C4D - If i deselect my main card, being a RTX 2080 and attempt to enable only my GTX 970 then attempt to render a scene- I will receive the error i stated above " There is no cuda device which is selected "


After clicking OK, c4d crashes with a bug report screen and quits. is there a way to view previous crash logs ?

EDIT : left the log open whilst running c4d, appears this build is only limited to x 1 GPU ?

EDIT 2 : This was just cleared up with Jules on the slack, ignore my inquiry

Posted on the Standalone page right in front of my stupid face :

Please be aware that Studio builds of 2018.1 now support only 1 GPU, and no network rendering

can't activate device 1, because the maximum limit of 1 GPUs has been reached
can't activate device 1, because the maximum limit of 1 GPUs has been reached

[Singular1974]

It will only support 1 gpu moving forward? Are you kidding me? I bought this setup knowing my octane subscription would support my 2080ti and my old 980ti - now you're renegging on that? Will you provide an avenue for customers to get their money back? This is insane.

[frankmci]

It will only support 1 gpu moving forward? Are you kidding me? I bought this setup knowing my octane subscription would support my 2080ti and my old 980ti - now you're renegging on that? Will you provide an avenue for customers to get their money back? This is insane.

From this FAQ
viewtopic.php?f=7&t=69646

Does my monthly subscription licence support more than 2 GPUs now?

Yes - with V4 (and V4 only) you can use up to 20 GPUs. Future versions with the RT-Vulkan backend will at least initially be released with the normal studio subscription 1-2 GPU limit (see below)

[FAZ]

Cool!

Does NVlink work with four RTX 2080 Ti's?

[Singular1974]

It will only support 1 gpu moving forward? Are you kidding me? I bought this setup knowing my octane subscription would support my 2080ti and my old 980ti - now you're renegging on that? Will you provide an avenue for customers to get their money back? This is insane.

From this FAQ
viewtopic.php?f=7&t=69646

Does my monthly subscription licence support more than 2 GPUs now?

Yes - with V4 (and V4 only) you can use up to 20 GPUs. Future versions with the RT-Vulkan backend will at least initially be released with the normal studio subscription 1-2 GPU limit (see below)

So this release i downloaded just now should work with two GPUs, my 2080ti and 980ti - but it simply isn't working because of a technical error? Is that what you are saying?