RTT submission as independent tasks?

Deadline
1

hi guys!

so we managed to get past our 3dsmax Render To Texture submission problems, thanks for the help (viewtopic.php?f=11&t=11536#p50624). we’re continuing our evaluation of the software and the step that we’re on now is throwing large files with lots of RTT objects in them through the queue. the file that i’m using to test is just over a gig in size. it has 2667 objects in it, 221 of which have RTT settings and need to be baked out.

the files make it through the network, all the RTTs get submitted, and the farm starts chewing on it. so far so good. the wall that i’m hitting now is that the RTT request is seen as just a single task in a single job, and one slave picks it up and starts working on them in series. no decision is made about parceling out the various RTT requests to more than one machine. topping that all off is that if 3dsmax dies, it starts all the way over from the beginning. i won’t get into max stability issues here, but suffice to say that the job has yet to complete successfully despite being left to run overnight.

so my question – or my appeal, really – is this: is there a way to make a single job submission with multiple RTT objects burns look like a frame-range submission instead, so that each RTT burn gets farmed out to a machine? or the ability to batch X RTTs together?

any help greatly appreciated – we’re really trying hard to get away from backburner. :smiley:

thanks in advance,

-tony.

2

Hi Tony,
We are looking at overhauling our support of RTT later this year. Our current implementation needs some TLC and the Autodesk RTT macroscript has limitations as well, when trying to work with a 3rd party render management software. We would love to get your feedback when we start looking at it. In fact, any and all feature requests for RTT improvements; things you love; things you hate, would be most welcome! What is your ideal / utopia for RTT implemetation?

I have a feeling this will be possible once we overhaul our implementation. I know this is probably not the answer you were hoping for. Unfortunately with so many really good client feature requests, sometimes the odd few don’t quite make the cut for the next immediate release. However, this doesn’t mean we’re not listening! :wink: