Resize the application surface to be the same size of the view, and then draw it scaled to the display width and height. This is because GameMaker’s trying to draw a 390×220 picture inside a 1366×768 surface (which is 3.5 times larger). Some lines (both columns and rows) are being skipped entirely while others are being drawn twice to fill the gaps (or at least that’s what it looks like). This is the worst possible kind of distortion for a Pixel Art game. Since my notebook display resolution is 1366×768, how is GameMaker supposed to scale a 390×220 image? The display resolution is more or less 3.5 times that of the image it’s not an integer multiple.Īnd so pixel decimation occurs. the view is set to the size of the image, but then I run the game in fullscreen. Now, my game consists of just this image, stretched to fullscreen (what a fun game!). It’s a 390×220 pattern I created in Photoshop to illustrate the issue. And since there is no such thing as half a pixel, distortion occurs.
When you resize an image to non integers multiples, GameMaker has to figure out where to draw the original pixels inside the new, bigger grid. Let’s see how to solve it using any resolution you want to use.
But the problem I was trying to address wasn’t pixel distortion. I wrote that myself to make a good looking low-res pixel art game on modern monitors, you should stick with a 384×216 resolution and scale it up 5 times to get a perfect 1920×1080 (1080p) game. It usually comes down to this simplistic rule: always resize 2D games by integer values (2x, 3x, 4x, 5x, etc) so pixel art will always look correct. Much has been written about resolution scaling in pixel art games.
0 kommentar(er)
