Maya to Unreal: Static and Skeletal Meshes

[antirotor]

Feature

This adds support for publishing Skeletal meshes for Unreal. Just select geo and joint root and publish.

Setup

First make sure you have maya2unreal template set:

And set the IntegrateAssetNew to use it in Template name profiles:
project_settings/global/publish/IntegrateAssetNew/template_name_profiles

Have skeletalMesh and staticMesh in the families list of Hero integrator if you like:
project_settings/global/publish/IntegrateHeroVersion/families

Next make sure you have correct Subset name profiles set:
project_settings/global/tools/creator/subset_name_profiles

You can configure hits about joint group here:
project_settings/maya/create/CreateUnrealSkeletalMesh

Testing

Say you have asset like this:

If you select Gun and run Unreal Skeletal Mesh creator, it will create instance like this:

jnt_org is joints root that is auto-picked using hints pre-configured in creator settings (see above). Top node (Gun in this case) must be name of the asset.

Publishing this will create fbx following unreal naming conventions - SK_Gun_v001.fbx with correct hierarchy. This has support for variants - different kinds of model using the same rig. You can create another Skeletal Mesh instance, just add _Scope to the variant name and it will create skeletalMesh_SK_Gun_Scope adding additional (selected) geometry along the joint group. This allows for multiple fbx file with the same hierarchy to be published and then easily switched inside the Unreal (most useful with the Hero versions).

Fix

Fixing bugs in unreal static mesh extraction.

There were few bugs. One was that extraction didn't considered scenarios with only one mesh. There was also flawed logic behind cleaning of nodes that were created during extraction and also the family name was shortened just to staticMesh.

Testing

Run the following code to create test scene and publish. You might need to disable Unreal Axis validator.
Expected result should be fbx file with two meshes in root, one called S_{asset} and UCX_{asset}.

Code to create test scene:

import avalon.api
from maya import cmds
from openpype.lib import get_creator_by_name


asset = avalon.api.Session["AVALON_ASSET"]                                   
root = cmds.createNode("transform", name="mesh_GRP")
geo_root = cmds.createNode("transform", name="geometry_GRP")
coll_root = cmds.createNode("transform", name="collision_GRP")
box = cmds.polyCube(sx=5, sy=5, sz=5, h=5, w=5, d=5)
cmds.polyTriangulate(box, ch=True);
cmds.parent(box, geo_root)
dup = cmds.duplicate(box, name="UCX_{}_1".format(asset), ic=True)
cmds.parent(dup, coll_root)
cmds.parent(geo_root, root)
cmds.parent(coll_root, root)

cmds.select(root, r=1, noExpand=True)
creator = get_creator_by_name("CreateUnrealStaticMesh")
asset = avalon.api.Session["AVALON_ASSET"]
container = avalon.api.create(creator, 
                              name=asset, 
                              asset=asset,
                              options={"useSelection": True})

---

⏫ This PR supersede #2764

[ynbot]

Task linked: OP-2795 Maya to Unreal - Skeletal Mesh

[m-u-r-p-h-y]

it is failing on static mesh name collision

b'Processing Unreal Static Mesh Name'
// Error: pyblish.ValidateUnrealStaticMeshName : Collision object name doesn't match static mesh name
// Error: pyblish.ValidateUnrealStaticMeshName : UCX_ball != UCX_ball[]*
// Error: pyblish.plugin : Traceback (most recent call last):
//   File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
//     runner(*args)
//   File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\validate_unreal_staticmesh_naming.py", line 143, in process
// RuntimeError: Model naming is invalid. See log.
// Traceback (most recent call last):
//   File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
//     runner(*args)
//   File "<string>", line 143, in process
// RuntimeError: Model naming is invalid. See log.
b'Processing Maya Units'

[m-u-r-p-h-y]

the previous error was caused by testing on old code in the wrong branch.

my bad

now it publishes the fbx with no error.

thx

it works as expected