A lesser-known use case: converting hard-surface meshes into cloth.
Workflow:
This bypasses retopology entirely. For game engines, artists can export the deformed mesh as a static LOD, preserving the exact cloth shape with zero runtime physics cost.
Absolutely, if you are:
Maybe not, if you:
The 3D industry is moving toward real-time rendering and faster iteration cycles. Native cloth modifiers force you to simulate, wait, crash, re-simulate. PolyCloth ClothBrush 2.07 moves the physics engine into the viewport.
Because it supports the massive version span of 2016 to 2025, studios don't have to worry about updating every single workstation to the latest Max version. You can have one artist on 2025 with an RTX 4090 and another on 2016 with a GTX 1080, both using the exact same 2.07 file format.
The brush system appeals to artists who hate math. You don't need to understand Euler integration to know that a towel should drape over a hook. You just grab the towel and pull it with the mouse.
While it feels like sculpting, the engine is pure physics. Version 2.07 improves the iteration solver, meaning you get realistic bending, shearing, and stretching without the mesh tearing. Features include:
PBR (Physically Based Rendering) requires realistic cloth draping. Using PolyCloth, you can generate high-poly cape meshes, bake them down to low-poly game assets, and guarantee that the normal maps capture realistic tension lines on the cloth.