Beta 0.5.9 (SDK 1.17 ) (old version)

[aoktar]

ok sorry, but if you have installed older standalone so can give problem? is it right?

Yes, if you are working on Mac OS and were using Octane standalone, but didn't update the standalone to any of the recent release candidates it may be that you have to de-activate and then re-activate your standalone license. That's because the machine identification has slightly changed to solve a problem with Mac Pros which have two identical Ethernet adapters.

The de-activation and re-activation can be done via the our web interface on http://render.otoy.com/account/octanelive.php

No need to install the standalone version.

I cannot found but installing last standalone resolve activation problem for some users

[abstrax]

I cannot found but installing last standalone resolve activation problem for some users

You shouldn't have to do this. Please let us know, when the problem pops up again.

[RK-art]

The new versions 0.5 and 0.5.9 causes my C4D R14 (32 and 64 bit) under Win7 64 bit to crash immediately while the startup procedure of R14 (loading the plugin). The previous version (0.3.4) worked flawless.
The crash also happens with no other plugins beside C4DOctane in the plugins folder.
I have the most current C4D build.

[aoktar]

The new versions 0.5 and 0.5.9 causes my C4D R14 (32 and 64 bit) under Win7 64 bit to crash immediately while the startup procedure of R14 (loading the plugin). The previous version (0.3.4) worked flawless.
The crash also happens with no other plugins beside C4DOctane in the plugins folder.
I have the most current C4D build.

did you remove old octane data from everywhere?
can you remove from layout octane windows first. After reinstal and try

[3Dfreak]

The new versions 0.5 and 0.5.9 causes my C4D R14 (32 and 64 bit) under Win7 64 bit to crash immediately while the startup procedure of R14 (loading the plugin). The previous version (0.3.4) worked flawless.
The crash also happens with no other plugins beside C4DOctane in the plugins folder.
I have the most current C4D build.

It sounds like you didn't follow the installation instructions for the plug-in. You HAVE TO copy three files from the libs64 folder in you c4dOctane folder to the Cinema 4D R14 ROOT folder. Also make sure every time you update the c4dOctane plugin. You delete the previous c4dOctane plugin folder first. Then put the updated plug in the plugins folder. Do not simply overwrite as this leaves the potential for problems. You can overwrite the three files in the Root directory. But you should do that every time you update the plugin. As well!

I hope this helps!

RJ

[RK-art]

Oops, yes, you are right.
Sorry and thanks.
I didn't overcopy the new files to the root directory.
Problem solved.

[3Dfreak]

Oops, yes, you are right.
Sorry and thanks.
I didn't overcopy the new files to the root directory.
Problem solved.

Glad it helped!! Happy rendering!

RJ

[aoktar]

Oops, yes, you are right.
Sorry and thanks.
I didn't overcopy the new files to the root directory.
Problem solved.

Glad it helped!! Happy rendering!

RJ

No longer no need to copying any libs files to c4d root directory. Plugin use any appropriate files from libs dir.

[RK-art]

OK, tried it with deleting the 3 files from the root folder and it works also fine.
So, the problem was that the 3 old files weren't deleted from the root folder.

[nehale]

Can someone please tell me how to get rid of this kind of noise, I'm rendering with PT and it seems to get more as time goes