[toybox]

Hi, I'm having a problem that's really confusing me. First, resume rendering had previously been working on our setup; I've gotten it to work before but there is a situation right now where it is failing. We've rendered a sequence that has a few frames with lower SL.

First, a systems background: all of our nodes and workstations are running Maxwell 2.7.20. Our workstations are running Win7. Our render nodes are running WinXP.


Now, I attempted to resume a particular frame (SL3) from executing a command line on one of our render nodes, it is failing by erroring out:

'...mxi is an invalid/obsolete mxi to resume. Unable to resume file.'

I opened the same mxi in the render node using maxwell.exe (with gui) and it gave me an error dialog 'Open MXI File Error' saying "...mxi could not be read"

So, next, I tried resume rendering it on my workstation: it worked. Then I opened up the mxi in maxwell.exe (gui) in my workstation, and it opened up just fine.

To test further, I opened up another mxi frame in the same sequence on the render nodes, and it opened up fine, too. (That was puzzling). So, to sum that up:

-there were some mxi files that could be opened in some computers (the workstations) but not in others (the render nodes)
-there were some mxi files that could be opened in both.


I just like to ask what on what situations is this likely to happen, and what can I do to avoid it?

I can provide two sample mxi (one that worked, and one that didn't) if it helps shed light on the situation.


Thanks.

[renbry]

I've had these symptoms a bunch of times - but they're always related to either : wrong version of maxwell on a node, corrupt file or file permissions. Neither of these options seem like they could be happening to you as we've got (probaby) a more complicated way of rendering (too smart for it's own good)

I thought i'd mention those three things anyway, just in case there's a chance of file permissions or wrong versions on a couple of nodes...

good luck,