Multi-Layered Cloth Simulation and Tearing: Which Solver Handles It

Multi-layered cloth simulation fails for two predictable reasons: layers without enough collision room, and tearing set up with the wrong tool.
- Collision Room: Marvelous Designer’s default simulation thickness is 1.5mm per side (3mm total) with a 3mm skin offset; tight layers need both adjusted together.
- Layer Values: Marvelous Designer support repeatedly advises resetting all layer values to 0 before animating, and staff have recommended CPU over GPU simulation for heavily layered garments.
- Vellum Layers: SideFX suggests raising post-collision passes for every cloth layer and keeping thickness below edge length.
- Tearing Built In: Vellum uses breakable welds, Maya nCloth uses a Tearable Surface constraint with Glue Strength, and Cinema 4D’s newer system tears without a Cloth Surface object.
- Practical Fix: Build layers in Marvelous Designer, tear in a shot solver (Marvelous Designer 2026.1 can now rip seams in beta). Our cloth software guide compares the solvers.
Table of Contents
When the Shirt Keeps Escaping the Trousers
Every costume artist has watched a tucked shirt crawl out of the trousers on frame 40, or a coat lining punch through the outer shell. Multi-layered cloth simulation is where most cloth tools show their limits, and tearing adds a second problem on top: the fabric has to hold together until the exact moment it should not.
This guide explains how the main cloth tools handle stacked layers and tearing, which settings matter, and which tool to use when a shot needs both.
1. Why Multi-Layered Cloth Simulation Breaks
Layered cloth breaks when the solver cannot keep two surfaces apart within the time it has per step. Thin collision thickness, uneven mesh density, folded normals and fast motion all shrink that margin until one layer passes through another, then jitters as the solver tries to push it back.
Every solver uses some form of collision thickness: an invisible shell around each surface. Two layers need enough combined thickness to stay apart, but not so much that they float off the body. Getting that balance right, and keeping mesh resolution consistent between layers, solves most layering problems before you touch advanced settings.
Figure 1.1 uses Marvelous Designer’s documented defaults: a simulation thickness of 1.5mm on each side of a pattern, 3mm in total, and a 3mm avatar skin offset. Marvelous Designer’s support documentation recommends adjusting skin offset together with simulation thickness for form-fitting garments.
2. Multi-Layered Cloth Simulation in Marvelous Designer
Marvelous Designer handles layered outfits well when layers are built in order and its layer values are reset before animation. Many layering threads on its support forum come back to leftover layer values, GPU mode on dense layers, or inconsistent particle distance.
2.1 Build Inside Out, Then Reset Layers
Marvelous Designer support staff recommend simulating the inner garment first, tightening it with shrinkage, freezing it, then simulating the next garment over it. Layer values can help during that build, but the support team repeatedly advises setting all layer values back to 0 before animating, because leftover layer values cause collision problems and visible sizzling in motion.
2.2 CPU Mode and Particle Distance for Final Passes
GPU simulation gained layer collision accuracy matching the CPU in version 2024.2, according to CG Channel’s release coverage. Older support answers, mostly from before that update, recommend CPU simulation for layered garments and treat GPU as a fast drafting mode, so CPU is still the safer final pass. Keep particle distance similar across touching layers; one support answer suggested 5mm for parts that need fine wrinkles, 10mm elsewhere, and switching everything to 7mm when many layers sit at 5mm.
Multi-Layered Cloth Simulation Settings by Tool
From CLO, SideFX, Autodesk and Maxon documentation and support pages, read November 2026.
| Tool | Key layer setting | What helps | Common mistake |
|---|---|---|---|
| Marvelous Designerpattern tool | Add’l Thickness-Collision: default 1.5mm per side, plus skin offset. | Inside-out build: freeze inner layers, CPU final pass. | Leftover layer values: cause sizzling in animation. |
| Houdini Vellumshot solver | Thickness (pscale): keep below edge length. | Post-collision passes: raise for every cloth layer. | Default thin cloth: leaves no room before hard collisions. |
| Maya nClothNucleus | Thickness and self-collision: on each nCloth object. | Correct Space Scale: 0.01 for centimetre scenes. | Default Space Scale: treats centimetres as metres. |
| Cinema 4D ClothSimulation System | Thickness: capped internally at 80% of the shortest connected edge. | Even meshes: objects with different meshes behave differently. | Thickness too high: Cinema 4D reduces it per point. |
3. Layered Cloth in Houdini Vellum, Maya nCloth and Cinema 4D
Shot solvers handle layers through thickness, collision passes and consistent mesh resolution rather than layer values. Each has one or two settings that matter far more than the rest.
3.1 Houdini Vellum
SideFX’s Vellum tips say to keep pscale and cloth thickness below edge length to avoid self-intersections, note that the default cloth is very thin, and suggest bumping post-collision passes for every layer of cloth. If layers poke through sharp colliders, raise collision passes up to the constraint iteration count and add substeps.
3.2 Maya nCloth
nCloth layering problems often start with scale. Autodesk’s documentation explains that at the default Space Scale of 1.0, the Nucleus solver interprets centimetres as metres, so a centimetre-based scene should use a Space Scale of 0.01. Fix that before tuning thickness and self-collision on each nCloth object.
3.3 Cinema 4D Cloth
Maxon’s help notes that if cloth thickness is set too high, Cinema 4D internally uses 80% of the shortest connected edge for affected points, for self-collision and cloth-to-cloth contact. It also shows that identical cloth settings on different meshes produce different results, so keep layer resolution consistent.
4. How Each Cloth Simulator Handles Tearing
Tearing works by breaking the connections that hold cloth together once stress passes a threshold. Vellum, Maya nCloth and Cinema 4D all document a tearing workflow, and Marvelous Designer 2026.1 added a beta tool that rips sewn seams; they differ in how you mark where tears can happen and how you control the threshold.
Cloth Tearing Workflows Compared
How each tool decides when fabric rips.
| Tool | Mechanism | Control |
|---|---|---|
| Houdini VellumSideFX docs | Breakable welds: Edge Fracture, then Vellum Weld Points with Breaking on. | Threshold per weld: stress based; Normalize Stress keeps it stable across substeps. |
| Maya nClothAutodesk docs | Tearable Surface constraint: nConstraint menu. | Glue Strength: 1 never breaks, 0 breaks at once; paintable map. |
| Cinema 4DMaxon docs | Tearing option: no Cloth Surface object needed in the new system. | Tear Past: on the Cloth tag, plus a vertex map for weak areas; Connector tags have their own Tear Past %. |
| Marvelous Designergarment tool | Seamline Rip (2026.1, beta): seams tear during simulation once force passes the rip resistance. | Seams only: tears across a panel, or tears that interact with other FX, still go to a shot solver. |
4.1 Houdini Vellum Breakable Welds
SideFX documents tearing as a pre-fracture plus breakable welds: run Edge Fracture on the patch, convert it with Vellum Configure Cloth, add Vellum Weld Points between Configure and the solver, and enable Breaking with a Threshold. SideFX notes that with Normalize Stress enabled, stress-based thresholds let you change substeps with only slight retuning of the threshold, which makes iteration easier.
4.2 Maya nCloth Tearable Surface
In Maya, select the nCloth object and choose nConstraint > Tearable Surface. Autodesk’s documentation explains that Glue Strength controls how easily the cloth tears, with 1 meaning the constraint never breaks and 0 meaning it breaks immediately, and that you can paint a Glue Strength map to direct where tearing happens. Raising Bend Resistance above 0.2 makes the cloth shatter instead of tear.
4.3 Cinema 4D Tearing
In Cinema 4D’s newer simulation system, Maxon lists among its new abilities that the Tearing function does not require a Cloth Surface object. The Cloth tag’s Tearing option uses Tear Past to set how far an edge may stretch before it breaks, and a vertex map can paint weak areas; Connector constraints offer a separate Tear Past percentage based on rest length.
5. Choosing a Tool for Layered and Torn Cloth
For layered costumes that only need to look right in motion, Marvelous Designer with careful layer handling is usually enough. Marvelous Designer 2026.1 can now rip seams during simulation (beta), but for tears across a panel, or tears that burn or interact with other effects, build the garment in Marvelous Designer and move the shot to Vellum or nCloth.
Pick the shot solver your studio already uses for animation. Houdini teams get breakable welds plus interaction with Pyro and grains; Maya teams get Tearable Surface with paintable Glue Strength inside the same scene as their rigs; motion designers in Cinema 4D get tearing alongside Pyro and liquids in the Simulation System.
6. SOP: A Layered Jacket That Tears in Vellum
This setup combines the layering and tearing advice above for a two-layer jacket that rips along one seam.
6.1 Step 1: Build and Export Layers Separately
Build the shirt and jacket in Marvelous Designer from the inside out, reset layer values to 0, and export each garment at rest as its own OBJ.
6.2 Step 2: Match Resolution and Thickness
Remesh both garments to similar edge lengths in Houdini and set each Vellum Configure Cloth thickness below that edge length, as SideFX advises.
6.3 Step 3: Pre-fracture the Tear Seam
Group the seam that should rip, run Edge Fracture on that region only, and rejoin it with Vellum Weld Points with Breaking enabled and a threshold you will tune.
6.4 Step 4: Raise Post-Collision Passes
On the Vellum Solver, increase post-collision passes for the second layer and prefer more substeps over more collision passes for fast motion.
6.5 Step 5: Cache and Check the Tear Frame
Cache the shot, then scrub the frames around the tear. Torn cloth changes topology, so motion blur after the tear usually needs a velocity attribute. Our article on simulations that fail frames on a farm lists other cache issues to check. For the final render, a stronger local GPU, a SaaS farm or a rented multi-GPU machine such as an iRender server can take the load. With a rented machine, remember that it keeps billing until you press Shutdown on the iRender web panel or app, or a Schedule Shutdown timer turns it off; simply closing the Remote Desktop window does not stop the meter.
Remote GPU option. Render torn, layered cloth shots on multi-GPU servers you control. Render with iRender →
See more: Why an RBD Destruction Sim Renders Differently on the Farm
FAQ: Multi-Layered Cloth Simulation and Tearing
Usually because the collision shells are too thin for the motion, the layers have very different mesh density, or folded normals confuse the solver. Give each layer enough collision thickness, match edge lengths across touching layers, and add substeps for fast moves before increasing iterations.
Marvelous Designer support recommends simulating the inner garment first, tightening it with shrinkage, freezing it, then simulating the trousers over it. If you used layer values while building, reset them all to 0 before animating, because leftover layer values cause collision problems and sizzling.
GPU mode gained layer collision accuracy matching the CPU in version 2024.2, but older Marvelous Designer support answers recommend CPU simulation for layered garments and describe it as the high-quality final pass. Use GPU for quick drapes and CPU for final layered results.
SideFX documents a breakable-weld workflow: run Edge Fracture on the patch, convert it with Vellum Configure Cloth, add Vellum Weld Points before the solver, and enable Breaking with a threshold. The welds hold until stress exceeds the threshold, then the cloth separates along the fractured edges.
Yes. Select the nCloth object and choose nConstraint, Tearable Surface. The Glue Strength attribute sets how easily it tears, from 1, which never breaks, to 0, which breaks immediately, and you can paint a Glue Strength map to control where tears happen. Raising Bend Resistance above 0.2 makes it shatter instead.
Yes. In Cinema 4D’s newer Simulation System, Maxon states that tearing does not require a Cloth Surface object. The Cloth tag’s Tearing option uses Tear Past and a vertex map to control where tears occur, and Connector constraints have their own Tear Past percentage.
Sources
- Marvelous Designer support, Adjust Collision Thickness, Simulation Properties, and support community answers on layers, read 18 November 2026.
- SideFX, Vellum tips and Breaking and tearing, read 18 November 2026.
- Autodesk Maya documentation, Create Tearable Surface constraints, nComponent node and Nucleus solver properties.
- Maxon, Cinema 4D Simulation System, Cloth tag and Connector constraint documentation.
- CG Channel coverage of Marvelous Designer 2024.2; iRender documentation (docs.gpuhub.net), read 18 November 2026.
No comments