Motionbuilder Python

[Merlino Riviere]

Iimagine you have plans to talk about UI creation in python? This is one of the things in the sdk I feel is the most non-intuitive at the moment, so if you have any tricks about this, it would be appreciated.

Does anyone know how to access the selected takes via python script? I have a script I wrote that I would only want to run on selected takes. Ideally I would like to find the selected takes and iterate over them. Conversely, I would settle for a way to manually run a script itself only on the selected takes. Any info would be appreciated. Thanks!!!

Thanks Francis. That totally helped. I actually solved it before you responded to me in a less efficient, newb way haha. I iterated through the components looking for the class_name to be FBTake. Your solution is much cleaner. I changed my code with it and it works great.

The ShotGrid engine for Motion Builder contains a standard platform for integrating ShotGrid Toolkit Apps into Motion Builder. It is light weight and straight forward and adds a ShotGrid menu to the main menu.

If you already have this item installed in a project and you want to get the latest version, you can run the update command. You can either navigate to the tank command that comes with that specific project, and run it there:

Newer versions of MotionBuilder need an additional configuration within the software_paths.yml file. The software_paths.yml file is available when you have taken over your configuration. Ensure that your reflects the following paths for MotionBuilder to launch, with your specific path, version, and application information added:

If you have access to the ShotGrid Pipeline Toolkit, you also have access to the source code for all apps, engines and frameworks in Github where we store and manage them. Feel free to evolve these items; use them as a base for further independent development, make changes (and submit pull requests back to us!) or simply tinker with them to see how they have been built and how the toolkit works. You can access this code repository at -motionbuilder.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

When Kaydara released Filmbox a long time ago, the software was litteraly 20 years ahead.That's the only software which anticipated the needs of the future: real-time playback, smooth transportation of animation (keys) between characters and softwares,node-based rigging, animation layering, auto-rigging...then later non linear animation, python/C++ scripting and so on. Today everyone is using FBX as animation transport and everyone is happy with it.

Despite all of that,I have the strong feeling that Autodesk is giving up on Motion Builder, replacing it with Maya. Think more of the creature in the horror movie 'The Thing' where one head of the creature is eating the other one: Autodesk (Entertainment) is the creature, Maya, 3DS Max are its 2 heads.

When @Sergey Solokhin (Neil3D) told me that all the juice of Motion builder is being absorbed by Maya, he really had a point. With his amazing plugins (paint tools, VR rendering,...), he didn't succeed to convince Autodesk to enhance Motion Builder like crazy. When @Štěpn Kment (who did some great stuff too) is saying that Motion Builder is more and more crashy, he has a point too! Today, one of the key new feature in Motion Builder 2018 is the availability to select and edit multiple tangent handles in the same time: I mean, SERIOUSLY? Is this the thing? Is it really justified to release a new version every 6 months for that?

Autodesk was about to give up his (adopted) baby already a few years ago when James Cameron showed up with Avatar and all his crazy previz , real time material and said that Motion Builder was a great piece of software. Today, his team(s) went to Giant and everyone is considering traditional engines to display real-time stuff.

The truth behind all this is that the core team of Kaydara left and no one is able to update the old tools anymore (the 'Actor' solving didn't change in 15 years for example and somehow Ikinema had nailed it, based on incomplete native tools). The sad thing is that Autodesk is reproducing the same errors with Maya. The software became such a white elephant today that it will become less and less upgradable (I mean deeply, not putting patches on patches, plugins on plugins), probably until the end of it. I don't even talk about 3DS Max (and 2 softwares owned by the same company to do the same things, how long will it last? Remember Softimage XSI?). At least, some softwares like @Blender or Akeytsu (@Nukeygara) are trying new things: of course success is not guaranteed but it's still emulating and that's what matters. And maybe in 20 years we would say they were 20 years ahead.

Maya won't be able to do everything and won't never become as powerful as Motion Builder, not because Motion Builder is best or whatever, simply because Motion Builder is (was) DEDICATED and DESIGNED to animate (both keyframe and mocap). Motion Builder is dead but we still are a strong community, remember that somehow even James Cameron was a part of it...

3a8082e126