Skip to content

ProtonDB Fixes to Games

Fixes applied to games running on Ubuntu GNU Linux operating system.

To bypass launcher issues on Native installations, go to the games local file directory (Game properties > Install Files > Browse) using Steam and find the binary, launch the game from the binary

  • Use Hide the top bar extension for windowed full screen
  • Works out of the box with proton experimental

  • For story mode, install Proton GE using asdf instructions on GE GitHub, restart steam, select GE and test story mode works ok

    • During Story Mode cut scenes, may need to press Enter to get rendering to work

Works using installation of EA App described at Running Windows Programs with Steam Proton - Running Windows Programs with Steam Proton. Install the EA App, then install FIFA 20 inside the app and run the game. During first run, configure game settings like display resolution, then press the button to run. As the game’s servers are turned off, the game will show a message the servers are down, but offline play is not affected.

To make it easier to launch FIFA, add a new non-Steam game. Use the same prefix as the EA App like these examples and set these settings for the Steam app:

  • Compatibility: Proton Experimental
  • Target: “/path/to/EAGames/pfx/pfx/drivec/Program Files/EA Games/FIFA 20/FIFA20.exe”
  • Start In: path/to/EAGames/pfx/pfx/drivec/Program Files/EA Games/FIFA 20
  • Launch Options: STEAMCOMPATDATAPATH=“/path/to/EAGames/pfx” %command%

Enable Compatibility: Force the use of a specific Steam Play compatibility tool: Steam Linux Runtime 1.0 (Scout). The lower version likely due to changes in Linux and its libraries over time and old version closer to the game’s release. Then launch War of the Chosen. Alternatively, legacy runtime 1.0 may work as well.

Game startup may take couple minutes until main menu.

Source: Linux Client is broken. :: XCOM 2 General Discussions

From Feral’s support feedback:

The issue you are seeing is suspected to be related to the game not finding the correct libraries due to changes in modern versions of Linux.

Right click the game in your Steam Library, and select Properties In the new window that appears, go to Installed Files and click Browse In the window, enter the ‘lib’ folder, then the ‘x8664’ folder Select all files in ‘x8664’, and Cut them using Ctrl+X Now, go back to the ‘lib’ folder and Paste the files using Ctrl+V Delete the remaining ‘x8664’ folder from the ‘lib’ folder Launch the game again

Had to apply these fixes

https://www.protondb.com/app/1084160#vf74V81EyK

Open the game folder (right click on the game, properties -> installed files -> browse) Navigate to Packs/Maps folder. Create some folder, name it as you like - i.e. bak or temp Find all the files with names starting with “MainMenu_” Move all those files to the folder you created in step 3. Launch the game. Game should launch to the menu but instead of the background with your mercs, it will be black. Open Options -> Video and change Reflections to anything other than Medium or High. Off, Low and Ultra are ok. Apply the change. Don’t try to play yet. You do not have some necessary files. Close the game. Restore the “MainMenu_” files to their previous location. Restart the game. Game should now go to the main menu, background with mercs should be there.

https://www.protondb.com/app/1084160#SkpINaDy8R

Windowing:Size

  • You might notice that mouse clicks apply slightly below where they are supposed to. This is because in full screen the window is slightly lower than expected. This can be observed by moving the mouse to the top of the screen and looking at the thin black area on the top.
  • To fix this, go to settings, set the windowed mode to “Windowed”, apply and then switch back to “Windowed fullscreen”. This will fix the clicks.
  • Needs to be done after every restart.

Game should work native without proton.

With issues with vkWaitForFences failed: -4 or similar errors related to Vulkan, try the following troubleshooting options based on Warhammer 3 crashing, Signal 6/vkwaitforfences failed:

  • Lower video settings
  • Use Windowed mode
  • Disable shadows

Game should work out of the box. See Fix 1 and 2 regarding VC Redist during initial game run.

Games that should work with no or minor changes

Section titled “Games that should work with no or minor changes”
  • Call of Duty: Infinite Warfare
  • Cities Skylines
  • Crusader Kinds 3 (see Paradox Games native workarounds)
  • CyberPunk 2077
  • Diablo 4 (IV)
  • Homeworld Deserts or Kharak, Remastered Collection
  • Injustice 2
  • Mechwarrior 5 Mercenaries
  • SpellForce Conquest of Eo
  • Stellaris
  • Total War: Pharaoh, Troy, Three Kingdoms, Warhammer 3 (Native), Attila
  • Uncharted: Legacy of Thieves
  • Warhammer 40,000 Dawn of War II Retribution
  • Warhammer 40,000 Rogue Trader
  • WWE 2K25

Games to take a while on first run, like due to install, installation scripts, or shader loading

Section titled “Games to take a while on first run, like due to install, installation scripts, or shader loading”
  • Battletech
  • Homeworld 3
  • Marvel’s Midnight Suns
  • Titanfall 2 - requires log in to EA app during launch
  • X COM Chimera Squad

VS Redist Package Issue and/or Scripts Stopping during initial run, first run of game

Section titled “VS Redist Package Issue and/or Scripts Stopping during initial run, first run of game”
  1. Fix 1: Clear Steam Download Cache

    See also fix for Steam Proton games stuck on “Installing: Microsoft VC Redist Package”, workaround from pewpewpewmoon:

    I get this from time to time. Clear your download cache, give it a minute and then try again. It will fix it most of the time

    Steam > Settings > Downloads > Clear Download Cache

    EDIT: This also happens on windows, it’s just an annoying thing that has always been a part of steam for some people

    Also can check integrity of game’s files if there are issues under Game’s Details > Installed Files

  2. Fix 2: Unmount all external drives

    Unmount any extra external drives. Stop the game and restart it. Remount drives after the game starts.

    Possible cause is Wine maps USB drives as extra Windows drives. Windows redistributable installers may query all drives during setup. If one of those drives is slow or unresponsive or has issues, the installer hangs waiting for it.

    If the script hangs, look for evidence of changed files with .vdf in ~/.steam/steam

  • protondb - crowdsourced Linux and Steam Deck game compatibility reports