# Simulator Resolution

**URL:** <https://forum.makecode.com/t/simulator-resolution/399>\
**Category:** Arcade\
**Created:** [August 4, 2019, 5:25pm UTC](https://forum.makecode.com/t/simulator-resolution/399 "2019-08-04T17:25:55Z")\
**Posts on this page:** 4\
**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:** [August 4, 2019, 5:25pm UTC](https://forum.makecode.com/t/simulator-resolution/399/1 "2019-08-04T17:25:55Z")

</div>

I note the target screen resolution for the hardware devices is 160x120. While all of them are currently 160x128 this is apparently to allow for easy/pleasant [320x240 upscaling](https://makecode.com/blog/arcade/01-18-2019#compatible-hardware).

The resolution of the simulator in Chrome on Windows varies but never matches an integer multiple of the target resolution. This makes screen grabs for the whole simulator/editor look a bit off particularly when using certain fine patterns.

This is the resolution in order as the window is _reduced_ in width:

1. 311x233
2. 188x141
3. 214x161

I measured those by hand in an image editor quickly but I think they are within +/- 1 pixel. What’s the thinking behing those resolution choices? I’m also curious why the simulator device section goes smaller but then gets bigger!?

The first is shown below (as a new user I can only add one):

![makecode-arcade-simulator-width-1-neat](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/1X/3b84745730ec64ab45d9c0735687766e59493ec2.png)

I’ll admit my “test card” image could be better, that’s 10 seconds of scrawl in the builtin editor 🙂

---

<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:** [August 4, 2019, 5:27pm UTC](https://forum.makecode.com/t/simulator-resolution/399/2 "2019-08-04T17:27:21Z")

</div>

Screen grab 2:

![makecode-arcade-simulator-width-2-neat](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/1X/81dbdfb8dd024f007765f4dd57d933f315223b68.png)

---

<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:** [August 4, 2019, 5:29pm UTC](https://forum.makecode.com/t/simulator-resolution/399/3 "2019-08-04T17:29:11Z")

</div>

Screen grab 3:

![makecode-arcade-simulator-width-3-neat](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/1X/a66a1a7994f5b78459e2734eadb12d60512135d2.png)

---

<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:** [August 4, 2019, 5:49pm UTC](https://forum.makecode.com/t/simulator-resolution/399/4 "2019-08-04T17:49:34Z")

</div>

Another peculiarity here is the simulator device gets a little bigger if, for example, the user clicks on the reset button. It changes to 328x246.

![makecode-arcade-simulator-width-4-widepressreset-neat](https://us1.discourse-cdn.com/flex020/uploads/makecode/original/1X/199b6698bc0064aae5bf7bb2bfc0aea3177d1486.png)