# \[🐛\] Zoom‑in limited by maximum texture size

**URL:** <https://forum.mapillary.com/t/zoom-in-limited-by-maximum-texture-size/7843>\
**Category:** Website\
**Created:** [February 29, 2024, 12:53pm UTC](https://forum.mapillary.com/t/zoom-in-limited-by-maximum-texture-size/7843 "2024-02-29T12:53:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![GITNE](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/gitne/32/70659_2.png) [@GITNE](https://forum.mapillary.com/u/GITNE)\
**Post date:** [February 29, 2024, 12:53pm UTC](https://forum.mapillary.com/t/zoom-in-limited-by-maximum-texture-size/7843/1 "2024-02-29T12:53:48Z")

</div>

This is more of an FYI for @boris because it is a [known issue](https://github.com/mapillary/mapillary-js/issues/226). But, it has been affecting me and potentially others, especially on mobile devices for quite some time now. For the affected, the issue is actually more about functionality than performance. There is indeed a performance aspect to this but imho even the trivial implementation solving this issue is going to perform well enough.

The basic problem comes down to that you cannot zoom‑in fully if `GL_MAX_TEXTURE_SIZE` is smaller than an image in one dimension.

| Zoom level | `GL_MAX_TEXTURE_SIZE` |
| --- | --- |
| 2 | `16384` | `4096` |
| ![GL_MAX_TEXTURE_SIZE == 16384](https://us1.discourse-cdn.com/flex015/uploads/mapillary/original/3X/c/9/c90bb5f55544ec06709066348277d795bda68be8.jpeg) | ![GL_MAX_TEXTURE_SIZE == 4096](https://us1.discourse-cdn.com/flex015/uploads/mapillary/original/3X/3/b/3b70d0a7428ce843454757f1d45bc0d04b7af521.jpeg) |

For example, my smartphone has a limit of `GL_MAX_TEXTURE_SIZE == 2048`. Hence, things look even worse than in the example above (often enough without zooming‑in). Strangely enough, even Mesa 3D’s software renderer has a limit of `GL_MAX_TEXTURE_SIZE == 16384` which you would normally expect to be `GL_MAX_TEXTURE_SIZE == 2147483647` because this is the maximum `GLint` value. Eventually the Mesa 3D software renderer is going to be affected too, especially when things should evolve to GP photography. But, I am sidetracking. Low `GL_MAX_TEXTURE_SIZE`s on mobile devices is an existing issue that cuts into functionality.

---

<div class="post-metadata">

**Author:** ![boris](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/boris/32/71767_2.png) [@boris](https://forum.mapillary.com/u/boris)\
**Post date:** [February 29, 2024, 2:46pm UTC](https://forum.mapillary.com/t/zoom-in-limited-by-maximum-texture-size/7843/2 "2024-02-29T14:46:32Z")

</div>

I’m seeing broken images in your post above - could you check?

---

<div class="post-metadata">

**Author:** ![boris](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.mapillary.com/boris/32/71767_2.png) [@boris](https://forum.mapillary.com/u/boris)\
**Post date:** [March 1, 2024, 2:06pm UTC](https://forum.mapillary.com/t/zoom-in-limited-by-maximum-texture-size/7843/4 "2024-03-01T14:06:44Z")

</div>

Thanks for the updated screenshots! cc: @nikola