So, I just got a new monitor, the XB270HU I've been testing my frame rates with GTX 970 SLI w/ DSR on a 1080p monitor to make sure I can handle 1440p, in games like battlefield 4, and on High settings, I was getting well over 144FPS. However, turning SLI off easily yielded over 144. I've tried so many things, turning off Vsync/GSync completely, setting Fixed Refresh Rate in Nvidia Control Panel and Highest Available refresh rate, reinstalling drivers, I just don't get it. And it's in every game I play that uses SLI. Black Ops 3, Crysis 3, etc. 112FPS with no Vsync, and 96FPS with Vsync enabled. HOWEVER, if I don't play at 1440p, my frame rate is just fine, utilizing both cards with no problem...So..what is it about 1440p @ 144Hz that causes my frame rate to cap itself at 96? I'm really stumped..
Better off just disabling v-sync when you have g-sync I've found. few things; * Could be thermal throttling? * Is a RTSS frame rate cap set? * Is this problem actually occuring when using the XB270HU or are you talking about 1440p DSR on the 1080p screen? Also DSR performs differently to actual real not downsampled resolutions, added mouse input lag too.
I thought enabling vsync with gsync the only time vsync kicked in was when your fps went over 144 (or 120 depending on refresh rate)?
Ive seen that already? Why would you need vsync if gsync is enabled? anything up to and including 144 fps vsync would be pointless anyway ?? i thought id read somewhere that it wont kick in untill gsync becomes useless (over 144 fps for example) so vsync would effectively cap your fps so gsync kept working? otherwise i dont know any other reason any one would want it?
The cable that shipped with this monitor would really cause that? Why would it work 144Hz with SLI disabled then?
You literally never ever get higher fps than 112, like it's capped? You say things worked fine with the 1080p monitor. Well the only thing that has changed since it was working 100%, is the new monitor. Could be something is faulty with it, replacing the DP cable as suggested may solve it. Firstly though, I'd just try google it, see if anyone else has had the problem and fixed it. Not a lot else you can do, It's a weird issue.
I gave in and just went ahead and ordered http://www.amazon.com/gp/product/B005H3Q59U But...If this cable doesn't change anything, then I'm really really lost.