MayaCmd & RedShift issue on cloud instances

Deadline
1

Hello,

Is the MayaCmd plugin supported with cloud instances launched from AWS Portal?

I’m currently setting up AWS Portal with a Maya/RedShift production and ran into an issue when rendering jobs with the MayaCmd plugin. Having difficulty troubleshooting. I wanted to confirm if this problem is a bug, or a limitation of the MayaCmd plugin. OR an honest PICNIC and I missed something in the docs/forums. :slight_smile:

Onprem Environment:
Deadline 10.1.6.4
Windows 10
Maya 2020 w/ RedShift 3.0.16
Cloud Environment:
AWS Portal for orchestration
G instance w/ custom AMI (updated RedShift to 3.0.16 on Thinkbox ami-0dca78b9ca7d2de96 which came with mayaIO 2020 and RedShift 2.6.51 originally)

Rendering the same scene with MayaBatch plugin works without issue. Here are the TestLogs.zip (12.3 KB).

One line from the MayaCmd log that I noticed but have not been able to figure out…
/home/ec2-user/Thinkbox/Deadline10/slave/ip-10-128-109-123/jobsData/5ed159b54b26370950133f3b/thread0_tempgQLI80/redshift_maya_test_v007.ma line 8: RuntimeError: file <maya console> line 1: Unable to dynamically load : /usr/redshift/redshift4maya/2020/redshift4maya.so

I’ve confirmed this particular file exists and has open permissions on the instance. I even ran another test instance using the provided ami from Thinkbox and got the same results: MayaBatch works, MayaCmd produces the same error.

I should note, there is no particular reason for using MayaCmd other than a couple of artists either forget to check or intentionally uncheck the use MayaBatch option on the submitter. I would much rather force use MayaBatch as I understand it has some extra sauce for render optimizations. I’ve only ever used MayaCmd for trouble shooting scene errors as they occur.

I would appreciate any thoughts or advice. Let me know if there is further information I can provide.

Thank you in advance,
-Alex

3

That error is from Maya failing to have already loaded Redshift. MayaBatch force loads plugins, where MayaCMD does not. Which would explain the difference you’re seeing.

Also MayaCMD can’t do path mapping inside of the scene file, which is really important in AWS Portal as I’m sure you know.

If you want to be sure artists are submitting using the batch plugin, you might want to look into a Custom Sanity Check to make sure that the batch plugin is getting used.

1 Like
4

Hey @Justin_B,

I apologize for not following up sooner. I really appreciate your insight on the MayaCmd RedShift error. As well, thank you for clarifying the importance of using MayaBatch over MayaCmd for cloud instances. I had completely forgotten about the path conversions! :weary:

I did have a CustomSanityCheck script setup but didn’t have it configured to set MayaBatch, this has been added now.

Thank you again,
-Alex

1 Like