# Why is the speed up to 153 floating point numbers?

**URL:** <https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255>\
**Category:** Arcade\
**Created:** [June 14, 2019, 6:59am UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255 "2019-06-14T06:59:35Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jwunderl](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/jwunderl/32/5308_2.png) [@jwunderl](https://forum.makecode.com/u/jwunderl)\
**Post date:** [September 20, 2019, 8:59pm UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255/6 "2019-09-20T20:59:57Z")

</div>

Yup, max speed is currently 500 in each direction by default. It’s easy to add an api for changing it (it’s currently a parameter on the PhysicsEngine constructor, but there shouldn’t be any risk to making it adjustable without creating a new one as it’s only used at the beginning of the movement during physics.) The new physics post I made when we updated to include it has more info / an example of how you can change it for now: [New Sprite Physics in beta!](https://forum.makecode.com/t/new-sprite-physics-in-beta/306)

Edit: Wrote up a bit more reasonable ts api: [https://github.com/microsoft/pxt-common-packages/pull/974](https://github.com/microsoft/pxt-common-packages/pull/974)

---

_[View the full topic](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255)._