Post
Making capes, flags, and dresses move like actual fabric instead of stiff cardboard attached to a character.
Cloth simulation models fabric as a grid of particles connected by constraints (springs) that are solved iteratively each frame. Each particle is affected by gravity, wind, and collision with the character's body and environment. The solver runs multiple iterations to keep the cloth from stretching unrealistically while maintaining the drape and flow of real fabric. The computational cost scales with the number of particles and iterations, so game cloth tends to be much lower resolution than film cloth -- a character's cape might use a few hundred particles versus tens of thousands in a movie. Modern approaches include position-based dynamics for stability, signed distance field collision for efficiency, and GPU-accelerated solvers for handling multiple cloth objects simultaneously.
Example
Batman's cape in the Arkham series became iconic partly because of its cloth simulation. The cape drapes, flutters, wraps around objects, and billows dramatically during glides, adding a physicality to the character that a rigid model could never achieve. Rocksteady iterated on the cape simulation across all four games because they understood how much it contributed to the feel of being Batman.
Why it matters
Cloth simulation is one of those details that players feel more than they consciously notice. A character with a flowing, reactive cape feels more present in the world than one with a stiff texture painted to look like fabric. It is a significant contributor to the overall visual quality and immersion of modern games.
Related concepts