AWS, 3ds Max, and Phoenix (render fail)

Deadline
1

I finally got some AWS render results (thanks to E.A. and Charles). What looks like the last issue to solve at this point is rendering with PhoenixFD.
Here are today’s results on an AWS test fleet:
Plain vanilla Max job: success.
V-Ray job, frames 0-20: success.
V-Ray job adding in Phoenix, frames 0-20: failure (no rendering started on slaves)
Going by Edwin’s suggestion on another message, I tried to grab the beginning of the slave log file. Looks like the cache files are transferred OK, though I think I missed the very beginning of the log (transfer of cache frames 0000 - 0008).
Any suggestions?
Thx.3dsMax-PhoenixRender_AWS_fail-edited_20181117.zip (6.1 KB)

2

Hmm. It looks like the task was requeued? There should be a re-queue report for that job to see if it was done by a human or by a system. Here’s the smoking gun from the report:

2018-11-17 17:51:16:  0: STDOUT: - 17:51:16.453 INFO: Begin resolve assembly 'PresentationFramework.Aero- 17:51:16.453 INFO: Cannot resolve assembly
2018-11-17 17:51:18:  Scheduler Thread - Task "2_2-2" could not be found because task has been modified or requeued:
2018-11-17 17:51:18:      current status = Rendering    new status = Suspended
2018-11-17 17:51:18:      current slave = IP-0A8011C1    new slave = 
2018-11-17 17:51:18:      current frames = 2-2    new frames = 2-2
2018-11-17 17:51:18:  Scheduler Thread - Cancelling task...
2018-11-17 17:51:18:  0: Executing plugin command of type 'Cancel Task'

I’m not seeing any assets here?

3

Thanks, Edwin. I’ll be doing some testing, post-holiday.