Briggs
Published
Launcher is invisible, and there is some graphics setting which when enabled causes the game to crash on load. Not that the latter matters since anything other than the lowest setting is too slow to play (Vulkan and DX11 run at about the same speed). I ran a benchmark just fine, and played part of the tutorial, but loading a save results in a crash, making it unplayable.
Crashed when trying to run benchmark (presumably I can expect similar from the actual game).
Launcher works, but the games ever actually launches.
I tried with both 4.11-8 and 4.19-GE-1. Same result.
In previous versions of Proton, it ran perfectly without any intervention at all, however when I tried to start the game this time, it wouldn't. I deleted the prefix and let Steam generate a new one and its now working normally again.
Played the tutorial and a quick skirmish with everything but AA set to max. AA was set to 4, and I'm not sure if my graphics card has the ability to play to use whatever AA=5 would be since nVidia removed some of the more esoteric AA modes a while ago.
On first run without any work around it launched but failed to run the actual game (got title screen and settings menu). After the first crash (well, I had to kill it) it would crash on trying to run the performance test. I uninstalled and reinstalled the game. Now it won't even launch with DXVK. The performance is abysmal (pun intended).
Can't get some of the DLC to work, otherwise everything works out of the box.
Perfectly stable even during long gaming sessions. Only issue is the frame rate which can dip down to low 20s. Still perfectly playable with no hanging or crashing.
Without PROTON_FORCE_LARGE_ADDRESS_AWARE =1 the game crashes when loading a save. Every time. With PROTON_USE_WINED3D=1 the save select screen is all black. With PROTON_USE_D9VK=1 or without forcing any DX9 stuff, I can play the game until an encounter. When a random encounter occurs the game crushes anywhere from instantly, to just after loading the battle (when the characters and UI are up). Sound, text, and cut scenes work without needing any winetricks. I did try manually setting MSAA to 2 (and leaving it be).
As has been noted, you need to disable the opening CS via config file and have to hit enter instead of clicking "log in".
In addition to this, I found that trying to change certain graphics settings cause system lock ups requiring the use of SysRq + REI (but not SUB).
- Proton did not properly create a prefix so I had to run proton directly from command line and initialize a prefix in the appropriate spot with winecfg.
- The new FF14 launcher needs to be disabled to run the game. This is done by changing
Browser 2
toBrowser 1
in the boot config file...I think. Or something like that.
The game does not like it when you change the graphics settings from in game. It doesn't matter if you are changing them up or down (its not just the real-time reflection).
Occasionally when launched, it will lock up my entire DE (Gnome Shell). To fix this I have to ctrl+alt+F2 and kill the entire login session.
When logging in with the old launcher you have to hit enter
. Clicking the button causes a Java error.
I didn't need to do anything that I wouldn't have had to do in Windows 7 (and in fact its somewhat easier since you don't deal with UAC). Configured controller just fine. Graphics are fine, FPS, fine...
Still runs great. Recent changes in 4.11-3 (vs -2) pretty much require you use Steam's controller emulation if want to use a PS4 controller. I don't consider this a real work around, partially because I was already doing that for other reasons, and because its a normal part of the Steam Client. Some might feel this would make it Gold, but I don't think so.
HUD cuts in and out as well as certain textures which greatly reduces playablility. Also, with a fresh character (no injuries) I have 0% vat hit chance against the tutorial monsters even when they are directly in front of me. Other than that, everything seems to work well. No mods, by the way.
Multi-second input delay with controller. Haven't tested with Mouse and keyboard (I have enough M+K-only RTS games).
Runs great. Don't need to connect to EA's server, which is the only significant bug if you ask me.
- Once a character's head was missing for a second or two in a cut scene.
- Sometimes you get these really nasty, game breaking artifacts. I'm not 100% sure what causes them. You can fix them by reloading the game.
*Keyboard and mouse input doesn't work with the latest version of Proton. If you want to play KB+M you need to go back to 4.9. Also, when inputting your email address, neither the shift key works for @
, nor does the ctrl key for pasting something in.
This can be worked around by manually setting your email address in the game's config file. blaze_email=
. You do not need to put the email address in quotes.
- For the controller to for in more recent versions of Proton (i.e. 4.11-7), you need to use the Steam controller API. Doing this, the DS4 works flawlessly.
Game no longer launches (this is a regression) (report I just sent in said Proton 3.16-4 which was wrong.)
No longer launches. Stuck at "Preparing to launch". Waited several minutes. This is not the normal "upgrading to new Proton version" type delay.
This runs less than perfectly, but is playable. I strongly suggest borderless windows, otherwise you're game can crash.
Also, as has been noted before, to get the game running at all you need Media Foundation stuff installed. For legal and security reasons I would advise using your own W7 DLLs instead of those provided in the Git repo people have been linking to. That said, the script is absolutely lovely so I would also strongly suggest its use.
The only real problem I've had are performance which go beyond the normal hit expected from using Wine. I don't have the greatest hardware in the world, but I shouldn't have to turn the graphics level to the very bottom to make the game run smoothly (the minimum req is a GTX460 and the recommended is a 970...I have a 950). Especially since the problem isn't the open world where there is more to render and compute, but rather the in-game menu. The equipment menu in particular cause the game to grind to a halt, so I suspect there is some kind of post processing going on which we can't disable any way other than to turn the graphics level all the way down. For me, I've got it set to "Good". I also turned on V-sync after about an hour of play because this game really needs it. I saw no performance penalty from using V-sync by the way.
I tried no_fsync, and wine_d3d. Forcing OpenGL D3D11 causes crashes on world load.
Pretty much everything I said in my previous report holds true (compare my system information). The only change is that I'm 6 hours in and now the game is a crash fest. I don't know if its due to the new drivers, for if this is just what happens after playing for a while. At first it was just on area transitions, but now it can happen at any time.
Notes Sometimes it gets stuck loading a save.
This runs very poorly with an nVidia 950. I've upgraded since my last report to an Radeon 5600 XT which should be overkill.
If you're max file limit (or whatever) is already raised (like on Ubuntu systems) it works out of the box, other wise you either need to raise that limit or disable Esync.
So far, it just runs. It installed, cinematic played, created an account, logged in, created a character, started a game, played for a little bit. No graphical problems, no glitches of any kind.
There is a single spot at the very beginning of the game where it crashes something like 80% of the time. Otherwise, no tweaks needed and no observable faults. If not for that crash (which I think might be present on Windows even) it would be Platinum.
Everything works. Controller, sound, full screen...the game itself. Huge improvement over "borked".