OTOY Forums

Hi everybody,
Here is first final version for V3.0. Enjoy it!

Standalone V3.0:
viewtopic.php?f=24&t=54150

New features of V3:
viewtopic.php?f=33&t=51679

OctaneRender for Cinema 4D WINDOWS VERSION(R13-R17):
V3.0-R1.1: https://render.otoy.com/customerdownloa ... .1-win.zip
V3.0-R1.0: https://render.otoy.com/customerdownloa ... .0-win.zip

OctaneRender for Cinema 4D OSX (R15-R17):
V3.0-R1.1: https://render.otoy.com/customerdownloa ... Macosx.zip
V3.0-R1.0: https://render.otoy.com/customerdownloa ... Macosx.zip

V3 SAMPLE SCENES SET(make a request if you need any spesific sample)
https://render.otoy.com/plugindownloads ... scenes.rar

CINEMA 4D TUTORIALS SECTION: viewforum.php?f=87
See attached samples too.

MANUALS
PDF version: under c4dOctane/manuals directory
Web manual: https://docs.otoy.com/#60Octane%20Rende ... r%20Manual


PLEASE IMPORTANT NOTICE
New License system:
We'll run it over the new license system and login window anymore. So you'll need to enter OTOY userid and password to able run the plugin and standalone. This is same combination to entering for Account page of Otoy.
This mean that you shouldn't try to use plugin id/pass pairs since this time. Also this system choose one of your licenses if you have many.

On any login issues see this post and topic:
viewtopic.php?f=30&t=54208&start=50#p276063

If you have C4D startup hangups try to delete these files.
Windows: %APPDATA%/OctaneRender/otoy_credentials
OSX: ~/Library/OctaneRender/otoy_credentials (you may have to use Finder's Go->Go To Folder... and type "~/Library/OctaneRender" - without the quotes - to get to that folder)

CUDA requirements

Due to a CUDA compiler bug we had switch to CUDA 7.5, which means on Windows and Linux you may need to update your NVIDIA graphics driver to a current version which supports at least CUDA 7.5. On Mac OSX you may have to update the CUDA driver for Mac to a current version supporting at least CUDA 7.5.

BUG REPORTS
I'll be happy, if anyone can be specific on their bug reports.
I need to know that your plugin version/Os/HW and last operations before crashes to reproduce and investigate the same problem.
And please attach a SCENE and BUGREPORT.ZIP.
Please post your reports in topic of version which is related or use bugreports section of this forum
Thanks for contributions

Changes of V3-R1.1
- Fix channel combo
- Fix: empty statistics on PV with render region
- Fix: Bug on license control for clean installs

changes of V3.0-R1
- Volume object: First volume filling method by spheres or particles. It's a very experimental and wip feature. Will be improved soon.
- Improvement image drag&drop to Node editor. Better multi drop and replacing old image names with dropped images.
- Loop mode in vdb sequences
- Fix: Crash on scatter

Changes of V3-b2.1
- New type parameter on volume object for allowing mode switch.
- Fix on PV and background alpha
- Fix on missed "invert absorption" on medium nodes
- Fix on rendershader function for C4D shaders
- Fix: Background object renderings

Changes of V3-beta2.0
-Improved render failure detection. See console for details.
-Volume object changes. Support for velocity channels, etc...
-Mix material icon
-Minor fix and improvements since alpha10.1
-V3-Beta2 SDK fixes

Hi....
I'm Happy Now. Thank.... Bro
Specially Volume object changes.

what is the difference between this and Octane 3.0 Alpha 10.1 ?
is this the newest preview version? sorry just confused

aaronsbot wrote:what is the difference between this and Octane 3.0 Alpha 10.1 ?
is this the newest preview version? sorry just confused

Yes Beta2 is latest. I wrote some changes. Also you know it's two part. Plugin side with lot of codes which create, convert and translates scene to renderer and renderer side which makes render.
It contains beta sdk with all fixes from renderer side. Also each plugin version has big or small changes, fixes, improvements. Mostly i don't write small fixes or revisions because they are too much and takes time. I barely finished a build and gone out of office.

-Volume object changes. Support for velocity channels, etc...


does this mean TFD volumes can have their own motion blur now? do you have an example of how to set that up? or documentation on it?

Hello,

Nice feature with the random colored trails. Just a quick question:
In your xp-trail3.c4d you render the particles in tandem with the trails, both using a random function to pick a color from a gradient. Is there a way to synchronize the two? So that the tip particle has the same color with the trail.

Thanks,
Bogdan

I just wanna say thanks Ahmet!

There are a lot of additions which I personally lobbied for (over-under stereo rendering, Mix icon in mix material, XP improvements)
And the IPR feels so much more responsive and fast!

keep rocking!

Is there support for the new render region tool?

DinoMuhic wrote:I just wanna say thanks Ahmet!

There are a lot of additions which I personally lobbied for (over-under stereo rendering, Mix icon in mix material, XP improvements)
And the IPR feels so much more responsive and fast!

keep rocking!

Thanks! Great you notified the small changes.

tomabobu wrote:Hello,

Nice feature with the random colored trails. Just a quick question:
In your xp-trail3.c4d you render the particles in tandem with the trails, both using a random function to pick a color from a gradient. Is there a way to synchronize the two? So that the tip particle has the same color with the trail.

Thanks,
Bogdan

In my sample, xp trails works as hairs via object tag. Gets the color with help of their uv coordinates. But spheres are render instances and no way to sync the colors by user. Just possible to use random texture over there. Another possible way to use mograph colors on non-render instances. But soon Otoy will bring a way to create custom texture for render instances. Waiting.....