liabru
liabru
Closing as I think this was covered by #777 which is now released in `0.19.0` (see the release notes). Thanks again.
Sounds like a nice solution for now, but reopening this as a feature request as it would be nice to have!
Up to and including the release `0.18.0` velocity and speed units are (effectively) `pixels per deltaTime ms` which I think is what you're seeing, for these versions: normalise the result...
I'm not quite sure but worth trying out the latest release `0.19.0` as that includes #777, which has some changes related to this topic that might help.
Closing this thread to refer to updates in #702 on this topic, thanks again for the reports here.
As of [0.20.0](https://github.com/liabru/matter-js/pull/1300) there is now built in `Matter.Runner` support by default for fixed timestep with high refresh displays see https://github.com/liabru/matter-js/pull/1300.
The docs were updated, `Matter.Engine` no longer requires time correction params. Thanks again.
I think the issue is that while `Matter.Runner` should be able to handle this, it actually doesn't because `runner.deltaMin` and `runner.deltaMax` clamp the frame delta for stability reasons, but this...
PR #1254 includes updates relating to this issue, see details in that branch if you wish to try it out.
As of [0.20.0](https://github.com/liabru/matter-js/pull/1300) there is now built in `Matter.Runner` support for fixed timestep with high refresh displays see https://github.com/liabru/matter-js/pull/1300. Closing this one. Thanks all!