Skip to content
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

Saved screenshots don't have the correct dimensions #1567

Closed
eisnerguy1 opened this issue Jul 15, 2024 · 2 comments
Closed

Saved screenshots don't have the correct dimensions #1567

eisnerguy1 opened this issue Jul 15, 2024 · 2 comments

Comments

@eisnerguy1
Copy link

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:

  1. Go to the "Tools" menu
  2. Click on 'Capture Screenshot', or press the hotkey "`"
  3. Open up the screenshots folder "/Users/eisnerguy1/Library/Application Support/ares/ScreenshotsNintendo 64", as an example on macOS
  4. See the odd saved screenshot dimensions.

Expected behavior
The saved screenshot should have normal dimensions, like 4x3, not stretched out like my examples below show.

Screenshots
F-Zero X (USA) 2024-07-14 15-10-19
NUD-EFZJ-JPN_LB_sealed 2024-07-15 06-26-38

Additional context
Here's what my settings in ares are
Screenshot 2024-07-15 at 5 51 53 PM
Screenshot 2024-07-15 at 5 52 03 PM
Screenshot 2024-07-15 at 5 52 06 PM

I've even tried to make sure all of the scaling options are 1:1 pixel perfect:
Screenshot 2024-07-15 at 7 12 27 PM
Screenshot 2024-07-15 at 7 12 34 PM
Screenshot 2024-07-15 at 7 12 39 PM

Am I missing something super obvious? Any help at all would be greatly appreciated! 👍🏻

@Screwtapello
Copy link
Contributor

This is behaving as intended.

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)

@eisnerguy1
Copy link
Author

Ah, gotcha. Thanks for the clarification 😄 I kinda managed to get 1:1 pixel screenshots with some trickery so, this can be closed 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants