Post
by liquidshadowfox » 22 May 2026, 00:01
Hey can you guys check something for me, I think I MIGHT have found a bug or maybe it's just my luck with the badly optimized games I like to play. I sent a bug report to nvidia already but wanted to see if anyone can reproduce what I'm seeing (using the asus pulsar monitor on latest nvidia drivers and latest firmware).
I also would like to mention I'm running an AMD ryzen 9800X3D + 5090 so I shouldn't be bottlenecked GPU wise. This currently observed in a steam game called "Eternal Return" (free to play), in nvidia control panel for this specific game, I set low latency mode to "on" and NOT ultra, Gsync enabled for full screen and borderless windowed mode, Vsync = application setting (this will be important later) and I also turn on the Gsync watermark indicator to show that Gsync is active, I also have riva tuner for FPS capping and frame time graph, monitor OSD to show FPS graph as well just to see if they both coincide and how fps capping lower affects Gsync pulsar motion clarity. Open up the game settings in top right corner (settings cog) and set the resolution to 2560 x 1440 if not already, Display mode = "borderless Fullscreen", Graphics = ultra, Enable Vsync turned ON. Now to test the settings real quick, go to "Game Start" -> "Training" -> "Practice Mode" -> select any character -> select "quick start" on bottom right. If you pan the camera from left to right using either the arrow keys or your mouse up against the edges, you'll see you can see your username above your character almost perfectly with no artifacts, double images/crosstalk. Now press ESC and change Vsync to OFF and set the FPS limit to either 120 or 144, get out of the menu and pan the camera again, you'll notice now there's visual crosstalk/double imaging on your name and elements across the screen. This happens regardless if you force Vsync = on through nvidia control panel, just recommended to put to "let 3d application decide" cause it would be easier to test. I tried fps capping using riva tuner to 144 (with the in game cap also set to 144) with front edge sync enabled and it did make the frame times more stable BUT the double images/crosstalk still persist and it makes no sense that capping the game to a lower refresh rate that the max hz of the monitor would lead to more crosstalk/double imaging than if you were to try to run at max refresh with somewhat inconsistent fps. Monitor OSD shows a solid 144 graph with both caps (a little more jittery with the in game cap but it should still show clear). I did a full GPU driver wipe with DDU 1 day ago so this isn't an old driver problem where there might be corruption in shader cache.
