Key takeaways

  • Layer values are temporary staging tools: The Layer property in Marvelous Designer establishes initial dressing priority during static draping. Leaving non-zero layer values active during animation causes simulation issues and collision conflicts, producing mesh instability and contact jitter.
  • Reset to zero before dynamic solving: Once an outfit's layering sequence is established in the initial drape, all pattern pieces should have their Layer property returned to 0 so the solver relies on physical collisions.
  • Audit physical clearances and hidden geometry: Interpenetration and buzzing artifacts often stem from active freezing on panels, hidden garment geometry, large avatar skin offsets, or collision thickness mismatches.
  • Adjust collision settings and mesh density before global physics: Address unstable contact zones by checking collision thicknesses and particle distance on the avatar and fabric meshes before modifying global simulation parameters.

Draping layer order vs dynamic collision detection

When assembling complex outfits, such as a shirt tucked into trousers, folded cuffs over sleeves, or layered pocket flaps, garment panels must settle in a distinct overlapping sequence. In Marvelous Designer, assigning a positive or negative integer to the Layer property determines which pattern settles inward or outward when multiple layers overlap during garment dressing.

However, the Layer property is not designed to function as a permanent constraint during character animation. The draping solver utilizes surface normals to evaluate orientation, and leaving active layer values on pattern pieces during animation causes collision conflicts:

  1. The collision solver evaluates surface interactions and collision offsets to prevent cloth interpenetration.
  2. The layer hierarchy evaluates assigned values relative to surface normals, which can create severe instability around folds and compressed areas.
  3. When animated motion forces intersecting contact, active layer values force competing directional calculations, causing vertices to pop across surfaces and create simulation sizzling or fluttering.

As documented in the Marvelous Designer Manual, the default Layer value of 0 means the layer function is off, and once draping in the desired order is complete, reverting all values back to 0 ensures stable simulation without changing the settled drape.

Staging vs dynamic simulation phases

  • Initial Drape Phase: The inner garment is set to Layer 0 and the outer garment is assigned Layer 1 (or negative values for tucked pieces). Activating simulation draws the higher-valued pattern outward over the lower-valued layer.
  • Dynamic Animation Phase: All pattern pieces across the entire outfit are returned to Layer 0. The simulation engine evaluates pure physical collisions across all meshes without hierarchy-driven overrides.

The layer drape lifecycle: Step-by-step procedure

To achieve stable layered outfits without simulation errors, treat the Layer property as a temporary initialization state. The following sequence establishes clean layering before moving into dynamic simulation:

1. Establish the base drape

Drape the foundational layer (such as an undershirt, inner lining, or base trousers) directly against the avatar with its Layer property set to 0. Allow the cloth to come to rest so the baseline arrangement order of the patterns is established.

2. Assign relative layer values to additions

When introducing an overlapping piece, such as a jacket over a shirt or a pocket patch on a bodice, select the target pattern pieces in the 2D Pattern Window or 3D Window. In the Property Editor:

  • Navigate to Simulation Properties and set the outer piece's Layer to 1 (or higher if arranging multiple overlapping tiers).
  • If tucking an inner garment beneath an already draped outer garment, set the tucked pattern piece to a negative value such as -1, as negative layers apply in the reverse order of positive numbers.

3. Run the initial drape

Activate the simulation button. The solver will position the patterns according to their assigned layer numbers, pulling outward or pushing inward relative to adjacent geometry. Allow the cloth to drape until the overlapping silhouette settles cleanly.

4. Reset all layer properties to default

Deactivate the simulation. Select all pattern pieces across the entire outfit, navigate to the Property Editor, and reset the Layer property back to 0. If the layer field appears in red when all patterns are selected, mixed values are present; revert the property to 0 once again so all patterns are unified.

The garments will maintain their draped geometric positions without alteration, as confirmed in the Marvelous Designer Manual. During subsequent animation solving, the simulation engine will treat all surfaces through standard collision handling rather than forced layer ordering.


Contact zone spatial audit: Tucks, cuffs, and pockets

When simulation instability persists after resetting layer values to 0, the root cause is frequently physical collision conflicts or improper thickness offsets in tight contact zones. The solver requires adequate spatial clearance and mesh density to resolve contact cleanly.

Contact AreaPotential Geometric IssueDiagnostic Focus
Tucked WaistbandInner shirt colliding with avatar and outer bandInspect avatar skin offset and adjust cloth collision thickness
Layered Sleeves / CuffsFolded normals creating instability across layersCheck fold normal directions and match material particle distance
Pockets & FlapsInwardly trapped geometry or conflicting layer tagsClear persistent layer offsets and adjust local mesh density

Normal orientation and folded geometry

Layer assignments rely on the direction of mesh normals. Consequently, when garments contain tight folds, collars, or cuffs, opposing surface normals can create severe collision instability if layer values remain active. Returning all layer properties to 0 removes normal-dependent hierarchy conflicts and allows standard collision geometry to resolve the fold.

Collision thickness and particle distance

Every interacting surface carries collision thickness and particle distance settings that govern proximity detection and mesh resolution.

  • Avatar and cloth collision thickness: If cloth layers are squeezed tightly against character geometry, reduce avatar skin offsets and cloth collision thicknesses to give the layers physical space.
  • Particle distance and mesh density: When reducing collision thickness offsets, increase mesh density by lowering the particle distance on interacting fabrics to prevent physical mesh interpenetration during motion.
  • As noted in Marvelous Designer Community Discussions, mismatched collision thicknesses and improper particle distances on layered panels are primary contributors to contact sizzling and vibration.

Audit protocol: Hidden geometry, deactivated patterns, and frozen panels

Unstable contact artifacts often originate from non-dynamic or unobserved scene elements in the 3D workspace. Before modifying global world physics properties, conduct a systematic audit of scene components.

Scene inspection steps

  1. Check hidden garments and avatar geometry: Reveal all hidden pattern pieces and inspect avatar sub-meshes to ensure no active collision boundaries are pushing unexpectedly against cloth layers.
  2. Turn off panel freezing: Unfreeze base garments and underlayers so that interacting panels can deform naturally under collision rather than acting as rigid barriers.
  3. Audit avatar skin offsets: Inspect the avatar for abnormally large skin offset values that may compress base layers into outer garments.
  4. Normalize material particle distances: Ensure interacting contact areas possess sufficient mesh resolution to resolve physical collisions smoothly.

1. Hidden garments and avatar geometry

If garments or avatar sections are hidden in the workspace, verify whether their collision calculations remain active. An uninspected hidden garment or an excessively large avatar skin offset will continue to exert collision force against adjacent cloth, trapping inner layers against outer garments and generating continuous jitter.

2. Frozen base garments

Freezing an undergarment locks its vertices in 3D space. When dynamic outer cloth compresses against a frozen inner panel, the static geometry cannot yield to incoming collision forces. According to Marvelous Designer Community Support, turning off Freezing alongside active layer values allows mutual surface compliance and produces significantly more stable results.

3. Layer conflicts across body components

Assigning conflicting layer values across separate pattern pieces—such as setting inner pocket panels to negative values while overlapping adjacent sleeves or bodices—can force vertices to pop back and forth across frames. Clearing all layer assignments to 0 prevents disparate body pieces from fighting during complex character motion.


Empirical testing: Isolate motion segments before modifying solver properties

When troubleshooting layered garment instability, adjusting global world physics parameters (such as global animation and physics properties) before resolving mesh-level conflicts can lead to inaccurate simulation behavior without solving the underlying defect.

Follow this progressive diagnostic sequence:

  1. Audit object-level settings first: Select the avatar and fabric meshes directly to adjust collision thicknesses, skin offsets, and particle distance rather than altering global world physics properties.
  2. Verify all layer values are zero: Confirm in the Property Editor that no pattern piece retains a non-zero Layer value across the entire outfit.
  3. Disable freezing on interacting layers: Ensure foundational garments are unfrozen so that dynamic collisions can resolve across all contacting surfaces.
  4. Evaluate solver presets and substeps when necessary: If high-speed motion causes instability after mesh properties are verified, consult the Marvelous Designer Simulation Properties Guide to select appropriate presets (such as Normal, Animation, or Fitting) or configure simulation substeps. Dividing a time step into multiple smaller substeps ensures numerically accurate calculations and stable collision handling during demanding dynamic motion.

Frequently asked questions

Why does my folded cuff or collar vibrate even when the Layer property is set to 0?

Layer calculations are influenced by normal directions, meaning internal folds and opposing normals can create instability if residual layer tags or extreme collision offsets are present. Ensure all layer values are set to 0, verify that base panels are unfrozen, and check that material particle distances are dense enough to support clean fold geometry.

Should I reduce avatar skin collision offset to make tucked shirts fit better?

Abnormally large skin offsets on the avatar can compress tucked inner garments against outer waistbands, causing severe collision jitter. Reducing avatar skin offsets and cloth collision thicknesses provides necessary physical clearance, provided particle distance is adjusted to maintain adequate mesh density.

How should pocket flaps be layered over pocket bags and jacket bodies?

When assembling layered pockets, assign positive Layer values to outer flaps or negative values to internal pocket bags so the solver can pull the pieces into their proper inward or outward arrangement during initial draping. Once the pieces settle cleanly into position, stop the simulation and reset all pattern Layer values back to 0 before starting animation solving.

When is it genuinely necessary to increase simulation substeps or adjust solver presets?

Increasing simulation substeps or choosing specific presets (such as Animation or Fitting in the Simulation Properties panel) is appropriate when rapid animation requires finer time sampling to resolve collision interactions accurately. Simulating multiple times across smaller time intervals enhances numerical precision and collision stability, though it requires greater calculation time. Global solver adjustments should be made after verifying that all layer values are zero, freezing is disabled, and object collision thicknesses are properly configured.