Hello.
Just installed latest deadline and tried to submit simulation job to my local slave, but there’s some things going on:
Submitter checks 3dsmax phx output, to be UNC or straight (set to real folders), while in phx there’s nice internal flags like $(scene_path), which is not recognized by dl submitter. While this is totally fine, to set that output field so something meaningful, that behavior only correct (imho) when you submitting scenefile with a job. Plain sim submission, where 3dsmax loaded can resolve phx output variables just fine, so there’s no need to straightly check output.
So, how patch that behavior, so dl submitter won’t crash when seeing phx output var, instead of own vars ?
P.S. Just imagine, you need to sim 10 scenes one after another…
Can you please provide the exact steps you used to submit the job?
For example, from your report it is not clear whether you used the Deadline submitter that Phoenix provides, or the Phoenix Workflow that Deadline provides within the integrated 3ds Max Submitter (aka SMTD).
SMTD does not allow you to submit simulations that use the $tokens of Phoenix as they are considered local and are usually relative to the scene’s location, which makes no sense for Deadline or AWS Portal work. So if I had to guess, I would say you used the submitter that came with Phoenix.
Oh. Provided screenshot was captured submitting through phx own routine, but it is using deadline scripts. Phx guys told me that they can’t mod dl files, so I should ask here. But I can’t find the difference between phx submitter and dl native, since error is the same… I’m using dl at home as a handy batch processing tool in free mode, so I don’t have any network nodes or aws I think users, who are using phx will say you a big thanks if submitting for a plain scene batch sims overnight would be a lil bit simplier!
I think users, who are using phx will say you a big thanks if submitting for a plain scene batch sims overnight would be a lil bit simplier!