# \[Issue\] HTML5 build gameplay is "zig-zaggy" when played on mobile

**URL:** <https://forum.defold.com/t/issue-html5-build-gameplay-is-zig-zaggy-when-played-on-mobile/50069>\
**Category:** Questions\
**Created:** [April 23, 2019, 8:26am UTC](https://forum.defold.com/t/issue-html5-build-gameplay-is-zig-zaggy-when-played-on-mobile/50069 "2019-04-23T08:26:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Mathias\_Westerdahl](https://forum-defold.b-cdn.net/user_avatar/forum.defold.com/mathias_westerdahl/32/228_2.png) [@Mathias\_Westerdahl](https://forum.defold.com/u/Mathias_Westerdahl)\
**Post date:** [April 23, 2019, 8:44am UTC](https://forum.defold.com/t/issue-html5-build-gameplay-is-zig-zaggy-when-played-on-mobile/50069/2 "2019-04-23T08:44:57Z")

</div>

Well, “ok” is a subjective term here. You have to decide what is ok. 🙂

It’s quite easy to get floating point precision issues, especially if you try to increment floating point numbers “forever”. Even though Lua supports double precision floats, we store them as single precision floats internally. And depending on your precision in your shaders, you can get artifacts there as well.

Here’s a [post about floating point precision](https://forum.defold.com/t/floating-point-precision/11247) with more info about the actual “issue”.

For you use case, I’d keep the player close to origin (e.g at a fixed position), and instead spawn geometry close by, and let it animate towards the player. That way all floating point values are quite low, and will keep their precision at an acceptable level.

---

_[View the full topic](https://forum.defold.com/t/issue-html5-build-gameplay-is-zig-zaggy-when-played-on-mobile/50069)._
