[quote=97985]640×480 default is set because higher resolutions will slow down rpi1s. In the past display resolution was switched which caused flickering and was not compatible with all screens. Rpi2 and 1080p should be fast enough if you use no shaders. Rpi1 and two share the same default configuration at the moment.

If you have a 16:9 screen resolution and 640×480 render resolution retroarch will increase your horizontal resolution to 853×480. So there should be no unequal pixels since Retropie 2.6 or 3.0.

[/quote]

The first statement makes sense, but I’m unclear on the second statement. A resolution of 853×480 is still going to be scaled to the native resolution of the display (either 1920×1080 or 1280×720), which will cause scaling artifacts on both axes. I’m definitely still seeing unequal pixels on my display with the default settings. Upscaling from a lower res to the native res will also cause input lag.

I was thinking, maybe it would be helpful to have “video profiles” so that one doesn’t have to mess about with RGUI so much. For example, I would hold “x” or “m” as a game launched to bring up the launch menu. I would scroll to “video profiles,” select “5x” and hit apply. The 5x profile would apply integer scale, crop overscan (if the core needs it for perfect scaling) and a custom aspect ratio for the system being played (since resolution is core-specific), at 5x vertical scale (so, 6×5 for NES, SNES, 5×5 for Genesis, etc.). You could also have 4x profile, 3x for 720p displays, etc.

currently there are a lot of settings for the user to configure and they are likely to get something wrong, causing problems. I’m just trying to think of ways that the configuration process could be streamlined/ made easier.

[quote=98024]You can set “any” vertical resolution (0-1080) in your retroarch.cfg. For example you could set something like 1080/2=540 or 1080/4=270 to get integer scaling. If the aspect ratio of your render resolution differs from your display resolution horizontal resolution will be recalculated. You can try to get the best fit for performance and visual appearence. Render resolution upscaling is for free (hardware). If render and display resolution is equal software integer scaling is used (performance penalty). It is also possible to modify the hardware upscaler to your needs: https://github.com/raspberrypi/firmware/issues/104

As i have said default visual settings are not optimized for rpi2 at the moment. If we find better defaults we can at them.

[/quote]

Ah, good to know- wasn’t aware of the hardware upscaling being configurable.

I’m a little confused, though- I thought if render resolution matched display resolution, no upscaling occurred. Is this incorrect?

So, are you saying that rather than setting display and render resolution to match, I should instead set my render resolution differently so that the GPU handles scaling? when I try setting render resolution to 960×720, for example, and display res at 1080p, there is noticeably more input lag vs. leaving both display and render res at 1920×1080. I assumed this was due to the additional upscaling.

[quote=98036]There is no upscaling if display and render resolutions are equal. Be aware your display resolution could be some pixels smaller if overscan (config.txt) is enabled. So if render resolution is 1920×1080 and your display resolution is 1910×1070 (overscan) there could be scaling artifacts.

If performance is ok i would recommend render = display resolution. If performance is to low (shaders, emulation speed) a mix of hardware upscaling and lower render resolutions should be used. Hardware upscaling is for free and needs no processing power.

I have not seen any input lag with hardware upscaling. Thought threaded video causes a small input lag.

[/quote]

I’ve noticed additional input lag setting the render resolution to 960×720 on my 1080p monitor, although it is slight. I’m playing a lot of fast-twitch games, though, so it might not be noticeable in most situations.

Logically, there is going to be an extra delay due to the additional processing that the gpu has to do. Whether or not this is noticeable depends largely on the individual and the game being played.

I wasn’t aware of the performance limitations of the raspberry pi 1, I can see now that the default video settings make sense.

I thought it might make sense to add something like “video profiles” to the launch menu, sort of like preconfigured video modes, but then I realized that each system would need its own custom resolution, and the idea started to seem too complicated.