Not to be a pest, but a Maya version has long been listed as “planned”. Is there any morsel of an update we might get as to when it might appear? We are among the large set of studios using Maya as our primary hub DCC, and it would be a very important update for us.
Well, the problem is that it is the most difficult by far to support. Most Maya users are also animation users, which means we have to solve multiple problems to meet expectations. Because of the complexities, we’ve been focused on bringing in static data from apps where that is more the norm. The good news is that we’re now solving for animation data in the coming months (in Datasmith API) and this at least gives us basic animation (rigid-body) support. Epic does support Maya and animation data via FBX and USD workflows, but this doesn’t include the complex material mapping that Datasmith does (because Game workflows don’t need it). If you’re working with animation data (especially characters) then we already have what you need.
So, we thought we’d get to Maya sooner, but we didn’t. Maya isn’t on the Datasmith roadmap at this time, but that could change. We do poll people with our release surveys and we ask what workflows we should support, Maya isn’t that high on the list, so we are trying to listen to the majority about their needs.
I am also interested in the Maya integration. Currently I just FBX things to Maya and then do a custom script for the camera animation which compensates for the two 90 degree rotations. This is then a separate FBX export to Unreal. Finally I build the materials manually one by one as they are assigned to the meshes through the FBX by default. Over time I am building a material library which will make the process of material assignment go quicker.
If there was a way to make this process a few steps easier that would be great. Currently we use Redshift. The main lineup issues I see to match scenes are…
The hdri environment adding to the skylight and its reflection and GI alignment rotated correctly.
Camera orientation. (Maya always seems to need a custom export that does a rotation offset.
3 Lightmap resolution accuracy per mesh as well as proper GI intensity through the lightmap contribution to match Maya redshift bounces and amounts.
Reflection box and reflection Captures setup
Area light falloff and intensity amounts being closer to 1 to 1 from Maya Redshift to Unreal.
While I see your point about Maya being animation focused, We would be perfectly happy having a static Datasmith workflow that is on some level of parity with the other DCCs while animation is being worked out. We animate in Maya, but we also do everything else too. Translate cad, model, uv… it’s many studios’ hub for lots of things. Animation isn’t required up front for it to be a useful tool.
Totally understand that it’s not a trivial ask, but I’m pretty surprised it sits so low on the priority list. I wouldn’t have expected that. That makes me sad So what DCC (besides Max) sits higher on the priority list? Max is just not an option for us.
The risk with Maya is that it would suck up a ton of development and you still wouldn’t like the results. There are some third party efforts.
Mirror:
PiStage:
Perhaps those might help you?
We are working on Cinema4D right now and animation support. After that, we can see if Maya makes sense, but there is no commitment to it (from a Datasmith standpoint, obviously we are very committed to support it via our LiveLink, FBX, USD and other Game and VFX-based workflows).
The risk with Maya is that it would suck up a ton of development and you still wouldn’t like the results. There are some third party efforts.
Mirror:
PiStage:
Perhaps those might help you?
We are working on Cinema4D right now and animation support. After that, we can see if Maya makes sense, but there is no commitment to it (from a Datasmith standpoint, obviously we are very committed to support it via our LiveLink, FBX, USD and other Game and VFX-based workflows).
[/QUOTE]
Is there any update on whether or not we will be seeing Maya being supported? I read your post above and you mentioned some Polls about how Maya isn’t a popular software in your surveys. Are you sure those are accurate numbers? Everywhere I go, especially in animation and vfx pipelines Maya is the go-to. Cinema4D is huge which is good. But im a Maya guy, so I have been aching for an update on Datasmith. My whole studio at work is even waiting for it actually. I appreciate the “Send to Unreal” function but its very messy.
My two cents here, but Unreal has always been a game engine, so perhaps those polls are being skewed a bit by those its prime industry? I just don’t want Maya to be overlooked. Especially in animation. Im sure many people see UE4 as the future of animation. It just needs more and more support for it, including with Maya! Really hope you can reconsider prioritizing it.
I am from Detroit, and a most of the studios here use Maya & Vray for rendering CGI for the automotive industry. It’s only a matter of time: real time raytracing is the future. I know they will be looking into the real time raytracing in Unreal, and how to export the cars into Unreal. Trust me, you WILL want to include a Maya to Unreal datasmith exporter. There are a ton of Maya users!
Unreal Studio would be fine for Maya without animation. I thought it would be possible to just disable the animation option as it would be better than nothing.
Agreed, im surprised that its not up there on the list, I wonder if its just the users that utilize Maya are not being vocal enough for supporting it? Maya is industry standard, especially for CGI, Film and animation. Even games. I wouldnt mind just having static data first, but would definitely expect animation data to be implemented at some point too.
Sorry for bumping this, but I’ve also been closely following Datasmith development since it’s announcement in the hopes that you guys will announce a Maya exporter, just give us the bare bones, expectations aren’t high for it being feature rich! Please!
Hrmm so they poll the users that get the new releases to find out what they would like next, but most of them came with a software pipeline in mind that did not include Maya, as a result, causes Maya to go farther down the list of requested updates to compatibility. Was there is some deal made with C4D for favorable treatment? Can we persuade Autodesk to do the same? I need my MayaTV! :))