Key takeaways
- Check the avatar and garment separately; keep a record of both input files.
- Decide whether you want resizing or size-preserving draping before selecting a command.
- Compare one controlled attempt with the starting project before changing another setting.
When a custom avatar is ready but a garment still will not fit, check the garment's preparation as well. The official STORE Auto Fitting walkthrough treats these as two separate checks: create the avatar's fitting suit, then confirm that the purchased garment contains fitting data. Completing the first does not establish the second.
Start with a copy of the troublesome project and decide what success means. Do you want the garment resized for another body, or do you want the same garment dimensions arranged on that body? Write that intention down before choosing a command. A result can look different without answering the question you meant to test.
Establish which assets you are testing
Record the Marvelous Designer version, the avatar file, and the garment file. If several copies have similar names, use a short test note identifying the exact pair. Keep the original files available so you can compare a corrected attempt with the starting point.
Treat a vendor description such as “ready to wear” as a reason to inspect the asset, not as your test result. Ask specifically about fitting data when the package information is unclear. A useful request names the garment and asks which avatar and software version were used to prepare it. Avoid guessing from a screenshot of a successful drape.
Check the avatar in the editor for your version
In the 2025 interface, open Avatar → Avatar Editor with the avatar present in the 3D window, and use the Fitting Suit tab. The Avatar Editor manual describes drawing the circumference reference lines and then draping the suit. It also documents an automatic creation option, with manual creation available when the automatic result needs correction. Inspect what was created before moving on.
Save the prepared avatar as an AVT file. The same manual distinguishes this from AVS, which saves size information rather than the full avatar. Keep the prepared avatar's filename in your test note; otherwise, a later test may accidentally reopen a different asset. This is a file-management recommendation, not a claim that every failed fitting operation comes from a save error.
Check the garment separately
The Auto Fitting manual requires a garment containing fitting data alongside the prepared avatar. It describes garments simulated on a supplied avatar from version 9.5 onward, or on an avatar with a created fitting suit. From version 11, the 3D view's display controls include separate views for the avatar suit and garment suit: Avatar Display and 3D Garment Display respectively.
Inspect both sides of the pair and record what you actually see. If the garment's preparation remains uncertain, return to its source project or ask its creator for a compatible prepared file. Do not repeatedly change unrelated settings while that basic question is unanswered. A clear missing-input question is more useful than a long list of unsuccessful combinations.
Do not decide compatibility from the OBJ extension alone
An imported OBJ is not automatically excluded from garment workflows. The OBJ import manual provides a garment import mode and an option to build 2D patterns from the UV map. That capability does not, by itself, confirm the fitting data required by Auto Fitting. Check how the asset was imported and prepared; do not equate visible geometry with a completed fitting setup.
For a shared asset, request the source project if it is available and permitted to share. Record whether your working file came from that project or from a mesh export. This helps the asset's creator reproduce your setup without turning a file extension into a blanket diagnosis.
Choose resizing or size-preserving draping deliberately
Auto Fitting changes garment size and simulates it on the target avatar. Re-Target Draping, named Re-Drape 3D Arrangement in the 2025 documentation, retains the garment's size. The former is under 2D Pattern → Fitting; the latter is under 3D Garment. The documented command descriptions are the basis for that distinction.
Choose the operation that matches the intention you recorded at the start. Before running it, capture a view of the garment and note the dimensions that matter to your task. Afterward, compare those same details. A loose fit is not automatically a failed command, and a close-looking fit is not enough to establish that every downstream requirement was preserved.
For this first check, keep the question narrow: did the intended operation run with the prepared asset pair? Evaluate texture placement, topology, or animation requirements separately before accepting the file for production. Do not treat a successful fitting test as a guarantee about an entire asset pipeline.
Make one result easy to reproduce
A compact test record can include:
- The exact application version and the two input filenames.
- Whether you confirmed fitting data for both assets, and where that confirmation came from.
- The command selected and the intended size behavior.
- A before-and-after view of the same garment area.
- Any error message copied exactly, plus the step at which it appeared.
If the corrected preparation resolves the problem, keep that working pair as your comparison case. If it does not, send the record with the smallest project that still shows the issue. Remove unrelated garments from the support example only in a copy, and explain any changes you made to simplify it.
The useful outcome is a traceable test, not a speculative explanation of the fitting algorithm. Confirm the two inputs, choose the intended operation, and evaluate the result against the task you actually need to complete.
FAQ
What should I ask the garment's creator for?
Ask how the exact file was prepared, which application version was used, and whether a source project is available. Include your target avatar and the step that fails so the creator can reproduce the pairing.
What if the first corrected attempt still fails?
Keep the original and revised files, capture the exact error, and describe which preparation step you changed. Use that evidence to ask for help with the remaining failure rather than trying unrelated settings at random.
How should I decide whether the result is acceptable?
Compare it with the intended size behavior you recorded before the test. Check the details important to your project separately, and retain the comparison files until the next production stage has been tested.