> For the complete documentation index, see [llms.txt](https://docs.overdare.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overdare.com/manual/studio-manual/asset-and-resource-creation/skeletal-mesh-import.md). # Skeletal Mesh Import ## Overview Importing a skeletal mesh (an FBX file that contains a mesh, skeleton, and animation) into OVERDARE Studio automatically creates a character structure in the Level Browser that can play animations. When you select a file, the Import Settings window opens, automatically analyzes the file, and displays errors/warnings in real time if any issues are found. After reviewing the analysis results, you can click the **Import** button to complete the import. For how to import other assets—such as static meshes, textures, or audio—and their options, see the document below. {% content-ref url="/pages/bS79pIBVkO3rjcUR9Zhi" %} [Asset Import](/manual/studio-manual/asset-and-resource-creation/asset-import.md) {% endcontent-ref %} ## Skeletal Mesh Import ### Opening the Import Settings Window In the top tab area of OVERDARE Studio, select the Home tab, then click the Import button and select the FBX file you want to import.

If the selected FBX file contains a skeleton (i.e., it is a skeletal mesh), the Import Settings window opens automatically. In beta, Import Settings can only import FBX files that meet all of the following conditions. * The file must contain a mesh, skeleton, and animation. * The mesh must be a single mesh. Files containing multiple meshes will produce an error and cannot be imported. Merge all meshes into one in an external tool and re-export the file. Static meshes without a skeleton are imported through the existing mesh import options window. ### Layout The Import Settings window consists of the following areas.

Area	Description
Top bar	Displays the path of the file being imported. You can select a different file using the Browse button.
File Structure	A tree view showing the elements contained in the file in a hierarchical structure. Selecting an item switches the option panel on the right to that item's settings. You can collapse the entire tree using the Collapse All button.
Issues	A list of errors/warnings found during file analysis. Always displayed at the bottom left.
Option panel	A settings panel whose content changes dynamically based on the item selected in the tree view. Options such as Rig Type and Skeleton are explained in detail in the Rig Type and Skeleton section below.
Bottom buttons	Contains the Cancel button and the Import button.

### File Structure (Hierarchy Tree View) Displays the elements contained in the file (root model, mesh, texture, bones, animation clips, etc.) in a hierarchical structure. Element types are distinguished by icons. * Clicking an item selects only that single item (single selection); the option panel on the right switches to that item's settings. * By default, only the root level is expanded and child items are collapsed. Currently, all elements contained in the file are imported together. Excluding individual elements from the import is not supported. #### Issue Indicators Problems found during file analysis are shown as icons on the corresponding item in the tree view.

Status	Display
⚠️ Warning	A yellow warning icon is shown on the right side of the row.
🔴 Error	The entire row is displayed with a red background, and a red X icon is shown on the right side of the row.

If a node is collapsed and hides its child items, the parent node displays a single icon representing the most severe issue among its children. ### Rig Type and Skeleton #### Rig Type Cards Rig Type is displayed as a card-style UI. One of the three cards is automatically selected based on the file analysis, and in beta it cannot be changed manually.

Card	Auto-Selection Condition	Description
None	No bone structure in the file	Imported as a static mesh without bones. (Static mesh, no skeleton)
Custom Skeleton	A non-ODA bone structure is detected	A freely structured rig, such as for NPCs or monsters.
ODA Rig	An ODA bone structure is detected	OVERDARE's default character rig. Handled using the engine's built-in ODA skeleton.

#### Skeleton Field The Skeleton field displays "Use skeleton from FBX" and uses the skeleton included in the imported FBX file as is. In beta, you cannot specify a different Skeleton asset. #### ODA Rig Auto-Detection Criteria The importer determines a file to have an ODA structure when it meets all of the following conditions.

Detection Item	Criteria
Skin-influencing bone names	Must include all 16 of the following: LowerTorso, UpperTorso01, UpperTorso02, Head, LeftUpperArm, LeftLowerArm, LeftHand, RightUpperArm, RightLowerArm, RightHand, LeftUpperLeg, LeftLowerLeg, LeftFoot, RightUpperLeg, RightLowerLeg, RightFoot.
Control bone names	Must include at least one of the following: Root, IKHandRoot, IKHandGun, IKLeftHand, IKRightHand, IKFootRoot, IKLeftFoot, IKRightFoot, ThirdPersonCamera.
Bone hierarchy	LowerTorso must be the spine root and must be located under Root.

> If the above conditions are only partially met, the file is detected as Custom Skeleton. Since Rig Type cannot be changed manually, if you want to import it as ODA Rig, modify the bone structure in an external tool so that it meets all of the conditions above, then import the file again. ### Issues Panel An area that is always fixed at the bottom left. It remains visible even when there are no issues. #### Status Display

Status	Display
✅ No issues	A message indicating there are no issues is displayed.
⚠️ Warnings only	A warning count badge is shown in the header, and the list of warning items is shown in the body.
🔴 Errors + warnings	Error count and warning count badges are shown side by side in the header; error items are listed first, followed by warning items, in the body.

Each issue item shows a description of the problem along with how to resolve it. Clicking the element name button shown in an issue item moves the focus to that item in the tree view. Conversely, clicking an item with an issue in the tree view also selects that item in the Issues panel. > ⚠️ **Warnings** do not block the import. You can review the details and proceed with the import as is.\ > 🔴 **Errors** must be resolved before you can import. #### Common Errors and Warnings

Type	Message	Details and Resolution
🔴 Error	Multiple mesh objects were detected in this file.	The file contains more than one mesh. Only a single mesh is currently supported, so merge all meshes into one in an external tool and re-export the file.
⚠️ Warning	Bones with no skin weights were found.	Bones with no skin weights were found. These bones do not deform the mesh. If they are unnecessary, remove them in an external tool and re-export the file.
⚠️ Warning	The file's axis orientation does not match OVERDARE's coordinate system.	The file's axis orientation does not match OVERDARE's coordinate system. The object may face an unexpected direction after import. Check the World forward / World up values in the option panel.
⚠️ Warning	One or more objects have unapplied transforms (rotation or scale).	One or more objects have unapplied rotation or scale transforms. The object's size or orientation may look different than expected after import, so apply the transforms in an external tool and re-export the file.
⚠️ Warning	Some vertices are influenced by more than 4 bones.	Some vertices are influenced by more than 4 bones. On import, only the top 4 most influential bones are kept automatically, so the mesh deformation may differ from the original.

### Automatic Detection and Real-Time Validation When the Import Settings window opens, it automatically analyzes the file and sets the main options. Changes to options are re-validated in real time.

Detection Item	Automatic Handling
Bone structure	Automatically sets the Rig Type. (None / Custom Skeleton / ODA Rig)
Animation data	Displays the list of animation clips in the tree view.
Non-triangulated polygons	Shows a warning and automatically triangulates them.
Bone skin weights/influence count	Detects bones with no skin weights, vertices influenced by more than 4 bones, and so on, and shows a warning.
Axis orientation/transform	Detects coordinate system mismatches and unapplied transforms (rotation/scale), and shows a warning.
Joint naming rule violations	Shows an error on the corresponding item in the tree view and provides a suggested fix.

## Level Browser Placement When you import a skeletal mesh with Import Settings, a character structure that can play animations is automatically created in the Level Browser.

Sub-Object	Description
Skeleton	The imported skeleton.
Animation clip	The animation clip included in the file. (e.g., Fly)
Mesh	The mesh responsible for the character's visual appearance. (e.g., dragon)
HumanoidRootPart	The root part responsible for the character's movement and physics.
Humanoid	The Humanoid object that controls the character's state and animation.

This structure behaves the same as an existing Humanoid-based character. This means you can use existing APIs that rely on Humanoid and HumanoidRootPart (movement, animation playback, etc.) as-is. ## Usage Example Imported animation clips can be played through the Humanoid's Animator, the same way as existing character animations.

## Notes * Currently, only a single mesh is supported in beta. If a file contains multiple meshes, merge them into one in an external tool and re-export the file. * If errors (🔴) remain, the Import button is disabled and the file cannot be imported. Refer to the resolutions shown in the Issues panel, fix the file in an external tool, and import it again. * The maximum importable polygon count is 30,000. You can check the current polygon count and limit in the Polygon count field of the option panel. * If a bone (joint) name does not follow the naming rules (for example, if it contains non-Latin characters), it may be flagged as an error. Bone names cannot be changed in Studio, so you must edit them in an external tool such as Blender. * Import Settings is a beta feature, and its UI and behavior may change in future updates.