Quick answer: Round the scroll position to whole pixels, enable pixel rounding in project properties, and avoid stacking ScrollTo with manual scroll on the same tick.
If your Construct 3 camera shimmers when following on a rotated layer, sub-pixel scrolling is the cause. Pixel rounding fixes it. Here is how.
How to fix it
1. Enable pixel rounding
Turn on Pixel rounding in Project Properties so layout scroll and object positions snap to whole pixels, removing the sub-pixel shimmer on rotated layers.
2. Avoid double scroll control
Do not combine the ScrollTo behavior with a Scroll to action on the same tick; the two write conflicting scroll values and fight each frame.
3. Round manual scroll
If you set scroll yourself, use round() on the X/Y before scrolling so the camera never lands between pixels on a parallaxed or rotated layer.
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.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.