[kami]

what I don't understand is, that the network render has been completely rewritten not long ago to improve it.
I don't know about before( since I never used it) but it is not working at all in a way you could expect it to work. the mxcl itself works perfectly, almost 0% errors (chrashes, etc ...) which is really great, so why is there this big discrepancy.
could somebody of nextlimit please chime in? is this a problem which could be caused by any operating system settings that I'm not aware of? or is it a problem that's been working on?

[brodie_geers]

I've wondered the same thing Kami. I was quite excited when I heard about the extensive network render work that was done. Sadly, I haven't seen much difference and am still having the same issues I did in the past. At the very least, it would be nice if the restart nodes option on the Monitor would work just as a manual restart. Currently I can't see it's use (sure it'll restart, but only if nothing's wrong? Seems more like a Reset or Purge would be more accurate).

Every time I need the node restarted it means getting ahold of IT and having them do it at their convenience. As a result I don't often use my node, and I've got a second node that goes completely unused because it would have to go on another workstation and I don't want to bother someone to keep restarting software for me.

-Brodie

[fuso]

Exactly the same here, only times 9... Our IT guys used to be good friends of mine. Now I need to buy a lot of pints on Friday
night, just to keep them happy...

[brodie_geers]

I feel you. That's part of the reason I'm hesitant to use the network too much. I'm currently in pretty good with them (although they wouldn't admit it, they love being able to order high end computer stuff almost as much as I love using it ), but it's a tenuous balancing act with IT guys. I pitty the 3d artist who isn't in the good graces of his IT guys.

-Brodie

[frosty_ramen]

i just had an odd network issue also, after 52 renderings (that worked just fine) the 53rd shows that all nodes are rendering but in reality 2 nodes say that they are connected for scene file reception, and have not changed in 24 minutes.

[numerobis]

yes, a working "reset node" would be helpful

btw. would it be possible to have an option to reuse the dependencies sent by last job? maybe with a pop-up like the file override question.
This could be really time saving for short tests on a job with many textures that don't change...

[fuso]

@ numerobis: I think it does reuse the dependencies as long as the other job is sent straight after and using the same settings.
At least I realised that here with my setup when watching the progress and it seemed to have skipped sending the files again
and went straight to voxelisation. I can imagine that this is because the current version does not delete the dependencies and
I'm not sure what I'd prefer if I had a choice. Maybe a little interface would be a good idea indeed.