Can't say i've experienced any of the issues you've had, running a 278Q 144hz since release.
Running fullscreen exclusive (game mode disabled, full screen optimisations disabled), capping fps at 141, vsync on in nvidia panel, vsync off in game fps counter never goes over 141.
What are you capping at ingame currently/vsync settings? It's been tested pretty thoroughly by the guys at blurbusters that the above are the best settings for minimal input lag and no tearing. Although as you noted, I suspect windows mode is causing a lot of issues. Really would advise running fullscreen exclusive with gsync where possible due to windowed mode being very buggy - even more so recently due to Microsoft constantly messing with WDDM.
English
-
Monitor is at 100 Hz max, FPS capped at 97, vsync off all over. I'm following all the recommended settings from Blurbusters etc. The problem is that it's not a "normal" issue with regards to those settings. I've got my monitor displaying it's refresh in the corner of the screen, and it's going all over the place at a rapid pace. The FPS is right about where I'd expect it and doesn't fluctuate too much. It's the dynamic monitor refresh itself. Even in orbit when the FPS sits pegged at the cap the refresh will be dipping sporadically all the way down into the 80s (think I've seen lower, too). It even jumps above the cap I've set sometimes; just now I tested by setting the cap down to 80, and I see the refresh jump up into the 90s here and there. These issues do seem to be largely reduced in full screen, but they still appear to be present. I prefer full-screen window, though, and can tolerate the issue. This isn't an issue I see in other games (in windowed or full screen mode), which is why I felt compelled to post about it. Something seems like it may be off with GSync in Destiny 2, specifically.
-
Ah yes I misread part of your post as: the ingame fps sometimes goes above the cap rather than the refresh does. What are you using to monitor the real time hz? There was an issue exactly like you describe, only affecting windowed mode, with many driver sets using the latest WDDM (in 1809). This was only very recently fixed - which windows build and drivers are you running? Failing that, i've not come across any other reports of this so far.
-
Sorry, to clarify the in-game FPS seems totally fine (as reported by the game itself). It's the monitor refresh that's seeming to indicate the presence of an issue. My monitor has a handy option I can turn on to just display what its real-time refresh is up in the corner like an FPS display. I'm also assuming the FPS counter in-game is not a running average or something but a live display that updates every half second or so. To answer your driver/build questions, if I'm reading DxDiag correctly, it looks like i've got... Windows 10.0 Build 17134 WDDM 2.4 NVidia Driver V 417.71 (looks like latest as of this post) Looking around I saw what seemed like reports of this issue but with more anecdotal information (having to judge based on feel, essentially). I had the monitor refresh info, so I kinda thought I'd make a post in case it was useful to Bungie or someone else. I'm not holding out much hope that I can do anything about it, but it's really not too much of a bother to me. Still, I'm open to further suggestions. I do appreciate the responses! :)
-
Edited by flamey: 2/4/2019 9:03:55 PMUnderstood, unfortunately I can't compare my realtime refresh due to having no OSD option for that. You would not be affected by the windowed mode issue I mentioned due to being on the latest drivers already. Only other thing I can think of is that it could be the frame pacing/stuttering issue in d2 causing this - especially if you are testing in public spaces? The frame spikes have definately got worse ever since forsaken release - even in menus and depending how often it polls could explain the difference between osd refresh and fps counter. edit: scrap what I said above, the windowed mode gsync out of sync is still an issue in dx9 and 11 only on 1803 and above therefore thats going to be the root cause.