You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want a screenshot of the game's output after things like shaders and aspect-ratio correction have been applied, you can use your operating system's built-in screenshot tool. The internal "save screenshot" feature captures the actual pixels the console produces, in whatever aspect ratio it produces them.
This often produces surprisingly wide screenshots, because although it's impractical to change the number of rows of pixels output (when connected to a standard standard-definition CRT TV), it's very easy to change the number of columns and consoles did, frequently.
I'm not sure exactly what the deal with the N64 was, but for the SNES games could present 256 pixels per scanline, or 512 pixels. Worse, they could switch between those two resolutions per scanline, not just per-frame. The emulator must set aside space to store the frame as it's being rendered, and since it doesn't know how wide the frame will be before it's rendered, it picks the maximum size just to be safe. As a result, even if the SNES is showing a 256×240 image, ares' internal screenshot tool will produce a 512×240 screenshot.
(As aside, the Mega Drive is even worse off—its two resolutions are 256px and 320px, so to make sure both resolutions can fit neatly in the same image, it produces 1280x240 screenshots)
Describe the bug
Whenever I take a screenshot, via ares v139 on macOS, the resulting images' dimensions are all messed up.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The saved screenshot should have normal dimensions, like 4x3, not stretched out like my examples below show.
Screenshots
Additional context
Here's what my settings in ares are
I've even tried to make sure all of the scaling options are 1:1 pixel perfect:
Am I missing something super obvious? Any help at all would be greatly appreciated! 👍🏻
The text was updated successfully, but these errors were encountered: