TheGoogleRider
Published
Played with a controller for like an hour, runs well with Proton Experimental, haven't seen any issues so far
PROTON_USE_WINED3D=1 %command%
I had to use WINED3D because of my older hardware (which has incomplete Vulkan support)
Yeah, this game requires some enthusiast-level tinkering, but it was not hard and in the end is enjoyable
PROTON_USE_WINED3D=1 %command%
The Uplay launcher which comes with the game is too old and is kinda required to run the game (I wasn't able to get it to run the game offline), so I had to use protontricks to install a newer version of the Ubisoft launcher to get the game running.
Crackling is because my very old hardware
The game seems to have trouble with some controllers, I highly recommend Sergeanur's EaglePatch which improves controller support and other nice things, and I also recommend just relay on Steam Input for controller (because I just can't get analog triggers to work)
This game would be perfect it they removed the Uplay/Ubisoft launcher, there are controller issues, but these issues are not linux specific and if you play with mouse and keyboard this shouldn't matter
Honestly this games runs phenomenally even on my old hardware and running it with WINED3D instead of DXVK, though controller require tinkers
WINEDLLOVERRIDES="dinput8=n,b" PROTON_USE_WINED3D=1 %command%
I found when set to a lower resolution, instead of utilizing all areas of the screen, the game just became smaller
AC1 and AC2 has some issues with newer controllers, I had to use Sergeanur's EaglePatch for improved controller support and other nice stuff, this is also what WINEDLLOVERRIDES="dinput8=n,b" is for
Honestly, if you play with Mouse and Keyboard it shouldn't be an issue (though I heard mouse and keyboard support is bad), playing with controller requires some tinkering either with the aforementioned EaglePatch or Steam Input configuration.
I still think the overall best way of playing the game is with EaglePatch and a controller though, as the EaglePatch also have some graphics settings improvements (if I understand correctly)
PROTON_USE_WINED3D=1 %command%
WINED3D is because of my old hardware
It works out of the box and I in-general recommend this version of the game over the original
PROTON_USE_WINED3D=1
I found since my hardware is so old (11year old i5) that even though the game graphically runs ok, sometimes the audio crackles, but I'm pretty sure with newer hardware this issue shouldn't really appear (maybe unless you 100% your cpu)
PROTON_USE_WINED3D=1 %command%
Crackling but mainly because of my aging 11 year old hardware
My entire saves got lost, not sure if it's a specifically Steam issue, but It just got deleted from my Steam Cloud after I switched distros. (But I want to replay it anyways)
Runs basically like Native (with Proton Experimental), Controller works, no issues with audio and stuff
PROTON_USE_WINED3D=1 %command%
Just had to use WINED3D because of my old hardware without Vulkan support
PROTON_USE_WINED3D=1 %command%
As of Proton 9.0-3, there are still flickers of textures and I suspect video cut-scene playback not working properly, but when using Proton-GE instead, the game ran perfectly without issues.
(Note: I had used WINED3D because my hardware is too old for DXVK)
PROTON_USE_WINED3D=1 %command%
A bit of crackling but honestly I blame my hardware for this
The only reason I used PROTON_USE_WINED3D=1 is because my GPU doesn't support Vulkan (which is needed for normal Proton), if you have a more recent GPU this is most likely not needed making this game basically install and play for most people.
Runs surprisingly well, Native works as it should.
I don't know a case yet to use Proton on this game, but like I said, Native runs perfectly even with controller support.
PROTON_USE_WINED3D=1 %command%
I just had to use WINED3D because my laptop vulkan version is too old, but even without Vulkan, the game ran really well for me (well it's locked at 30FPS), but yeah
I played with controller and it seems to me with an 8Bitdo Xbox style controller that everything was working as it supposed too (played without Steam Input API, so Native)
PROTON_USE_WINED3D=1 %command%
Sometimes the music crackles, though it doesn't always happen and I don't consider it a deal breaker
Because my IGPU (Intel Iris 5100-Haswell) has incomplete vulkan support, I had to lauch with "PROTON_USE_WINED3D=1 %command%", but overall I had a blast playing this game on linux.
PROTON_USE_WINED3D=1 %command%
Again I had to use WINED3D because of my older hardware.
But overall, ran shockingly like Native, didn't see any issues at all. (Note: there are glitches in the game but those are intentional).
LD_PRELOAD=/usr/lib32/libjack.so %command%
I used this guide to get everything working
But for more details:
Requires RS_asio + WineASIO + Native-Jack to work
If done correctly, then everything is fine
Ahhh It's difficult to get this game working properly, honestly it took me ~3 Hours to get everything working correctly on Arch Linux.
I wish there would be a one-click solution for this later on in the future, but until then I recommend this guide.
Yeah, I have been playing Civ5 on Linux basically weekly, it's been going well and I can recommend it
PROTON_USE_WINED3D=1
Crackling because of my very old hardware
Honestly occasional rather rare crashes but it's isn't anything major, likely because of my old hardware
Fun game, I honestly haven't tried Online (and Local-Network) Multiplayer, but offline-single player works like a charm, the only reason I use PROTON_USE_WINED3D is because my pc is old, you can run it without this on newer hardware.
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.
PROTON_USE_WINED3D=1 %command%
Crashed once in my 3 hour playthrough, I think it's the game itself though
Used WINED3D because of old hardware
Basically Native works out of the box, no need for Proton
played 2 game throughs, haven't had any issues at all.
PROTON_USE_WINED3D=1 %command%
Had to use WINED3D because of older hardware, but overall most people with newer hardware would definitely be able to run this without any tinkering
PROTON_USE_WINED3D=1 %command%
Had to use WINED3D because of old hardware.
