# Maze tile map navigation issues

**URL:** <https://forum.makecode.com/t/maze-tile-map-navigation-issues/484>\
**Category:** Arcade\
**Created:** [August 25, 2019, 4:44pm UTC](https://forum.makecode.com/t/maze-tile-map-navigation-issues/484 "2019-08-25T16:44:04Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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 16, 2019, 5:44pm UTC](https://forum.makecode.com/t/maze-tile-map-navigation-issues/484/10 "2019-09-16T17:44:07Z")

</div>

There are some definite issues/quirks with the mix of real numbers for physics and the discrete world of MakeCode Arcade’s tile maps and sprites. This example with maze navigation is frustrating and I suspect it’ll prove difficult to explain this behaviour to children.

I’ve put together some other tests which test things that are currently ok and highlight some problems with a 16x16 sprite passing a 16 wide gap slowly with acceleration toward that gap, see [Physics engine tests?](https://forum.makecode.com/t/physics-engine-tests/509/5/). Those might be useful to verify any changes made don’t alter desirable/current behaviour and to see what they do in terms of improving gap passing.

---

_[View the full topic](https://forum.makecode.com/t/maze-tile-map-navigation-issues/484)._