05-01-2007, 05:36 PM
vjeko Wrote:Next time this "wrong frame" occurs, please send us the log file (max/network/max.log) from that render node. Mark the frame that rendered wrong, and if possible, see what frame fumefx loaded instead of the one it should have. You said (1 frame earlier than it should). Does this mean that for rendering frame 20, ffx uses the cache for 21? Is it always like that?
In NR, a node is assigned first a job with 1 or 2 frames, than another job with more frames, then again more etc.. maybe some pattern there?
Vjeko
We are seeing this same issue here. In our case, all frames are batched in single frames, i.e. a single machine is rendering a single frame. What we are seeing is that, for example, frame 20 and 21 will both be using the cache from frame 20, making it look like the sim freezes for a frame and then jumps ahead 2 frames. Requeueing the frame generally fixes the problem, as the frames often render correctly the second time. But, as mentioned earlier in the thread, these types of render errors are tougher to catch and very time consuming to check everything that renders.
I will attempt to post the logs here when I can isloate a bad frame, although, since we are using Rush as the queueing system here, I'm not sure exactly what I can get that would be useful.
-nathan