Key takeaways
- Inspect the imported character and garment pattern as separate inputs.
- Use a saved comparison to test one intended pattern change.
- Recheck folds after flipping a pattern and keep other changes traceable.
When clothing moves into an imported character or appears to face the wrong way, start by separating the objects involved. The avatar is one input; each garment pattern is another. A screenshot of a bad result is a reason to inspect both, not enough evidence to name one universal cause.
This guide focuses on the documented garment Flip Normal operation and a controlled way to test it. It does not prescribe an external modeling application's repair commands or promise that flipping a pattern will fix an imported avatar. Keep the investigation tied to what changes in your own project.
Capture the problem before changing it
Save a project copy and record the Marvelous Designer version, the imported character file, and the garment involved. Capture the arrangement before simulation and a second view showing the problem. Use a similar camera view for the comparison, so that movement is easier to follow.
Write a short observation: for example, “the left front panel crosses the torso after simulation starts.” Avoid replacing the observation with an untested explanation such as “the solver pulls reversed faces inward.” The first statement can be checked in your file; the second would require evidence about the cause.
If you simplify the scene for a support example, work in a copy and note what you removed. The purpose is to make one problem reproducible while retaining the original for comparison. Keep unrelated pattern redesign and material experiments outside this first test.
Check the imported object's role and orientation
For OBJ files, confirm the chosen import type. The OBJ manual distinguishes avatar, garment, and trim imports; trim is not the collision object you want when testing clothing against a body. The dialog also provides scale and axis-conversion controls. Record those settings and compare the imported orientation with the source asset before diagnosing pattern facing.
Do not assign the same diagnosis to every visible failure. A rotated character, an unexpected size, a wrong import role, and an incorrectly facing garment are different observations. If you find an import mistake, correct that input in your test copy and repeat the same simple scene before adding another change.
This check is deliberately limited to the import information you can verify. It does not provide a universal unit preset or infer avatar surface direction from a single rendered image. If the imported mesh remains suspect, ask its creator to inspect it in the source application and supply a corrected comparison file with an explanation of the change.
Apply Flip Normal only to the pattern you intend to change
The official Flip Normal instructions describe reversing the fabric's front and back on a selected pattern, before or after draping. Use Select/Move, select that pattern, then choose Pattern → Flip Normal in the garment's context menu.
The same instructions say the fold-angle value changes when the normal is flipped. Do not add a blanket manual fold-angle reversal afterward. Inspect the resulting value and crease behavior against your intended design before making a further adjustment. A second automatic-looking correction can make your test harder to interpret.
For the first attempt, choose one affected pattern and keep a record of what you selected. Compare its appearance and simulation result with the saved starting point. If several panels are involved, work through a clear selection plan rather than flipping every pattern without checking which faces needed attention.
Treat this as a garment operation. The command's documented target is the selected pattern, so it does not establish that an imported avatar has been repaired. If the garment result improves but the character still appears problematic, keep those two findings separate in your notes.
Keep simulation settings stable during the comparison
The Simulation Properties manual locates these controls under Scene → Environment in the Object Browser, and also in the 3D background options. It recommends default settings for several advanced parameters, including time step and self-collision iterations, and describes collision-detection controls separately from intersection resolution.
Record any custom settings already in use. For a controlled comparison, avoid changing gravity, collision options, and pattern facing at the same time. If you decide to return a setting to its documented default, record that as a separate test. Do not label a combined set of changes as proof that one of them caused the improvement.
The manual also includes direction choices within Intersection Resolution. Those are simulation settings, not the selected-pattern Flip Normal command. Do not substitute one for the other merely because both mention normals. Use the operation that matches the specific object or setting you are investigating.
Compare the result with the original problem
After the pattern test, check the same area that first showed the issue. Has the unwanted movement changed? Does the fabric face now match your intention? Are the folds still suitable? Record the answers as observations about this file, without presenting them as a diagnosis for all inward-moving cloth.
A successful appearance check is not a reason to discard the source project. Keep the before-and-after copies until the garment has passed the rest of your workflow's requirements. If your next step is animation or export, test that step on the corrected copy rather than assuming a static check covers it.
If the issue remains, restore the comparison state and narrow the next question. For example, ask whether the same garment behaves differently with a corrected character file. Change one input deliberately, and preserve the original input's filename. That makes a useful result easier to attribute and an unsuccessful attempt easier to undo.
Send a reproducible support case if it is still unresolved
Include the application version, import role and settings, a minimal project you are permitted to share, and the exact steps that produce the behavior. Identify the pattern you flipped and describe what happened to its facing and folds. Attach the paired screenshots and mention any custom simulation settings.
Ask for help with the remaining observation rather than asserting an unconfirmed normals defect. This gives support or the asset creator something concrete to inspect. Rebuilding the garment may eventually be appropriate, but first establish whether a documented pattern operation or a corrected input changes the original problem.
FAQ
Should I flip every garment pattern at once?
Begin with a deliberate selection of an affected pattern in a project copy. Compare that result with the original problem before expanding the change. Record what you selected so the test can be repeated.
Should I manually reverse the fold angle after Flip Normal?
Check the resulting value and fold behavior first. The documented operation already changes the fold-angle value; an additional blanket reversal is not the recommended diagnostic step here.
What should I send when I cannot isolate the cause?
Provide the application version, exact import settings, a shareable minimal project, and paired screenshots. List each change you tried and its observed result, so the next investigation begins with evidence rather than an assumed cause.