Choose your operating system:
Windows
macOS
Linux
This page contains tips, tricks, and best practices for working with the FBX content pipeline in Unreal Engine 4 used by artists at Epic Games.
Static Mesh Workflow
-
Export the mesh to an FBX file from your 3D application.
-
Common export settings used by artists at Epic include:
-
Smoothing Groups enabled
-
Tangents and Binormals disabled
-
Preserve Edge Orientation enabled
-
-
-
Import the FBX file using the Content Browser in Unreal.
Useful Links
Skeletal Mesh Workflow
-
Export the mesh and skeleton to an FBX file.
-
Select the items you want to export (mesh and joint chain root) and 'export selected'.
-
Common export settings used by artists at Epic include:
-
Smooth Mesh disabled
-
Smoothing Groups enabled
-
-
-
Import the FBX file using the Content Browser in Unreal.
Useful Links
Animation Workflow
-
Export the animation to an FBX file.
-
Select the items you want to export (joint chain root, mesh if desired) and 'export selected'.
-
Export settings:
-
Animation enabled
-
-
-
Import the FBX file as an animation into the Content Browser .
Useful Links
Morph Target Workflow
-
Export the morph target(s) to an FBX file.
-
Select the items you want to export (mesh with blendshapes/morpher modifier) and 'export selected'.
-
Export settings:
-
Animation enabled
-
Deformed Models/Deformations enabled - all options
-
-
-
Import the FBX file as an animation into the Content Browser .
Useful Links
Naming Schemes
Epic's artists typically follow the following naming schemes for exported files:
-
Static Meshes: SM_ <PackageName>_<AssetName>_<Index>
-
Skeletal Meshes: SK_ <PackageName>_<AssetName>_<Index>
Using a project-wide naming scheme makes it easy to organize and identify asset files.
However, the concept of a "Package", that many long time Unreal users will be intimately familiar with, has changed dramatically in Unreal 4 versus previous incarnations. Package files now only contain one file, and the directory structure of the game defines the various levels of what you would find in an old .upk file. See Assets and Packages for more information.
In this image, the StoneBox is in a folder called Meshes, much in the same way UE3 would have a package (Game) with a grouping (Meshes) that contains the asset (StoneBox).
Scene Management
Epic's artists usually store similar assets in a single file. For example, for a Static Mesh that has three different states: normal, damaged, and broken; all three are in the same file. However, each mesh is exported as a single FBX file.
It is easier to have a clean "export" file which is the mesh bound to the skeleton. This mesh will only be used for exporting. The rig is built from this file, but saved into a separate rig file.
Separate rig file.
Each animation is usually stored in its own file as well so that it is simple to keep track of all the different animations in the file system.
Renaming Content in Unreal Editor
You can rename any object in the Content Browser either by selecting the item you wish to rename and hitting F2 or by Right-Clicking it and selecting Rename . This will highlight the object's name in the Content Browser and allow you to type in a new name, just like editing a file name in Windows.
You will probably get a notification about the undo cache. This is normal as the object in the cache is listed under the old name and it will need to be cleared as to not to cause an issue later.
Useful Links
Whole Scene Import/Export
This is useful for exporting out cameras that have been created in Matinee, or vehicle paths that have been animated in Matinee, as well as all of the information is needed to recreate a cinematic in a 3D content creation package. After tweaking is done inside a 3D content creation package, it can then be exported out as a FBX and imported back into Unreal Engine 4.
Exporting out from Matinee.
FBX is currently the only supported export type for Export All so just give it a name and click OK.
From within the Matinee interface, you can also import FBX data (presumably after tweaking has been done in the 3rd party package).
