


at first launch didnt prompt anything but after second install worked perfectly
potential cause is meddling with wine, lutris or proton versions
nothing happens after pressing play button

Initial loading screen takes 10 minutes
Works just fine with Proton GE, Variable Refresh Rate works with v-sync 1 frame too and framerate is as stable as on windows!
DXVK_ASYNC=1 gamemoderun %command%

Micro-freezing in fullscreen if v-sync is disabled
Not sure how to not get it to stutter and/or freeze without having to enable v-sync but otherwise it works fine

The game wouldn't install uPlay when I intially tried running it. So it wouldn't launch. I fixed this by installing and running a different ubisoft title (Scott Pilgrim vs. The World in this case) and that installed uPlay. After that I was able to run the game without any issues.

broken after update ;(
After a very recent game update, the game will not launch. No obvious indications of why with PROTON_LOG=1. I did see RPC_S_SERVER_UNAVAILABLE but I'm not sure this is the issue

dont work
PROTON_LOG=1 %command%
Installed Ubisoft Connect manually, disabled Steam & Ubisoft overlay, but it won’t start. mfc100.dll error persists after installing VC++ 2010.

The game works immediately after installation
After installation, the game works immediately, you just need to log in to your Ubisoft account each time you start the game, at least in my case.

game-performance %command%
The Ubisoft launcher will ask for your password every time. The game doesn't seem to inhibit screensaver so during cutscenes my screen would dim or turn off. Added the launch option to force performance mode.
WINE_CPU_TOPOLOGY=29 %command%
I only needed to do: Install ProtonUp-Qt, and within the app GE-Proton9-22 Restart Steam and select GE-Proton in game's properties

Needed to log into Ubisoft Connect every time you launch the game. Very annoying.
The crackling was very minor. Slightly noticeable whilst driving.
I set my Refresh Rate to 45 Hz. Game worked happily. No framerate drops yet.

MANGOHUD=1 MANGOHUD_CONFIG=cpu_temp,gpu_temp,ram,vram gamemoderun DXVK_ASYNC=1 %command%
O game rodou tranquilamente com as alterações que fiz. Por padrão sempre coloco nos games a linha de comando "MANGOHUD=1 MANGOHUD_CONFIG=cpu_temp,gpu_temp,ram,vram gamemoderun DXVK_ASYNC=1 %command%" juntamente com o ProtonGE, e se rodar, não testo outra config. Nesse caso o game está aprovado, e ainda rodou melhor do que no Windows 10, já que o game é mal otimizado para maquinas muito fracas, e máquinas mais recentes tem problemas de compatibilidade ocasionando lentidão, não no caso do Linux... Vai entender! kkk

PULSE_LATENCY_MSEC=90 %command%
Cannot get audio to work properly no matter what runner I use, previous reports stated PULSE_LATENCY_MSEC=90 was able to resolve, but has had no such effect on my game. PULSE_LATENCY_MSEC seems to have no effect on the process at all as raising this value does not cause the audio latency to increase at all. I was able to test in Lutris games and noticed that PULSE_LATENCY_MSEC is respected there in a few games, but not on several steam games including this one.
After some time playing fine the game start to "stutter"
No matter which version of steam-provided proton or ge-proton I try, the game does not start

Game doesn't launch
Game refuses to launch, pressing play nothing really happens other than steam reporting that I'm playing the game for a few seconds.

Works
Performs very well

Had to disable Steam Overlay, otherwise it wouldnt start

Download the UbisoftConnectInstaller ( https://www.ubisoft.com/en-us/ubisoft-connect/download )
Add the installer as a non-steam-game to Steam and execute it (Compatibility mode - Proton 9.0.2 - might also work on newer/older versions)
Remove the installer from your steam-games-list and add the now installed Ubisoft Connect ( UbisoftConnect.exe ) as a non-steam-game to Steam
Open Ubisoft Connect (Compatibility mode - Proton Experimental) and download Far Cry 3
Once the download has finished, open the "Far Cry 3"-directory
Rename the file " FC3Update.exe " to " FC3Update.exe.backup "
Create a shortcut called " FC3Update.exe " that points to the file " farcry3_d3d11.exe "
How to create a shortcut: 7.1.: Right-click in the "Far Cry 3"-directory --> "Create new" (in german: "Neu erstellen") --> "shortcut to file or directory" (in german: "Verknüpfung zu Datei oder Ordner")
Start Ubisoft Connect via Steam
Start Far Cry 3
Disclaimer:
It might also work with other compatibility modes, your mileage may vary.
A really, really big thanks to HazMan07 !
gamemoderun %command%
mangohud gamemoderun %command%

Doesn't run at all. Hit Play and nothing happends
I tried force launching Ubisoft Connect, and after that, the game runs to the main menu but still crashes when trying to start the story.

Had to disable the Steam overlay - otherwise the game just infinitely loads once it opens. There is some minor artifacting but it is not that prevelant.

The game will not launch at all
There was a point where the Ubisoft Connect splash screen would pop up but after that, nothing has worked. I have tried every proton version under the sun and it will just not turn on for me.

If the game gets stuck on the loading screen, try to disable Steam overlay.

Steam Overlay
The game runs perfect, just remember to disable Steam Overlay because for some reason the new overlay is making the game stuck on Loading screen and never go to the menu.

black screen and crash before startup

Disabled Steam overlay for this game.

Switched back to Proton 8.0
Deactivate Steam-Overlay for this game to prevent an infinite loading loop after the game has started

DXVK_ASYNC=1 %command% -offline -skipintro
Inject 32bit DXVK (d3d11.dll and dxgi.dll). D3D11MultithreadedRendering="1" in GamerProfile.xml. In game: VSYNC=1, 1280x800, MSAA off, mix of Medium/Low graphics settings. Deck settings: FPS/Refresh Rate=72 on OLED, 60 on LCD. Rock solid performance and looks great.
Ubisoft Connect
All above steps required for steady fps

WINEDLLOVERRIDES="crypt32=b,n" %command% prime-run %command% gamemoderun mangohud %command% -fulllscreen
Uplay starts working after I added WINEDLLOVERRIDES="crypt32=b,n" option. Proton logs were missleading and inaccurate.

Ubisoft Connect gives the error "Connection lost: A Ubisoft service is currently unavailable. Please try again later.", which means you cannot get into the game if their servers haven't connected on this install before.
To fix this I simply ran:
echo net.ipv4.tcp_mtu_probing=1 | sudo tee /etc/sysctl.d/custom-mtu-probing.conf
This enables MTU probing which, after a reboot, enabled Ubisoft Connect to connect to their servers.
Since it has now connected once, if one wanted to reverse this change, they could run:
sudo rm /etc/sysctl.d/custom-mtu-probing.conf
Besides Ubisoft Connect errors, the game runs perfectly fine.

Not working, no uplay, no main screen, just launching and crashing
err:module:import_dll Library XINPUT1_3.dll which is needed by L"..\SteamLibrary\steamapps\common\Far Cry 3\bin\FC3_d3d11.dll") not found

Steam Overlay needed to be disabled to get the game past its loading screen. The Ubisoft launcher needs to be shut down manually even when configured to shut down on exit.
mangohud gamemoderun %command%

gamemoderun gamescope -w 1920 -h 1200 -f mangohud %command%
Performs well on an AMD APU at high settings. Switching to DirectX 9 yielded a significant performance benefit.
Ubisoft launcher forces a sign in on every launch by default; this can be worked around by launching without internet access, prompting the launcher to offer a switch to offline mode and circumventing future login prompts, even when internet access is re-enabled. On my bspwm setup, the laucher refused to tile properly, instead floating around on the screen. Forcing fullscreen with gamescope fixes this.

Disabled Steam Overlay
Enabling MSAA caused some artifacts with waterfalls, where a strip of the view near the center of frame is invisible.
Aside from the MSAA and Steam Overlay issues, the only thing noteworthy is the abysmal performance of the Ubisoft Connect launcher, which significantly extends the launch time of the game, and requires manually closing the launcher after exiting the game (else Steam would consider the game still running, if you care for playtime counters). Other than that, it didn't feel much different than it did on Windows.