Scaler issue, expected behavior?
Posted: Wed Aug 12, 2020 9:54 am
Hi
I have an issue where v-sync =2 only works consistently in 720p mode, whereas it will "bug out" for some cores in 1080p.
It seems related to the refresh rate of the specific core. E.g. SNES works with v-sync=2 in both 720p and 1080p (60.1Hz). While NeoGeo works with v-sync =2 in 720p only (59.1 Hz ? I forget exactly) . In 1080p it looks deinterlaced somehow (vertical height stretches beyond the screen and looks similar to bob deinterlace flicker). In both cases, my TV itself reports the correct resolutions (1280x720 and 1920x1080 respectively).
It also happens on many arcade cores where refresh can be significantly below 60Hz.
From my (admittedly not fully exhaustive) testing, it seems to make no difference which scaling mode (i.e. integer or fill vertical) is used.
I know that v-sync=2 is not expected to have full compatibility, but I thought it weird that my TV is reporting a valid format (1920x1080), but still displaying this weird image.
Is this expected behavior? Anything to test to resolve this?
Cheers
I have an issue where v-sync =2 only works consistently in 720p mode, whereas it will "bug out" for some cores in 1080p.
It seems related to the refresh rate of the specific core. E.g. SNES works with v-sync=2 in both 720p and 1080p (60.1Hz). While NeoGeo works with v-sync =2 in 720p only (59.1 Hz ? I forget exactly) . In 1080p it looks deinterlaced somehow (vertical height stretches beyond the screen and looks similar to bob deinterlace flicker). In both cases, my TV itself reports the correct resolutions (1280x720 and 1920x1080 respectively).
It also happens on many arcade cores where refresh can be significantly below 60Hz.
From my (admittedly not fully exhaustive) testing, it seems to make no difference which scaling mode (i.e. integer or fill vertical) is used.
I know that v-sync=2 is not expected to have full compatibility, but I thought it weird that my TV is reporting a valid format (1920x1080), but still displaying this weird image.
Is this expected behavior? Anything to test to resolve this?
Cheers