Lexden
Published
Works perfectly out of the box
Completed first step of the game (30-60 minutes of active play) with no issues at all.
Zero issues for me. Ran immediately without any modifications and have completed the entire game with zero issues.
While technically a tinker report, I always force proton experimental on Steam.
Takes a couple config changes to get it working, but it plays great.
Fullscreen worked when I had my secondary monitor connected, but when I had it disabled, fullscreen resulted in just a black screen. Also, due to how my desktop environment is, windowed has to be adjusted to scale-down vertical height, otherwise all the button hitboxes are skewed.
It can tank when entering a new zone and just takes some time to cache assets I'm assuming. When running things like CLL (48-man raid), things can get pretty bad and even can crash occasionally. Setting effects to limited gets around that though.
Noted previously, but mostly avoidable with limited effects set for other players.
So this is an Endlwalker (Patch 6.0 update). Previously you could only get the launcher working by setting:
Browser 0
in FFXIV_BOOT.cfg (there are plenty of reports highlighting this), but with the 6.0 update, I kept having the launcher crash when it was looking for the update. I fixed it by setting:
Browser 1
Otherwise, still remember to set the normal FFXIV.cfg change:
CutsceneMovieOpening 1
Fullscreen appears to cause the game to freeze, so I just leave it in borderless windowed
Did not play extensively yet, just tested updating and playing the game since I had heard that the new launcher was working on the latest Proton experimental build.
On Proton 7.0-2, I was still not able to get the launcher working.
On the newest experimental build, it works properly, but the login is displayed at the bottom of the launcher rather than the side, so you need to scroll down to find it.
Works perfectly out of the box on Proton Experimental (this was selected by default for me)
Getting windowed/borderless working properly is a pain to force 1440p on, but can be manually entered. When windowed, the button hitbox can become detached from the actual location on the screen. Borderless and full screen work perfectly fine though.
There are very occasional textures that load improperly and create a pretty awful z-fighting strobe effect. However, this has only ever occured twice in around 20 hours of playtime and moving slightly in any direction fixes it when it does occur. I later reinstalled FFXIV using XIVLauncher. To build it for Debian/Ubuntu, you need to use this version: https://mpr.makedeb.org/packages/xivlauncher. You can see how to install makedeb from the home page of the site. Using this, you can install and run FFXIV through Dalamud/XIVLauncher! Using this, I was able to install mods and plugins with no problem! I did have to check the box "Limit mouse operation to game window." under System Configuration->Mouse Settings. Otherwise, inputs would be frequently not captured by the game.
Occasionally, part of the floor in random areas will just turn pure blinding white which is rather annoying and distracting. And it is very clearly some sort of z-fighting issue because it rapidly flickers between pure white and the normal texture as I rotate the camera.
Through the entirety of Dawntrail, everything was completely fine. Until the final area. The game brings me into the final area and it just crashes the game. I try to log back in and it crashes again. I am now stuck. I crash the second the game logs in because of the area/cutscene I am in. It gives me "A fatal DirectX error has occurred.(11000001)"
The flickering textures can be pretty annoying because they are so startlingly bright, but they're infrequent enough that I don't particularly mind them. The crash in the final zone of Dawntrail (or at least the cutscene as I enter it), is a real problem though. I tried repairing my game files to no avail. I think I will have to try loading it up on Windows and getting through that cutscene before switching back to Linux.
%command% -dx11
When looking at our house, framerate tanks to 20fps, but when out and about, framerate is up at 100fps. The PEEP.R mode seems to drop fps considerably as well.
Even multiplayer worked for me with no issues.
When starting a save, it freezes at "Pumping sim once". The game becomes entirely unresponsive and never recovers.
bash -c 'exec "${@/%"PDLauncher/LauncherPatcher.exe"/KSP2_x64.exe}"' -- %command% -popupwindow
Occassionally, when it freezes, it causes my entire desktop to freeze, forcing me to switch tty and kill it in that environment. I have never gotten the game to run properly.
