DX11 Issue

[voltheiy]

So, basically like everyone else... I still have random issues with DX11, seems like DX9 has a poor performance but doesn't crash. It just says a bunch of "???+.dll" or the sort.

I have a GTX MSI 750 ti, WIndows 10 (Creator Update) and I use the Steam Version.

I've already, uninstalled, made a clean install, Rolledback, disabled the Game stuff, and the overlays. Doesn't work. This awful. >.<

[Vaulisel]

Hey fam!

I run a r9 380 in my rig, and was having the same problems pretty much everyone was having while using dx11 and windows 10. After some searching and experimenting, I finally settled on uninstalling the latest drivers and installing the 16.3.2 drivers, as they claimed to fix the issue in the patch notes http://support.amd.com/en-us/kb-arti...on-16-3-2.aspx

Not running any overlays (all steam / discord overlays turned off) and it's been two days since I've 11000002'd. Worth a shot. Good luck!

Just tried this. Sadly, it did not work for me. I'm running an R9 380, just like everyone else.

[livingwithgames]

I have the same i thought it was the graphics card but it isn't it was my optical speakers when i used those speakers as sound it would crash. When i switched to a USB headset or my TV as sound it works just fine.

[Ryon17]

I too have this problem. I too run a R9 380. No other games present this problem, and it cuts in randomly in FF XIV.

I have seen threads on here and on other forums that date back to 2015 with this exact problem, how come that there has not been taken any action to fight this, apparently very common, problem?

Also, this is my first reply here. Checking the forums leads me to think there is not much technical support, or support from the developers´side at al...

[Ephemeris]

I too have this problem. I too run a R9 380. No other games present this problem, and it cuts in randomly in FF XIV.

I have seen threads on here and on other forums that date back to 2015 with this exact problem, how come that there has not been taken any action to fight this, apparently very common, problem?

Also, this is my first reply here. Checking the forums leads me to think there is not much technical support, or support from the developers´side at al...

It seems that this game suffers from what all other games developed outside of US/EU suffer from - zero direct communication with the development team due to the language barrier and non-existing technical support.

Competing MMOs like GW2 and ESO have developer presence both on forums and Reddit, and big issues are always addressed and tracked. Here it seems to be an echo chamber. I do not think it's fair to ask for a monthly subscription and still treat US/EU as second-rate customers when there are alternatives on the market that provide more for less.

The last hope for me is that someone has been listening in the background and it will be magically fixed with the Stormblood launch patch. If it is not then I must say that my faith in this product is gone and I won't be renewing anymore.

[Phaelen]

I was having a lot of dx11 crashes which perplexed me since on my old laptop I had no issues and new one was much better. I reinstalled windows and worked flawless when I do get the dx11 crash I discovered it was due to a new driver or driver from another device. My experience is it seems to be something with offending drivers doesn't help but also provides some explanation why it's been so tricky to diagnose

[Gold_God]

That's unbelievable. I am new to this game. And thank god I am going to quit now that is early. Can't login to the game 3 hours now.

[BernAlmasy]

after patch 4.1, im having those everytime. random crashes the whole day. its annoying

[ufoundwaldo]

Any update on this. I just cleaned out my pc, dust and all, new thermal paste, completed wiped and reinstalled windows, verified latest updates on everything was installed and then installed ffxiv and am still having issues with both dx11 and dx9.
amd 8350 watercooled
msi 390x factory overclocked 8 gig graphics
32gigs ddr3 memory
m.2 Samsung evo 256gig hdd

I should mention that this started happening after 4.01 update.