software:
Maya

Script Language:
Python

what it does:
– copies mocap data ( imported as fbx file) on rigged characters

how it does:
– opens the fbx file
– cleans up the names
– imports the rigged characters and tries to automatically match up the height of the character
– copies the animation from mocap onto the animation controllers
– removes all the mocap data
– animation now can be tweaked/cleaned/enhanced by the animators
– prepares the file for export

notes:
– mocap files were pretty messy, naming wise and structure wise
– a mocap file could have between 1 and 11 players with multiple footballs, the script is handling all the cases
– occasionally the user had to get his/her hands dirty ( like properly naming/duplicating the footballs)

bdFootballUtils from Bogdan Diaconu on Vimeo.

Software:
Softimage

Scripting Language:
Python

what it does:
– keeps track of all the weapon files ( rig files, model files, 1st person view and 3rd person view animation files ) for a FPS type of game

how it does:
– reads the weapon list from an XML file
– based on the above, creates all the paths needed to grab the file names
– uses several filters: character, weapon type, file type
– based on the filters, displays all the files sorted by date ( the most recent on top of the list)

video:

bdWeaponAdmin from Bogdan Diaconu on Vimeo.

Software:
Softimage

Scripting Language:
Python

what it does:
– setups everything needed in regards to adding a new weapon in a FPS type of game

how it does:
– creates the weapon project ( Softimage)
– creates the folder structure for the weapon: the one for the weapon rig, the one for the 1st person view animation of and the one of the 3rd person view animation
– adds the weapon to the XML file that keeps the weapon list
– imports all the weapon parts as obj’s and assigns individual shaders per part
– forces a naming convention
– creates the general skeleton for a weapon and skins the dynamic meshes to those
 

bdWeaponUtils from Bogdan Diaconu on Vimeo.

Software:
Softimage

Scripting Language:
Python

what it does:
– saves poses using XML files

how it does:
– on the first run the user has to setup a global path for the poses and to add characters
– those above will be saved as user preference and automatically used upon new runs. They can also be modified and the preferences will be updated
– with a character open, the user will have to select the desired controllers
– when the pose is saved, the plugin creates a XML file to store the pose, a synoptic file ( basically an HTML file) that holds the ‘image button’ for the pose and finally a thumbnail preview used in the synoptic file.
– updates the UI with the created pose

PS. Was slightly painful to code the UI due to the dynamic refreshing of it. Also, saving the preferences using softimage’s preferences system is not really friendly, proabably would have been better to save them as an XML file too. Maybe in another iteration

bdPoseLibrary from Bogdan Diaconu on Vimeo.

© 2017 Moving Pixels Suffusion theme by Sayontan Sinha