Directx11 error

[Brandter]

Nope, it's mixed. I had no crashes on my old rig with a 1070 and it crashes 2-3 times a day with a 3070. This is a client side issue, the problem is that SE has to fix it, it's been going on for over 5 years and they have NEVER responded to the issue apart from automatic replies that close the threads with no help. What they should do is scrap the DX11 entirely and either update the client to DX12 or even Vulkan. The DX error overall is a red herring, it's almost never has anything to do with the CPU or the GPU but some other peripheral like wireless mice, keyboards, headphones, USB Hubs, and more. For me I removed almost all crashes by just having a mouse, keyboard and microphone connected, no other devices and it started to be a lot more stable, not completely but much more stable. The game has some conflict with drivers, peripherals, monitors, and so on and the error that shows up is a DX11 error. It's not that DX11 causes the crash, it's that DX11 is affected by the crash. And SE needs to get this through their thick skulls that it needs to be looked at! They've ignored the issue for years!

[IceMan1763]

Nope, it's mixed. I had no crashes on my old rig with a 1070 and it crashes 2-3 times a day with a 3070. This is a client side issue, the problem is that SE has to fix it, it's been going on for over 5 years and they have NEVER responded to the issue apart from automatic replies that close the threads with no help. What they should do is scrap the DX11 entirely and either update the client to DX12 or even Vulkan. The DX error overall is a red herring, it's almost never has anything to do with the CPU or the GPU but some other peripheral like wireless mice, keyboards, headphones, USB Hubs, and more. For me I removed almost all crashes by just having a mouse, keyboard and microphone connected, no other devices and it started to be a lot more stable, not completely but much more stable. The game has some conflict with drivers, peripherals, monitors, and so on and the error that shows up is a DX11 error. It's not that DX11 causes the crash, it's that DX11 is affected by the crash. And SE needs to get this through their thick skulls that it needs to be looked at! They've ignored the issue for years!

Part of the problem is that, even within this thread, you can tell these are probably different issues causing the same error message. I definitely agree that some seem to be connected to random peripherals, which I find just weird that they can hard crash a game with this big of a development team behind it. For example, my crash is caused simply by having "Headset (Arctis 7 Chat)" as my audio source (but mine hard crashes right at launch). Every other audio source, including "Headphones (Arctis 7 Game)" which literally is the same headset, work with no problem.

In addition, that same audio source works without issue for at least 10 other games that I have played over the last year or so.

[Brandter]

Yeah, I'm not saying it isn't weird, it's something that SE needs to fix because the game shouldn't crash like this. I had a corsair MMO mouse that crashed the game before this, now I have a razer and it hasn't crashed with that mouse so far. But the error I got was still DX11 error which makes absolutely no sense. The issue happens client-side, but it's the FF14 client that has issues. I have 0 crashes on my computer apart from FF14 that crash all the time if I have too many peripherals connected. I even had crashes when using VoiceMeter, which again shows that the game has audio issues, this can also be seen if you change the audio device while the game is running, the client is unable to update the audio device. EVERY other game I know can do that, but not this client. If I use the default speaker as output and connect my wireless headphones I have to restart the client for them to work, that's just amateurish programming. I know the client is a potato client, but still, it REALLY needs an update, not only serverside but also clientside.