Blender Quiz: Set Up Basic Cloth Simulation And Collision Objects Intro

10 questions · exam conditions

0:00

Set Up Basic Cloth Simulation And Collision Objects IntroQuestion 1 of 10

A rectangular plane has been subdivided and positioned above a table. Cloth physics is enabled on the plane, but when the timeline plays, the cloth falls through the table. The table is a separate mesh object with no physics settings.

Which change most directly establishes the missing interaction while preserving the table as a stationary object?

Enable Collision physics on the table and keep Cloth physics on the plane.

Enable Cloth physics on the table and keep Cloth physics on the plane.

Enable Self Collision on the plane and leave the table without physics.

Make the table a rigid body and remove Cloth physics from the plane.

← Back to quizzes

Blender Quiz

Blender Quiz: Set Up Basic Cloth Simulation And Collision Objects Intro

Practice Set Up Basic Cloth Simulation And Collision Objects Intro in Blender with focused quiz questions that help you check what you know, review explanations, and build confidence with test-style prompts.

What this quiz covers

This quiz focuses on Set Up Basic Cloth Simulation And Collision Objects Intro, giving you a quick way to practice the rules, question types, and explanations that matter most for Blender.

How to use this quiz

Try each quiz question before looking at the correct answer. Use the explanations to review missed ideas, then come back to similar questions until the pattern feels familiar.

All questions

Question 1

Which change most directly establishes the missing interaction while preserving the table as a stationary object?

Enable Collision physics on the table and keep Cloth physics on the plane. (correct answer)
Enable Cloth physics on the table and keep Cloth physics on the plane.
Enable Self Collision on the plane and leave the table without physics.
Make the table a rigid body and remove Cloth physics from the plane.

Explanation: Whenever you see a Blender physics question involving two separate objects interacting, ask yourself: what role does each object need to play? Blender's physics system is opt-in — an object doesn't participate in any simulation until you explicitly assign it a physics type. A cloth object will happily fall through any mesh that hasn't been given a physics role, because from the simulation's perspective, that mesh simply doesn't exist. In this scenario, the plane correctly has Cloth physics, so it will simulate fabric-like behavior. The missing piece is that the table has no physics assignment at all. To make the cloth land on the table rather than pass through it, the table needs to be registered as a Collision object. This is a lightweight physics type — it doesn't make the table move or simulate anything; it simply tells the cloth solver "treat this surface as a barrier." That's exactly what answer A provides: Collision on the table, Cloth on the plane. Answer B is wrong because giving the table Cloth physics would turn it into a second piece of fabric, causing both objects to fall and drape — not what you want from a solid table. Answer C addresses self-collision, which controls whether the cloth itself folds and intersects with its own surface; it has nothing to do with interaction between the cloth and a separate object. Answer D converts the table into an active rigid body and removes cloth entirely, which breaks the original setup and changes the simulation type unnecessarily. Remember: Cloth needs Collision — these two physics types are designed as a pair. When cloth falls through another object, your first instinct should always be to check whether that object has Collision enabled.

Question 2

An artist wants the upper edge of a hanging banner to remain attached while the rest of the mesh responds to gravity. A vertex group named Top contains the upper-edge vertices with weight 1.0. Cloth physics is already enabled, but the entire banner still falls.

What additional setup is required to use the existing group as the attachment?

Assign Top as the cloth Pin Group in the cloth shape settings. (correct answer)
Assign Top as the cloth Collision Group in the collision settings.
Assign Top as the cloth Self Collision group in the collision settings.
Assign Top to a Hook modifier placed after the cloth modifier.

Explanation: When working with Blender's cloth simulation, the key question to ask is: how does the simulation know which vertices should be fixed in place? Cloth physics on its own treats every vertex as free to move — you must explicitly tell it which vertices are "pinned" and should ignore gravity. The mechanism for this is the Pin Group field, found in the cloth modifier's Shape settings. When you assign a vertex group there, Blender reads each vertex's weight (0.0 to 1.0) to determine how strongly it resists simulation forces. Since your Top group has weight 1.0, those upper-edge vertices will be completely immovable — exactly the hanging-banner behavior you want. So option A is the correct setup, and the cloth simulation will then treat those vertices as anchors while the rest drapes naturally. Option B is a trap: the Collision Group controls which other objects this cloth can collide with, not which of its own vertices stay fixed. Option C, the Self Collision group, limits which parts of the cloth check for collisions against itself — useful for preventing a garment from clipping through its own fabric, but irrelevant to pinning. Option D describes a real Blender tool — Hook modifiers can pull vertices toward an object — but placing a Hook after the cloth modifier in the stack is actually incorrect workflow; Hooks used for pinning must come before or be handled differently, and regardless, the question already provides a vertex group meant for pinning, making the Hook approach unnecessarily complex. A useful rule of thumb: whenever a cloth object needs fixed vertices, go straight to Shape → Pin Group. That's the dedicated, purpose-built control for this exact scenario.

Question 3

A low-resolution cloth plane has a Subdivision Surface modifier and a Cloth modifier. With Subdivision placed after Cloth, the rendered fabric looks smooth, but the simulation still bends in broad, angular sections.

Which modifier arrangement is most appropriate if the added subdivisions must participate in the cloth calculation?

Place Subdivision before Cloth so the solver receives the denser evaluated mesh. (correct answer)
Place Cloth before Subdivision so the solver receives the smoothed final surface.
Place Subdivision after Cloth and increase only the render subdivision level.
Apply Cloth first, then place Subdivision before the baked animation data.

Explanation: When working with modifier stacks in Blender, the critical principle is that modifiers execute from top to bottom, and each modifier only "sees" the mesh that exists when it runs. This question tests whether you understand how that order affects physics simulations specifically. The Cloth modifier simulates physics on whatever geometry it receives as input. If the mesh it receives has only a few hundred polygons, the simulation treats those low-resolution vertices as its control points — meaning bending and folding can only occur where those sparse vertices exist, producing the broad, angular deformation the passage describes. To give the cloth solver more points to work with, you need the subdivided mesh to arrive before Cloth runs. That's exactly what placing Subdivision Surface above Cloth in the stack accomplishes — the solver receives a denser mesh and can produce finer, more realistic folds. A is correct. B gets the logic backwards. Placing Cloth before Subdivision means the simulation runs on the coarse mesh first, and Subdivision only smooths the visual result afterward — the underlying simulation data is still low-resolution. This is precisely the problem described in the passage. C is a partial workaround trap. Increasing the render subdivision level only affects how the final surface looks in renders; it does nothing to feed extra geometry into the physics calculation itself. D is a workflow dead-end. Applying the Cloth modifier bakes its result into static geometry — there's no simulation to feed subdivisions into afterward, so reordering accomplishes nothing meaningful. Study tip: Whenever a question involves physics simulations and modifier order, ask yourself: "What does the physics solver actually receive?" That input mesh determines simulation quality — smoothing applied after physics is purely cosmetic.

Question 4

A cape and a character were scaled together in Object Mode to one-tenth of their original size. Neither object's scale has been applied. Cloth and Collision physics are then added using default distance and thickness values, and the cape appears unusually stiff and separated from the character.

Which workflow is the best first correction before tuning the cloth properties?

Convert both objects to curves, restore their scale, and add Cloth again.
Apply Location to both objects, rebake the cache, and reduce gravity.
Increase collision thickness on both objects, then raise cloth stiffness.
Apply Scale to both objects, clear the simulation cache, and test again. (correct answer)

Explanation: Whenever you see a question about physics simulations behaving strangely after scaling objects in Blender, the first thing to investigate is whether scale has been applied. Blender's physics engines — Cloth, Rigid Body, Collision — read real-world dimensions based on the object's applied scale, not its visual size. When you scale an object in Object Mode without applying the scale, Blender internally still treats the mesh as its original size. So a cape scaled to one-tenth its size but with an unapplied scale of 0.1 is seen by the physics engine as ten times larger than it appears. Default cloth stiffness and collision distance values are calibrated for that inflated internal size, which is exactly why the cape looks stiff and floats away from the character. The correct workflow is D: apply scale to both objects (Ctrl+A → Scale), then clear the simulation cache and run a fresh bake. This forces the physics engine to recalculate using accurate dimensions, making default values behave as expected. A is wrong because converting to curves doesn't fix the underlying scale problem — it changes the object type unnecessarily and complicates the workflow. B is a trap: applying Location has no effect on physics calculations, which depend on scale, not position. Rebaking and adjusting gravity won't fix geometry the engine is misreading. C attempts to compensate for the symptom by cranking up thickness and stiffness, but you'd be endlessly chasing values without solving the root cause. A good rule of thumb: before adding any physics simulation in Blender, always apply scale with Ctrl+A. Make it a non-negotiable first step in your setup checklist.

Question 5

A cloth simulation has already been baked. The artist then increases bending stiffness and changes the collider's position, but playback continues to show the old result.

What should the artist do to evaluate the revised setup correctly?

Increase the cache end frame, preserve baked frames, and render the animation.
Disable viewport overlays, reload the scene, and play from the current frame.
Apply the Cloth modifier, retain the existing bake, and move the collider again.
Delete or free the cloth bake, return to the cache start frame, and simulate again. (correct answer)

Explanation: Whenever you see a question about cloth simulations and baking in Blender, think about how the cache system works: a bake is a stored recording of a simulation. Once baked, Blender reads from that cache rather than recalculating physics, which means any changes you make afterward are completely ignored during playback until you clear that stored data. This is exactly why D is correct. To evaluate a revised setup, you must first free (delete) the existing bake so Blender knows to recalculate rather than replay the old recording. You then return to the cache start frame — because Blender needs initial conditions to compute the simulation forward — and play through so the physics engine processes your updated bending stiffness and new collider position fresh. A is a trap that sounds procedural but misses the core problem. Increasing the end frame and rendering while preserving the bake just outputs the old cached result in higher quality — nothing changes because the stale bake is still in control. B confuses viewport display settings (overlays) with simulation data. Disabling overlays and reloading the scene doesn't touch the physics cache; you'd still see the same old result. C reflects a misunderstanding of the modifier stack. Applying the Cloth modifier converts the simulation result to static geometry — it doesn't let you re-simulate with new parameters. Keeping the existing bake on top of that makes things worse, not better. The key study tip: in Blender physics, bake = locked. Whenever a question mentions that changes "aren't showing up" after baking, your first instinct should always be to free the bake and re-simulate from the start frame.

Question 6

A wide cloth strip folds over itself after landing on a pedestal. It collides correctly with the pedestal, but opposite layers of the strip pass through one another. The pedestal already has Collision physics enabled.

Which change addresses the layer-to-layer penetration without replacing the pedestal setup?

Enable Self Collision on the cloth and use suitable self-collision distance and quality. (correct answer)
Enable another Collision modifier on the pedestal and increase its outer thickness.
Duplicate the cloth modifier and place the duplicate below the original modifier.
Disable collisions on the pedestal and increase the cloth's structural stiffness.

Explanation: When a cloth object folds or crumples in Blender, you're dealing with two distinct collision problems: the cloth hitting external objects, and the cloth hitting itself. These are handled by completely separate systems. External collisions are controlled by the Collision modifier on other objects, while self-collision — layers of the same mesh passing through each other — is controlled by a dedicated setting inside the Cloth modifier itself. Since the cloth already collides correctly with the pedestal, the external collision system is working fine. The problem is that opposite layers of the cloth ignore each other. This is exactly what Self Collision in the Cloth modifier's properties is designed to solve. Enabling it, then tuning the Distance value (how close cloth faces can get before repelling) and Quality (simulation steps for self-collision resolution), directly addresses layer-to-layer penetration — making A the correct answer. B is incorrect because adding another Collision modifier to the pedestal only affects how the cloth interacts with the pedestal, not with itself. Increasing outer thickness would actually make the pedestal collision thicker, doing nothing for cloth-on-cloth issues. C is a nonsense operation — duplicating a Cloth modifier doesn't create a self-collision layer; Blender doesn't work that way, and stacking cloth modifiers would break the simulation. D moves in the wrong direction entirely: disabling pedestal collision removes the working part of your setup, and increasing structural stiffness makes cloth stiffer, not collision-aware — the layers would still pass through each other, just more rigidly. Remember: external collision = Collision modifier on the other object; self-collision = setting inside the Cloth modifier. Keeping these two systems mentally separate will help you diagnose cloth problems quickly.

Question 7

A small collision object moves rapidly through a hanging cloth between adjacent animation frames. Slow-moving tests collide correctly, but at full speed the object sometimes passes through the cloth even though Collision physics is enabled.

Which change is most likely to improve detection of the fast interaction?

Increase only the cloth's bending stiffness and preserve the existing cache to retain the old result.
Decrease cloth simulation quality so the collider advances through the solver in fewer, larger steps.
Increase cloth simulation quality or time-step sampling, then recompute the simulation. (correct answer)
Add a Solidify modifier to the collision object and increase its thickness to compensate for missed frames.

Explanation: When a fast-moving object tunnels through cloth in Blender, you're dealing with a temporal resolution problem. The physics solver advances time in discrete steps; if those steps are too large, the collider can jump from one side of the cloth to the other between calculations, and no collision is ever detected. This is sometimes called "tunneling." The fix is to make the solver sample time more finely so it catches the object mid-passage. That's exactly what C addresses. Increasing the cloth's simulation quality (found in the Cloth properties as "Quality Steps") subdivides each frame into more sub-steps, giving the solver more opportunities to detect the collision. Increasing time-step sampling works the same way. Crucially, you must then recompute the simulation — cached results store the old, flawed calculation, so clearing and rebaking is essential. A fails on two counts: bending stiffness controls how the cloth resists folding, not whether collisions are detected, and preserving the old cache means you're keeping the broken result — the exact opposite of what's needed. B actively worsens the problem. Decreasing quality means fewer, larger sub-steps, which makes tunneling more likely, not less. D is a common misconception. Adding a Solidify modifier to a collision object changes its visual geometry but does not directly increase the collision margin in a way that compensates for fast-moving tunneling. Collision thickness/margin settings exist in the Physics properties, and even those are a secondary fix compared to improving step resolution. Study tip: Whenever you see cloth or soft-body artifacts that only appear at high speeds, think "temporal resolution first" — more quality steps, then rebake.

Question 8

A character's shoulder is deformed by an Armature modifier. Collision physics is enabled on the character, but the cloth reacts to the shoulder's undeformed rest shape rather than its animated position. In the character's modifier stack, Collision is evaluated before Armature.

Which modification most directly makes the collision surface follow the evaluated armature deformation?

Place Collision before Armature and increase the cloth's pinning weights.
Place the Armature deformation before Collision in the character's modifier stack. (correct answer)
Move the character's Armature modifier onto the cloth below its Cloth modifier.
Remove Collision from the character and enable Self Collision on the cloth.

Explanation: Whenever you see a question about modifiers and physics interactions in Blender, think about modifier stack order: Blender evaluates modifiers top-to-bottom, and each modifier receives the mesh output of the one above it. This means the order determines what geometry a modifier actually "sees." In this scenario, the Collision modifier is sitting above the Armature modifier. That means Blender evaluates Collision first — against the original, undeformed rest mesh — before the Armature has a chance to pose the shoulder. The cloth simulation never knows the shoulder moved. The fix is to ensure the Armature deforms the mesh before Collision reports that geometry to the physics system. B is correct because placing the Armature modifier above Collision in the stack means the mesh is fully posed when Collision is evaluated. The cloth then reacts to the shoulder's actual animated position, exactly as intended. A is wrong because it reverses the modifier placement (putting Collision before Armature again, which is the original broken setup) and adding pinning weights addresses cloth attachment, not the collision surface accuracy. It doesn't solve the root problem. C is wrong because moving the character's Armature modifier onto the cloth object makes no sense — the armature deforms the character mesh, not the cloth. Misplacing it there would break the character's deformation entirely. D is wrong because removing Collision from the character and enabling Self Collision on the cloth are separate features. Self Collision prevents the cloth from intersecting itself, not from colliding with the character's body. When troubleshooting physics in Blender, always ask: "Is the geometry fully evaluated before the physics modifier sees it?"

Question 9

A cloth cache begins at frame 1. After opening the file, an artist jumps directly to frame 80 and judges the cloth from that frame. The displayed state is incorrect, although the settings and collision objects appear valid and no bake exists.

What is the most reliable next step for obtaining the intended frame-80 state?

Stay on frame 80 and repeatedly toggle the Cloth modifier's viewport visibility.
Return to frame 1 and play or calculate the simulation sequentially through frame 80. (correct answer)
Change the cache start to frame 80 and evaluate only that single timeline frame.
Apply the Cloth modifier at frame 80 and then restart playback from frame 1.

Explanation: Whenever you see a question about cloth simulations in Blender, think about how physics caches work: they store sequential, interdependent frame states. Each frame's result depends on every frame that came before it — the simulation must be computed in order, starting from the cache's beginning frame. This is why jumping directly to frame 80 produces an incorrect state. Without a bake, Blender hasn't calculated frames 1 through 79, so it has no valid data to build frame 80 from. The cloth essentially has no history, and the displayed result is meaningless. The reliable fix is B: return to frame 1 and play or step through the simulation sequentially, allowing Blender to compute each frame in order until it reaches frame 80. This gives the solver the complete chain of states it needs. A is a trap — toggling viewport visibility simply refreshes the display, but it doesn't supply the missing simulation history. You'll still see a broken result because the underlying data was never computed. C is fundamentally flawed: changing the cache start to frame 80 tells Blender to begin the simulation there, which means the cloth has zero frames of prior motion — it produces a completely different (and still wrong) result, not the intended one. D makes no sense in this context; applying the modifier at frame 80 collapses the mesh into static geometry at that broken state and discards the simulation entirely, which doesn't recover anything. As a study tip, remember: Blender cloth simulations are sequential by nature. Any time a question involves jumping to a mid-timeline frame without a bake, the answer will always involve computing from the start.

Question 10

A thin sheet lands on a rounded collision object without penetrating it, but it visibly floats too far above the surface. The collider and cloth both have applied scale, and the mesh resolution is adequate.

Which adjustment most directly reduces the gap while retaining collision detection?

Reduce cloth bending stiffness and disable collision on the rounded object.
Increase the relevant cloth and collider collision-distance settings, then rebake.
Reduce the relevant cloth and collider collision-distance settings, then clear the cache. (correct answer)
Increase cloth mass and disable self-collision before replaying the timeline.

Explanation: When troubleshooting cloth simulation gaps in Blender, focus on the collision distance parameters — specifically the "Distance" value under the cloth's Collision settings and the collider object's Collision modifier distance. These values define how close the cloth mesh can get to a surface before the solver pushes it away. If these distances are too large, the cloth hovers visibly above the surface even though collision is technically working. This is exactly why C is correct: reducing both the cloth collision distance and the collider's collision distance directly shrinks that invisible buffer zone, letting the cloth settle much closer to the surface. Clearing the cache afterward is essential — without it, Blender replays old baked frames that don't reflect your changes, so you'd see no difference. A is a trap because disabling collision on the rounded object removes the detection entirely, causing the cloth to pass through the surface rather than rest on it. Reducing bending stiffness changes drape behavior but doesn't close the floating gap. B goes in the wrong direction entirely. Increasing collision distances makes the gap larger, not smaller — it pushes the cloth even further from the surface. Rebaking won't save you when the root setting is working against you. D addresses mass and self-collision, neither of which control the gap between the cloth and a collider object. Heavier cloth may drape differently, but if the collision distance buffer is large, the cloth still floats above it. A useful rule of thumb: whenever cloth floats above a collider, think "distance values too high." Whenever cloth passes through, think "distance values too low or collision disabled."