no issues prior to early release, now dx11 errors

[LordBalthazarr]

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.

[Nataruma]

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.

This will void your warranty on your laptop should anything go wrong, so unfortunately people with laptops have a higher risk factor and while I know it works, I would prefer if an official fix would be implemented than me potentially screwing up my hardware.

[LordBalthazarr]

This will void your warranty on your laptop should anything go wrong, so unfortunately people with laptops have a higher risk factor and while I know it works, I would prefer if an official fix would be implemented than me potentially screwing up my hardware.

This will not void your manufacturer's warranty. I am not suggesting that you run the panel at the new refresh rates, merely that you add them to the list of supported modes so that when FFXIV checks them, it will pass without throwing an error. I apologize if I made it seem otherwise.

[Nataruma]

This will not void your manufacturer's warranty. I am not suggesting that you run the panel at the new refresh rates, merely that you add them to the list of supported modes so that when FFXIV checks them, it will pass without throwing an error. I apologize if I made it seem otherwise.

I am not sure I fully follow, are you suggesting to add the custom refresh rate but not use it? Ah wait I think I see what you mean now, to create the custom modes and leave them in the list but not utilizing them. Hmmm, worth a shot, I will try this.

[LordBalthazarr]

I am not sure I fully follow, are you suggesting to add the custom refresh rate but not use it? Ah wait I think I see what you mean now, to create the custom modes and leave them in the list but not utilizing them. Hmmm, worth a shot, I will try this.

Yes this exactly. The game just needs to see that you have a display that it supports. Right now as it stands, the client is looking for displays that support up too, but no higher than 90hz. So by adding these to the list of supported modes it tricks the client into thinking you have a supported display.

[Nataruma]

Yes this exactly. The game just needs to see that you have a display that it supports. Right now as it stands, the client is looking for displays that support up too, but no higher than 90hz. So by adding these to the list of supported modes it tricks the client into thinking you have a supported display.

I will try launching the game after maintenance and see if this works for me

Update: This did not seem to work :/ too bad.

[Sergster1]

Word of advice, if you're going to post dxdiag make sure you aren't running certain programs that could get you in trouble.