ByKe
Published
Change Compatibility to Proton 5.13-6 and it should install and work properly. Desync/Unable to connect may be due to alt-tab.
Audio may reset volume level if you alt-tab out
Due to changes from proton 5.x and 6.x, newer versions CAN'T save the game properly (can't save cities!)
I believe alt-tabbing in Multiplayer may cause desyncs or "unable to connect" messages. Playing with zero alt-tabbing gave me no issues until now.
Playable with stutters because of bad PC port. Incredibly smooth after a fix is applied, works like a charm!
Proton 6.1-GE-2 GloriousEggroll
winecfg to enable dinput8 override
Sometimes there'll be degradations depending on CPU usage. Can be fixed by patch.
The performance is as bad as on Windows because of the bad port. Can be patched.
I highly recommend following the notes by neptune [nachos] (https://www.protondb.com/app/292120#5VhnSA17zR) below. I adapted his process and my results should be similar or better for less powerful hardware.
I'm using Proton GE 6.1 because that's my default version, but the game also works with the newest proton 5.13 (as of writing this) and Experimental.
My Launch Options line on Steam (right click Final Fantasy XIII > Properties > General > Launch Options) is
DXVK_HUD=compiler WINEARCH=win32 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
DON'T use
tasksetas older reports suggest. The fix makes multithreading beneficial
You can ommit DXVK_HUD, but I like it to check when my computer is compiling shaders (thus using more CPU than necessary to make the game run, for a brief moment).
I'm playing on 1080p, 2048x2048 shaders, 2x MSAA. Disable the settings screen after you get a comfortable setting.
- The real magic is this repository:
I downloaded version 1.4.6 from the release page and extracted to my game folder:
<your steam library path>/steamapps/common/FINAL FANTASY XIII/white_data/prog/win/bin/
Then, you have to enable dinput8.dll. protontricks makes it way easier to manage Proton wineprefixes
protontricks 292120 winecfg
Go to Libraries > New override for library > dinput8 > Add. Then press OK to exit the screen.
- You can now modify the FF13Fix.ini file you copied from the repository. I'm using:
Borderless = true
ForceWindowedMode = false (true will make it a fullscreen windowed game. I like seeing my desktop)
PresentationInterval = 1 for VSync
FFXIIIIngameFrameRateLimit = 60
FullScreeRefreshRate = 0 (or a number of your choice)
TripleBuffering = false
There's been some discussion about this when using DXVK. Allegedly, setting it to true makes the game stutter a bit. Test it and pick your own.
If the game still stutters, it may be temporary shader compiling (wait 30s).
The game seems to have some problem with DXVK's shader cache system. Regular WINED3D has smaller stutters
Minor problems with hair, shading, then 1 big problem when a specific character got into "sillouette mode". It definitely wasn't common and didn't spoil my experience.
For some reason, the game's engine is poorly optimized with DXVK (which usually helps in performance)
- I'm on Fedora 34 KDE (for some reason not captured my Steam System Information).
- Played through the whole game on a wireless dualshock 4.
- I tried all available alternatives (including proton tkg and proton ge), even DXVK ASYNC, that runs smooth but that TOTALLY breaks the game to an unplayable state. Apparently, the game has to load scenes and assets in a given time and a given order for its quick-time events.
- I found the best compromise was to disable DXVK, then stutters and load times were way more bearable.
- The game seems to benefit heavily from raw cpu performance (GHz).
- I disabled cloud saving because of some recommendations, but I don't recommend it, since I didn't feel that much of a difference. Try it for yourself and see if there's any difference. If you want to keep your progress through different installations, leave it on.
It runs great once you dial the settings which prevent crashing, but it's very frustrating otherwise.
gamemoderun %command% --use-d3d11
White border initially, bug fixed if you change fullscreen mode. Game always starts minimized, but just alt-tab into it.
Apparently, FSR causes Plasma to crash after about 1h of play (probably AMD only), tested in Ultra Quality. After I set it to Native and locked fps to 60 (just in case), I played a 4h session with no problem.
Crossplay is turned on, I did missions with at least PC and Playstation players
Without tinkering it should work fine, but I added the d3d11 flag just in case, from other reports. Crashing after 1h mission would be terrible.
The game installs and plays seamlessly!
Only the first two missions were tried and have worked succesfully, even alt-tabbing was fine. It needs more playtime, but it's definitely in a good state
After turning off upscaling, everything works. Used GE Proton to try to fix upscaling, but it doesn't. Almost 60 fps with my PC lowest conf.
Can't use any upscaling option, screen turns black.
Playing on an HDD will make your wait times be about 3-5 minutes per map! With an SSD, that number falls to 30s-1min
You need to put certain options to be able to play without stutters. This shouldn't be necessary when playing on windows
On "set launch options", use %command% --waitforpreload --noasync. The first one will load initial assets. The second one will attempt to load ALL map assets before going into the map, and it's the key to being able to playing smoothly!! A lot of people suggest the "-gc 2" option. It used to be really relevant because PoE used to eat a lot of RAM. Use this option ONLY if your game closes unexpectedly after long hours of play! (usually, if you have 8GB of ram and an iGPU)
I can play the game with shadows High+GI (ULTRA mode really stutters!! requires high-end GPU), no antialising and the rest pretty much on High!
No VSYNC and framerate limited to 75 (not necessary).
Engine multithreading is ON.
WINEDLLOVERRIDES="dxgi=n" %command% as launch options to make the game start
Enable Proton Experimental and try to launch the game. If it doesn't work, add the WINEDLLOVERRIDES line and it should start up the game.
The game is run on Vulkan (Beta) renderer and I tested on borderless window with most settings on low and 1080p resolution. With Experimental, the game will be locked to 60fps and dip to 40fps on high-intensity scenes (given my laptop 1650 dGPU).
Playable, but we miss videos.Test this yourself and share their results. Game could pass new game screen and become playable with keyboard.
Videos don't play
Played on Open Beta, experience may change in full game if they add DRM or anti-cheat that doesn't go well with linux.
I played a Ranked Match using matchmaking and everything worked as intended.
