We have a character pipeline were we use a master Maya file to derive various LOD’s and versions of the character procedurally. In other words, the master asset gives birth to stripped down versions for the game engine, cinematics, LOD’s, and a MotionBuilder version for our animators.
The process of creating these child versions is scripted to make character updates as painless as possible. All iterations are done on a master Maya file, then in a single click, all the other versions are created and saved to their proper location in the file depot.
Because we use version control ( p4), we have different paths on different computers for our artists. Some may have a P drive, some may be on a C drive. In Maya, we use the project settings to derive were these procedurally generated assets need to live relative to their unique drive letters.
This works well until I get to Motionbuilder. In a single click, my maya script does stuff and sends the character to MotionBuilder. Once in MoBu, I run another script that creates the control rig, characterizes, makes groups, etc.
Issue 1: My MoBu setup tool also recreates Maya set driven keys with relation constraints. I merge in the constraints and connect them procedurally. Up till now, I’ve been putting the constraints file into C: Temp. I would rather put them in my P4 depot so I can administrate them remotely.
Issue2: I would also like for MotionBuilder to automatically save my files in the correct location. So I’m hoping that if I can find something like MotionBuilders scripts folder, I can derive were the file actually goes from there.
I think I could do both with help from Maya by exporting the directory info into a .metadata ( text) file with the MoBu character and having MotionBuilder subsequently look for that info when it’s doing it’s thing. It would maybe be simpler if MotionBuilder had something like a cmds.workspace command.
I hope this makes sense and thanks for taking a minute to read. Super wordy I know.