Fix: Construct 3 Physics World Scale Too Small Causes Jitter

You’re building a tabletop-style puzzle with small physics objects — 12×12 pixel dominoes, marbles, dice. They jitter while “resting”, slowly drift, and stack unstably. A pile of dominoes can’t stay still even when nothing’s touching them. Scaling sprites up 4× in a test layout fixes the jitter completely.

Box2D’s Numerical Sweet Spot

Box2D was tuned for objects in the “real human” size range: 0.1 to 10 meters. The constraint solver uses iterative position correction with tolerances calibrated for that range. Below 0.1m, sub-millimeter errors become significant relative to object size, and the solver fails to converge — bodies oscillate or drift instead of settling.

Construct 3 abstracts the meter system via the Pixel Scale setting (default 50 px/m). A 12×12 px sprite is 0.24×0.24 meters — just inside the preferred range but at its lower bound. Bunch a few together with contact forces and the solver struggles.

Fix 1: Resize Sprites

Make the smallest physics-affected sprite at least 25 pixels in its smaller dimension. That’s 0.5m at default Pixel Scale — comfortably inside Box2D’s reliable range. Adjust your art and tilesets accordingly.

For a top-down marble game where marbles need to be small visually, scale up the whole world: make marbles 40px, walls proportionally larger, viewports zoomed in. Physics math operates on the same units as before, just at a more solver-friendly scale.

Fix 2: Lower Pixel Scale

Go to Project Properties → Physics → Pixel Scale. Default is 50. Try 25:

• At 50 px/m: a 12px object is 0.24m.
• At 25 px/m: a 12px object is 0.48m — doubled in Box2D’s units.

Physics behavior changes accordingly: same visual size, but the solver treats it as a larger object. Gravity feels weaker (more travel time per fall); tune Physics Gravity to compensate (e.g., raise from 10 to 20).

Fix 3: Increase Solver Iterations

If you can’t change object size, give the solver more iterations to converge:

In Project Properties → Physics, raise Velocity Iterations from 8 to 16, and Position Iterations from 3 to 6. Cost is double-ish CPU on physics step. Helps but doesn’t fully eliminate jitter for very small objects.

Fix 4: Lock Sleep Threshold

Once objects stop moving, Box2D puts them to “sleep”. Sleeping objects don’t simulate and don’t jitter. The threshold for sleep is tied to linear/angular velocity. If small objects never quite hit zero velocity (they always wobble at 0.5 m/s due to solver imprecision), they never sleep.

Force sleep on idle objects via event:

If Domino.Physics.LinearVelocity < 5 AND Domino.Physics.AngularVelocity < 5
    Domino.Physics.SetAwake False

The object is forced asleep when below your threshold. Manual but effective.

Verifying

Spawn 20 small objects in a pile and let them settle. Add a counter that increments each tick if any object’s position changed by more than 0.1 px. Before the fix, the counter keeps climbing forever. After the fix, the counter stops within 2–3 seconds of pile formation.

Understanding the issue

Physics simulations rely on deterministic, frame-by-frame integration of forces and constraints. When a single step misbehaves, the consequences cascade through subsequent frames - velocities accumulate error, contacts re-solve, and what should have been a clean interaction becomes visible jitter or unbounded motion.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Construct 3. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Construct 3-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Construct 3, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Box2D wants meters. If your pixels-to-meters ratio puts objects below 0.1m, the solver loses precision. Resize up or scale down the world.”

For small-prop physics games, pick Pixel Scale early and design art to match. Retrofitting later means reshooting all sprite assets.