PlayableShow Details
Unknown
Gal Civ III works flawlessly with Proton GE 9.7 I didn't have to do anything else.
With games that include launchers, I always get a bit nervous since they tend to mess things up. I was pleasantly surprised when everything went off without a hitch and just worked. The game ran smoothly, no noticable bugs from my time playing. Still a fantastic game today.
Wine -lutris-ge-6.14-x86_64
Crash at game start
The Stardock launcher runs normally, but the game itself crashes immediately when started from the launcher. I tried with Proton versions 5.11-6 and 4.11-13.
Works very well. If you don't need the tutorial, you can play ery well.
The marker hexagon is usually not where the mouse pointer is. Makes it a little bit difficult but is manageable.
Tutorial crashes on first colonization. This works in normal game play.
I did not check any size limits.
Installs, opens launcher menu, doesn't open the game
I can't reach the game menu. Steam recognizes the game as running, but nothing shows up in the screen.
It has some bugs in tutorial and occasional frame drops. Apart from these issues seems fine overall.
Game dropped below 60 fps during cutscenes.
Planet colonization in tutorial always crashes the game!
For some reasons game launcher becomes darker when interacted with
I played it for a couple minutes. More testing should be conducted I guess.
some screen flickering rarely
feels a bit slower than on my previous Win7 PC build, given my Hardware this should not be the reason.
might need to switch some video card options ingame or in the nvidia driver to get best experience.
Proton-5.9-GE-5-ST GloriousEggroll
Likewise Proton 4.2, when I play with more than 20 civilizations, lots of objects (planets, resources, ships, shipyards, anomalies, etc) just don't appear on the map (when I play with 21 civs, a ship disappears; with 22, artfacts disappears, and so on).
Galciv3 version: 4.0.1.0 (all DLCs minus Worlds in Crisis and Villans of Star Control: Origins)
Runs well and stable at 50 fps (not 60, I don't know why), with v-sync disabled (using NVIDIA adaptative v-sync), 1920x1080, Preset High, anti-aliasing 4X (is working fine now).
Also works with Proton-5.11-GE-3-MF and Proton-tkg 5.14.r0.gb71d588d.
Regular Proton (5.0.9 now) still unable to run the game (it crashes on start).
changed proton version
Highest graphic settings are fine. I did not need specific Wine start options. Proton 4.11 and 5 did crash. I changed proton version to 3.16.9 and previously broken UI work, start option %command% /nolauncher to prevent the launcher from starting.
PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% /nolauncher
overlapping UI resulting in not beeing able to click on tiles in the planet development
partly Broken UI
added /nolauncher so it skips stardock's launcher
Needed PROTON_USE_WINED3D=1 %command% also added /nolauncher, to remove the useless launcher
Version 3.9, before 4.0 update. The does not able to start.
It crush even with these laaunch parameters: PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% /nolauncher
The release of Proton 5.0 didn’t make the game playable again. For now, your only hope is still Proton 4.2-9.
I’ve tested GalCiv3 recently under newly released Proton 5.0-1, and the net result was no different than with 4.11 --- the game’s splash screen (which is pitch black, by the way) opened for a short time, followed by the game’s internal “Looks like the game crashed” window. Disabling ESYNC and FSYNC doesn’t appear to work, and the game is also oblivious to switching between DXVK and WineD3D.
I’ve disabled Stardock’s launcher because 1) it’s not necessary to have it running when Steam’s client exists and 2) it’s reported to be glitchy.
Proton 4.2-9 remains the latest version of Proton that can still run the game. The game can sometimes crash under DXVK (and will apparently crash on loading too big maps), but is otherwise playable. Disabling DXVK leads to graphics anomalies (incorrect star background, transparency in UI elements, custom ship designs not having icons).
Unplayable.
No graphics (Regardless of D3D vs DXVK or ESYNC) when using Proton 4.11-11. Game starts with working graphics using Proton 4.2-9, 3.16-9, and 3.7-8, however the game grashes when "generating galaxy" or trying to click the options menu in-game.
Although the game presents some issues, we can play it with two conditions: less than 20 civs and anti-aliasing disabled.
When I play with more than 20 civilizations, lots of objects (planets, resources, ships, shipyards, anomalies, etc) juns don't appear on the map.
Some freezing in the beggining of the turn (more often on large maps). It' about 50% of the Windows version performance.
The game eventually crashes on loadings.
Crashing on colonizing a planet
I tried again to launch the game with 4.2-9 and disabling DXVK and this time the game actually started. Not sure what was different from last time I tried.
Tried the tutorial and the game constantly crashes upon colonizing the first planet (first step in the tutorial).
Have not bothered trying a normal gameplay since others have also reported frequent crashing.
Crashes on initial load screen
The launcher loads just fine but pressing play game causes the game to crash on initial load screen. Tried with WineD3D and other fixes reported by other players but nothing works. It either crashes on load screen or does not load at all.
Have also tried Proton 4.2-9 with similar results.
Unknown(> 10 hours with Proton)Worked smoothly with DXVK until the 3.9 game update, afterwards it began to crash regularily, most notably on the diplomacy screen, once on attempting space combat and another time on the United Planets screen. With 3.95, the game crashes just after loading the world. Also tested on Proton 4.2-9. Disabling DXVK appears to work, but it leads to performance degradation.
Unknown(> 10 hours with Proton)
This one didn't want to cooperate at all until I launched it with the following parameters (PROTON_NO_ESYNC=1 PROTON_USE_WINED3D=1 %command% /nolauncher). Prior to that, it kept crashing just before the intro cinematic. After several hours of play, everything seems to be both stable and functional.
Unknown(> 10 hours with Proton)Game runs initially fine, but in the lategame it starts to crash frequently, mostly - but not exclusively - on the diplomatic-screen.Save often, it is still playable with patience.
Unknown(> 10 hours with Proton)Unknown(2+ hours with Proton)Works perfectly fine.
Unknown(2+ hours with Proton)Unknown(2+ hours with Proton)Single player works fine, Multiplayer seems to desync/crash after 20-30 turns. Leaves processes running after quitting that require killing.
Unknown(2+ hours with Proton)Unknown(2+ hours with Proton)Runs very good on Intel IGPU (low settings) after disabling the stardock-launcher in steam-launchoptions ("/nolauncher").
Unknown(2+ hours with Proton)Unknown(> 10 hours with Proton)The stardock launcher seemed a bit flaky but it's not required and easily bypassed with /nolauncher, after that the game seems to work perfectly. Played for 10 hours, no problems. Have not tried multiplayer but Crusade and Intrigue expansions work perfectly.
Unknown(> 10 hours with Proton)
Ran the game fine over several turns .
Unknown(> 10 hours with Proton)Tweaks: protontricks quartz mf. Might be unnecessary. Tested: Single player, custom civilizations from steam workshop. Not tested: Civilization builder, multiplayer, mods
Unknown(> 10 hours with Proton)
