OctaneRender® beta 2.43 (lin/mac/win) [OBSOLETE]

Sat Feb 05, 2011 4:34 pm

Actually it seems the '-r' command-line option (relink) is completely ignored by Octane.

I'd would be nice Marcus have a look at that...

Sat Feb 05, 2011 5:55 pm

hi marcus.

due to high frequent crashes while rendering with cuda3.2. i changed to the cuda 3.0 version:
cant say if anythink works more stable, because if i load the same ocs file with 3.0 mostly all material is lost/mixed up!???
real strange

???
so i stepped back again to cuda3.2, file loads completely correct again. ..but crashes somehow often (longest time up was under 1,5h) sadly not enough for firefly free pathtracing of my scene.

the crashes happen mostly without any notice, just simply closing.
is there any debug info mode/option to be started from terminal?

cheers dave
still on ubuntu64 10.10

Sat Feb 05, 2011 6:15 pm

I'm having odd issues... The error window (attached screenshot) comes up every time I try to run the Cuda 3.2 version, even though I have Cuda 3.2 installed.
When I try running the 3.0 version, it loads...until I punch in my Live user account information. It says "Cannot Connect to Live Server" and retries over and over. It's not my firewall or Antivirus (I still had the problem after disabling both).

Any ideas?

Sat Feb 05, 2011 7:14 pm

gvnwst wrote:I'm having odd issues... The error window (attached screenshot) comes up every time I try to run the Cuda 3.2 version, even though I have Cuda 3.2 installed.
When I try running the 3.0 version, it loads...until I punch in my Live user account information. It says "Cannot Connect to Live Server" and retries over and over. It's not my firewall or Antivirus (I still had the problem after disabling both).

Any ideas?

On Windows you do NOT have to install any CUDA toolkits or drivers. Just install the latest NVIDIA graphics driver (266.58) and it should work without problems.

Cheers,
Marcus

Sat Feb 05, 2011 7:18 pm

yoyoz wrote:Actually it seems the '-r' command-line option (relink) is completely ignored by Octane.

I'd would be nice Marcus have a look at that...

Sorry, but it does not get ignored. Could you please post a scene that shows the problem? I also need the command line that is used to launch Octane, because I can't reproduce the problem here and relinking works as far as I know with the C4D exporter.

One important thing to know: Relinking happens via material names. -> The name of materials must not change between two exports.

Cheers,
Marcus

Sat Feb 05, 2011 7:20 pm

@gvnwst: I have the same issue but on linux. You have internet connection and you can ping live1.refractivesoftware.com? If yes, try to login customer area and deactivate octane. Wait 30 mins and run again. Imho some problem about the licence checking and we get wrong error message.

Sat Feb 05, 2011 7:40 pm

matej wrote:I'm still getting all (most) of my macro to mesh connections messed up, when I add or remove a material in Blender and then re-export. I thought this was solved? I'm using Blender2.49b with the official exporter.

Regarding the first issue: I still need an example that shows the problem, because I can't reproduce it here.

Cheers,
Marcus

Sat Feb 05, 2011 7:50 pm

dave62 wrote: the crashes happen mostly without any notice, just simply closing.
is there any debug info mode/option to be started from terminal?

cheers dave
still on ubuntu64 10.10

Sorry, no debug mode and please don't mix several things together. Let's try to untangle that mess:

cant say if anythink works more stable, because if i load the same ocs file with 3.0 mostly all material is lost/mixed up!???

- What does "messed up" mean? Does it mean that they are rendered incorrectly or that the materials have incorrect settings after loading from the OCS file?
- Are the test scenes rendered/loaded correctly?
- Why do you mean that the CUDA 3.0 build is no more stable than the CUDA 3.2 build? Does it crash, if yes when?
- When you use the CUDA 3.0 build - do you also remove the CUDA 3.2 toolkit and install the CUDA 3.0 toolkit?

so i stepped back again to cuda3.2, file loads completely correct again. ..but crashes somehow often (longest time up was under 1,5h) sadly not enough for firefly free pathtracing of my scene.

- Have you been doing anything else while rendering on the computer?
- Do other scenes (like the test scenes) render correctly and longer than 1.5h?
- What do you see in the terminal if you launch Octane via command line and it crashed?
- Again, could you please send us a scene that makes Octane crash while rendering?

Sorry for the many questions, but if we want to make things more stable, we have to find, isolate and fix the culprit(s) which is impossible without more information.

Cheers,
Marcus

Sat Feb 05, 2011 7:59 pm

abstrax wrote:Sorry, but it does not get ignored. Could you please post a scene that shows the problem? I also need the command line that is used to launch Octane, because I can't reproduce the problem here and relinking works as far as I know with the C4D exporter.

One important thing to know: Relinking happens via material names. -> The name of materials must not change between two exports.

Cheers,
Marcus

I suspect a difference between the 2 builds (cuda 3.0 and cuda 3.2) but I need to investigate furthermore to confirm. Do you prefer I upload the results here or via a PM?

Thanks,
Lionel

Sat Feb 05, 2011 8:31 pm

abstrax wrote:
matej wrote:I'm still getting all (most) of my macro to mesh connections messed up, when I add or remove a material in Blender and then re-export. I thought this was solved? I'm using Blender2.49b with the official exporter.
Regarding the first issue: I still need an example that shows the problem, because I can't reproduce it here.

Cheers,
Marcus

Well, it's happening with my competition scene, which is huge and I can't post it. When I'm finished with it, I'll create a test scene and a reproducible procedure, if I'll still experience any problems.