liabru

This is now released as of [0.20.0](https://github.com/liabru/matter-js/pull/1300), thanks all!

Closing this thread to refer to updates in #702 on this topic, thanks again for the report 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.

@photonstorm thanks for taking a look - I've pushed an update re. sleeping bodies here, hopefully that covers it?

@photonstorm I've just pushed a couple more changes to handle pair removal in composite removal cases, that might be the last part here so I think I'll get this merged...

Thanks for your comments on this. The way timing works is being overhauled in this PR #777 which I hope to revisit now that I have implemented a better way...

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 for fixed timestep with high refresh displays see https://github.com/liabru/matter-js/pull/1300. Closing this one. Thanks for the report!

There's nothing built in for this at the moment. The current ray casting approach is very basic as it mostly leverages the built in collision detection so I could get...

If you're using circles for everything, it might be a good idea to write an optimised [ray-circle cast](http://stackoverflow.com/questions/1073336/circle-line-segment-collision-detection-algorithm) because built in one is not particularly efficient for this case (at...