Had issues but kernel update fixed the problem, should work with default settings.
Set to 8.0-5 (reinstall). Don't forget your UPLAY login.
I forgot my UPLAY login from years back and no longer have access to the email it's attached to - that's on me - but I could not get around this issue. Even though I bought the game and was playing the game digitally on steam the CDKEY was tied to the old account. Strangely sometimes the game would start and UPLAY would autolog me into my original account allowing me to play. Very inconsistent. BUT the game itself was buggy when run on experimental so I had to switch to 8.0-5, which required uninstalling and reinstalling the game completely. It did work great the one time I got to play. The next time after that however it wouldn't let me past the UPLAY login because you know, I don't have my login from years back. Whomp whomp.
Smooth easy experience
It just works, without any tinkering.
It's a fine game and runs fine and is as expected - _once you get past the uplay madness_!
-offline
The Ubisoft Uplay madness. It required me to change my network MTU to 1452. Before I did that it said it couldn't connect, but just before saying that it made me log in and part of that process was sending me an email - so I know it connected to something!
It's not unusual with Ubisoft games for me to spend an hour trying to get it past the Uplay launcher when running through proton on Linux. There's no sanity to it. Sometimes you restart Steam. Sometimes you just relaunch the game 5 times. Sometimes you log into Uplay like it tells you to. Sometimes you need to turn off the Steam overlay. Sometimes you add an option like -offline
and sometimes that doesn't do anything.
I was running FCPrimal and put 15 hours into running perfectly well but then I moved and in my new location the game won't launch getting hung up with the uplay launcher. I tried everything I could think of (all the versions of Proton, reinstalling, logging in to uplay in different ways, the -offline option, Steam overlay off, etc). Currently the error I get from the uplay launcher is "Connection lost - A Ubisoft service is currently unavailable. Please try again later." Not terribly helpful when I can log in just fine from a browser. Not only that but they make you log in to uplay and that requires an email verification code; since I received that, I'm sure connectivity to Ubisoft is not my problem. And I was at a dead end for a long time.
I finally had the bright idea to update my system - it wasn't that far out of date but there was some nvidia* packages and that was probably important. Then to get past the putative inability to connect, I changed my MTU for the interface to 1452 (got that strangely particular value somewhere on a forum) using this command:
sudo ip link set dev enp4s0 mtu 1452
And finally it started and I could resume my game.
I really wish there were better more systematic and informative troubleshooting recommendations somewhere for this uplay launcher issue which has burned me in some way on pretty much every ubisoft game. But if you can get past that, these games run great on proton.
Used to work fine but Uplay killed it.
-offline
It's not unusual with Ubisoft games for me to spend an hour trying to get it past the Uplay launcher when running through proton on Linux. There's no sanity to it. Sometimes you restart Steam. Sometimes you just relaunch the game 5 times. Sometimes you log into Uplay like it tells you to. Sometimes you need to turn off the Steam overlay. Sometimes you add an option like -offline
and sometimes that doesn't do anything.
I was running FCPrimal and put 15 hours into running perfectly well but then I moved and in my new location the game won't launch getting hung up with the uplay launcher. I tried everything I could think of (all the versions of Proton, reinstalling, logging in to uplay in different ways, the -offline
option, Steam overlay off, etc). Currently the error I get from the uplay launcher is "Connection lost - A Ubisoft service is currently unavailable. Please try again later." Not terribly helpful when I can log in just fine from a browser. And that's a dead end. I wish there were better more systematic and informative troubleshooting recommendations somewhere for this uplay launcher issue which has burned me in some way on pretty much every ubisoft game.
Средние настройки графики, полёт отличный
45 fps
ENABLE_VKBASALT=1 %command%
Fullscreen and Borderless mode make the window flicker for a split second when clicking with the mouse. In KDE Plasma (not sure if this problem even exists in other Desktop Environments) this can be fixed by adding a Window Rule with the "Fullscreen" option set to "Force". (Workaround only tested on Wayland, might work on X11 as well)
45 fps lock
Use Proton 8.0-5 (ot 8.0-4) to avoid game renders at one single pixel dot on Deck OLED
Shadows, PostFX and Volumetrics on medium, high for all other settings
Doesn't Work on OLED Steam Deck
When launched, the game shows up as a tiny dot in the center of the screen. This dot changes brightness and color while the sounds of the intro videos and menu play. If I had to guess, I'd say it was launching at a resoluton of something like 2x2. This problem only happens in gaming mode. The game is able to launch from desktop mode, and seems to work fine there.
I still have my old 512 GB LCD Deck, and have confirmed that it still works on that one running the same version of SteamOS and Proton as my OLED, so the issue definitely has something to do with the OLED Steam Deck specifically. I also know that I'm not the only one who has encountered this problem. I've tried a number of different versions of Proton, and have tried doing resolution tweaks in the game configuration. Nothing has fixed it so far.
Works great, the initial launcher setup is a little annoying but after first launch that stops being a thing.
Installed and played straight away.
Just make sure you install Ubisoft Connect and run with proton experimental.
Proton 8 is the answer to the "Uplay error" with previous versions of Proton on Pop!_OS.
Do NOT revert to older versions of Proton, as it will look for the old Uplay (as opposed to the newer Connect), which it won't be able to find, and even going back up to a newer version of Proton won't fix it and you'll need to reinstall the game.
Works as expected
When stopping the game upc.exe keeps running in the background, which needs to be killed manually to be able to start the game again.
游玩20分钟,显示一个ubisoft无法保存的错误,自动退到菜单页
每次打开都需要登录ubisoft,不会自动记录登录信息。
From my point of view Platinum. No issues on my Linux PC.
No Tinkering, only Steam Beta participation.
Worked almost perfectly, very good performance.
When clicking, the taskbar would show for a split second.
This game ran right out the box just fine. I use GEProton7-43(it gives a tiny performance boost), experimental also works fine.
gamemoderun %command%
Ubisoft Connect is borked, install Uplay from protontricks as a workaround
In the home village, lighting is wonky. Sometimes a third of the screen in certain cutscenes will be fully bright.
Ubisoft Connect is broken and cannot update itself and will not allow you to start playing. First, I clicked Play and was stuck on Ubisoft Connect saying "Looking for patches". I had to go into the compat data for 371660, rename the Ubisoft folder in Program Files (x86) to something else, then install Uplay from protontricks and let that update to Ubisoft Connect. Then I could run the game normally.
While I was playing Ubisoft Connect rolled out a new update, so I had to redo the renaming, protontricks install, but my game save was missing! Some brilliant mind at Ubisoft put it under the Program Files (x86)/Ubisoft folder. You must copy the savegames folder from the old Ubisoft folder (hopefully you renamed and didn't delete) to the new Ubisoft folder.
WINE_CPU_TOPOLOGY=31:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30 %command%
protontricks 371660 uplay
For those of you who are getting stuck on the Far Cry Primal splash screen indefinitely, apparently this is an issue with newer CPUs. This is what eventually worked for me:
WINE_CPU_TOPOLOGY=31:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30 %command%
Many many thanks to the awesome work by ChaosBlades and Blisto91 in this thread: https://github.com/ValveSoftware/Proton/issues/2143
Also see some more valuable Far Cry information here: https://github.com/ValveSoftware/Proton/issues/5927
Before I found out about this fix, I had previously tried the trick of copying another Far Cry's Ubisoft folder over this one. That didn't help and eventually Uplay stopped launching altogether. To fix it I deleted the ~/.local/share/Steam/steamapps/compatdata/371660/pfx/drive_c/Program Files (x86)/Ubisoft/ folder and ran 'protontricks 371660 uplay' to reinstall it. Didn't have another Uplay issue after doing that.
Once click-resolution issue was fixed by swapping between windowed and fullscreen, game ran fantastically.
Ran into a very strange issue where clicking inside the game at all would cause the resolution to momentarily shrink, showing my KDE status bars. This happens on every launch. Going into display settings and swapping between windowed and fullscreen seems to fix this, but I have to do it every time the game boots up.
Occasional framerate hiccups which were probably due to shaders being calculated. Framerate was great and mostly stable otherwise.
Steam thinks the game is still running after you exit. This seems to be because of Ubisoft Connect continuing to run after exiting the game. Upon exiting out of Ubisoft Connect, Steam correctly notices the game as being closed.
The resolution clicking bug is definitely a big problem, but easily fixed and otherwise the experience is great. Performance was solid, and there was no need to tinker with launch options or any other configuration. No need to call protontricks either, as Steam + Proton automatically downloaded and installed Ubisoft Connect correctly. Once things are working, the game "just runs" like it should.
Can't play
PROTON_USE_WINED3D=1 %command%
The game starts, into is fine, once in the game, the background is full of odd textures and flickering that makes the game unplayable.
high settings, locked30 FPS.
Runs on Ultra
Had to manually install uplay
A bright square present in village
Lag spikes were a bit annoying, disappeared after the start, might not be proton specific
protontricks 371660 uplay
Occasional lag spikes, I got these regardless of graphics settings.
Can't even reach the main menu
Even if I install uplay through protontricks I couldn't alt tab to the game, I can only hear the sounds but the game doesnt let me interact with it.
Game does not launch
a message pops up saying you need to install ubisoft connect and then goes nowhere.
Installs but doesn't run
When first installing the game, it launches the splash screen but since uplay isn't installed it errors and exits. Installed Uplay Connect and now doesn't even get to the splash screen
Able to get to the splash screen once uplay is installed but not further
Upon initial launch after setup I was greeted by a Uplay Error so I used proton tricks to setup Uplay.I Created an Account as it was asked and registered/login successfully.
This made the Uplay Error go away but when I launch the game :
- First I see the Farcry Primal SplashScreen for a few seconds
- Then I see a Uplay window reporting successful connection to my account and synchronisation of whatever,
- Finally the Farcry Primal Splash screen appears again never to leave.
The Process Behind "Far Cry Primal\bin\FCPrimal.exe -uplay_steam_mode" is taking 100% of a core to himself and around 230Mo of ram (quite much for displaying a splashcreen but not so much for a Farcry game)
Kubuntu 21.10 Crashes from Uplay launcher
Unable to get Far Cry 4 or Primal to launch past the Uplay launcher. It just thinks for a minute and then crashes. Tried some of the protontricks workarounds but no luck so far.
Basically the game should run fine.
You have to install uplay with winetricks or protontricks and connect with your Ubisoft account for your saved games.
Runs perfectly fine with Proton 6.3-4
When starting the game, the keyboard isn't detected for about half a minute
Requires installing UPlay with winetricks.
6.5-GE-2 GloriousEggroll
Need to install UPlay thru Protontricks and GloriousEggroll seems to fix missing vegetation for the most part.
If you just purchased the game you may run into the Uplay authentication issue as I did. You will need to install the game with Lutris using Wine-Steam and install Uplay. The authentication link was only working from Wine-Steam to Wine-Uplay. After is runs in Lutris you can run it normally from your native install of Steam. This tends to happen with alot of UPlay games and it seems that Uplay needs to fix or enable this on a game by game basis. (FC4 required the same treatment)
This game runs perfectly
The game wont launch without UPlay installed. You need to use protontricks or winetricks to install "uplay":
Through Protontricks
protontricks 371660 uplay
Using Winetricks
WINEPREFIX=~/.steam/steam/steamapps/compatdata/371660/pfx/ winetricks
I was using GloriousEggroll before, then I just installed xact64 to be sure that wouldn't have any issues, for that I used protontricks:
protontricks 371660 xact64
A lot of random glitches and trees fading when you get near. Before I was using the "Proton-6.1-GE-2" and had the same problem. Apparently I resolved installing the MF patches mf-install and mf-installcab. For that I just did:
git clone https://github.com/z0z0z/mf-install.git
WINEPREFIX=~/.steam/steam/steamapps/compatdata/371660/pfx/ ./mf-install/mf-install.sh
git clone https://github.com/z0z0z/mf-installcab.git
WINEPREFIX=~/.steam/steam/steamapps/compatdata/371660/pfx/ ./mf-installcab/install-mf-64.sh
cp mf-installcab/mfplat.dll "$HOME/.steam/steam/steamapps/common/Far Cry Primal/bin"
The game won't open without uplay, then I installed it through:
protontricks 371660 uplay