> For the complete documentation index, see [llms.txt](https://docs.motorica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motorica.com/learn/concepts/motion-factory.md). # Motion Factory {% hint style="info" icon="exclamation" %} Motion Factory is an enterprise solution, not available for free-trial customers. Contact Sales for more information. {% endhint %} ## Overview
A popup saying "Welcome to Motion Factory!" with two options for a Simplified or Custom Trail Sets workflow, and UI elements surround the space.

Example of an initial startup project in Motion Factory.

Motion Factory eliminates mocap recording and data cleanup by generating fully-covered locomotion datasets for motion matching systems. Similar to Motion Stage, Motion Factory uses the same [Motion Engine](/learn/concepts/the-motion-engine.md) technology for generating locomotion animations. We recommend testing how animations can be fine-tuned and generated within Motion Stage first before generating batch datasets with Motion Factory. However, Motion Factory includes more tooling for customizing trailing behavior with the Trail Set Manager module. ## Trail Set Manager Module The virtual actor always follows a trail when performing any given animation. Motion Factory, alongside Motion Stage, comes with preset trails for most motion matching use-cases. For more control over these trails, you can use the Trail Set Manager to customize our preset trails or create your own from scratch. Trails are split into Segments with settings and parameters for defining the Segment's Gait (overall speed), duration, turning angle rate, and more. This system allows Trails to encompass any range of motion, from walking breakout circles to jogs that turn into sprints after arcing turns. Unreal Engine users can also capture capsule movement and upload said movement as a Trail in a specified JSON format. Learn more about this feature in Motion Factory's [Pure Root Motion Format](/documentation/motion-factory/reference/pure-root-motion-format.md) reference doc.i ## Workflows There are two workflow options when using Motion Factory: Simplified, and Custom Trail Sets. ### Simplified A fast and streamlined workflow that's built based on our research from motion matching experts, studios known for their motion matching quality, and our own internal testing. This workflow fits most dataset use cases for common motion matching systems. ### Custom Trail Set A fully customizable workflow that allows you to use custom Trails created with the Trail Set Manager module instead of the predefined Trails in the Simplified workflow. ## Finalizing Datasets After using either the Simplified or Custom Trail Set workflow, you'll have additional options to override an animation's Seed, choose whether animations loop, and choose whether to generate animations with foot variations using the Phase Shifting feature. --- # 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: ``` GET https://docs.motorica.com/learn/concepts/motion-factory.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.