# What's the plan on how to support higher resolution displays?

**URL:** <https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712>\
**Category:** Arcade\
**Created:** [October 28, 2019, 12:43pm UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712 "2019-10-28T12:43:27Z")\
**Posts on this page:** 5\
**Page:** 1

<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:** [October 28, 2019, 12:43pm UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712/1 "2019-10-28T12:43:27Z")

</div>

I’ve read the current use of 160x120 (rather than the physical 128) is to support 320x240 in the future. I’m wondering how well existing code will work when the resolution changes.

Tutorials like Chase the Pizza specifically use 160 and 120 values. Some code may use the `screen width` and `screen height` variables to derive positions on the screen. The current physics engine also uses pixels per second as a measurement.

What’s the plan for supporting higher resolutions? Is there a good practice guide for developers on how to future proof their code for this eventuality?

On a slightly related note, I’ve previously raised the issue that the simulator does not default to integer mulitples of the screen resolution like Scratch does [Simulator Resolution](https://forum.makecode.com/t/simulator-resolution/399).

---

<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:** [October 28, 2019, 1:27pm UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712/2 "2019-10-28T13:27:05Z")

</div>

And for Chase the Pizza, were the random ranges intended to be `8` to `152` and `8` to `112`?

---

<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:** [October 28, 2019, 3:47pm UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712/3 "2019-10-28T15:47:09Z")

</div>

> [@kjw](#):
>
> What’s the plan for supporting higher resolutions? Is there a good practice guide for developers on how to future proof their code for this eventuality?

The resolution in game will not change. However, we support rendering the games to screen with higher definitions (eg. 4:3 screen like ILI9341 or just about any screen using Rpi0).

---

<div class="post-metadata">

**Author:** ![mmoskal](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/mmoskal/32/20_2.png) [@mmoskal](https://forum.makecode.com/u/mmoskal)\
**Post date:** [October 29, 2019, 7:20pm UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712/4 "2019-10-29T19:20:59Z")

</div>

To be clear, each pixel is just drawn as four physical pixels on 320x240. It looks great!

---

<div class="post-metadata">

**Author:** ![204maker](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.makecode.com/204maker/32/447_2.png) [@204maker](https://forum.makecode.com/u/204maker)\
**Post date:** [October 30, 2019, 2:38am UTC](https://forum.makecode.com/t/whats-the-plan-on-how-to-support-higher-resolution-displays/712/5 "2019-10-30T02:38:49Z")

</div>

When will a 320x480 resolution be supported? 😏