# 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:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hogan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/hogan/32/17525_2.png) [@hogan](https://forum.makecode.com/u/hogan)\
**Post date:** [June 14, 2019, 6:59am UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255/1 "2019-06-14T06:59:36Z")

</div>

![accc](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/1X/d5b0a3e14d261eb27f1dab8d8efc01afb0e59ba5.png)  
…

---

<div class="post-metadata">

**Author:** ![peli](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/peli/32/12_2.png) [@peli](https://forum.makecode.com/u/peli)\
**Post date:** [June 17, 2019, 8:55pm UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255/2 "2019-06-17T20:55:26Z")

</div>

This is a current limitation of the physics engine. See issue [https://github.com/microsoft/pxt-arcade/issues/1057](https://github.com/microsoft/pxt-arcade/issues/1057)

---

<div class="post-metadata">

**Author:** ![hogan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/hogan/32/17525_2.png) [@hogan](https://forum.makecode.com/u/hogan)\
**Post date:** [June 18, 2019, 1:59am UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255/3 "2019-06-18T01:59:57Z")

</div>

thank u~

---

<div class="post-metadata">

**Author:** ![kjw](https://avatars.discourse-cdn.com/v4/letter/k/e79b87/32.png) [@kjw](https://forum.makecode.com/u/kjw)\
**Post date:** [September 20, 2019, 2:09pm UTC](https://forum.makecode.com/t/why-is-the-speed-up-to-153-floating-point-numbers/255/4 "2019-09-20T14:09:15Z")

</div>

Is there still a maximum speed, what is it? How is that applied to an accelerating object?

---

<div class="post-metadata">

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

</div>

There is still a max speed, but it’s much higher now and we can change it if people feel it is still too slow. @jwunderl any chance we could get a TS API for changing it?

---

<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)