OTOY Forums

i have a scene with 300 frames, exported to octane - everything is right. But, after every 10 frames rendered with octane a window popped up "can´t launch octane..."

What is the Problem, why the Connection is broken?

I had a good dreamy Sleep, because i thought, i have a finished Animation in the morning...



Thanks...

Are you using Mac OS 10.5? Someone reported a problem like this before a while ago, but I think we never figured out, what's going on here. If not, what OS and which C4D are you using? Can you reproduce the problem?

Cheers,
Marcus

abstrax wrote:Are you using Mac OS 10.5? Someone reported a problem like this before a while ago, but I think we never figured out, what's going on here. If not, what OS and which C4D are you using? Can you reproduce the problem?

Cheers,
Marcus

fast answer, thanks.....

i have osx 10.6 and c4d 11, in the past i had rendered some animationsequences without this problem, but this time it is like i wrote....

now in this moment the longest duration was 20 frames - after this the same window popped up....

it is not a big catastrophe, but i must watch everytime at my Monitor for eventually broken processes..... and a overnight rendering is not possible.....

lassinger wrote:

abstrax wrote:Are you using Mac OS 10.5? Someone reported a problem like this before a while ago, but I think we never figured out, what's going on here. If not, what OS and which C4D are you using? Can you reproduce the problem?

Cheers,
Marcus

fast answer, thanks.....

i have osx 10.6 and c4d 11, in the past i had rendered some animationsequences without this problem, but this time it is like i wrote....

now in this moment the longest duration was 20 frames - after this the same window popped up....

it is not a big catastrophe, but i must watch everytime at my Monitor for eventually broken processes..... and a overnight rendering is not possible.....

Is Octane launched although the error message pops up? Or is Octane really not launched?

Cheers,
Marcus

abstrax wrote:

lassinger wrote:

abstrax wrote:Are you using Mac OS 10.5? Someone reported a problem like this before a while ago, but I think we never figured out, what's going on here. If not, what OS and which C4D are you using? Can you reproduce the problem?

Cheers,
Marcus

fast answer, thanks.....

i have osx 10.6 and c4d 11, in the past i had rendered some animationsequences without this problem, but this time it is like i wrote....

now in this moment the longest duration was 20 frames - after this the same window popped up....

it is not a big catastrophe, but i must watch everytime at my Monitor for eventually broken processes..... and a overnight rendering is not possible.....

Is Octane launched although the error message pops up? Or is Octane really not launched?

Cheers,
Marcus

hi marcus,

it happens between two frames, that means one frame is rendered and than octane window is closed and than octane loading the next frame..... and in this short "between" i have this problem...

todays history:

3 frames rendered
error
next 7 frames rendered
error
next 20 frames rendered
error
next 9 frames rendered
error
next 5 frames rendered


.
.
.
.

lassinger wrote:hi marcus,

it happens between two frames, that means one frame is rendered and than octane window is closed and than octane loading the next frame..... and in this short "between" i have this problem...

todays history:

3 frames rendered
error
next 7 frames rendered
error
next 20 frames rendered
error
next 9 frames rendered
error
next 5 frames rendered

Ok, so how I understand it, the plugin launches Octane, but doesn't detect the successful launch of Octane. If that's the case, it's probably a timing thing: At the moment the plugin waits for 1 second until it verifies whether the process was launched successfully. It seems that sometimes this time is not enough. I think, I will change it to check every 1/2 second for up to 10 seconds (i.e. 20 times) until the plugin gives up. That hopefully should solve the problem.

Cheers,
Marcus

abstrax wrote:

lassinger wrote:hi marcus,

it happens between two frames, that means one frame is rendered and than octane window is closed and than octane loading the next frame..... and in this short "between" i have this problem...

todays history:

3 frames rendered
error
next 7 frames rendered
error
next 20 frames rendered
error
next 9 frames rendered
error
next 5 frames rendered

Ok, so how I understand it, the plugin launches Octane, but doesn't detect the successful launch of Octane. If that's the case, it's probably a timing thing: At the moment the plugin waits for 1 second until it verifies whether the process was launched successfully. It seems that sometimes this time is not enough. I think, I will change it to check every 1/2 second for up to 10 seconds (i.e. 20 times) until the plugin gives up. That hopefully should solve the problem.

Cheers,
Marcus

sounds very good!!! Thank You!!!

best, Lars