Shifter: FBX exporter Intergration with Unreal

[SimonBenAnderson]

Reporting

• Add warning on import if the animation layer does not exist, but a Clip is using it. (Import Configuration preset)

Unreal

• Specify where the new FBX files should be imported in Unreal. or have it detect the folder from Unreal.
• List available skeleton definitions, or allow new skeleton definition to be created in Unreal.
• Import the FBX Animation Clips into Unreal.

[SimonBenAnderson]

• ueGear: Get Skeletons
• ueGear: Get Skeletons Meshes
• ueGear: Get Selected Folder
• ueGear: Custom Animation Importer - specify FBX source and skeleton(SK) or SkeletonMesh(SKM) to use.
• ueGear: Generate New SKM, SK from FBX source

[SimonBenAnderson]

Branch in development
ueGear: https://github.com/mgear-dev/ueGear/tree/Shifter_mGear_309
mGear: https://github.com/mgear-dev/mgear4/tree/Shifter_unreal_309

[SimonBenAnderson]

Status update: Working on the inter-application commands.

[SimonBenAnderson]

Commands have been implemented.
Starting UI development

• Working on final Export SKM or Animation button trigger event

[SimonBenAnderson]

Update Partitions Serialisation

• Export and Import serialisation
• UI change, should update the FBX Maya node

[SimonBenAnderson]

• Skeletal Mesh from Maya to Unreal pipline.

Tests for animation export are all working correctly. You can select a skeleton and export the animation, and have it import the skeletal animation in Unreal, referencing the specified skeleton.

Area of concern:
We do not perform any skeletal checks on the skeleton in Unreal and the skeleton in Maya. We are assuming that the user knows that the skeletons should match.

• I have written a bone counter, but not a tree structure verifier. We could but we would need to compile some c++ plugins as the names are not exposed on the unreal python skeletalNode object.

[SimonBenAnderson]

In review
#316
mgear-dev/ueGear#12