I recently got a new monitor with GSync and up to 120 Hz refresh. I've got the in-game FPS counter turned on and recently enabled my monitor refresh rate display on the monitor itself while investigating something else. I noticed in destiny that the refresh seemed to be jumping all over the place compared to the FPS counter, which was largely stable, even when in menus or staring at the sky. I have an FPS cap set, and the refresh even jumps above that at times. Additionally, it seems to dip down into the 60-70 range easily, which isn't normal for me according to the FPS counter. At one point it got into a state where the refresh would actually drop to what seemed like a refresh FLOOR at 60 Hz, but the weird part is it would do it when looking at a menu or the sky, and then going back up when looking at more graphically taxing things. I don't notice issues like these in other games.
I run in fullscreen-windowed mode, and enabling regular fullscreen seems to mostly alleviate the issue, although it's still jumping around in a narrower range and going above my frame cap. I've also messed with all the combinations of various v-sync and g-sync settings as well as exiting various other programs I have running that may cause issues (overlays and such).
I went looking for others having the issue and seemed to find that there's a known issue with Destiny and GSync, but I didn't see anyone mentioning the fact that their monitor reported refresh rate was unstable like I'm seeing. I figured I'd post the information here in case it's useful, and in case anyone has more recent information/fixes than I was finding.
Specs:
Acer Predator X34P Monitor
NVidia GTX 1080ti Graphics Card
Intel Core i7 8700K Processor
Asus ROG Z370-I Mobo
32 GB DDR4-2666
Samsung 960 EVO
-
Edited by Cidcaldensfey: 2/2/2019 4:24:48 PMI'm pretty confident that you cannot play Destiny 2 above 60Hz. The main reason why is because Destiny 2 uses Havok for its physics, clothing physics, and some of its scripts. And Havok isn't made to work properly above 60Hz. Another example is the Crew 2 which was released in July 2018, and that game had its fps locked at 60Hz on PC. Monster Hunter: World also uses Havok and that game has stuttering/microstuttering issues reported on the PC. Theres a few other games with other issues with Havok, most notably Skyrim. Seriously, the issue is Havok and how not able to run correctly above 60Hz. It has something to due with how it calculates physics and how the extra work it has to do above 60Hz is the root cause. Fallout 4 also uses Havok and it has issues running above 60Hz.
-
Edited by flamey: 2/1/2019 3:49:17 PMCan'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.
-
Make sure you find out if your monitor is set to fast or slow response this can affect the appearance you might be experiencing.