Fix: Construct 3 Physics Joint Anchor Drift After Pause

A physics puzzle uses revolute joints. Pausing via Time Scale = 0, resuming, then waiting a moment — the jointed bodies have slightly separated from their anchors. Each pause cycle adds drift. Eventually visible misalignment.

Why Time Scale Zero Drifts

Setting time scale to 0 makes dt = 0 for the Box2D step. The solver still runs each tick, just with no time elapsed. Some solver passes still apply position correction (Baumgarte stabilization, for example) even at dt=0, accumulating tiny corrections per tick that show as drift.

The Fix

// On pause
System Set global variable IsPaused to true
System Set time scale to 0
PhysicsWorld Stop simulation   // the key step

// On resume
PhysicsWorld Resume simulation
System Set time scale to 1
System Set IsPaused false

Stop simulation halts all Box2D internal step calls. The solver doesn’t run; corrections aren’t applied; no drift. Resume restarts cleanly.

Rebuild Joints if Drifted Already

If your project already has accumulated drift, rebuild joints on resume:

On resume:
    Sprite(joint A) Physics Destroy joint "swing"
    Sprite(joint A) Physics Create revolute joint "swing" to SpriteB at currentX, currentY

The new joint anchors at current positions; the visual state is preserved while the solver gets a fresh start.

Physics Time Step vs Game Time

Physics behavior has its own internal time step (Project Settings → Physics → Step Size). For deterministic physics, set Stepping Mode = Fixed and pick a step appropriate for your game (1/60s is common). Variable stepping can also contribute to drift.

Verifying

Pause and resume 50 times in a stress test. Anchor positions should stay identical to before pausing. Print global positions of jointed bodies before and after each pause; diff should be zero.

Understanding the issue

The challenge with physics-related bugs is reproducibility. A symptom you see in a 30 fps build may vanish at 60 fps because the integrator's step size changed. Reproducing reliably means controlling both your inputs and the engine's tick rate.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“Time scale 0 isn’t a real pause for Box2D — the solver still nudges. Stop simulation is the clean pause.”

For any game using physics joints, build a centralized pause routine that Stops physics and Resumes — never scatter time scale tweaks.