Stabile version 1.01 (SDK 1.20.3) **** 17.01.14 ****

[pulsegroup]

pulsegorup: have you a win7 system to check it? Maybe a problem on some win8.1 systems during activation. Some people worked on W8.1's

Hi - no win 7 system but I tried it out on the mac side (10.8+ and 10.9) and works fine - ideally would like it to run on the win 8 side though.
Does it activate for all user accounts? I may try to create a clean user and activate that way - I'll let you know what happens.

[aoktar]

pulsegorup: have you a win7 system to check it? Maybe a problem on some win8.1 systems during activation. Some people worked on W8.1's

Hi - no win 7 system but I tried it out on the mac side (10.8+ and 10.9) and works fine - ideally would like it to run on the win 8 side though.
Does it activate for all user accounts? I may try to create a clean user and activate that way - I'll let you know what happens.

which mac version did you tryed? I was removed 0.99 from MacOs

[amtberg]

I got a crash trying to load a scene that was saved with assets, where the scene had some downloaded materials and one offline material. I understand that the offline material wouldn't load (?), but there should be a warning or something instead of a crash. Bug report attached.

[aoktar]

I got a crash trying to load a scene that was saved with assets, where the scene had some downloaded materials and one offline material. I understand that the offline material wouldn't load (?), but there should be a warning or something instead of a crash. Bug report attached.

no, it shouldn't give any error. If you put the materials to scene which has not been depended to liveDB manager no longer. maybe a bug. Can you reproduce same crash? We have used this system about 2-3 weeks long, without major problems. Problem can be related with material previews
And, any crashes will not be occured if we could detect every problem

[brasco]

Still getting the startup crash,

0.99f
R15.037
Win 8.1
R331.82

Unfortunately, I can't go back too far with the NV drivers or I get compatibility issues with other software. If I have a break in work I'll try and go back to an old driver to test. Sadly that means I can't use Octane, which is annoying as it's so awesome! I'm sure it'll be solved in time.

cheers
brasc

[SVITAdmin]

ok. Back to testing. 99f seems to lock up C4D whenever i open an octane file on our PCs

why? It's very great for everyone

ok, i updated the nvidia drivers and all seems well with 99f now on PC win 8.0

[aoktar]

Ok, for all users who has startup problem on R15

Please be sure you removed all previous octane.dll, octane.dat, nvapi.dll and don't use the vnapi.dll to c4doctane directory if you can't start.

Still i cannot figure problems. But i did a search on forum, driver 331.65 seems to have some problems. please try 327.23 or something. Also i notified all reports done by Win8.1 users, and i haven't this system for weekend. If you can't resolve the problem, i'll do some tests for next days.

But my idea is that can be a driver or win8.1 problem. If you have possibility please test it on a different Os except win8.1.

Also users who can operate without any problem on R15 and Win8.1, please note this with specs

[dinf]

Any other reply for last version? I'm curious about is it working or has problems on startup or others?

Found two different issues with the 99e and f versions.
In 99e, directly after opening an old scene file while octane was updating the materials, closing C4D with no bugreports. Probably because of using the partial installs over 098a instead over the complete 096 installer. This was gone with 99f complete installation.
The second one is about using the "Lock resolution" button. In 99e I got Cinema to freeze after clicking the button some times, fast. In 99f installed after that there was an odd behaviour using the lock. The picture was cropped very wide with only a few pixel height and didn't want to go into defined resolution after switching. I'll try to reproduce that one.
Right now, Cinema closed immideately after opening a new scene with Octane Live Viewer, holding a non Octane scene in background. You got PM.
Didn't check the new DB browser.

All in all Octane feels a bit more tipsy in R15 than in R14 to me. And all in all, you fixed a lot of issues and brought in some good stuff. I like the new centered display in the Live Viewer and the DB functions looks good also!

[aoktar]

Dinf, Wha's your OS and drivers? are you sure that you have not old octane files? we have tested since a few weeks on mostly win7 systems without any problem. Also resizing lag, check the gpu priority

Please be sure you removed all old octane.dll, octane.dat, nvapi.dll from Cinema 4D root and plugins\c4doctane directory and also remove the vnapi.dll from c4doctane directory if you still can't start.

Still i cannot figure problems. But i did a search on forum, driver 331.65 seems to have some problems. please try 327.23 or something. Also i notified all reports done by Win8.1 users

But my idea is that can be a driver or win8.1 problem. If you have possibility please test it on a different Os except win8.1.

Also users who can operate without any problem on R15 and Win8.1, please note this with specs

LAST ONE: i see lot of plugins, please remove all and give a try

[dinf]

Hi aoktar

Dinf, Wha's your OS and drivers?

See bugreport I pm'ed you. It is win7 pro 64 and driver 327.23 as you mentioned.

are you sure that you have not old octane files?

Yes. I only use c4doctane folder since my first Octane use and delete one folder before installing a new one. Exception is when installing the partial files we sometimes got from you. In this case I drag&drop the new partial files directly onto the old ones. Wich worked well until I dropped 99e onto 98. I corrected that immediately after the first error.

we have tested since a few weeks on mostly win7 systems without any problem.

Yep, very mostly. As said, all in all I'm hot on using Octane. I wouldn't have posted if you wouldn't have asked for it