(06-04-2017, 11:56 AM)mirh Wrote: Can you confirm if whenever you have tearing you are in exclusive fullscreen btw?
I think it is. Tearing is solved if I force vsync in the drivers (I usually do that always, but I wanted to test if tearing would appear without it).
(06-04-2017, 11:56 AM)mirh Wrote: And could you check if the v-sync setting in pcsx2 can fix it?
The PCSX2 vsync setting doesn't do anything in my case, enabled or disabled. As long as I force vsync in the drivers or fps are inside the G-Sync range, there isn't any tearing.
Another reason why I think it's exclusive fullscreen is because I had been forcing G-Sync months ago using one version of Kaldaien's SpecialK. If I didn't alt+enter, moving the mouse would interfere with G-Sync, producing doubled frames, while in true fullscreen mode the mouse was in sync with the fps of the emulator. This last behavior is what is happening here now (I'm not forcing G-Sync with that DLL now, obviously).
And I have also seen a different behavior depending on when the PCSX2 frame limiter is disabled. If I double click the PCSX2 window while the frame limiter was already disabled, there isn't any strange thing happening to the fps.... Until I reach a loading screen that drops the fps, and then suddenly fps can't go up from 90-96fps.
It's as if G-Sync were trying to guess the native fps of PCSX2 and it weren't trying it unless fps dropped to some point. For example, entering fullscreen that way, enabling the frame limiter and disabling it immediately, triggers this behavior. I checked the fps in MSI afterburner. Straight 120fps line before doing that, and then not (frametimes are also bad after. I notice the monitor flickering mildly because I use G-Sync+ULMB). This is in some way GPU dependant for some reason, I think. 105-106fps at native resolution when that strange thing happens, compared to 90-96fps at 6x native. I don't know if this fps drop problem is completely related to the 60fps problem I described in my previous post.
By the way, in any case, even in windowed mode I can't exceed the fps of my monitor. I saw tearing when I was just at the fps limit that G-Sync needs to break (only if I don't force vsync in the drivers). However, switching the frame limiter off and on again fixes tearing. But I can't test this properly because I can't reach the fps>Hz case in any way.
Ugh, maybe I'm confusing you more than helping
.
The DX11 renderer doesn't trigger G-Sync at all.
(06-04-2017, 11:56 AM)mirh Wrote: Also, I have some dumb test-cases attached. I'd be curious to know if they tear.
What do I do with them? It's just an static image of a cube in both cases. RTSS reports 0fps. It doesn't trigger G-Sync, if that's why you posted them.
(06-04-2017, 11:56 AM)mirh Wrote: p.s. would be cool if "latest drivers" was quantified
382.33, on Windows 10 (not Creators Update).