10-01-2016, 12:10 AM
The are two "problems" with native resolution multipliers.
1- The X axis is left with a lower resolution compared to the Y axis when you play in 16:9 (and games usually have a 512x448 internal resolution, even less wide than 4:3), so games will look more easily aliased horizontally and antialiased vertically. Not a problem, just a curiosity. This can be compensated with custom resolutions.
2- We need more high resolution multipliers or a custom multiplier in the GUI, because there are games that use a lower internal resolution than reported (DBZ Infinite World and Ratchet and Clank, for example. 2560x1440 in my 1440p monitor looks low res). I can use "upscale_multiplier" in GSdx.ini, but it's annoying because to change it I have to close the emulator. The highest multiplier I can use is 12 (6144x5376 in Ratchet and Clank, for example). Anything higher than that causes a Visual C++ runtime error. However, with custom resolutions I can use anything up to 8192x8064 (sometimes a lower vertical resolution in other games. I can notice the image quality improvement compared to 12x native).
7680x4320 is what I sometimes use for internally low res games (3 times my monitor resolution per axis). Horizontally, the equivalent would be 15x native, but that would also put the Y resolution to 6720, so it would be 55.56% more demanding .
However, in games that use the inputted resolution 1:1, it's noticeable that PCSX2 uses a bad downscaler at a higher than 2x2 monitor resolution (7680x4320 looks very aliased in Persona 4). Asmodean's bicubic filtering doesn't look as good as I would expect (maybe it isn't supposed to be a substitute of PCSX2 downscaler?), and 5120x2880 with 4xMSAA looks a lot more antialiased.
In my opinion, it's good to have the custom resolution option. I'm aware that some games are incorrect with it, and I'll use native resolution multipliers with them (in normal circumstances I do it for most games, except for those that have low internal resolutions).
1- The X axis is left with a lower resolution compared to the Y axis when you play in 16:9 (and games usually have a 512x448 internal resolution, even less wide than 4:3), so games will look more easily aliased horizontally and antialiased vertically. Not a problem, just a curiosity. This can be compensated with custom resolutions.
2- We need more high resolution multipliers or a custom multiplier in the GUI, because there are games that use a lower internal resolution than reported (DBZ Infinite World and Ratchet and Clank, for example. 2560x1440 in my 1440p monitor looks low res). I can use "upscale_multiplier" in GSdx.ini, but it's annoying because to change it I have to close the emulator. The highest multiplier I can use is 12 (6144x5376 in Ratchet and Clank, for example). Anything higher than that causes a Visual C++ runtime error. However, with custom resolutions I can use anything up to 8192x8064 (sometimes a lower vertical resolution in other games. I can notice the image quality improvement compared to 12x native).
7680x4320 is what I sometimes use for internally low res games (3 times my monitor resolution per axis). Horizontally, the equivalent would be 15x native, but that would also put the Y resolution to 6720, so it would be 55.56% more demanding .
However, in games that use the inputted resolution 1:1, it's noticeable that PCSX2 uses a bad downscaler at a higher than 2x2 monitor resolution (7680x4320 looks very aliased in Persona 4). Asmodean's bicubic filtering doesn't look as good as I would expect (maybe it isn't supposed to be a substitute of PCSX2 downscaler?), and 5120x2880 with 4xMSAA looks a lot more antialiased.
In my opinion, it's good to have the custom resolution option. I'm aware that some games are incorrect with it, and I'll use native resolution multipliers with them (in normal circumstances I do it for most games, except for those that have low internal resolutions).
CPU: AMD Ryzen 7 7800X3D
GPU: Nvidia GeForce RTX 2080 Ti GAMING X TRIO
Motherboard: ASUS ROG Strix X670E-F Gaming WiFi
RAM: Corsair Vengeance 6000MHz CL30 DDR5
Monitor: Asus PG278QR
OS: Windows 11
GPU: Nvidia GeForce RTX 2080 Ti GAMING X TRIO
Motherboard: ASUS ROG Strix X670E-F Gaming WiFi
RAM: Corsair Vengeance 6000MHz CL30 DDR5
Monitor: Asus PG278QR
OS: Windows 11