Screenshot Borders When It Shouldn't?

[wildgoosespeeder]

Describe the bug
Black border when there shouldn't be?

To Reproduce


See emulator settings attached and then take a screenshot. Paper Mario at title screen shows it best, but any game that doesn't do black borders or letterboxing during rendering also good for demonstration.

Expected behavior

Angrylion screenshot (actually screenshots are 320x237, but was black pixel padded so a comparison between screenshots can be made pixel per pixel 1:1)

Screenshots


Additional context
Why is output 640x240 and not 320x240? This emulator is so close for me being a full replacement for Project64 and angrylion 1.5 plug-in. I don't like GLideN64. angrylion is the closest thing I ever experienced to it being 1:1 with real hardware, but emulated instead.

[wildgoosespeeder]

Seems like high resolution games have issues too. I see a bouncing image when a game tries to go high resolution. Doesn't seem to happen with angrylion.

[remutro]

This is a known issue and has to do with how ares internally works. Systems that can output in multiple resolutions means that ares will choose the largest resolution by default so that if a game switches between resolutions it will handle it properly. As a result, screenshots are currently tied to the largest internal resolution for that particular system.

[Screwtapello]

In addition to the "screenshots are wider than you'd expect" issue remutro refers to...

I see a bouncing image when a game tries to go high resolution.

This is how an actual N64 works. TVs of the era could not display a 480p image; they would display the even rows of pixels on one frame, then the odd rows on the next, making for a 240p image that "jumps", otherwise known as 480i or an "interlaced" image.

[wildgoosespeeder]

This is a known issue and has to do with how ares internally works. Systems that can output in multiple resolutions means that ares will choose the largest resolution by default so that if a game switches between resolutions it will handle it properly. As a result, screenshots are currently tied to the largest internal resolution for that particular system.

At least it doesn't appear to affect 320x240 images.

In addition to the "screenshots are wider than you'd expect" issue remutro refers to...

I see a bouncing image when a game tries to go high resolution.

This is how an actual N64 works. TVs of the era could not display a 480p image; they would display the even rows of pixels on one frame, then the odd rows on the next, making for a 240p image that "jumps", otherwise known as 480i or an "interlaced" image.

I am familiar with interlaced video but wasn't 100% sure that is what that was. Is there a deinterlace option? I am guessing that is how angrylion plug-in operates? That Weave Deinterlace option doesn't seem to work.

[wildgoosespeeder]

PAL region games do 640 x 288 or 320 x 288.