PlayerNotFoundException
Published
Stuck on Loading Screen
The loading screen doesn't finish and gets stuck just before highlighting the last section of text. (The text represents loading progress and starts highlighting depending on how far the game is into loading)
Other reports claim that the launch failure is due to Anti-Cheat but I do not know enough to support or deny that theory. (Though the window of what looked like an Anti-Cheat Software was visible for 2 seconds before disappearing and being replaced by the loading screen)
Patch 7.21 broke the Launcher
TZ=UTC %command%
The new version of the launcher distributed with FFXIV patch 7.21 doesn't work on Proton anymore. :(
TZ=UTC %command%
Due to changes in the Launcher, I had to switch Proton Experimental to the beta branch "bleeding-edge" in order to log in and launch the game. If you're reading this in the future, the required Proton patch may have been included a Proton release, so this step may no longer be necessary. The TZ=UTC is because FF14's ingame clocks are broken on Linux. With that flag, at least server time is accurate.
I've noticed performance degradation over the course of long play sessions. Exiting and restarting the game solves those temporarily.
Crash when selecting microphone
The Game crashes to Desktop when selecting any microphone in settings or on starting a new game. As a microphone is strictly required for this game, that makes it borked.
Game starts up but modifying the sound settings (in particular the device) or finishing the initial cutscene crashes the game
The game is sadly completely unusable
Had a lot of fun with this game so far. After messing with dotnet, I was able to play with the crashes typical of this game.
Had to manually install a version of dotnet with a fragile installer into the prefix - Other reports are more in-depth
The game always opens the crash report window even when exiting the game normally. No idea why. I was unable to go past normal graphics settings and still get a good gaming experience but I suspect that's the fault of weak hardware on my end and not the is-not-emulation-but-thats-the-best-word-for-it
