Quote Originally Posted by LordBalthazarr View Post
I have done extensive testing of the issue through last night and today. The issue occurs when the client tries to determine the (supported) refresh rates of the display (as to what the EDID information reports to windows).

If your utilizing a laptop or a desktop with a display that natively only allows a high refresh rate (anything higher than 60hz), in my case 120hz, then when the client goes to call the (GetDisplayMode) function in directx11 and doesn't see an expected value (in this case a 60hz/90hz capable display) it then terminates the function and throws the error we are seeing. My current workaround is this,

Utilizing a Custom Resolution Utility , manually create a new supported display mode for the monitor. In my case I created a 90hz and a 60hz (because I don't know specifically what the client is looking for in this scenario). Once you've created them using the utility, restart windows, then check to make sure that both of these refresh rates are now listed as supported modes. After that has been done, you can leave the display running at its native refresh rate (mine is 120hz), and proceed to start the client. This time, when the client goes to make the directx11 call to get the supported display modes, windows will now reply with values that the client actually "supports". I've had success with this on 3 PCs now. A Dell Inspiron 15 G7 with a 120hz panel , a MSI GS63VR with a 144hz panel, and a custom desktop with a 144hz panel.

None of this will be necessary if Square manages to fix this tonight during hotfixes, but if they are unable, then this should be a sufficient workaround until they can.
I sincerely hope, and will continue to post this, that SQENIX's "fix" is simply a full reversal of the cap.

High framerates have never once caused me issues in this game, nor have I ever heard of such issues before this patch. Whatever they thought they were fixing is no where near as big a problem as this cap.