Page 1 of 1

Frustrating rendering animations "license activation drop"

Posted: Thu Dec 16, 2010 9:03 am
by PeterCGS
Im rendering out animations overnight, and every now and then I came back to the office, just to see that only 10% of the nights batch has been rendered out, due to something funky going on with the internet connection, greeting me with a license activation pop-up in the morning :(

Please fix, so that you can start render with octane without it checking the license every 5 min... Very very annoying :(

/Regards Peter K

Re: Frustrating rendering animations "license activation drop"

Posted: Thu Dec 16, 2010 9:16 am
by abstrax
Yep, it's noted. There won't be a solution in the next release, but maybe we have a solution in v6, that doesn't need too many changes in the exporter plugins. Radiance already has a good idea :)

Later - probably after 1.0 final - we will look into workflow and integration try to come up with a better and more direct integration into the 3D apps, but this has to wait until the core things have settled.

Cheers,
Marcus

Re: Frustrating rendering animations "license activation drop"

Posted: Thu Dec 16, 2010 9:19 am
by abstrax
Hmm, maybe - as an intermediate solution - we can add a command line parameter, that makes Octane try to connect infinitely, without any dialogs and user interaction, until a connection is established. I will have a look into that.

Cheers,
Marcus

Re: Frustrating rendering animations "license activation drop"

Posted: Thu Dec 16, 2010 9:42 am
by PeterCGS
Thanx Marcus! Would be awesome if there was a switch to start Octane in "render" mode.. :)

Re: Frustrating rendering animations "license activation drop"

Posted: Thu Dec 16, 2010 10:05 am
by abstrax
PeterCGS wrote:Thanx Marcus! Would be awesome if there was a switch to start Octane in "render" mode.. :)
You will still need an internet connection, there is no way around it. In the future we might change Octane, that it doesn' get closed, when one frame has been finished, i.e. the internet connection can then go away as long as Octane stays open. But for now, the only quick-fix is to make Octane try and try again, until it succeeds - without an error dialog and without waiting for some user interaction. But I have to look at the code first.

Cheers,
Marcus