PlayableShow Details
Unknown
Starting the game takes a lot of time and includes killing the game process once for some reason
taskset -c 0-1 %command% -skipintro -force-d3d9
- Lauch the game through Steam
- Wait for Ubisoft Connect to start
- Game doesn't start, System Monitor shows FarCry4.exe with 0.X% CPU usage
- Terminate FarCry4.exe using System Monitor
- Wait for FarCry4.exe to start again this time with higher CPU and RAM usage
- Wait a considerable amout of time for the "Steam is not responding" dialog
- Press "Wait" and wait some more
%command% -skipintro
Sometimes the game has trouble keeping the cursor in the game window
Sometimes the game freezes when starting the game. Restarting the game may help
Freezes when starting the game is pain in ass. I don't have any clue why this is happening. Restarting the game or Steam may help or not. These freezes are completely random
every one listed on proton db
launches but freezes during initial loading and there isn't a way to fix it (actual pc specs: AMD Ryzen 9 7900x, Asus 9070xt OC, 32gb of ddr5, OS: Bazzite)
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json:/usr/share/vulkan/icd.d/amd_icd32.json %command%
Instead of using RADV I needed to switch to AMDVLK. Otherwise the game would freeze at startup or producing massive artefacts.
WIN + ENTER to change to windowed and back to fullscreen, otherwise the mouse doesn´t work in game.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only %command%
If you're playing on a laptop that has a dedicated graphics card like NVIDIA, please try this tinker. After trying many fixes and testing for 3 days, this was the thinker that finally worked. Seems like this game switch to integrate sometimes, which was resulting in crash.
DXVK_ASYNC=1 %command% -skipintro -force-d3d9
It wasn't launching at first. I tried every tweak in the list, but the one tinker suggested here was the only one that worked. Thanks to Nickyecen for the tip!
issues are extremely tiny, they can be solved by using proton ge
Game refuses to capture my cursor unless im playing it in Borderless mode
game runs at ~90-100 fps at medium/high settings
ENABLE_VKBASALT=1 %command% -skipintro
The game won't start under GNOME; it gets stuck in a minimized state. I ran it in KDE Plasma.
Doesn't work no clue what to do for now.
WINE_CPU_TOPOLOGY=15:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 gamescope -w 1920 -h 1080 mangohud %command% -skipintro -force-d3d9
mangohud %command%
mangohud %command% -skipintro
mangohud %command% -skipintro -force-d3d9
DXVK_ASYNC=1 mangohud %command% -skipintro -force-d3d9
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 mangohud %command% -skipintro -force-d3d9
Doesn't work at all.
Steam Version works out of the box. No issues. Limited to 55fps, few framedrops. Disable godrays. Graphical settings overall set to medium.
55fps limit, Godrays disabled, SMAA enabled
no problems encountered. i played through the ubisoft connect version and noticed no differences from playing through steam
you can lower graphics to improve battery
works perfectly with slight framedrops on ultra graphics while sacrificing battery life (i got 1hr 20 on 100%)
based game
Runs great, a few crashy bugs you need to be aware of
Minimizing the game while in FULLSCREEN mode sometimes crashes the game and Wayland on Arch Linux for me, I play in Windowed Borderless to avoid this when I need to multitask.
Half the time starting the game freezes on the very first loading bar screen, needs to be stopped by Steam and restarted a couple times
gamemoderun %command% -skipintro
Joining a coop game may crash
My friend (who is using windows) invited me to a coop session and i couldn't join
I had to disable the steam recording, otherwise after 45 mins it would begin to stutter. I couldn't join my friends coop session nor could he join my session, but joining a random coop session is fine.
Game wont start without -skipintro
Played for 4 hours straight, no issues.
Game runs okay, you do need to add ' -skipintro ' otherwise you'll have a 50/50 chance of crashing to desktop on every launch.
-skip intro
Stuttering after approx. 2 hrs continuous play
I tried everything i could find to try and fix the major stuttering as it would always begin after 1-2 hours of play and then I would have to quit the game and restart it, I could not find a source (CPU/GPU usage did not go over 50%, RAM usage 3gb/16gb, normal temps <50 degrees C). Theory is that is the game engine or its interaction with proton. All of these tested individually and in almost every combination nothing helped : taskset -c 0-1 ; PROTON_USE_WINED3D=1 ; DXVK_ASYNC=1 ; PROTON_NO_ESYNC=1 ; PROTON_NO_FSYNC=1 ; force-d3d9 ; editing config file.
Doesn't start.
taskset -c 0-1
I'm probably being an idiot though..
taskset -c 0-1 %command% -skipintro
FarCry 4 is a fairly difficult game to play, when running with plain wine, the Direct X11 renderer has many artifacts that make the game unplayable. When using DXVK, the game immediately hangs on the first frame. If Ubisoft Connect is used under steam the problem remains; running the steam version is the only way to get Farcry 4 to play.
After install, the game would hang a few seconds or even a minute or so after launch, it appears that Farcry 4 doesn't like a large number of cores so to work around that, the "taskset -c 0-1" command was used in the launch arguments. taskset specifies which processor cores to allocate to the next command so "taskset -c 0-1 %command%" will only allocate processor zero and one to the game; using more causes the game to hang after a few seconds.
Using only two cores is ample for this game and results in good playability, frame rate and no crashes.
Unless your system only has four or so threads available, using taskset will improve your experience with Farcry 4.
-skipintro
Played it on PS4. Played it on Uplay (PC) when I was still a Windows user. Now playing it again on Steam. And it's as great as ever.
Launch parameter '-skipintro' is just for convenience to skip all those startup clips which feel like an eternity if you have to see them every time you launch the game.
As with every game which launches Uplay via Steam in the background: you have to manually exit Uplay after playing the game to make Steam recognize the game isn't running any more. As a KDE user with a functioning system tray (sorry GNOME users... ;) ) this is easy as the tray icon of Uplay is visible after running the game.
-skipintro
Edited the ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Far Cry 4/bin/FC64.dll in a hex editor for ultra widescreen (21:9 3440x1440) support.
https://steamcommunity.com/app/298110/discussions/1/3017941618737295450/?l=koreana
Game works OOTB with Proton, but needs widescreen fix for ultra wide monitors.
PROTON_USE_WINED3D=1 %command%
100% working with startup option - PROTON_USE_WINED3D=1 %command%
DXVK_ASYNC=1 %command% -skipintro -force-d3d9
When launching without any tinkering, the game freezes at the starting screen. To fix this, I just disabled Steam Overlay and added the launch options.
I've seen people adding these and more to the game, but be careful, there are many launch options that could lose you performance, such as WINE_CPU_TOPOLOGY, PROTON_NO_ESYNC and PROTON_NO_FSYNC. Only use them if necessary or, of course, if you know well what you're doing.
"-skipintro" may not be necessary, but you might want to add it.
The game also worked for me when using PROTON_USE_WINED3D=1 %command%, but it was a bit more laggy.
After certain cutscenes, the game freezes on a black screen. Switch from Wayland to X11 seems to fix this issue.
Wayland = issues. Nvidia 555 drivers will likely fix this, but they're aren't on my distro yet so that's speculation.
mangohud %command% -skipintro
Bei Proton 9.0(Beta) und Proton Experimental werden Teile vom Spiel vom Hintergrund übertlagert. Proton 8.0.-5 läuft bestens. Getestet mit X11 und Wayland.
gamemoderun gamescope -w 1920 -h 1200 -f mangohud %command% -skipintro
The game runs very well on my AMD APU even at fairly high settings with textures set to ultra.
There are a few minor annoyances, primarily the mandatory Ubisoft launcher. By default, this will require you to sign in on every launch. This can be mitigated by signing in once, then executing the game with internet access disabled, prompting the launcher to offer you to switch to an offline mode. This will avoid future logins, even when internet access is re-enabled. On my bspwm setup, the launcher window refused to tile properly, instead floating across the screen until forced into fullscreen; using gamescope fixes this by blowing up the launcher to a full-screen window. The game also does not quit properly when exiting through the game window (probably because the ubisoft launcher refuses to shut down), but can be turned off from Steam.
There is letterboxing when playing on a 16:10 display; this is not a Linux-specific issue.
Problem: Crash after startup. Solution: The configuration file GamerProfil.xml was missing after installation. Path: /home/USERS/.steam/steam/steamapps/compatdata/298110/pfx/drive_c/users/steamuser/Documents/My Games/Far Cry 4/USER-ID/GamerProfil.xml. Created file and added std configuration (found on the Internet)
The configuration file GamerProfil.xml was missing after installation.
I just disabled Steam Overlay in General in Properties, General Menu.
The game works almost out-of-the-box as soon as I disabled the Steam overlay. No launch options needed, just selecting Proton Experimental or GE.
freezes on first loading screen
tried some launching commands but was not able to play
WINE_CPU_TOPOLOGY=15:0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 DXVK_ASYNC=1 %command -skipintro -force-d3d9
After a hard time of getting the game to start, i finally managed to run it by disabling the steam ingame overlay BEFORE starting the game, which fixed the loading screen freeze for me, actually i do not know if it would run without the launch option because i tried the launch option first and the with all these changes combined i had a great expierience. As a linux enthusiast i would say it was OK to tinker around and get the game running, especially because it would always crash on my windows drive, same hardware btw xD
After applying these fixes, I would describe it like this: As good as native, in my own case even better as it did not crash my laptop anymore :D
%command% -skipintro
Crash on first loading screen, but only sometimes
I have no idea how to make this game start up reliably, it's always a coin toss whether it hangs in the first loading screen or makes it to the main menu. If it actually does then it plays without any problems, if it doesn't then I have to stop the game via Steam and try launching it again until it works.
Switching to Proton Experimental or not doesn't seem to matter, I've had it work without it a few times too. Launch options have not helped either.
Freeze and blackscreen
I start the game, it goes to the loading screen, it starts freezing, I try lauch option "PROTON_USE_WINED3D11=1 %command%" Starts booting to the main menu but the screen is black, tested "all proton version"
Ubisoft launcher continues to be finicky, but it seems that when you work around it once you're set. As long as you log in with your credentials while online at least once, it seems to work moving forward even if you don't have internet. I've played several hours without a connection thus far.
I run graphics on high with motion blur off and maintain an almost entirely stable 40 FPS lock in handeld mode. I don't have a variable refresh rate TV/monitor so my docked experience fluctuates between 40-60 FPS with graphics still set to high. Just be careful with anti aliasing and ambient occlusion, as more than one of their presets can severely hinder performance. Just figure out which ones to avoid and go from there.
