MiSTer FPGA Forum

So I have had my Mister for a week now and love it.

I am using vsync_adjust=2 and the lag is great. I don't have an SNAC, but my USB controller lag is fantastic (and I am very sensitive to it).

The only issue is that it’s a trade-off. Either have barely any lag, but every time I load a core, the monitor gets out of sync for a second (it just turns black). Sometimes, it happens twice when loading a core and sometimes between games, but that is rare.

Is there a solution to this? I looked at the VRR settings and played around and was not sure if having vsync_adjust=0 plus enabling VRR improved the lag or not, but the sync issues did go away. Are there any other workaropunds to not having your screen flash black or is that what you have to pay for having low lag?

I also tried changing min VRR FPS to 59 and max VRR FPS to 60.
Also, I have a Freesync monitor, but I'm not sure what that can do. I have always thought enabling Freesync ADDs to lag.

A final note, I have heard form everyone that you cannot use VRR and vync_adjust=2 at the same time. But on the very help github page it says the following here: https://mister-devel.github.io/MkDocs_M ... ync_adjust

MiSTer FPGA now supports Variable Refresh Rate (VRR). The advantage of using Variable Refresh Rate is a reduction in sync loss on your display when the core is outputting non-standard refresh rates and you are using a low-lag vsync_adjust setting such as 1 or 2.

Am I taking crazy pills, or does that say using VRR while using vync_adjust=2 helps with the sync issues? Why would it say that if they cancel each other out.

I use VRR and vsync_adjust=2. No issues on my end. Low lag, no screen-tearing or issues. My TV is an LG C3 connected to MiSTer via HDMI.

RalphJB wrote: ↑Sat Jun 01, 2024 12:45 am

I use VRR and vsync_adjust=2. No issues on my end. Low lag, no screen-tearing or issues. My TV is an LG C3 connected to MiSTer via HDMI.

I think you misunderstood my post.
I dont have tearing issues.

I am talking about thew sccreen going black when you load a new core because it needs to SYNC. It lasts about a second and is not really an issue but was just curious about ficing it and keeping the input lag low.

There's currently no real solution here short of using analog output. You need vsync_adjust=2 (no framebuffer) for minimal lag and that's going to necessitate drops when changing cores at least.

VRR isn't fully implemented unless vsync_adjust=0 but even then it seems implemented incorrectly. (I get a lot of wobble on an LG C1 when doing this.)

The black screens while switching resolutions, sometimes even during gameplay, was too much for me.
I changed it to vsync_adjust=1 and hope the lag is low enough...