Page 1 of 1

[ISSUE] Runing free slave node with licensed version

Posted: Sat Dec 19, 2009 6:40 pm
by rendigo
This is probably not too important - in my case it was a bit disturbing though: for a few weeks I have been running alot of tests with the free version of Indigo just to figure out different things and only during the last week I activated my license and started 'real' work. Unfortunatly I forgot to kill all of the slave nodes that were running in free mode. Then after starting several renderings for a client and waiting a considerable amount of time to judge the results I noticed strange effects and first I figured it was some bug in my scene/camera setup or whatever. Only very late I realized that in every production rendering I had 1 smaller copy of the rendering showing up - so obviously that node running in free mode still contributed to the rendering process.
If I may suggest it would be better to make the slaves running in free mode do a check before contributing, otherwise large amounts of time can be wasted by the non informed (like me ;-).
Thanks in advance for considering!

Re: [ISSUE] Runing free slave node with licensed version

Posted: Tue Feb 23, 2010 2:39 pm
by BluShift
I like this idea. Although I doubt I'll ever purchase a license, I think this could be very important on large render farms if they are migrating from a test environment to a production environment.

Re: [ISSUE] Runing free slave node with licensed version

Posted: Tue Feb 23, 2010 2:59 pm
by benn
Good idea. Added to the tracker.

Re: [ISSUE] Runing free slave node with licensed version

Posted: Tue Feb 23, 2010 6:40 pm
by galinette
Keep the possibility to use free nodes with a licensed master! The only case where it should not, is when the resolution is too high.

Etienne

Re: [ISSUE] Runing free slave node with licensed version

Posted: Tue Feb 23, 2010 7:32 pm
by OnoSendai
I've already added a check that the buffer from the slave is the same size before merging it into the master buffer. Not quite the same as the request, but will still help avoid busted renders :) Will be available in 2.4.1.