How to Fix Platform Behavior Vibrating on a Moving Platform Seam in Construct 3

Standing where two moving platforms touch, your character buzzes up and down. The platform behavior keeps re-resolving which solid it is on as their sub-pixel positions diverge. Merging or parenting removes the seam jitter.

How to fix it

1. Use one continuous solid

Where the player walks across, span the gap with a single solid object instead of two adjacent ones so there is no seam for the platform behavior to flip between.

2. Pin the player to the platform

While the player is on a moving platform, add its movement to the player's position (or pin it) each tick so it rides smoothly instead of re-landing every frame.

3. Snap platform positions

Move platforms by integer pixel amounts (or round their positions) so abutting platforms stay perfectly aligned and the overlap test does not flicker.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Construct 3 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.