Version 3.00 - R1.1 (25.05.2016) Tweet

[aoktar]

Problem found.

When c4d background object is on, The image is not saved properly in picture viewer / saved blank.
Take a look at the images attached, one (Crappy) with background object on, and one standard.

It's about alpha processing with background image+render buffer. Will be fixed.

Thank you!

(just saw that i didn't post the images mentioned, sorry for that)

Actually it's fixed, but i'm checking a few more things.

[Lambe]

Hi
I'm using Octane on a Mac Pro and an iMac 27. Both are going faster with 3,0
But especially the iMac became fluid now. Changing camera with the live viewer running was painful,
I had to wait a few seconds between each action. the change is impressive and this machine, which is not the fastest, is now usable comfortably.
I do not really know why...
but congratulations for this update.

Previous version was always debug builds until now. With latest update we have two boost. One from plugin side and second is from Octane's geometry compiling. Guys from Otoy spend some effort to make the multi-processing better.
But i think you have also some driver problems. We can't do nothing i suppose. Just try to keep "render priority=LOW and selected".

With the same drivers and cuda update on the same scene, 2,25 version is almost impossible to Use on my iMac (GTX780M), while everything runs fast with 3,00 Beta2,0
This to say that this Update is really great and to congrats the team.

[Proxell]

Hello Aoktar,

I've tested v.3 b2 at different scenes. I know that the V3 core is different from the V2, but In V2 I can upload all my cards to 99% via priority and in V3 cloudn't.
Its float from scene to scence in about 79% to 94%. Does it architecture specificity or am I doing something wrong?

[Huv]

Hi,
had a crash while rendering with Octane (beta2), since then, no way to relaunch c4d...
Only solution was to delete octane from the plugin menu...

[aoktar]

Hi,
had a crash while rendering with Octane (beta2), since then, no way to relaunch c4d...
Only solution was to delete octane from the plugin menu...

Can you give me a better information as always expected?

[aoktar]

Hello Aoktar,

I've tested v.3 b2 at different scenes. I know that the V3 core is different from the V2, but In V2 I can upload all my cards to 99% via priority and in V3 cloudn't.
Its float from scene to scence in about 79% to 94%. Does it architecture specificity or am I doing something wrong?

Hello,
V3 is working different than V2. Having more clever on balancing the cores on works as i know. So that's not a matter to don't use all %100. Compare results for render times. It's significantly better performer on most scenes.

[Huv]

Unfortunately i do not know what else to say, i have no crash reports.
Nothing except the fact that after crash, when re-launching, c4d is not passing the "Initializing plugin" window...
I have to kill the app to be able to do something.
I''ve tried re-installing the plugin, but no way. If i do not delete the "octane" folder in the plugin folder, c4d does not restart...

[zoppo]

Did you try this:

try to delete this file to reset your session:

Windows:
%APPDATA%/OctaneRender/otoy_credentials

Linux:
~/.OctaneRender/otoy_credentials

OSX: (you may have to use Finder's Go->Go To Folder... and type "~/Library/OctaneRender" - without the quotes - to get to that folder)

~/Library/OctaneRender/otoy_credentials

[dinf]

Yes, you are right Chriz, thats what I meant. Thanks.
Every Objekt wich I put under the new 1-Volume Generator will be moved with its Axis to one side and couldn't be moved nor resized.

Btw., did you check the old setups?
Thanks as well!

Hey Ahmet,
...
About the new volume object: one simply drags any object below the volume, is that right?
If so, is there a way right now to center or position this object in the "domain"?
Mine will always move to an edge.

you're welcome. I have changed volume object for having two different behavior. 1-Volume generator 2-Vdb loader. I think old setups are corrupted due this. I'll check it.
Vdb sequences are very big for quality outputs. So i haven't consider to upload it. Someone can re-simulate via houdini scene file.
I couldn't get the last question. Any images?

Hi aoktar,

i guess this is wthat he meant. I got the same behavior here. I know, disabeling the sphere will make it invisible. But the Fog seems to be centered at the edge of the FogVolume

shifted.jpg

[Proxell]

Hello Aoktar,

I've tested v.3 b2 at different scenes. I know that the V3 core is different from the V2, but In V2 I can upload all my cards to 99% via priority and in V3 cloudn't.
Its float from scene to scence in about 79% to 94%. Does it architecture specificity or am I doing something wrong?

Hello,
V3 is working different than V2. Having more clever on balancing the cores on works as i know. So that's not a matter to don't use all %100. Compare results for render times. It's significantly better performer on most scenes.

Ок, I see.