I am working on a project with some finer details, and I noticed that they didn't show up well in the Scratch running box thing. I did some research and found that Scratch's display is a low resolution 480x360 screen size. Is there any way to improve the resolution or quality? Maybe you could customize it upon opening a project, like next to the title and see project page buttons. Thanks for considering.

bump

Though there are many upsides to this, such as higher quality images, what would this update do to current projects? The coordinate system would become completely messed up if the resolution was increased because current projects assume the stage size is 480x360. If it were to be upscaled, how would the coordinates scale properly? It's not like the ST can go through everyone's projects and change the code.

If you really want this update, you don't need to wait for Scratch to add it. Turbowarp.org has this feature where you can customize the stage size.

Maybe Scratch could do something like

if <<[(date project created)] < [2/8/23]>> then 
set screen resolution to 480x360
  

else
set screen resolution to 1440x1080

end

-PolyCode-testing wrote:

Maybe Scratch could do something like

if <<[(date project created)] < [2/8/23]>> then 
set screen resolution to 480x360
  

else
set screen resolution to 1440x1080

end

What about backpacked code? If I wanted to use a bit of code earlier than the update and transfer it to a project with the increased screen resolution, the code wouldn't be compatible due to different screen sizes. I also think remixing might have this issue.

This topic is technically a duplicate, as the topic found here is also asking for a wider screen space (16x9 to be exact).
However, that topic is specifically asking for 16x9, and it's unclear if this topic is asking for that or something different.

bump

Use fullscreen for higher quality unless there's bitmap

qwerty_wasd_gone wrote:

Use fullscreen for higher quality

Fullscreen changes the screen size, not the stage size. The stage stays as 480x360 no matter if it's in fullscreen or not.

No support. Not everything needs to be widescreen and/or high quality.

Another reason is text. If you have some small text, it often cuts out due to the limit in pixels. I liked @PhiPhenomenon's idea of having backpackable code or an option to toggle it on.

-PolyCode-testing wrote:

I liked @PhiPhenomenon's idea of having backpackable code

Backpacked code is an issue, not a fix. How do you convert pre-update code to it being compatible with the screen size?

As someone who creates operating system projects, you get my full support. I have tried to implement a feature like this before in one of my projects, but it was clunky, as you had to use TurboWarp (which most Scratchers probably don't even know exists, let alone use) to access the higher resolutions; I think this would help make resolution features less clunky and more accessible to the ordinary Scratcher.