Key takeaways
- Morph Target preserves active cloth arrangements: Importing a new pose as an OBJ Morph Target gradually translates avatar vertices in 3D space, allowing the physics solver to calculate garment drape during the transition instead of dropping cloth around an abruptly swapped mesh.
- Mesh structural identity is mandatory: Source and target OBJ files must share the exact same mesh structure and vertex topology. At least two OBJ files with identical mesh structure are required to morph an object without mesh distortion or simulation breakdown.
- Transition pacing prevents simulation failure: Morphing interpolates along the minimum distance between points rather than rotating skeletal joints. Setting a higher Transition Frame Count slows the transition, giving the solver time to simulate cloth motion. For extreme pose shifts, staging the process with interim pose OBJs prevents garments from falling off.
- Select/Move adjustments resolve local collisions: When simulation activates, the interface automatically provides the Select/Move tool to pull pinched cloth segments away from avatar collision surfaces and adjust fabric placement after reaching the final pose.
Avatar import modes and garment preservation
In digital character production and costume creation, changing an avatar's pose after constructing and draping a complex garment is a standard workflow challenge. When digital clothing is simulated on a character in an initial T-pose or A-pose, the cloth geometry depends directly on the spatial coordinates and collision boundaries of that specific avatar. According to the Marvelous Designer OBJ Import/Export documentation, arrangement points and fitting options function properly when imported OBJ avatars are in a standard T-pose or A-pose.
Understanding how Marvelous Designer handles external 3D geometry is critical when modifying a character's stance. The Marvelous Designer 3D File (OBJ) Import/Export manual defines several distinct import behaviors when bringing OBJ files into an active workspace:
- Open Avatar / Replace Avatar: Loading an avatar through standard open or replace operations replaces the original avatar with the incoming object. Because the existing collision reference disappears or abruptly alters coordinates, active garments collapse or intersect heavily with the newly replaced geometry.
- Add Avatar: Importing an OBJ with the Add command places an additional object entity into the workspace alongside the existing avatar.
- Morph Target Import: Loading an OBJ specifically as a Morph Target morphs the original avatar object into the target object over a user-defined transition frame count.
TABLE / Scroll horizontally for all columns →
| Stage | Process | Solver Action |
|---|---|---|
| 1. Base Setup | Dressed avatar stabilized in initial T-pose or A-pose | Baseline cloth drape and collision established |
| 2. Target Import | Load matching mesh OBJ as Morph Target | Reads target vertex coordinates and transition frame count |
| 3. Interpolation | Avatar vertices translate across configured frames | Dynamic cloth solver calculates drape in accordance with movement |
| 4. Final Settling | Target pose achieved | Remaining folds and hems settle naturally under gravity |
As documented in the Marvelous Designer Change Pose by OBJ Morphing guide, vertex morphing maintains the avatar's final form without distortion. Because morphing gradually changes one object's appearance into another, the active garment simulates in accordance with the moving surface, preserving realistic draping and eliminating the need to rebuild or re-sew patterns from scratch.
Mesh structural identity and DCC export requirements
Morph target interpolation operates by shifting point coordinates across 3D space: the pose changes by the minimum distances between points in the avatar rather than through rotational joint units. This mechanism requires strict topological consistency across both files.
The identical topology rule
For an OBJ morph target to function predictably, the base avatar already inside Marvelous Designer and the target pose exported from your Digital Content Creation (DCC) software (such as Maya, 3ds Max, Blender, or ZBrush) must share an identical mesh structure:
- Identical vertex count: The target mesh cannot have added, deleted, welded, or subdivided vertices.
- Identical vertex ordering: Point indices must correspond to the exact same anatomical locations on both meshes.
- Identical polygon topology: The polygonal face connectivity (quads or triangles) must remain completely unaltered.
If the vertex count differs or vertex ordering is modified during export, the morph interpolation calculates linear trajectories between mismatched points. This causes severe geometric deformation across the avatar's surface, tearing the simulated garment.
DCC export checklist
To prevent export corruption when generating OBJ morph targets in external modeling applications, verify the following configuration points:
TABLE / Scroll horizontally for all columns →
| Parameter | Required Configuration | Reason |
|---|---|---|
| Geometry Structure | Unmodified base cage | Ensures identical vertex count and mesh structure between base and target. |
| Modifiers / Deformers | Baked to vertex positions only | Prevents dynamic subdivision or topology regeneration during export. |
| Export Normals | Consistent smoothing groups | Prevents visual surface flipping during simulation. |
| Scale and Units | Same working units (e.g., cm or mm) | Avoids sudden avatar scale inflation or shrinkage during import. |
| Axis Orientation | Match base avatar axis (Y-Up or Z-Up) | Prevents the character from rotating unexpectedly during transition. |
| Material / Group Splitting | Disabled (Single unified group) | Prevents export tools from re-sorting vertex tables by material assignment. |
While default avatars inside Marvelous Designer can be posed using joint functions, third-party meshes from other 3D software programs (such as Maya or 3ds Max) often lack compatible joint rigs. In those workflows, generating morph target OBJ files in external DCC software allows artists to modify an avatar's pose or body shape reliably.
Step-by-step: Importing an OBJ morph target
Once both the base T-pose/A-pose avatar and the target pose OBJ have been exported from your DCC package with matching topology and scale, execute the following workflow:
1. Prepare the workspace and active garment
Before initiating the pose change, ensure the active garment is completely draped and stable on the base avatar. At least two OBJ files are required: the base avatar file (in T-pose or A-pose) and the avatar in the desired target pose.
2. Access the Morph Target import dialogue
In the main application menu, navigate to the file import options:
- Select File > Import > OBJ (or choose the dedicated Morph Target option depending on your workspace layout).
- Select the base OBJ file to establish the initial avatar if not already present.
- Select File > Import > OBJ again and choose the target pose OBJ file.
- In the OBJ Import Options window, set the Object Type to Load as Morph Target.
3. Configure import parameters
In the OBJ Import Configuration window, set the following parameters:
TABLE / Scroll horizontally for all columns →
| Setting | Recommended Value | Description |
|---|---|---|
| Object Type / Load Type | Load as Morph Target | Morphs the original object into the designated target object. |
| Scale | Match source scale / unit (e.g., 100% or cm) | Manually enters values or selects the desired unit to match the base avatar. |
| Axis Conversion | Match base avatar axis | Changes the directions of each axis of an object to avoid unintended rotation. |
| Transition Frame Count | 30–60 frames (or higher) | Sets the morphing duration; higher frame counts slow the transition speed. |
The Transition Frame Count setting dictates the speed of the morphing process. Entering a higher frame count slows down the transition, giving the solver adequate time to compute dynamic fold changes. If there is a substantial difference between the starting and ending pose, creating an interim pose OBJ file and morphing stage-by-stage is recommended to prevent garments from falling off.
Simulation workflow and dynamic drape inspection
After confirming the import dialogue, Marvelous Designer executes the morph transition across the specified frame duration.
Activating the transition simulation
- Upon confirming the morph target import, the Simulation button automatically activates per the Marvelous Designer Change Pose documentation.
- The avatar pose slowly shifts according to the configured frame count.
- The garment simulates continuously in accordance with the avatar's movement.
- Once the avatar reaches the final target stance, allow the simulation to continue running briefly to let dangling fabric, folds, and hems settle naturally under gravity.
Critical inspection zones
During the morph transition, inspect high-compression contact areas where avatar limbs approach each other or compress against the torso:
- Axillary regions (Armpits): When arms move from a T-pose downward to an A-pose or resting position, fabric in the armpit can become pinched between the arm and torso collision volumes.
- Elbow and knee creases: Acute joint bending compresses sleeve or trouser fabric, requiring sufficient mesh resolution to fold cleanly.
- Waist and crotch seams: Poses involving hip flexion or seated postures drastically alter tension across waistbands and inseams.
TABLE / Scroll horizontally for all columns →
| Morph Phase | Avatar State | Cloth Simulation Response | Focus |
|---|---|---|---|
| Initial (Frame 01) | T-pose or A-pose | Initial garment drape active | Baseline positioning |
| Transition (Mid-morph) | Intermediate point translation | Garment deforms dynamically with avatar motion | Continuous collision and fold tracking |
| Target Reached | Final target pose | Dynamic fabric compression and tension | Contact resolution |
| Settling | Static target pose | Garments settle under gravity | Final drape adjustment |
Post-morph settling and recovery techniques
When the simulation solver is activated, Marvelous Designer automatically switches the active cursor to the Select/Move tool according to the Marvelous Designer Simulation documentation. Use these non-destructive recovery techniques to adjust fabric fit without altering your 2D pattern design:
Surface pulling and dynamic manipulation
While the simulation solver is active in the final pose, use the Select/Move cursor to gently pull pinched cloth away from avatar collision surfaces:
- Left-click and hold the pinched cloth segment directly in the 3D viewport.
- Drag outward perpendicular to the avatar's skin until the mesh clears the collision boundary.
- Release the mouse button to allow the physics solver to pull the fabric back naturally against the avatar surface.
Pin constraints
For areas that repeatedly collapse into joint crevices during settling:
- Select the Pin (Box) or Pin (Lasso) tool.
- Place temporary pins along the edge of the hem or sleeve to hold the cloth away from deep body crevices.
- Resume simulation to let the surrounding fabric drape naturally around the pinned anchor.
- Delete the pins once the fabric has settled into a stable, non-penetrating equilibrium.
Adjusting local cloth positioning in the 3D viewport preserves the underlying pattern dimensions, ensuring pattern pieces remain ready for export to downstream DCC, sculpting, texturing, animation, game, or VFX tools. For broader application details, consult the Marvelous Designer Manual.
Frequently asked questions
Why did my avatar explode into a spike mesh when I imported the OBJ morph target?
A spike mesh or vertex explosion occurs when the target OBJ file does not share identical vertex indexing with the base avatar. Morphing calculates linear translation across corresponding vertex indices. If the vertex ordering is changed during export in external software, point 0 on the base mesh translates toward an unrelated point on the target mesh. Ensure the target stance was generated strictly by moving existing vertices without modifying mesh structure, and verify that export settings preserve vertex order.
What is the difference between loading an avatar pose file and importing an OBJ morph target?
Avatar pose files rely on skeletal joint hierarchies. For avatars with standard joint setups, pose files rotate bones directly. An OBJ morph target is a geometric deformation that requires no internal skeleton, changing the pose by interpolating the minimum distances between points in 3D space. This makes OBJ morph targets ideal for custom character sculpts and meshes imported from external DCC software that lack joint definitions.
Why does my avatar jump instantly to the new pose instead of transitioning gradually?
This behavior occurs if the Transition Frame Count parameter in the OBJ Import dialogue is set to a single frame. A frame count of 1 forces avatar vertices to snap instantly to their new coordinates, which can cause cloth collision failures and garment drop. Setting a higher frame count (such as 30 to 60 frames or more) slows down the morphing process, allowing the simulation solver to track avatar movement.
How do I fix scale mismatches between the base avatar and the morph target?
If the morph target expands or shrinks relative to the base character, the export unit scale in your DCC package differed from the original base mesh export settings. Verify that both the base avatar OBJ and the target pose OBJ are exported using identical system units (such as centimeters), and verify that the Scale setting in the Marvelous Designer OBJ Import/Export dialogue matches the base avatar import settings.