I’m just sorting Vray on our AWS Instances, but noticed that on the precalc jobs that render, none of the Vray .vrmap & .vrlmap files get sent back.
I’ve enabled it to write out all files and elements on the precalc job as a test (instead of just the cache files), and all files and elements get transferred back to me once the job is complete - minus the .vrmap/.vrlmap files.
I have added those filetypes to the asset server in Output File Extensions, and the job output lists the vray caches with the rest of the output files.
I’ve attached a slave log, but I can’t see anything wrong.
The transfer system tracks any files which are written to the storage volume (which lives on the Gateway when using Windows machines).
So, since the render log shows this is on Windows and 3DS Max that means they should be sitting on the Gateway somewhere. The job report is showing that not only are your exceptions being set:
I believe this might be an issue within the Central Controller and grabbing the logs from that might be good. You should be able to get that by right-clicking your infrastructure to get the CloudWatch logs. If you’ve Stop/Started the infrastructure you’d have to throw another render through I believe.
I’ll pass this to one of our developers to get more background on the issue as well.
I’ve messaged you the test file and submission script.
Not sure if it’s true, but I’ve done a few more test renders and it looks like it might be using the cache files that are on the remapped drive on AWS - I don’t get any errors on loading the cache files from the slaves, and the assembled tile image doesn’t look iffy at all.
We definitely want those textures to be on that virtual drive as that’s where they’ll be available… It’s just a matter of finding out why they’re not loading properly. What makes you think that they are being accessed from that location?
It looks like this is an issue with our path mapping system. When I rendered your job, the vrmap and vrlmap files were written to the instance’s C: drive, instead of the E: drive where they need to be to get sent back. Such path transformations are supposed to be handled by our path mapping system. Unfortunately I am not very familiar with that system, so I will forward your issue to someone who knows it better.
It’s not an urgent problem to fix for us, as I can just send the precalc jobs to our local slaves to process - Then hopefully that will get sent along with the main render job to the correct location when complete.