SLI performance

[Ryios]

Glad I could help,

Let me mention one final thing a lot of people don't know.

If you are running Windows 8, the metro UI and the UI in general uses DirectX, and it Forces Vertical Sync to be on, you cannot turn it off. As such, if you run FFXIV in a window (even a borderless window) virtual sync will be on even if you tell nvidia to turn it off, The OS overrides anything you tell it about vertical sync, therefore when running the game in a window you will never see your FPS go higher than your monitor's refresh rate (usually 60).

Only way around that at the moment, that I know of, is to go back to windows 7.

This is why running the benchmark for FFXI on windows 8 in a window performs so much worse than full screen. When in full screen you can turn vertical sync off, but not windowed.

Hopefulyl MS will patch in a way to turn vertical sync off on the OS UI so we don't have to deal with that.

It's a shame too, because windows 8 has a faster kernel than 7 and performs better in fullscreen mode than windows 7. So for me, I stuck with windows 8, run the game windowed, and just deal with the 60 fps cap, not a big deal since my 760 can handle it.

[Dhalmel]

SLI works fine for me on the latest beta driver on Windows 8.1


Unless you've set your frame cap limit to unlocked or run at a very large resolution (2560*1440+) you shouldn't see 90~100% gpu usage that often. If you have the game's fps capped at 60 the gpu is only going to utilize the needed process for what the client demands.

Honestly the game with this kind of visual quality (at the technical side) doesn't really push a single 680 much let alone SLU configuration, maybe when the DX11/texture update is made available.

[Ryios]

On windows 8, if you run the game windowed you are capped at 60 no matter what. Because the Desktop Windows Manager in windows 8 overrides driver settings for vsync and forces it to stay on all the time. The only way around it is windows 7 or run games full screen.

[necrosis]

Also make sure you are running in true fullscreen. Not fullscreen borderless or whatever its called.

You probably are in true fullscreen just throwing ideas out there of things to check.

[klepp0906]

FWIW - SLI doesn't work when using NVSurround. Atleast not in the benchmark (and im not reformatting my pc and installing the game until I have SLI working there first as I have no reason to believe the game will be any different)

I have quad titans and I get 4k @ 4680x2560 lol. It worked in the past and I got about 12k but between then and now something has stopped SLI from triggering completely. I recently discovered the visual SLI indicator which just adds proof to the pudding so to speak. It shows up in 3dmark, valley, heaven w/e else I choose to run but something for some reason with the FFXIV benchmark isn't letting SLI work.

again, this has something to do w/ surround because if I change to 1 monitor POOF SLI and SLI indicator works fine and the performance that comes along with it.

I didn't build a quad titan rig for 30 fps >.< help!

[klepp0906]

I guess i should have listed my specs first

AMD 8150
120GB SSD
2 GTX 770s SLI
Verizon FIOS 75/35


the more i mess around with the more i think its a software thing on my end. many of my games are showing the SLI visual indicator and perfoming just like I would like them to. Once is load FFXIV I loose the visual indicator and notice the performance hit

Have you found a fix for this get? This is my exact situation. Im running quad titans and surround and I get sli and indicator in everything but ffxiv and ffxiv benchmark. No indicator and I get 30fps from 4 titans which is clearly unacceptable lol.

Im dying to play the game but not going to bother until the PC I built specifically to do so is working right Not enough people use sli or surround to draw attention to it and nvidia doesnt communicate with the people who put food on their table so Im afraid it could take months to fix this and the game is already months old.

[klepp0906]

TTT aggiegamer09 hollatchaboy!

[klepp0906]

FTR and for anyone who comes across this with a similar issue... after working w/ the guys at NVidia - they were able to reproduce it in the lab. They are now working on a fix. MUCH time wasted in denying the problem and/or assuming it was on the customers end BUT hats off to Josh at Nvidia for giving me the benefit of the doubt. He worked with me to confirm I did put my legwork in and wasn't crazy/ignorant (god knows they likely get MANY such cases. Anyhow its now out of my hands.

2 dozen reformats and a couple weeks later >.<