UnsupportedShow Details
Unknown
PROTON_USE_WINED3D=1 %command%
Randomly Crashes, can be mitigated with frequent saves (and AutoSaves), but still really annoying
Save a lot, I feel like this game is kinda the abandon blacksheep of the Civ Games tbh
WINED3D is only because of my old hardware.
I am glad prton gave this game the abilty to run
As you pan the map there is artifacting
The launch from steam is slow, after that is runs fine
When I installed the game the native linux port did not work; All it did was open & crash. Running this over proton; I was amazed that is worked as it did not in previous versions of proton. I would recomend keeping the graphics at medum to keep performace issues to a minium.
Tried fixes from https://github.com/bmaupin/civ-be-linux-fixes/
Can't play longer than 5 minutes
With proton game didn't launch. With native version i can't play longer than 5 minutes without crash.
If using Proton experimental and not entering the Options menu until *after* starting a game, then it works well.
Crashes if entering the options menu from the initial main menu. If first starting a game and then returning to main menu, one can enter the options menu and change settings without a crash.
Doesn't seem to run as native on Linux, I have to use Proton (Experimental).
The native Linux version has major bugs out of the box. I gathered fixes for the most significant problems I found and I put them here:
Some people reported that the audio would stop after a while. This didn't happen to me but I did notice a missing audio library, which I added to the fixes.
Terrain doesn't always display correctly before fixes are applied.
Game crashes with mods without installing a patch. Game also crashes if libtbb.so.2 isn't copied. Both of these are solved by the fixes above.
I ran the game with Proton for a while but I kept having problems with it, particularly with mods. So I figured out fixes for the most common problems with the native Linux version, and now I prefer that over Proton.
Works on Proton but not natively.
It crashed every time I tried to go to Options from the main menu. After starting a game first, it worked fine.
The native version would crash when trying to start a new game.
Simply doesn't work.
Occasionally fails to start, but rarely. But I can never play for more than 2-3 minutes at most without a crash.
The native version crashes when trying to load the mods menu. It was crashing in Proton too but it seemed to work the first time I installed a mod, so I used these launch options to delete the mods directory every time I launched the game and it seemed to work:
find "/home/$USER/.steam/steam/steamapps/compatdata/65980/pfx/drive_c/users/steamuser/Documents/My Games/Sid Meier's Civilization Beyond Earth/MODS/" -delete; PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_HEAP_DELAY_FREE=1 /home/$USER/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=65980 -- /home/$USER/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- "/home/$USER/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper"/_v2-entry-point --verb=waitforexitandrun -- "/home/$USER/.local/share/Steam/steamapps/common/Proton 8.0"/proton waitforexitandrun "/home/$USER/.local/share/Steam/steamapps/common/Sid Meier's Civilization Beyond Earth/CivilizationBE_DX11.exe" # %command%
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command%
Same as boredbanana below.
It's definitely enjoyable. Copying
libtbb.so.2 from ~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/ into the game's folder
made it possible for the game to lauch!
Very rare crashes
Proton 6.3-8 also works, but has mouse input issues where you can't drag around the map properly, or at all in the tech tree which makes late game play impossible. All other proton versions and the native version would crash within 30 seconds of starting a new game. If you switch between different proton version, verify the integrity of the game files through steam. Otherwise it'll crash on startup. On 8.0-5 though the game runs perfectly.
Won't start regardless of proton version or native
Crashes in the menu
8 and 7 CTD when you press a button in the starting menu, earlier versions don't even load the menu, and Experimental throws an exception. This is very unfortunate, as the native version doesn't play well with mods.
Steam is stuck on "launching"
Just use the native version. It might be poorly optimised and slightly unstable but at least it starts.
Worked great out of the box
No issues noted, using recommended Proton 8.0-2.
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command%
The game runs both vanilla and modded (Codex overhaul and some other mods) perfectly fine, taking into account rare crashes I had running the game on Windows 10. Native Linux version also works fine, but sadly there is no Workshop support.
If you experience crashes with native Linux version of the game:
- Load libtbb2_4.2~20130725-1.1ubuntu1_i386.deb from Ubuntu archive
- Extract files from .deb package using ar command \ ar emulator \ something else
- Copy library ./data/usr/lib/libtbb.so.2 to game's root directory (path_to_your_steam/steamapps/common/Sid Meier's Civilization Beyond Earth)
- [Optional] Add argument LD_PRELOAD="full_path_to_the_lib_directory/libtbb.so.2" to Steam Launch Options
Game is borked for both Native and Proton; Main Menu is about as far as you can get
Game will hang when using any of the buttons on the main menu when ran via proton, and if ran natively will appear to work until you click the 'play' button and will then CTD.
Unplayable currently for my setup.
Running native seemed to have good performance (prior to crashing), various proton versions all seemed a little laggy
Cannot play the game beyond 5-10 turns, it will crash no matter running native, or with any of the available proton options. Also, trying to run mods wouldn't even start a game without crashing.
At the start the game seems to freeze but it's just loading stuff on the background.
Gives an error and crashes
Error message is blank. Only has an 'OK' button
Worked fine in a short test
Some jitteryness but nothing major
Ran a little rough but seemed playable so far
Sometimes there was a loading screen poping up for all players, but the game always resumed without issue
To run the game you need to chose the first option when launching the game (AMD option just crashed on Steam Deck).
I found out that when using Proton Experimental instead of Proton 7.0-4 it will fix the issue with the research tree. With Proton 7.0-4 you are unable to move the research tree, so it's not easy to do any advanced research (you need to manually search for it).
The previous report from me was incorrect, I forgot that I was originally playing with Proton Experimental and didn't check the research tree after change to 7.0-4.
Played of few hours without any problem
I played it with Proton 7.0-4 and noticed that you need to choose the first option on lauch, the second one will either crash or stay stuck in loading screen indefinitely.
Proton experimental appears to have resolved the tech tree response issue. If you force experimental the game should play normally now.
Tech tree screen unresponsive to any control inputs regardless of key assignment changes.
Had to copy a file into the game's folder
It's definitely enjoyable. Copying
libtbb.so.2 from ~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/i386-linux-gnu/ into the game's folder
made it possible for the game to lauch!
It does run really well and my PC seems to stay cooler while playing this game on Linux than on Windows.
I definitely recommend it, if it runs on it's first launch or you don't mind fixing the game.
Controls work fine once you figure them out, but it's not immediately clear what everything does. I still haven't figured out how to scroll the tech tree, but I didn't spend too long trying. I assume you can remap controls to your preference, but I didn't try. Definitely playable even with default controllers though.
Stuck on menu screen
Game loads and runs intro sequence, but the first menu never appears. Game is stuck on background picture and sound running.
Works through Proton but native is preferred and has fewer problems
Mouse not detected for scrolling with edges. Can't click and drag through the tech tree.
If you are into achievements (like I am), the my2K account connection doesn't work on native but works through Proton. This is indeed required to complete Sid Meier's Starships but I digress :-)
Unfortunately, the sound disappears after a few minutes of play
After a few minutes of playing (not in the main menu), all the sounds (music, interface) stop and do not come back.
With proton didnt even get to menu
With proton I never got to a game main menu. Native started to main menu, i was able to set up game, but actual game crashed before game started
The game runs really well, and it's one of my favorite Civilization games. My PC is from 2015, nothing impressive, but the game runs smooth.
I've played the game a few times here in Linux, during my 1st time playing, the audio stopped working after 30 minutes. Ever since then, it's been working fine. Not sure what happened, but nothing game breaking.
Still doesn't launch via Proton
I still have periodic audio issues with the native Linux version, and was encouraged that some recentish Proton updates have let Civ 6 work under Proton, so I figured I'd try out Civ:BE in Proton again, just in case the Windows version worked better for me. Alas, it still doesn't seem to launch. Tried with both Proton 6.3 and whatever the "Proton Experimental" version was, as of 2021-08-24. The native version still does mostly work, at least.
So this report is for the NATIVE version of the game, there doesn't seem to be a way to enter a report for NATIVE games, so that's why I listed proton 5.1 on here.
I wasn't able to launch the game as it would instantly crash after pressing play, however, if you click on properties and select "force use of a steam play compatability tool", then select "Steam Linux Runtime" it will work flawlessly for me. I couldn't find any information about my error online, and it was really frustrating, so I wanted to put this out there in case anyone else has the same issue.
