Deadline 6 - Vray Irradiance MAps

Deadline
1

Edit:
Running 3DS Max 2011 with Vray 2.40.0 AND
3DS Max 2013 with Vray 2.30.0
I’ve searched high and low and have yet to find a solution.
Since upgrading to Deadline 6.0, we are having a hell of a time trying to get Irradiance Map jobs sent to the farm.

Our strategy is to allow only a single job to process each IR map.
Previous workflow told us that within the deadline submission we needed to set the frames as per normal, and save the IRMap Base file and change to it Multiframe Incremental.

When we do this now, our job output shows that it is trying to create VRMap_000.irmap, VRMap_010.irmap, VRMap_020.irmap and so on.
What it should be doing though, is opening VRMap.irmap, calculating the photons, adding them, and moving to the next frame.

But we cannot for the life of us seem to get deadline to take these jobs like that since we’ve upgraded.

Does anyone have any help or a solution?

I’m thinking I’m going to have to draft up a submissions script/render script to do the legwork. But this wasn’t required before. Did we miss something in the update?

Thanks,

2

In Max 2011, there seems to be issue with sticky value on the “Restart Renderer between frames”. We disable this and test and about 80% of jobs are successful.
In Max 2013 however, this seems to have zero effect on jobs.

Max 2013 Throws this to Deadline:

3

Hi,
Unfortunately a slave scheduling bug shipped in v6.0 which causes 3dsMax to “think” it should re-queue it’s task. As a result, things such as VRay IR maps in “multiframe incremental” mode get reset on each frame. This has all been fixed in the v6.1 beta. Interested in joining the beta? Send an email to "beta@thinkboxsoftware.com" to request access or you could for the time being, just calculate your IR maps locally?
Sorry about this, but at least we know what it is and it is fixed :slight_smile:
Mike

4

Mike,

Would this bug also affect machines trying to load IR Maps to render scenes?

This is an attached log from a frequent but random task failure. Some jobs render the first third or half just fine and then machines throw this:

5

Nope, shouldn’t do. The IR maps will still get calculated but will be wrong due to the reset bug. So, the IR maps will load…it’s just your lighting will look wrong when your render slaves render the subsequent Max file using the ‘wrong’ IR map files.

There’s quite a few reasons why one or more of your machines is failing at this point. If you’re wondering, it’s nothing to do with the “customise.ms” file…that’s just the entry point of failure as the Max scene settings are applied. I would need to see a dump of a local slave’s logs combined with log/error job reports from the same period of time, when a job & that slave has displayed this issue.

6

We had the same issues, I wrote a hack to get around this…

viewtopic.php?f=11&t=9743&p=42532&hilit=nth+frame#p42532