-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional aspect ratios & resolutions #102
Comments
Some additional thoughts on this topic: The current resolutions were picked due to their ability to scale perfectly into either 1080p , 720p, or both. The currently supported resolutions are:
So with that in mind, we should target these resolutions
And work our way down. Alternatively, we could just open up the resolutions and allow them to be input by the user, with some prevention of going over 1920 x 1080, and recommending those with pixel perfect scaling. Include useful data like aspect ratio, and some common recommended ones. |
I think a stricter selection is better. An oft-cited benefit of developing for a virtual console is that it is helpfully constrained. You may even consider determining a default resolution that’s already set for people who just wanna get going as quickly as possible. I reckon that ought to be either the Low or High resolution; can only be one though! |
The default resolution is currently the
Yep exactly the reason for opening this up to discussion. Flexibility is good, but too much could let people shoot themselves in the foot and end up with huge black bars or bad scaling.. Consistency is good, but too much and everything is the same. But I do think it would be great to add in some square resolutions, like
And potentially some 4:3 ones... but there are ~12 decent resolutions we could use to cover flexibility back towards the 1920x1080 target with good scaling. Some of the iconic classics like 320x240, 640x480, would likely be OK, but 800x600, 1024x768, are too big and would end up with borders. |
Took a second pass at 4:3 resolutions...
We lose those "iconic" resolutions from previous times, but make up for it with solid consistency and a similar distribution against the standard 16:9 ones. Square resolutions can be:
Squares are kinda a special case andI'm fine with them having borders around the edges. Also I decided against including 720x720 and 1080x1080 just to keep with the "powers of 2-ish" theme. I think in the farther future we could add something like "Exotic Resolutions" for advanced usesrs, and use things like 720 and 1080 squares, portrait resolutions, and those iconic 4:3 ones which just don't scale well these days. Anyway, I think breaking this into a selection process of (1) Aspect Ratio, then (2) Resolution helps keep it simple. Instead of bombarding the user with 21 new resolution choices, they are presented with the default 16:9, Low, and can adjust to Square or Retro (or Classic, the name for 4:3), and are still presented with the familiar Ultra/Low/Med/High settings. |
Closing this as it will be resolved in #98 |
I think it would be benefecial to explore a bigger variety of aspect ratios.
Currently, the console is using a 16:9 aspect ratio, but it could be benefecial to also support others such as 4:3, 1:1, or other common sizes, such as tall or portrait style ones.
This can be done a few different ways:
Resolution
enum to be a struct, and hold both a size (ultralow, medium, high, etc) and an aspect ratio (wide, square, standard etc).LowSquare
orHighWide
It's important to choose resolutions which scale up to pixel perfect sizes, or can display cleanly on 16:9 displays though, as this is currently the target platforms.
This would likely break older versions, but I think it's worth getting this done now as opposed to later.
The text was updated successfully, but these errors were encountered: