1.50.00 DR - slaves render previous scene

[sv]

This is a problem i've experienced for a while, but thought it might be fixed with 1.50.00, but it's not for us. It's so odd.

Distributed Rendering works perfectly, apart from the pretty major fact that the DR slaves render the previously submitted DR job.

(*) It happens from machine to machine throughout our network
(*) We have since had our entire domain rebuilt from scratch (new server, new routers, new domain name and rules etc)
(*) When submitting a job, all the DR slaves will start rendering the previously submitted scene
(*) time doesn't matter - scenes can be rendered that were submitted days or weeks ago, once the machines have been restarted and shut down etc
(*) It's like the saved file for all DR slaves to render from isn't overwriting itself properly - it is stuck on the last scene

Has anyone else ever experienced this?
Is it a permissions thing?, as i'm lead to think something like this as it all works, but it appears to not overwrite the last scene.......or something like this........
My profile is a domain administrator, so i shouldn't have permissions issues i don't think.

(*) It's quite an easy fix for us - just click render, wait a few seconds for it all to connect and start rendering > cancel it > submit again.

[Rt3]

like this?




I see this only in DR via BB. along with:

1. Files over 30mb always encounter problems (this is likely more to do with network than with vray.)
2. The minute you add a camera of any kind you get the image above. If you remove it everything goes back to normal.

DR sent from a workstation works great in any situation so pretty much avoiding BB at all costs.

[sv]

well i get wrong buckets like this, but it's the strangest thing; and it happens as a DR job submitted through backburner as well.

What ever the previously submitted DR render is (whether it was submitted 5 seconds before or two weeks before after pc shutdowns and 3dsMax reboots) my workstation will render the correct buckets, but all other slaves will render the previously submitted DR job.

It's as simple and as strange as that.

(of course i can just start a render, stop it, and submit again and all is fine, but it's annoying)

[Rt3]

So this happens to you from both BB AND your workstation? perhaps sp1 will take care of this. I'm just glad to have it working consistently from the workstation this time around...

[u4ia]

Great!

I thought I was the only one getting it! Mine started the same and the only way I found to fix it was to save the file with a completely new name and resubmit it. I have to save the file without doing any more work and then render it. Most of the times it worked, but then DR stopped completely so I'm thinking of updating to 1.5 Final to see if it helps.

I've only used DR directly from the workstation and not via BB.

[RErender]

Do any of you use "increment on save"?

[vlado]

This appears to happen when you turn on the "increment on save" feature of 3ds Max.

Best regards,
Vlado

[sv]

ahhhh.... good, this is what i was thinking about last night......

yep, i religiously use incremental save.
i was thinking it was related to this, as i noticed that i had two vray_client_scenes in the folder:

C:\Documents and Settings\Steve.Ellis.CLUSTA\Local Settings\Application Data\Autodesk\3dsmax\9 - 64bit\enu\temp


Is there going to be a fix for this, or is it something you can't fix?
<perhaps an overwrite for the incremental feature when submitting to DR?>

[Rt3]

I do not use "increment on save"...

[tom schuelke]

i only had similar things, when i forgot to save one time my scene befor i press render via dr.

so one time saving before rendering mayby solves it.


Tom

[3ddesign]

I've had the same problem when rendering without saving the scene first.

C

[sv]

vlado,

could you just confirm if this is considered a 'bug' and you guys will look into it, or if it's just expected behaviour and we shouldn't use incremental save.....?

thanks.

[vlado]

It depends on whether there is a way to get/set the state of the "Increment on save" option programmatically. I didn't find a function for this in the SDK, so I have asked at the Autodesk Developer Network. If there is a way to disable this option before saving the file for DR and then enable it again, then the issue can be solved. If not, there is nothing that we can do.

Best regards,
Vlado

[sv]

thanks vlado -

as always, above and beyond!

[vlado]

So it looks like there might be a way to do this properly; I'm trying now.

Best regards,
Vlado