Question about Matter.js and its update loop

[LuisAFK]

This happened to me on one of my games and posted an issue on the Matter.js GitHub, it’s been a while since I looked.

[samme]

Matter Physics in Phaser v3.60

I don’t really use Matter and I don’t have a 144Hz monitor but here are my impressions. By default Matter makes a variable-sized step using the minimum delta from the last 60 frames, clamped within 16–33ms: These values are fine for browser animation rates of 30–60fps but above or below that Matter will be running ahead or behind the game step rate. You could limit Phaser’s frame rate to 60fps also: new Phaser.Game({ fps: { forceSetTimeOut: true, target: 60 }, physic…

[samme]

As of Phaser v3.90 or thereabouts, Matter Physics uses a fixed-size step, so I don’t think you should see any timing inconsistencies around the browser’s animation rate or need any workarounds.

There are some options for smoothing, snapping, and clamping. See the settings in MatterRunnerConfig.