Proton
Proton copied to clipboard
ValveSoftware
Far Cry 4 (298110)
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:
- [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.
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.
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.
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.
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.
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.
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.
With Proton 4.2-4 the game working with follow issues:
- No sound after first cutscene, this issue can be workarounded:
$ WINEPREFIX=~/.steam/steam/steamapps/compatdata/298110/pfx/ winecfgand set Windows Version to Windows XP
$ WINEPREFIX=~/.steam/steam/steamapps/compatdata/298110/pfx/ winetricks xact
-
Appearing on random locations rectangular dimming in game:
How it looks in dynamic I demonstrate on Youtube video: https://youtu.be/6O_LUtFXP58 -
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.
-
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
The game is crashes when I enable renderdoc (ENABLE_VULKAN_RENDERDOC_CAPTURE=1) for record a trace.
To fix flickering foliage, install/compile dxvk 1.4.4 or less for now. Related: https://github.com/doitsujin/dxvk/issues/1257
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.
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
I've bisected the flickering issue, it's caused by this commit in DXVK.
Have you reported it to DXVK?
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 (https://github.com/doitsujin/dxvk/issues/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 https://github.com/doitsujin/dxvk/issues/1257#issuecomment-558790007)
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.
Far Cry 4 launches from UPlay then immediately crashes
Issue transferred from https://github.com/ValveSoftware/Proton/issues/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.
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.
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.
Hello @ChaosBlades, the link you posted is tainted by legally problematic workaround(s) and has been removed.
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.
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.
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
I have been, just tested it again with the latest version. No change on the issue. Also just tested with Resizable BAR disabled. I can see plenty of people reporting they are using official versions of Proton without issue as well.
Edit: Also for clarity all my other UPlay games work fine. Several Assassin Creed games, Watch Dogs, etc. So definitely an issue specific to Far Cry 4.
I'm in the exact same boat as you @ChaosBlades I've got an Nvidia system, Farcry 5 works no problem, Farcry 4 refuses to launch.
I have finally got this game to launch on something. I am now fairly confident this is some kind of hardware specific issue. I installed ChimeraOS 33 on my living room PC and the game works without issue. I then install ChimeraOS 33 on my desktop PC that I have been having this issue on and just like with every single other distro I tried it will not launch. Here is the hardware breakdown on both systems.
Living Room PC (Works) CPU: AMD 5800X RAM 32GB DDR4 Mobo: ASUS TUF GAMING X570-PLUS (WI-FI) GPU: Nvidia GTX 1660 Super Storage: PCI 3.0 NVMe SSD
Desktop PC (Does Not Launch) CPU: AMD 5950X RAM: 32GB DDR4 Mobo: ASUS ROG Crosshair VIII Dark Hero (X570) GPU: AMD 6900XT Storage: PCI 3.0 NVMe SSD
Based on my research I can not find anyone reporting this game to work on any CPU that has more than 12 cores 24 thread. Every reference to this game not working with a CPU model listed is reporting they have a 5950X that I am able to find.
@makeclean What CPU do you have?
I went into the BIOS and limited the CPU to 1 CCD (8 core 16 thread).... Game Launches!
That is the issue, it is some kind of core count limitation.
Now that we have identified the issue can we get a developer to look into this? Let me know if you need any logs or anything from me. I did post a log back in Sept of 2021 but if that isn't enough let me know.
I'll also update my report on protondb to reflect this issue.
Does it work if you launch the game with WINED3D? I have already made a dxvk issue since i noticed i got stuck in the pre company logos loading screen 1/2 times with dxvk, but not with WINED3D. The game have apparently been finicky with dxvk in the past.
I added PROTON_USE_WINED3D=1 %command% to the launch options and no it does not launch. Same result as before.