I’ve been trying to work through a rendering error when using Phoenix FD on an AWS farm. Here’s the latest from Svetlin N. at Chaos support:
" Hmmm, I’m afraid I am out of ideas. There seems to be something going wrong with the automation that transfers the data, but not sure what exactly - according to the logs Phoenix does not read the cache files at all. Have you already tried contacting the AWS guys?
Meanwhile, we are trying to get our license running so we can try and reproduce the issue here, but seems like it’s gonna take some time…
Svetlin Nikolov, Lead Phoenix FD developer"
I’m bringing it up here in case anyone has ideas. If not, I have to move to using a VPN on Azure, most likely.
My most recent AMI is a custom image built from Deadline (Windows) base, using Max 2019 sp2, VRay Next 4.1, and PhoenixFD 3.1.200. Sample render comparison and a section of the Asset Server log are attached. The image is from testing with a VRay Volume rather than a Phoenix Volume, but the results are the same in both cases: the cache data seems to be transferred, but not read.
AWS_asset_server_phoenix-jobs_2018-12-14.zip (23.6 KB)