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

Screen tearing with 57 Hz + VRR #109

Open
coolbho3k opened this issue Aug 28, 2022 · 5 comments
Open

Screen tearing with 57 Hz + VRR #109

coolbho3k opened this issue Aug 28, 2022 · 5 comments

Comments

@coolbho3k
Copy link

coolbho3k commented Aug 28, 2022

Hi! I get screen tearing at the bottom of the screen with 57 Hz mode and VRR. It doesn't happen with 60 Hz mode. It doesn't matter which way the game is rotated, the tearing always appears at the "bottom" of the TV.

Here's a brief video of the issue: https://youtu.be/C9HAeyCuBbc

The core doesn't display with my TV at 57 Hz without VRR, although it actually used to work with this display. It may be because of a TV firmware update and not the core.

Here are my video settings:

video_mode=8
vsync_adjust=2
vrr_mode=1 (it doesn't matter if it's 1, 2, or 3)
vrr_min_framerate=0
vrr_max_framerate=120
vrr_vesa_framerate=60

The TV is a Samsung S95B.

@Gazpr0m
Copy link

Gazpr0m commented Sep 1, 2022

Wow nice TV :)

Anyway, I get the exact same type of tearing on my Samsung Q9FN (their 2018 LCD flagship but it only supports freesync 48-60hz) on pretty much any console or arcade core when enabling VRR and running refresh rates other then 50 or 60hz.
I don't think its specific to the Cave core.

The tearing line does move to a different position depending on the refresh rate thought. 57hz is in the bottom half on the screen for me as well.

You could try the R-Type core from Wickerwaka, it has different refresh rate options in the menu to see if the tearing changes position depending on the refresh rate.
You should really talk to him anyway about this, he is the guy behind the VRR function and a lot of the HDMI code lately.

My suspicion is that something isn't initialized quite right and Samsung TVs dont like that. Its a real bummer since I can't get the tv to display most of these non-standard refresh rates without enabling VRR.

@coolbho3k
Copy link
Author

The Neo Geo core actually seemed fine at 57 Hz, let me try the R-Type core.

I also remember this core working without VRR at 57 Hz, with no tearing, but maybe a firmware update on the TV or MiSTer side broke it :( It's not possible to tell now.

@coolbho3k
Copy link
Author

Yup, happens in the R-Type core too, although it's far less noticeable in that game as it's a horizontal scroller.

@desolationjones
Copy link

I also remember this core working without VRR at 57 Hz, with no tearing, but maybe a firmware update on the TV or MiSTer side broke it :( It's not possible to tell now.

You are not alone here. I am on a Samsung Q6FN and it's been hell getting MiSTer working since about September.

@KawaiiDinosaur
Copy link

I know it's an old issue, but I fixed it by forcing AMD FreeSync on the MiSTer.ini (vrr_mode=2). I have a Samsung S90C and it recgonizes it as "FreeSync Premium", with no issues. I tested a bunch of cores with weird refresh rates and they all work without tearing.

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

4 participants