AWS Thinkbox Discussion Forums

Maya 2019 support

Deadline
#1

Just wondering if there is maya 2019 support ETA?

#2

Same. Just came here to search for this topic again. Deadline is the only thing holding up our migration here.

Thanks,

Ricky

#3

I’ll let the folks here know. You’re both logged internally. So is @mlager8 for this post:

#4

Hi there, wondering if there’s any news on this?
thanks very much

#5

Just got merged in yesterday. Will ship with SP24. No release date on that one just yet, but you can sign up to be notified.

#6

Thanks for the update, Edwin! :+1:

#7

signed up… hope that update will be live soon. redshift added support for 2019, now only waiting for deadline as well :slight_smile:

#8

Hello! I appear to be in the same boat. I’ve upgraded to 2019, and just today was using it with the latest Redshift build and decided to submit a job. I didn’t think twice because the Deadline shelf was there (came over from my previous settings?) and then when I fired up Deadline Monitor, I notice the job was suspending and failing onto the next frames. I assume i’ll need to re-install Deadline once it supports 2019?

Thx!

-Steve

#9

Just wondering if there is any ETA on maya 2019 support please?

#10

Please any updates on this would be great? I stupidly assumed this wouldn’t be a problem and moved a project over to Maya 2019 and deadline is the issue now. :expressionless:

#11

Is it really not possible to edit a few config files on the current version to get DL to open up a config slot for Maya 2019? There’s probably no actual changes in batch commands or anything like that. I’d be happy with a hack while waiting for official support.

#12

yea I was kinda hoping for at least that fast hack as it was done before with other versions, while waiting for official version upgrade :slight_smile:

#13

Deadline 10 Service Pack 24 will deliver support for Maya 2019. No ETA, but its getting closer.

#14

Is there a lot of stuff that needs to be tweaked for Maya 2019 specifically? I can kind of get it to work just by editing MayaBatch.param, but I’m having issues on slaves other than my workstation which have Maya installed locally. The correct process is launched from the network location, just like 2018, but quits right away, not sure why yet.

Is “closer” a couple of days, or weeks? :slight_smile: If the latter, I definitely need to get this going by hacking it.

#15

Turns out it was easy to add 2019 to the current Deadline version, but Maya 2019 itself don’t want to run from a copied network folder anymore, so it has to be deployed on each machine locally. I’m guessing something changed in Maya 2019 in regards to this.

#16

There was a discussion on the SSA Slack channel about getting Maya 2019 running end of last month.
https://studiosysadmins.slack.com/messages/C1WCS4ZV5
DM me with your email address if you need an invite/add.

#17

Hi Arvid,

Would you mind describing the process you used to get Deadline to submit 2019 jobs? I changed the MayaBatch.param file to include 2019 paths, but I’m not quite sure how to update the submission dialogue to include 2019, and what other steps maybe necessary.

Thanks for any help you could provide!

#18

Deadline 10.0.24.2 is now released which includes support for Maya 2019. Here’s the release notes.

So if you’re able to upgrade that might be the easier route to go.

Cheers
Morgan

#19

Thanks mepp, that seems to work with 2019. However, I am having issues with arnold standin files referenced into the scene. If I create a new standin, in scene, the render completes, but if the standin is referenced in with a namespace, the frames fail out, with the following error before failure:

2019-03-13 18:34:26: 0: STDOUT: 00:06:24 7768MB ERROR | [ass] can’t read in C:/Users/renderfarm/AppData/Local/Thinkbox/Deadline10/slave/wsrender3/jobsData/5c89adf12102c48d7824f5e6/thread0_tempFCmOc0/GreatWall_terrainLayout_REF:greatWall_standinShape/GreatWall_terrainLayout_standin_A.ass: No such file or directory
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 7572MB | creating root object list …
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 7572MB | node initialization done in 0:01.07 (multithreaded)
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 7572MB WARNING | aborting render pass setup: received abort signal
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 7572MB |
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 7572MB | releasing resources
2019-03-13 18:34:27: 0: STDOUT: 00:06:25 6823MB | Arnold shutdown
2019-03-13 18:34:27: 0: WARNING: [mtoa] Failed batch render

I have narrowed the issue down to namespaces, if I import the file into the scene it still fails as long as the namespace remains. Once I remove the namespace it succeeds.

Is there a workaround for this? Thanks for any help with this issue

Privacy | Site terms | Cookie preferences