Hi ,
I’ve tried 2 approach rendering my scenes (Maya Vray Yeti) and submit through Deadline (with I believe the proper limits tag this time ).
1- First approach submitting .vrscene to the spot fleet with Yeti
my renders are going through except no Hair with this warnings:
–> Failed to create object of type “pgYetiVRay”
I would get the same error rendering locally Vray Standalone with Deadline if my env variable is not set properly.
2- Second approach was to submit Maya 2018 scene with Vray, which error out right away for missing :
–> Plug-in, “pgYetiMaya”, was not found on MAYA_PLUG_IN_PATH.
Do I have to set up manually the Spot instances environment variables for Yeti by Building/using Amazon Machine Images (AMIs) ?
or something else I missed in Deadline …?
or AWS Portal Settings Advances Add Environment Variables for used plugins?
Yeti is not installed by default on our pre-configured AMIs. Which means if you want to use Yeti you need to customize our Maya 2018 AMI with a Yeti Installation.
You can setup the env variable on the AMI or use AWS Portal Settings > Advanced > Environment Variables. When using AWS Portal those env vars set when a fleet starts.
still trying with VRay Standalone (with my custom “Use AMI ID” linux)
It is unclear if Yeti is loading properly: "Loading plugins from “/home/ec2-user/Yeti-v3.0.7/bin/libvray_*.so” as my render is failing for missing file.
Comparing the render log that went through with default Spot Fleet and my Custom AMI ID.
After Executing plugin command of type ‘Start Job’
This command transfered my assets:
INFO: Executing global asset transfer preload script ‘/home/ec2-user/Thinkbox/Deadline10/slave/ip-10-128-22-22/plugins/5be2581dc827cf14848851ff/GlobalAssetTransferPreLoad.py’
which i do not have while using my AMI ID, do I have to setup an asset transfer pre-loading for GlobalAssetTransferPreLoad.py to be execute at the start ?
INFO: The include file /mnt/Data/EThinkBoxDeadlineDataBase10ThinkBox_data48aed8ef2717eb7790691c9e250c1437/scene/sceneV18_0001.vrscene does not exist.
Did you base your AMI off one of ours? Meaning, start an instance from one of our AMIs, customize it, and create your own AMI? AWS Portal will only work with our AMIs, which is why those must be the base for customization.
Are you able to provide the full job report?
I’d also take a look at the asset server log to make sure there are no errors attempting to upload files.
I did Follow the documentations, I’ve used one owned by Thinkbox “357466774442”
If this should be running by default, maybe I can create an image with the most recent built.
I’ll get awsportalassetserver_controller.log information later tonight.
Your first instinct was right…
While doing the AMI search all I’ve done was:
“Owner:357466774442” and “VRay” which ended up with only 11 associations. (I picked the most recent)
I redid the search Adding Maya 2018 and got much more appropriate Instance.
Renders are going through but still struggling with vray yeti:
STDOUT: Error: pgYetiMayaVRay::pgYetiVRay plugin doesn’t exsist, please check your VRAY plugin paths.
as much I’ve researched and compare my local environment Var to the one added in advance … along with your links.
I think it might be time to set up a meeting for us to work through this with you. Can you send an e-mail off to support@thinkboxsoftware.com so we can coordinate a time?
I really like, once you’ve setup your Image, it’s very easy to get back to it and make modifications.
I’m getting short in time for my project delivery and “testing”. I tried few back n forth and adding more environments variables… which I had to compensate locally for Yeti.
As for my status: I’ve setup my AMI with the proper “instance” .
Once I setup the Maya and Vray plugins env, it doesn’t complains with Yeti:
Error: V-Ray error: ERROR: Could not create plugin SettingsRTEngine !
I waned to say that, As far as Maya with/or Vray standalone things have been pretty straight forward.
and Thanks Edwin I guess I’m way off from my comfort zone.
I guess I’m way off from my comfort zone.