Far Cry 4 (298110)

[Holzhaus]

Compatibility Report

• Name of the game with compatibility issues: Far Cry 4
• Steam AppID of the game: 298110

System Information

• GPU: PowerColor Radeon RX Vega 64 Red Devil 8GB
• Driver/LLVM version: Mesa 19.0.0-devel (git-e2ae5f2f0a), LLVM 8.0.0
• Kernel version: 4.20.0-rc7-mainline
• Link to full system information report as Gist: https://gist.github.com/Holzhaus/837a0fb4e7ee0783effc43968a31e73f
• Proton version: 3.16.6

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

A Uplay window with the title "Looking for updates" appears, accompanied by an error message box that tells us that Uplay has detected an unrecoverable error and must shut down.

Log file: steam-298110.log

Uplay crash dump (GZipped):
Uplay.exe_4.8.1.3617_2018-12-26_18-53-02.dmp.gz

Reproduction

Install Far Cry 4 and click the "Play" button.

[ATypescriptEnjoyer]

This has been raised before, can be fixed by manually installing older version of uplay into the prefix and then changing the version number. https://www.reddit.com/r/linux_gaming/comments/a8f2kl/proton_3166_beta_released/ecbdi99/ Not a nice fix, but a fix at that.

[ATypescriptEnjoyer]

I've managed to get this game running after doing the above steps, but am now encountering lack of audio and a rendering bug, I've uploaded the video of my issue here: https://jackryder.co.uk/stuff/far-cry-rendering-bug.mp4

@kisak-valve would my issue be best in a separate issue? Didn't want to create another open issue for the same game.

[kisak-valve]

Hello @jackryder, unless you find the root cause of an issue and the issue affects multiple games or the game is whitelisted, then it's best to discuss the game specific issues here.

Please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the issue, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[ATypescriptEnjoyer]

system info :https://gist.github.com/JackRyder/d706d3038a2b8893595214a95e930045

Since the game runs, the proton log is pretty hefty so I split it into two parts, I imagine the second part would be the best for infomation, but i'll attach both anyway.
steam-298110A.log
steam-298110B.log

Also using proton 3.16-6 Beta.

[ghost]

I was able to get it working with Proton 3.16-8 Beta, and I got sound working too. I achieved this by using protontricks to run winecfg and add FarCry4.exe with the compatibility mode set to Windows XP, then using protontricks to install xact. Now I have an issue where the game is freezing every few minutes. This is because I'm on Ryzen isn't it? The issue reminded me of another issue I had with other Dunia Engine games on wine-staging because I had too many CPU cores. This is definitely not the culprit (and shouldn't be since esync is enabled). The stuttering seems to be caused my me rapidly moving my mouse. Any ideas? I plugged a different mouse into my computer and the freezing went away. Thanks Corsair.

[pklampros]

Had the same mouse problem but disabling Uplay overlay fixed it..!

[NTMan]

With Proton 4.2-4 the game working with follow issues:

1. No sound after first cutscene, this issue can be workarounded:

• $ WINEPREFIX=~/.steam/steam/steamapps/compatdata/298110/pfx/ winecfg
  and set Windows Version to Windows XP
  
• $ WINEPREFIX=~/.steam/steam/steamapps/compatdata/298110/pfx/ winetricks xact

2. Appearing on random locations rectangular dimming in game:
   
   How it looks in dynamic I demonstrate on Youtube video: https://youtu.be/6O_LUtFXP58

3. After switching to another application and returning to game by pressing "Alt -Tab" unable rotate protagonist on 360 degrees (only 180 is possible), this issue can be workarounded if in main game menu (Escape button) and select "Resume" item.

4. Not working gamepad in my case it Dualshok 4

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 5.1.0-ea5aee6d97fd+ x86_64 bits: 64 Desktop: Gnome 3.33.1 
           Distro: Fedora release 31 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 2202 date: 04/11/2019 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 3779 MHz min/max: 2200/3700 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.4 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: AMD Radeon VII (VEGA20 DRM 3.32.0 5.1.0-ea5aee6d97fd+ LLVM 8.0.0) v: 4.5 Mesa 19.1.0-rc2 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: N/A 
Drives:    Local Storage: total: 11.57 TiB used: 8.15 TiB (70.4%) 
Info:      Processes: 456 Uptime: 6h 58m Memory: 31.40 GiB used: 16.62 GiB (52.9%) Shell: bash inxi: 3.0.34 

[NTMan]

The game is crashes when I enable renderdoc (ENABLE_VULKAN_RENDERDOC_CAPTURE=1) for record a trace.

steam-298110.log

[xDShot]

Gamepad controls are not recognized in the game...

[xDShot]

Also all foliage appears flickering

[xDShot]

To fix flickering foliage, install/compile dxvk 1.4.4 or less for now.
Related: doitsujin/dxvk#1257

[Hanouta]

I've bisected the flickering issue, it's caused by this commit in DXVK.

[spamatica]

As Far Cry 4 was on sale I got it. Works with an nvidia card as far as I can see. The audio issues still exist but can be worked around as previously detailed.
I would like to get the controller part to work though. Any ideas how to go about it? The initial menu react to controller input but seem to misinterpret the input. This probably leads to controllers being disabled.
Any ideas how to go about debugging this? I'm not very experienced with wine/proton debugging.
Searching for this issue I see that Far Cry Primal also has trouble with controllers, same issue maybe.

[open-antux]

Far Cry 4 don't run. Uplay run correctly without any problem, but when I click play on Far Cry 4 it didn't run

[sandsmark]

I've bisected the flickering issue, it's caused by this commit in DXVK.

Have you reported it to DXVK?

[Hanouta]

I've bisected the flickering issue, it's caused by this commit in DXVK.

Have you reported it to DXVK?

I wrote a comment about it in the Far Cry Primal issue (doitsujin/dxvk#1257) because that seems to have the same problem. Unfortunately they don't really know what's causing the issue, and are not really interested in fixing it(see doitsujin/dxvk#1257 (comment))

[sandsmark]

Unfortunately they don't really know what's causing the issue, and are not really interested in fixing it

from the later comment it seems like it you tracked it down pretty closely. I guess the next step (unless someone spots the issue) would be to look at the disassembly (ghidra has a diffing mode) with and without the call. not in the mood to wade through x86 assembly now, though.

[Carusu]

it seems to work fine with Proton-6.0-GE-1

[kisak-valve]

Far Cry 4 launches from UPlay then immediately crashes

Issue transferred from #5149.
@ChaosBlades posted on 2021-09-10T11:09:18:

Compatibility Report

• Name of the game with compatibility issues: Far Cry 4
• Steam AppID of the game: 298110

System Information

• GPU: 6900XT
• Driver/LLVM version: Mesa 21.0.1
• Kernel version: 5.13.15-xanmod1
• Link to full system information report as Gist: https://gist.github.com/ChaosBlades/afc2f85876c2427f6a86c7832273c1a4
• Proton version: Any

I confirm:

• [ X] that I haven't found an existing compatibility report for this game.
• [ X] that I have checked whether there are updates for my system available.

steam-298110.log

Symptoms

Uplay launches the game then it immediately closes.
I see in the proton logs an error for...
[0828/085556.679:ERROR:dxva_video_decode_accelerator_win.cc(1440)] DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: Module not found. (0x7E)\

... I tried to download that dll from the internet and put it in system32 but that did not seem to help

Reproduction

I have tried a completely stock fresh install of Pop OS.
Up to date modded xanmod kernel
Proton GE
Adding mesa and wine repo
All versions of Proton available in Steam
This is the only game I have tried that does not work. Other UPlay games work without issue
I have Far Cry 4 Gold edition with all the DLC if that matters.

[ChaosBlades]

It seems msmpeg2vdec.dll is part of the Windows Media Feature Pack which led me to a winetricks github issue. that can not be linked here

It seems this is a really old issue which makes me think it is not the reason Far Cry 4 is not launching for me because it clearly worked several months ago.

[kisak-valve]

Hello @ChaosBlades, the link you posted is tainted by legally problematic workaround(s) and has been removed.

[ChaosBlades]

I did some testing on this...

Ubisoft Connect does not work on Proton 5.13-6 or older. So that leaves only Proton 6.3-7 and Experimental.
I tried fresh installs of Pop!_OS, Manjaro, and Garuda Linux. All the the same issue.
Either Far Cry 4 works on an older Proton Version but Ubisoft Connect won't work on or this is a specific issue with my hardware config... 5950x and a 6900xt
Looking at ProtonDB I can see that this was working on the latest Pop!_OS with Proton Experimental 2 months ago with a Ryzen 5 2600 and Nvidia 1650 so perhaps this is an AMD GPU issue.

[ChaosBlades]

It has been months now and I am still having this issue and over these last several months I look at protondb and I see random people also having the same experience as I do appear either the game runs great or it never launches. Does not seem to matter what hardware brand you have, what version of proton you are using, or what linux distro you are on. Either you are lucky and it works or you are not lucky and it doesn't launch past UPlay. I tried multiple distros both debian and arch based, tried multiple Proton versions including experimental bleeding edge, as well as tried removing all DLC and just running the base game.

[ATypescriptEnjoyer]

It has been months now and I am still having this issue and over these last several months I look at protondb and I see random people also having the same experience as I do appear either the game runs great or it never launches. Does not seem to matter what hardware brand you have, what version of proton you are using, or what linux distro you are on. Either you are lucky and it works or you are not lucky and it doesn't launch past UPlay. I tried multiple distros both debian and arch based, tried multiple Proton versions including experimental bleeding edge, as well as tried removing all DLC and just running the base game.

Try using the GloriousEggroll proton versions, they work better with 3rd party DRM

[ngreve]

System Information

• OS: Arch LinuxKERNEL: 5.18.9-arch1-1
• CPU: AMD Ryzen 7 3700X 8-Core
• GPU: AMD Radeon RX 6900 XT (sienna_cichlid, LLVM 14.0.6, DRM 3.46, 5.18.9-arch1-1)
• GPU DRIVER: 4.6 Mesa 22.1.3RAM: 16 GB
• Proton 7.0-3 and GE-Proton-7-24
  System Information

Symptoms:

• with no launch options, Ubisoft Connect starts, but the game does not launch

• vk_radv %command%: Same as with no launch options - Ubisoft Connect starts, but the game does not launch

• vk_amdvlk %command%: Launches but freezes immediately at the very first loading screen; it does not even reach the main menu:
  

• PROTON_USE_WINED3D=1 %command%: Game runs, but with massive graphic glitches, see video:

2022-07-07.12-46-42.mp4

Changing between different ingame graphics settings does not have any effect on these glitches.

[Blisto91]

@ngreve It's likely a dxvk issue. I also reproduce a hang at the initial loading screen. Tho that is with radv.
I have made a issue about it here doitsujin/dxvk#2669
And there is another issue from a windows user that the game crashes when they use dxvk.

Does it say anything interesting in the proton log when you try to launch with radv or amdvlk?

Edit: i am sorry i accidently pinged the wrong person first time

[ngreve]

Running with vk_radv the last message says (steam-298110-radv.log):

5862.720:0150:0154:trace:seh:raise (22)
terminate called after throwing an instance of 'dxvk::DxvkError'
5862.720:0150:0154:fixme:msvcrt:__clean_type_info_names_internal (1000B488) stub

Running with vk_amdvlk i can't find anything interesting, but that's because I actually do not know what I am looking for (steam-298110-amdvlk.log).

[Blisto91]

This in your radv log is very odd.

info:  Required Vulkan extension VK_KHR_surface not supported

That should not happen as i'm pretty sure that is a pretty old supported extension (and required for anything to work). Could you try reinstalling radv and see if anything changes?
Be sure to install both 32bit and 64 bit version.

[kisak-valve]

Hello @ngreve, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[ngreve]

The requested system information (also updated my OP)

I've reinstalled vulkan-radeon and installed - the missing - 32bit version of it.
Now running with Proton-7.0-3 and vk_radv, the game freezes in the beginning just like with vk_amdvlk, but the message Required Vulkan extension VK_KHR_surface not supported disappeared, I guess that's progress (?).

But I also revisited ProtonDB and saw that people got the game running with Proton 6.3 in the past.
So, I've tested it with Proton 6.3-8 and I've got it running with with vk_radv and vk_amdvlk.

But I encountered another bug. At some point, if you switch between different Proton versions, an error message appeared that said something like "No Ubisoft Connect installed. Install it so run the game... (blabla)". This error occurred every time when I've switched from Proton 7.0 down to 6.3. Switching back to 7.0 did not fixed the error, I needed to reinstall the whole game.

So, to get it running with Proton 6.3, I firstly needed to uninstall the game.
With the game uninstalled, go into Properties -> Compatibility -> Select Proton 6.3-8, then install the game.
Now Steam/Proton finds Ubisoft Connect and starts the game.

Again, the game now runs with Proton 6.3-8 and both vk_radv and vk_amdvlk.

[kisak-valve]

Thanks, https://gist.github.com/ngreve/1cce2333b360acc6229ea68457ecc4d0#file-gistfile1-txt-L278-L291 and https://gist.github.com/ngreve/1cce2333b360acc6229ea68457ecc4d0#file-gistfile1-txt-L439-L452 looks like GPUOpen-Drivers/AMDVLK#278 could be interfering with your testing.

[Blisto91]

If they are using https://aur.archlinux.org/packages/amd-vulkan-prefixes i think as long as they launch with vk_radv %command% it should be fine. In the game at least. But yes the lines look odd in the system report.

@ngreve Good to hear with some progress. Could i get you to try and start the game 3-4 times into the main menu with 6.3-8 and see if it succeeds each time? at least my own issue was that it only happened some times. If it doesn't freeze with 6.3-8 at all thats a good data point to try and find a regression for when i test it again later.

[ngreve]

I've entered the main menu multiple times now and played for ~5min and it seems to run fine with two little caveats:

• Before you enter the main menu, there is this splash screen with the FarCry 4 Logo and the message "Press any key". When I now press a key, the game focus gets lost and I have to alt+tab into the game again. But then I am in fact in the main menu and can play the game.

• The game freezes, as soon as I try to enter the steam community overlay with shift+tab steam-298110-steam-overlay-crash.log.

EDIT: Btw, thanks for the exchange of ideas and getting it running in the end.

[Blisto91]

Okay thanks for testing.

On the second point i think i remember seeing that too when i was testing Far Cry 2. When i brought up the steam overlay it froze. Forgot to make a comment about it.

[ChaosBlades]

But I encountered another bug. At some point, if you switch between different Proton versions, an error message appeared that said something like "No Ubisoft Connect installed. Install it so run the game... (blabla)". This error occurred every time when I've switched from Proton 7.0 down to 6.3. Switching back to 7.0 did not fixed the error, I needed to reinstall the whole game.

You just need to delete the compatdata folder for the game. You don't need to reinstall the entire game.

[makeclean]

Replying to #2143 (comment)

Genius! Yes, I have 64 cores that will be it! Man that's quite the find.

[kisak-valve]

Far Cry 4: It's impossible to play under any version of Proton

Issue transferred from #6942.
@Plarpoon posted on 2023-07-21T00:58:38:

Compatibility Report

• Name of the game with compatibility issues: Far Cry® 4
• Steam AppID of the game: 298110

System Information

• GPU:
• Driver/LLVM version: AMD AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.52, 6.4.3-1-default)
• Kernel version: 6.4.3-1-default
• Link to full system information report as Gist:
• Proton version: All versions up to 8.0-2 (for now)

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Note:

• For all of the following logs I have used nothing else but the parameter "PROTON_LOG=1 %command%".
• My Linux distro of choice is OpenSUSE Tumbleweed, this distro has AppArmor constantly enabled in the background, this is noteworthy when doing debugging.

This log is with Proton 8.0-2, it fails immediately after having done the initialization of Ubisoft Connect, it can't even create the window of the game. You have to stop the process manually from within the Steam app by pressing "STOP" as after failure it will remain open in the background forever.
steam-298110 8.0-2.log

This log is done with GE-Proton8-6, I am aware this is not the place to report Proton GE issues but I am using it only to report what happens once you pass the Ubisoft connect phase and actually manage to create a window. In this case as said the window gets fully created but it crashes a few seconds in during the very first loading screen, not even allowing me to enter into the main menu.
In this case as-well the process will hang forever and the only way to make it stop is by stopping it from withing the Steam app.
steam-298110 GE-Proton8-6.log

Many reports on the game's ProtonDB page suggest switching to a Proton version equal or inferior to 6.3 as that's the patch that broke the game into the current situation it's in. Unfortunately the behavior is virtually identical to the one of 8.0-2 as it can't pass from the Ubisoft connect launcher properly and it crashes before creating the game window.
steam-298110 6.3-8.log

I have also added a log with proton experimental (timestamped) but it behaves exactly like Proton 8.0-2.
steam-298110 Proton Experimental 21 Jul 2023.log

Currently for me it's impossible to play this game in any way shape or form, if I can be useful for any ulterior testing let me know and I will provide all the help I can!
Thank you in advance! :)

[agurenko]

@kisak-valve did you managed to get it working by any chance? Just got it on a sale and it's dead stuck for me and I'm also using RX 7900 XTX.

[Plarpoon]

For the sake of the argument, I also did not give up on this, my hardware is still the same and I tried a couple of months ago again. It still won't boot.

[agurenko]

For the sake of the argument, I also did not give up on this, my hardware is still the same and I tried a couple of months ago again. It still won't boot.

It weird though, there are quite a few fairly recent report on ProtonDB that it works, both nVidia and AMD users, but well, tough luck then I guess

[Plarpoon]

I mean.. yeah.. but if possible I would definitely like to play that one, it's the one that is missing out from my collection of Far Crys

[makeclean]

I'll be honest the following did it 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%

[agurenko]

I'll be honest the following did it 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%

I've been trying all of those yesterday with no luck. I'm using 5900X, so it's 12C/24T, I've also tried

WINE_CPU_TOPOLOGY=4:0,2,12,14 %command%

Still hangs at the loading screen:

[simifor]

@agurenko Assuming you're using proton stable, could you try using Proton 9 (currently in beta) and see if you still have the issue? You might need to delete the game's prefix.

[agurenko]

@agurenko Assuming you're using proton stable, could you try using Proton 9 (currently in beta) and see if you still have the issue? You might need to delete the game's prefix.

I've tried all versions from 6 to 9, Experimental and GE both 8 and 9, so no dice

[intelligentgaming]

I can confirm that the game no-longer works using Steam Proton Experimental or 9.0.1.

Ubuntu 24.04 - Nvidia RTX 3080 - 535.171.04

Clicking the Play button should initially start the installation process for Ubisoft Connect, but this never happens, I see the processing Vulkan shaders and then it returns to the Play button again.

Native Steam package with the game installed on an Ext4 formatted partition.

[intelligentgaming]

OK, so I managed to get it working.

Install UbisoftConnectInstaller.exe as a non-steam game using Proton Experimental.

Then launch the game again, and it correctly will launch Ubisoft Connect and load the game.

You still need to disable the Steam Overlay however.

[Plarpoon]

Thank you a lot @intelligentgaming, not only your solution fixed Far Cry 4 for me but also allowed me to solve another issue I had on Mass Effect LE! 🎉

[rdlf4]

I remember a week ago I used to play "Outpost Master" non stop because I could quickly reload the stage and assess my approaches, it was fun.
But then, I progressed further in the game. After making the Arena available and conquering the first fortress in the game, every-single-outpost now takes forever and then some to load. Quick reloads are gone, they take additional time, ruining the fun. I've tried Glorious Eggroll, Proton, Linux runtime, you name it but apparently this is something I can't workarond.

I guess you can't have too much fun with an Ubisoft game.