Version 2.05.0 - Updated on (14.08.14)

[decade]

Thanks for your hard work Aoktar. All the new features are working for me now.

[aoktar]

Thanks for your hard work Aoktar. All the new features are working for me now.

nice to hear. Everybody is well? No sound since last one hour, i'm starting to worry

[FractalMotion]

I think people having fun since one hour Aoktar

Thank you for all your amazing job !

[dinf]

Everybody is having fun

My post seems a kind of flubbing away, so my question again: can you say something about point 2 and 3, render passes and volumetrics? I know it is not fair to ask now, you have enough to work on, but I have to ask

[aoktar]

Cool. Thanks to all guys for interest and comprehension. I'll need some time to fix current/reported problems.

2.0 will get some updates for Render Passes. Currently i have a development version with all needed passes. I heard the volumetrics will be targetted in some time period.

Also, i'll continue to write After Effects plugin after this madness. This is other news for you.

[slash]

It is working great for me. Thank you!

[dinf]

2.0 will get some updates for Render Passes. Currently i have a development version with all needed passes. I heard the volumetrics will be targetted in some time period.

Also, i'll continue to write After Effects plugin after this madness. This is other news for you.

Great to hear, all of it!

Displacement:
- eg. loading a noise, it makes visible steps and spikes. Is there an easy way to get rid of them?
- loading a texture does not show up in live viewer info lines as a loaded map. So it is processed before?
- loading a 32 bit floating tif or hdri does not show any response. Is that impossible to use right now?

[SVITAdmin]

I gotta admit, having to wait for IT approval and purchase is making me insane. I'm envious of all you freelancers out there right now.

[macray]

long time passed since I've been here the last time, but today I upgraded, installed 2.0 and the plugin 2.00.22

I got 2 things that don't work as intended I guess:

1.
whenever I start Cinema I get an error message for Octane while loading the plugin. (please see below this post)
after confirming the error message I can start c4d and use Octane.

2.
Octane shows up in main menu > plugins > c4dOctane with 4 options to choose from
AND
Octane shows up in main menu > Octane with 3 options to choose from

Why are these 2 ways to start Octane related stuff different?
Why are there 2 ways to call up Octane?
Which one is the correct place to start it from?
Could you give a short explanation why these 2 locations are necessary or is this possibly related to the error message I get starting Cinema?

[TonyBoy]

I went to download the plugin and saw nothing for C4D Ver 12. Will one be available soon? I can't imagine how busy you must be.