Schotty
Published
For those having issues getting past the monitor part, the fix is simple, yet not straightforward. When installing the mfplat components, you must use the proton prefix you are going to be using (Proton 5 will work). Sadly networking seems to be broken. GloriousEggroll and Valve are both working on getting things working, and in the latter's case -- not needing mfplat.
PROTON="/home/username/path-to-steam/Steam/steamapps/common/Proton 5.0" WINEPREFIX="/home/username/path-to-steam/Steam/steamapps/compatdata/397540/pfx" ./mf-install.sh -proton
PROTON="/home/username/path-to-steam/Steam/steamapps/common/Proton 5.0" WINEPREFIX="/home/username/path-to-steam/Steam/steamapps/compatdata/397540/pfx" ./install-mf-64.sh -proton
Played a few hours thru the campaign. Nothing didn't function as expected. No crashes or glitches. Even alt-tabbed out frequently to deal with things in Discord. Zero problems. Have yet to get a multiplayer match going. I have my graphics maxed out with vsync, still getting 60 ferps -- so great performance.
Ran with Proton Experimental as it's the default Proton when the dev doesn't specify. Crashed on first launch. Relaunched with zero issues.
Game works perfectly after the mouse issue is corrected.
You need to change your mouse refresh to 125hz to aboid the mouse jitter.
STEAMDECK=1 %command%
Runs perfectly out of the box
Although the Battle.net version is also perfectly playable, this is just that much simpler, as you don't need to deal with Battle.net and its nonsense. Once loading up you will be asked to link your existing (if you have one) Battle.net account. After that your full account is accessible, from existing characters to any DLC/extras that are from Battle.net.
Runs perfectly out of the box.
Although the Battle.net version is also perfectly playable, this is just that much simpler, as you don't need to deal with Battle.net and its nonsense. Once loading up you will be asked to link your existing (if you have one) Battle.net account. After that your full account is accessible, from existing characters to any DLC/extras that are from Battle.net.
PROTON_NO_FSYNC=1 %command%
The game will work ONLY if you have an existing acct
It is impossible to accept ToS, thus impossible to play on a fresh acct. Stereotypical nonsense from Square on the PC. Solution is to use Windows to install and accept the ToS. None of the reg hacks work, xivlauncher does not help here.
RADV_PERFTEST=gpl WINE_CPU_TOPOLOGY=8:0,2,4,6,8,10,12,14 %command%
Limiting wine to using fewer cores on high core count CPUs is the current fix for this.
Used to work, after the update 14 Aug 2019, it barfs out prior to your avatar spawning on a planet.
A little jittery upon map loads.
Somewhat stuttery on initial map loads & shader cache creation. Slower than windows, but not terrible, after all of that is over -- guessing %85 that of native windows.
If you can enable the Vulkan renderer ingame, do so. On amdgpu driver based systems, usage of amdvlk is a must at the moment due to a bug in mesa's radv. But using the ingame Vulkan renderer, I have seen zero microstutters and everything is quite perfect. Using dxvk + radv + aco + dx11 renderer, I did encounter a fair share of microstuttering that was resolved with the move to the new Vulkan renderer.
AMD_VULKAN_ICD=RADV RADV_PERFTEST=rt,emulate_rt %command%
The game runs great, using the launch options.
Use the latest Proton-GE. Delete your old compdata/39120 folder prior to using any new Proton version.
I tend to prefer windowed mode, and switching resolutions did not crash for me, as others have stated. I did reinstall this game and did not record my old configuration. Thus I did run into issues with the vanilla Proton not working correctly these days. ProtonGE without any command line parameters worked perfectly.
This game runs via dosbox, but there is a sourceport from the nblood gang via [rednukem](https://github.com/nukeykt/NBlood).
Start the game (not the 64-bit), it will fail. Use protontricks to fix it:
'protontricks 217140 dotnet40'
Game runs very well.
Multiplayer will work by an invite from another individual thru steam.
Required the use of the following launch parameters:
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 PROTON_USE_WINED3D11=1 %command%
I also am using Proton-GE.
