PlayableShow Details
Unknown
Ubisoft Connect needs to reenter password each launch.
Ubisoft no longer supports multiplayer for this title.
Requires online connection to play. Ubisoft Connect now installs automatically.
I did all the testing using the customized GE-Proton9-2 version.
It worked a few days ago, then after an update, I can't get past the ubisoft login (fails to connect to the Ubisoft servers).
gamemoderun gamescope -H 1440 -r 165 -f --force-grab-cursor -- %command% -playoffline
Recommendation: just pirate the game to avoid the Ubisoft Connect crap
The second game in The Ezio Collection, a classic. Maxed out graphics give a mostly consistent 90fps on Steam Deck.
Used protontricks to backup and restore save games when I switched Proton versions.
A transparent to the user Ubisoft Connect process is launched that inhibits a clean exit without additional tinkering.
After first launch, in which controller is detected fine, subsequent launches failed to detect the controller. Resolved by forcing use of Proton 8.0-5, however one needs to enable developer mode and delete proton files before switching, otherwise the game will crash on launch.
Cloud Saves didn't sync.
2 game-states that lead to a consistent crash. Both when one first transitions from part N of a mission (including replays of the mission) to N + 1. After relaunching the transition happened and the game starts past the failure point. One of these was during the Flying Bomber War Machine mission, I forget the other.
An aesthetic skin from the DLC never unlocked. You can find save games from other people online and either use theirs or patch the raw binary data if you're into reverse engineering to regain that skin, and the Project Legacy capes.
A transparent to the user Ubisoft procrss inhibits clean exit of the game. One can configure it to close when the game does in Desktop mode by launching Ubisoft Connect manually.
Ubisoft password required on game launch. I didn't bother tinkering with offline mode, as the method to achieve it has repeatedly changed over the years.
Works pretty much out of the box, you will see some stutters in the beginning, but they should be gone after a while.
DXVK_FRAME_RATE=120 %command%
There will be some stutters while you are in new areas of the map for the first time, but when the shaders compile (at least, that is my guess) it starts running extremely well. After 30 minutes of gameplay it should become a lot more stable, or you should maybe turn on Shader pre-compilation.
I limited the FPS because there might have been degradations otherwise, and luckily Linux allows us to do that through Proton commands and by using 3rd party tools, so it was just a simple command to write down. I totally recommend playing the game in 2025!
NO INTRO MOVIES: (game_root/Videos/) UBI_LOGO.bik -> UBI_LOGO.bik_bak (game_root/Videos/en/) warning_disclaimer.bik -> warning_disclaimer.bik_bak
Ubisoft Connect does not save log in details requiring inputting password every play.
Doesn't turn off properly in Steam. Probably Ubisoft Connect running in the background. Manually stop after game exit.
Played through Ubisoft Connect with bottles. No issues.
Its basically a click play experience
The animation showing the ubisoft logo when starting the game has audio crackling, I haven't seen it in the actual game though
Aside from the audio thing I haven't noticed a single problem. Ubisoft connect works fine as well
Need to type Ubisoft Connect password on each launch
Controllers don't work on Proton 9
Doesn't support steam cloud saves
Downgrade to Proton 8.05 before installation to get controller inputs working. If you launch the game on Proton 9, you need to reinstall.
UbisoftConnect
UbisoftConnect seems to mess with controller detection.
Ubisoft Connect is a mess. Using an older proton version atleast the controller is detected. However i have to start the game in online mode and enter my Ubisoft password every single time. -playoffline doesn't work. Also the online services are dead.
*Mostly* free of issues, launched and played as normal, but would suggest buying on Ubi Connect over Steam
In certain missions, notably the castle attack at the beginning, the game will bug out when above 60 FPS and the missions will be nearly impossible to complete. AC1 also has this issue, but turning V-Sync on fixed it. It does not in Brotherhood. To fix it, you have to use Mangohud to limit the FPS or manually change your refresh rate in your display settings. In most of the game 180fps works fine, so you can keep it on until you encounter issues.
This is not a Proton issue, just an old game issue.
Ubisoft seemed to have replaced the UPlay launcher with Ubisoft Connect, so the steps from older ProtonDB reports about replacing UPlay are not necessary anymore. You can install the game and Ubisoft Connect will appear, no tinkering/installing required.
However, perhaps due to being "contained" in the Wine prefix, it seems Ubisoft connect will forget your login info everytime you close the game and you'll have to input it on the next boot. You can add a "note" to Steam and save your login info to just paste it in, but it is annoying. Using say, Ubisoft Connect from Lutris does not have this issue.
It should also be noted this game doesn't have cloud saves (not a Proton issue, but I didn't know and lost my saves).
Unless you really want it for collection purposes, I would suggest buying it on Ubisoft Connect instead so you do not have to deal with the login annoyance. Other than that, flawless performance and controller support out of the box. Works the same as native.
-playoffline
Game might not come back to fullscreen on tiling WMs
Check the steam guide for more information if the game doesn't launch.
-playoffline
Nothing to complain
-playoffline
Added -playoffline to the launch options to bypass Ubisoft Connect
Framerate is fairly variable depending on the enviroment; interiors and smaller-scope areas frequently stick to the 90 FPS cap but cities sometimes can drop as low as the high 60s.
Existing save with DLC wasn't working due to an issue unlocking DLC: "Load failed. A required downloadable content is missing."
Solved by overriding winmm DLL:
Navigate to "Wine configuration" > "Libraries":
- Add new override for library:
winmm - Edit
winmmand set toNative, then Builtin. - Save by pressing OK.
Existing save game now works with DLC unlocked.
Shadows sometimes flicker
Game runs fine, turns out i had a problem with my vulkan library. had lib32-amdvlk installed but running it on nvidia hardware.
-playoffline
runs fine
Game won't open even using custom flag "-playoffline"
-playoffline
Completely borked
Borked
Does not work out of the box. Needs Ubisoft Connect
-playoffline
Run relatively well out of the box. Recommend using the command to avoid the uplay launcher. Some stutters but shouldn't affect gameplay
-playoffline
uplay keeps asking for password
Stutters, especially on cutscenes. It happens when the camera suddenly changes to a new angle
Uplay launcher, for some reason, is especially bad on this title. It keeps asking for password
-playoffline
It's running perfectly fine and feels exactly the same as when I played it on Windows.
Just like AC2, game runs fine with the highest settings. Ubisoft Connect aint much of an issue, you can easily bypass it. Still has blackbars tho.
-playoffline
I enabled launch flag -playoffline to disable the password popup from Ubisoft Connect
If you're OK with entering your password, works great. If you're not, launch flag will solve it.
-playoffline
Sutter in beginning of the game that seems present on all Linux systems (from my Steam Deck to this guy's NVIDIA GTX 1080 system: https://youtu.be/UFbKOUD4FKE). Will update later to see if stutters improve later in the game once I make more progress.
-playoffline
Cutscenes sometimes don't sync with dialog
UPlay likes to sign you out after each session is shutdown
Install Ubisoft Connect, install Steam for Windows, Install AC: Brotherhood
On Proton, Ubisoft Connect could not detect my controller AT ALL. Installing AC:B through Lutris instead worked
Stuttering in the early game
Ubisoft Connect in the AC:Brotherhood Proton prefix could not detect my controller and I couldn't get the controller to work at all despite having no controller issue in AC1 and AC2. I got both the game and controller to work by installing AC:Brotherhood on Lutris through Ubisoft Connect. It annoyingly installed Steam for Windows on Wine too, but it works!
https://imgur.com/a/Bv9tsk1 Some of the textures have a weird (inconsistent) shade applied to them.
Significant stutter especially during cutscenes when there is a cut.
Long, but will probably work
Install Lutris, install Ubisoft Connect through Lutris, open and sign-in to Ubisoft Connect, grab the CD Key through one of the fixes mentioned here, add AC Brotherhood to Ubisoft account, install AC Brotherhood, Sign into Steam, install AC Brotherhood through steam installed on Ubisoft installed through Lutris, finally play game.
it is long, but it should work for anyone
gamemoderun %command%
I didn't need the assfix until now, dunno why. And using it reinstalled Ubisoft Connect and seems to have erased my save.
I have the STANDARD version of Brotherhood, meaning the assfix program will not successfully patch this. Follow the steps in this post, which requires Steam Metadata Editor and protontricks: https://github.com/smintman/assfix/issues/3#issue-1160472059
Next, I personally had an issue where it did not install the Ubisoft connect launcher by default, so I used protontricks, went to Install an Application, and installed uplay manually. This fixed that issue.
--CONTROLLER:
Last, I used a Switch Pro controller, and if you also want to use the Pro controller, you'll need to enable xbox configuration support in controller settings, then use an xbox controller bind configuation from the community configs, and then you MUST launch from Big Picture Mode in order for it to catch the controller.
The password prompt thing kept happening, couldn't figure out why, it's slightly inconvenient but not game-breaking.
Hope this helps for anyone looking for help!
See description, I needed to enable xbox config support for my Switch Pro controller and launch from Big Picture Mode
Spoiler warning: Sequence 9 bug, if you make it to the top of the thing, and find that the cutscene isn't triggering, make sure vsync is on, and set BOTH your system refresh rate AND the in-game rate to 60fps. This will also fix the Da Vinci glider thing which caused the controls to lock up.
"Would a typical gamer enjoy playing this game on Linux as you've played it?" Since it needs a fix I don't think so.
In order to work it needs a change of the DLCs in the appinfo.vdf file from "DLC" to "hidden_DLC". Needed fix: https://github.com/begin-theadventure/acfix/releases/tag/ACB
Whole issue is ancient, oldest issue on GitHub is from 2013! It's on Valve's side, they just don't seem care enough to fix it..
Created some shell scripts to fix and allow game to run please have a look.
Basically scripted the fixes that I detailed in my previous report.
I used ProtonUP, Gamemode and ACO shader comiler
