> For the complete documentation index, see [llms.txt](https://docs.procedural-anatomy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.procedural-anatomy.com/setup/applying-animation/animation-import.md).
# Animation Import
Below are the initial steps to setting up a character with Procedural Anatomy
#### 1. Anatomy Anim Import (Input Mode)
Creating an animation setup with input mode.
This mode is used to set up a single character and animation data.
**Setup Steps:**
As with the example above, create the node setup by selecting\
\&#xNAN;*Procedural Anatomy / Anatomy Create Animation.*
1. **Character File:** Select the file node ***character\_file*** and navigate to the bgeo file that you created in the muscle setup stage.
* Press **Reload Character** if characters animation skeleton does not appear.
2. **Character Name:** If your characters name does not automatically load or you want to change it:
* Toggle on **Character Name Override**
* Set the name of the character that will be used to save the animation file.
3. **T-Pose File:** Select the FBX Animation Import node named ***t-pose***, navigate to, then load the T-pose reference file.
4. **Animation File:** Select the FBX Animation Import node named ***animation***, navigate to, then load the animation file you would like to apply to the character.
* Use **Reload Animation** if the input animation skeleton does not appear.
5. **Animation Name:** If your animation name does not automatically load or you want to change it:
* Toggle on **Character Name Override**
* Set the name of the animation that will be used to save the animation file.
6. **Mapping Attributes:** Select the appropriate mapping based on your character's rig structure and the animation skeleton names.
* If you do not know which one to use, set the display flag to ***anatomy\_anim\_match\_pose*** and view the results. The characters pose will shift to match the t-pose.
7. **Naming Overrides:** Utilize the Character Name Override or Animation Name Override parameters if you need to adjust how the asset names are processed or displayed.
8. **Frame Range:** Define the T-pose start and end frames (or use **Set Frame Range**) to control the simulation boundaries.
{% hint style="warning" %}
To set the **animation start frame**
* Navigate to the timing tab of the FBX Animation Import node named ***animation*** and set the desired animation playback start frame (default is often 1000).
{% endhint %}
#### 2. Anatomy Anim Import (List Mode)
Creating an animation setup with list mode.
This mode manages multiple characters and animations within a single setup, allowing for batch processing. \
\
Create the node setup by selecting:\
\&#xNAN;*Procedural Anatomy / Anatomy Create Animation (list).*
**Setup Steps:**
1. **Character Setup:** Load character assets into the list structure. This works the same as setting the character based on input, however you must
* Provide the character file to the parameter in the character list
* Provide the character name to its parameter
* Use **Reload Geometry** if necessary.
2. **Animation Setup:** For each animation instance in the list:
* Load the file or set the frame for the T-pose and frame range parameters, similar to Input Mode.
3. **List Control:** Use the toggle switches to enable or disable specific character/animation caches for testing or selective processing. Buttons are available to
* Enable / Disable All, or Toggle Caching status.
* Collapse all list entries. This is meant for scrolling through larger lists and keeping a clean UI.
**Data Management (Import / Export)**\
This section handles saving and loading configurations for batch use. This will export the data set you've created in the UI to a file and enable you to load or modify paths as a CSV file in an external editor.
The import/export parameters.
* **Exporting Settings:** Templates are available for both characters and animations. You can export the current UI configuration as a CSV file or directly to a spreadsheet format.
This allows you to modify character lists, animation names, and settings externally.
* **Importing Settings:** Use the imported CSV/spreadsheet data to re-populate and update the toolset's parameters in the user interface.
#### 3. Pose Verification and Refinement
These nodes ensure that the source pose matches the target rig requirements before simulation.
* **Match Pose / FBIK:** These nodes operate by connecting with other Houdini nodes; they do not contain internal settings but facilitate data flow between systems.
* **Pose Matching:** Use the **Anim Match Pose** node to verify if the source and target poses are congruent based on bone angles. If a mismatch occurs, manual adjustments may be required.
* **Point Mapping:** The **Map Points** node helps visualize connections and identify discrepancies between different nodes based on shared naming conventions.
* **Pose Refinement (Rig Match Pose):** To make necessary pose changes:
1. Place the **Rig Match Pose** node after the Anatomy and Match Pose nodes.
2. Disable "Enable Match Bound."
3. Set a rest frame that aligns with the desired output.
4. To apply changes, disable the source data flow and enable the target data flow within the node settings.
#### 4. Skel Solve
This node accepts the
* Character skeleton as input 1
* The animation applied to the skeleton as input 2.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.procedural-anatomy.com/setup/applying-animation/animation-import.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.