DR Image Sequence Fail

[mike_verta]

Two objects in my scene use locally-referenced image sequences, which render fine, locally. I'm getting errors when Bucket rendering DR to local servers saying the files couldn't be sent because they "don't exist." They do exist, and in fact, the various servers appear to receive/render using them, but they all have errors/blocky regions, missing sections, etc. Transfer Missing Assets is enabled.

Ideas?

Thanks,

_Mike

[SonyBoy]

I've had this issue in the past but unfortunately can't really recall what the solution was. I've never been entirely sure what the point of "Transfer Missing Assets" is, since it's normal to want to have pathing the same on any and all machines you want to render on. If that's how your servers are set up I'd try turning that off (in theory you do not need it turned on). If that doesn't work try messing with the cache settings, or versioning up to force an update on the remote boxes.

[mike_verta]

Well it also appears to be purely a Bucket issue. Progressive renders just fine, though it still sends up the constant warnings about the files not existing...

EDIT: Scratch that. Just failed.

[mike_verta]

I notice that the error reports the image frame number without its leading zeros. For example, a file called "file.00236.png" will attempt to send to the servers "file.236.png."

[Morbid Angel]

Its a guess, as we don't use transfer missing assets option but generally speaking you should have 4 digit padding in the file name, some times it may cause issues if you don't.

[mike_verta]

I do have 4-digit padding in the filename. I just notice that the file name as V-Ray reports it missing, doesn't.

[Morbid Angel]

can you print the path where the file is and also what the output window is showing you?

[waaazoo]

I'm always using file_####.png and the file sequence is in the Maya project folder. It should work well.
But as Dmitry said, maybe you can show us the path input/output.