Cinema 4D version 2018.1-R3(obsoletestable) - 29.03.2019 Tweet

[aoktar]

Hi All,

This is the first release of the Cinema 4D 2018.1 plugin which is based on 2018.1 SDK and matches OctaneRender Standalone 2018.1.

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:

What's new in 2018
Cryptomatte
Deep render passes (not yet in plugin)
Vectron (analytic geometry)
Vertex Attributes
Spectron (procedural volumetric light system)
Much less volume render noise
NV Link support on RTX 2080 and RTX 2080 Ti (Enterprise only)
Direct Levelset surface rendering from VDB (can be fed into Vectron)
Scatter depth limiting (i.e. fast fog rendering)
Cached compressed textures

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...


Changes of 2018.1-R3
- Fix: Reloading issues in ImageTexture
- Fix: Filename conflict with absolute path against relatives, when we have same files in texture search paths
- Addon: Custom LUT combobox in Camera Imagers and settings
- Fix: Connection problem into color pins of osl scripts with some internal octane types(rgb,float,gaussian,...)
- Added ability to break rendering in Picture Viewer at material creation phase


Changes of 2018.1-R2
- Fix: inoperative color/texture parameters of osl scripts in Osl Camera.
- Fix: Uninitialized sheen parameter
- Fix: Mix to Blend material conversion
- Fix: Missing parameters in cryptomatte settings

Changes of 2018.1
- Added: Spectron(Volumetric spot light)
- Fix: ImageTexture and Texture Manager linking problem
- Missing new coating and sheen parameters added
- Fix for InstanceColor id interactivity problems with render instance and multi-instances
- Extended 3rd party support with connection functions
- Fix: Possible memory leak on usage of "Use denoised beauty pass" parameter.
- Fix: Node previews work without having render session.
- Fix: Wrong IDs for light linking invert


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 ENTERPRISE BUILD (R16-R20)
https://render.otoy.com/customerdownloa ... R3_win.rar

WINDOWS SUBSCRIPTION(Studio) BUILD (R16-R20)
https://render.otoy.com/customerdownloa ... R3_win.rar

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

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

WINDOWS DEMO BUILD (R15-R20)
https://render.otoy.com/plugindownloads ... R2_win.rar

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

[VVG]

thanks aoktar, but

Where is the demo version of the 'final version 2018.1'?

Why should I trust you in working v5 and pay $ 199 for 'upgrade' from v4?
previous version of RC6 didn't work properly (C4D r20.057 constantly freezes with octane v5).

The new license system Otoy is insane.

[aoktar]

thanks aoktar, but
Where is the demo version of the 'final version 2018.1'?
The new license system Otoy is insane.

I'll prepare demo versions asap too. We'll see what happens! But this said since it's a test version.

Why should I trust you in working v5

Interesting doubt to who wrote this plugin since V1

[VVG]

Interesting doubt to who wrote this plugin since V1

i know, but users with regular licenses covered this painful journey with you

ps
coming Arnold GPU ))

[Kalua]

Rock Solid build so far!
Thank you, Aoktar!

[nvisuals]

So, I have to buy a subscription to use this update? Am I understanding this correctly?

[dearthman]

thanks aoktar, but
Where is the demo version of the 'final version 2018.1'?
The new license system Otoy is insane.

I'll prepare demo versions asap too. We'll see what happens! But this said since it's a test version.

Why should I trust you in working v5

Interesting doubt to who wrote this plugin since V1

Aoktar,

I appreciate the hard work you've put into developing Octane for C4D, and that you are very active on the forum. Octane 2018 and 2019 are incredible pieces of technology and thanks for working to bring all of that to C4D. But I think a lot of people here struggle with good communication from you and Otoy.

VVG obviously is not being very nice, but they're clearly frustrated and your reply here is not helpful to anyone. This isn't just a hobby or fun thing to mess around with for many of us, we pay money to a well-established company and rely on this product to do our jobs. It's important that users know exactly what is or isn't working with a build. The new licensing system is difficult to understand, finding the proper builds for standalone and the host app plugin with the right license type is difficult (why is there a main download page on the Otoy website if even some production builds are not on it???). I know that stuff is not your fault, but please remember it's very easy to get upset about Octane just from these things, before we even find issues with the C4D Octane plugin.

A ton of people were reporting problems with volumes in the RC6 thread, and now there is released as a full version, but no comment on whether that was fixed or not. I assume so, but why not say that? It doesn't matter as much to me since I already have an all-access license, but for those deciding to upgrade or not it is important to know what issues remain when the last build was clearly not working for many people.

Maybe you need more help? I don't doubt being the only developer AND support person on Octane for C4D is way too much work! Otoy needs to know that people here on the forum and also almost anyone I know/work with in real life joke about how difficult Octane is to use and stay up to date with. Studios hate using it because it is unreliable and has no enterprise support. I get this stuff is cutting edge technology and you don't have any control over how people have their computers set up, or if NVIDIA or Windows breaks something, or if users are doing something the wrong way. I also get every build will not be perfect, but if there isn't better and more professional communication/support people are going to stop using Octane, it's that simple. I asked you a while ago about hair object instance coloring no longer working the way it used to. Your reply was to read the manual, and I responded that others have had this issue as well, and then no response. At least say if you are sure that we are all doing it wrong then, don't just disappear.

[protokol]

Just bit the bullet and bought the subscription.

A project I was working on now loads to the live viewer considerably quicker. Also before it would often crash my C4D as it has a high poly count and massive amounts of trees in object scatter - seems much more stable now.

Great work Aoktar

[aoktar]

A ton of people were reporting problems with volumes in the RC6 thread, and now there is released as a full version, but no comment on whether that was fixed or not. I assume so, but why not say that?

I couldn't reproduce the issues in this build. And issues cannot be related with plugin side. Things are much complicated on my side while working different versions. I believe there is not volume problems in this core.

[natemac00]

In SpotLight - "Camera visibility" shouldn't that also control if the barndoors are visible, or how do you hide those?

Also why is there a shadow in the middle of the spotlight beam?