Compatibility Report

If you change the BELauncher.ini file to have the 64bit exe set to GRB_vulkan.exe instead of GRB.exe it will launch, so that's one workaround for now.

Additionally: it has the same bug as God of War where the RAM spikes up to ~14GB and then it will hard crash, and at times reboot the Steam Deck too. https://github.com/ValveSoftware/Proton/issues/5511#issuecomment-1399504207. I'll try to get a log file of the crash the next time I play it and add it in here.

GRB_vulkan.exe

nice tip, works here now with proton-GE 7-47 or experimental (bleeding Edge), but with 30 or less fps and window set to 1280x720, even if I set to full screen don't catch my monitor resolution, if someone know how to fix it please help!!!!

System Information

• GPU: AMD Radeon 7900XTX
• Driver/LLVM version: Mesa 23.0-git/15.0.7
• Kernel version: 6.3-rc5
• Link to full system information report as gist
• Proton version: experimental-bleeding-edge-7.0-34062

steam-2231380-dx11-experimental-bleeding-edge-7.0-34062.log
steam-2231380-vulkan-experimental-bleeding-edge-7.0-34062.log

Symptoms

At the launch game pop's "DirectX error" even if Vulkan was selected in the launcher.

Replying to https://github.com/ValveSoftware/Proton/issues/6471#issuecomment-1401441959

get the tip from @LiamDawe above, game will starts,but here with resolution bug only 1280x720

@LiamDawe 's tip worked for me as well, but I used grb_upp_vulkan.exe, although I have no idea what the difference is.

GRB_vulkan.exe

nice tip, works here now with proton-GE 7-47 or experimental (bleeding Edge), but with 30 or less fps and window set to 1280x720, even if I set to full screen don't catch my monitor resolution, if someone know how to fix it please help!!!!

I'm having this bug too where I can't full screen the game. The workaround by OP allows to successfully launch the game indeed.

The only workaround for the fullscreening issue I've found is to window the game and then use your Window Manager (Kwin Wayland here) to then fullscreen the window. However it still gives out a bastardized resolution. Maybe Gamescope can help here, I've yet to test.

I'm able to start the game setting GRB_vulkan.exe in BELauncher.ini, but sway just opens a 720p black screen with nothing else loading. I need to use gamescope to actually get in-game, but in-game resolution is locked to 720p.

There's a fix noted in my article on the resolution issue. It seems it's just an issue in the Vulkan version as a whole, as it does it even on Windows to some people. So it's a game issue, not specifically a Proton problem I think.

I have done the GRB_vulcan.exe change, but breakpoint still doesn't seem to be running. Seems to do the start up procedure right, then gets stuck on the steam loading screen, all the while steam thinks it is running, any ideas?

You spelt vulkan wrong.

I have done the GRB_vulcan.exe change, but breakpoint still doesn't seem to be running. Seems to do the start up procedure right, then gets stuck on the steam loading screen, all the while steam thinks it is running, any ideas?

remove BE.launher.ini, reapair the game, do it again, it happen to me.

There's a fix noted in my article on the resolution issue. It seems it's just an issue in the Vulkan version as a whole, as it does it even on Windows to some people. So it's a game issue, not specifically a Proton problem I think.

Right buttom on windows border more acrion/fullscreen on kde will put in fullscreen with a little black border.

Either in full screen mode the the resolution is fixed limited to 1280x720 and the screen is NOT switched to the target resolution OR you can use normal window mode and resize to full screen but with just < 10 FPS on a 4k display.

So, the games is currently completly unuseable on Linux. Given the fact, that the older GR wildlands worked fine, it shows how badly programmed the game is. Possibly UBI did it by intention to prevent Linux gaming, which is as bad as bad programming.

Can anyone make their mic detected in game for push-to-talk?

Anybody using KDE plasma can get a plasmoid to toggle the visibility of the panel, and to set a keybind to hide the border of the window. After doing the GRB.ini edit that is described on the GamingOnLinux article, you can hide the panel, maximize the window of the game, then use the keybind to hide the border. The game will run fine though not at 1920x1080, because there is a black border still visible, and the in game settings report a 1920x1065 resolution. Ideally you wouldn't use any workspace corner actions on plasma because the mouse has escaped for me a few times and activated one of those actions. I tried going full screen with it on i3 and sway as well, i3 wouldn't maximize it at all, sway showed a black 720p box. DWM did the same as sway.

Also ubisoft said they dropped post launch support for the game, which sucks, considering the issue may be a vulkan specific problem. I'm no programmer so I'm not sure how it works but I've seen people say vulkan doesn't work right on windows either. Maybe there's some sort of proton fix that can be applied to the game to interact differently with the compositor but right now a janky 1920x1065 experience is the best we can get.
EDIT: 1920x1065 for people with 1920x1080 displays, higher resolutions would most likely just some pixels will be replaced from the bottom of the screen with a black bar

Thanks for reporting this. This is caused by the nvapi hack in DXVK. I submitted a fix, please see https://github.com/doitsujin/dxvk/pull/3309. You can also create a dxvk.conf to disable it.

Thanks for reporting this. This is caused by the nvapi hack in DXVK. I submitted a fix, please see https://github.com/doitsujin/dxvk/pull/3309. You can create a dxvk.conf to disable it.

Hopefully that fixes the directx error for AMD GPU's as well

It will not.
I will check that out here later

And what about the vulkan version? The patch does only disable it for the directx version (GRB.exe), since the vulkan version uses a different binary GRB_vulkan.exe.

dxvk doesn't touch natively Vulkan games.
Whats the issue with that one?

I think the main issue for most users is the fact that one can not run in fullscreen.

For AMD GPUs, amd_ags_x64.dll needs to be set to use built-in. And then add an agsSetDisplayMode() stub. Please wait for future Proton releases.

0001-amd_ags_x64-Stub-agsSetDisplayMode.txt
0002-wine.inf-Set-amd_ags_x64-to-built-in-for-Ghost-Recon-B.txt

Switched to Proton Experimental and it just works in Fullscreen. Thanks a lot :+1:

Switched to Proton Experimental and it finally works in Fullscreen. Thanks a lot :+1:

Can confirm, performance is great too. Proton devs deserve tons of praise

Can anyone make their mic detected in game for push-to-talk?

I am having the same issue as @DistantThunder. The microphone cannot be detected by the game in the menu and the VOIP options are greyed out.

I can confirm that the microphone can be detected by other games. In addition, I have also run the game via GeForce Now on the Steam Deck (which is running the game on a Windows based cloud server) and the microphone is picked up without any issue (so the issue occurs specifically when using the proton compatibility layer on Steam OS).

I am currently running the game in Proton Experimental and have tried other versions of Proton including GE, but unfortunately the problem persists.

Has anyone got any suggested fixes for microphone issues like this?

I have another problem after clear install

Same here

steam-2231380.zip

Hello, this game does not launch on my Intel Arc A380 system. After the initial small logo/game name window, the game itself does not pop up. This happens with both the DX11 and the Vulkan renderer. I tried Proton versions 7, 8, experimental and ge-custom (AUR). It also happens when using Ubisoft Connect standalone via Lutris.

When using the PROTON_USE_WINED3D env var, it launches fine when using DX11, but suffers from performance issues and graphical errors in the game itself, like missing terrain, but that is to be expect I guess. PROTON_USE_WINED3D with Vulkan behaves the same as without the env var.

I am running Arch Linux. I tried the linux-zen kernel and a customized linux-tkg kernel, as well as stable mesa and mesa-git. The result is the same with all of those combinations. It is worth mentioning that my system and installation has been working fine with most other games I have tried and played the last 1-2 months, so I don't believe it is an issue with configuration or missing drivers/packages.

Attached are the Proton logs with DX11 and Vulkan without PROTON_USE_WINED3D, as well as one "working" DX11 log with PROTON_USE_WINED3D:

steam-2231380_DX11.log
steam-2231380_VULKAN.log
steam-2231380_WINED3D.log

Are there any other places I should make issue reports as well, like the DXVK and mesa repos?

Thanks!

Hello @Vinjul1704, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report. Also, please note what system Vulkan loader version you're using.

I suspect you're using the 1.3.273 release of the Vulkan loader which has a regression and is fixed in 1.3.274.

Thank you. I am using vulkan-icd-loader version 1.3.274-1.

Steam Runtime Diagnostics: https://gist.github.com/Vinjul1704/35b9a462ed28e02c6387ac3b7cfce4cf

Thanks, can you check how the game behaves with a current point release of mesa instead of a bleeding edge git commit?

The two details I'm seeing that hint in the direction of the video driver is warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7fd95f45e460: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/vulkan/4/libvulkan_intel.so + 0x65e460. telling us there was an access violation in mesa/ANV and MESA-INTEL: warning: cannot initialize blitter engine in the runtime diagnostics which is suspicious, but I haven't seen that warning before to know how significant it is.

Unfortunately it behaves the same.

Steam Runtime Diagnostics: https://gist.github.com/Vinjul1704/df8c8a5146cc26dfc3b75f4091ec37bc

Logs:

steam-2231380_DX11_MESASTABLE.log
steam-2231380_VULKAN_MESASTABLE.log
steam-2231380_WINED3D_MESASTABLE.log

Anyone else just completly unable to load into a game? it always crashes on the load screen

Just one question: anyone have tried Ghost War mode (PVP)? Because it seems it depends on Battleye funcionality, and the few times I tried before, it won't connect.

steam-2231380.zip

The game still not work with latest Proton Experimental.

Indeed it keeps bugging me about Uplay. I'm on Fedora 42 and I tried with default proton and with experimental. I also tried to install Ubisoft Connect using protontricks, but the bugger still complains about Uplay not being available. I know for a fact it worked in the past, but I can't recall exactly when.

For anyone wondering, the game broke on linux with steam bc ubisoft removed the installscript that installs ubisoft connect on first launch in an update post launch (see https://steamdb.info/patchnotes/12244108/ Removed – support/installscript.vdf )
This is an issue on windows and on linux but is less visible on windows since ubi connect install is shared while on linux its per game/proton prefix

I've unsuccessfully tried contacting ubisoft's support about this, but they simply closed my ticket for linux not being supported (also an issue on windows....)
I've recently tried contacting steam support about this with clear steps to fix this so i'm hopeful they will do something about it

This issue would be solved by rolling back depot 2231387 from the manifest 356052933198522110 to the manifest 8753060000816184451

Replying to https://github.com/ValveSoftware/Proton/issues/6471#issuecomment-3132664835

I've found you can still get this to work with the following launch options on Fedora 43 -

PROTON_ENABLE_WAYLAND=1 gamescope -W <displayWidth> -H <displayHight> -r <displayrefreshrate> -f -- %command%

Noting this does still need gamescope installed, but helps rolling back to an older version

With DX11, water looks bright and weird like this. I guess the workaround would be to switch to Vulkan, but it always crashes maybe after playing for 1h

@tommipontinen76 the first body of water I found doesn't look like that

Is every body of water broken to you? how do you get to that specific part? and what is your setup like? (cpu/gpu/driver version/proton version/game settings)

@tommipontinen76 the first body of water I found doesn't look like that

Is every body of water broken to you? how do you get to that specific part? and what is your setup like? (cpu/gpu/driver version/proton version/game settings)

Every part, i5-12400f, rtx 3070, latest nvidia driver, I used proton experimental

@tommipontinen76
this is on a nvidia 4060m and 590.48, both proton 10 and experimental. Latest doesn't mean much, because different distros have different packages and some lag behind others (that and nvidia also has a beta branch and a stable branch

Looks fine to me. If it really isn't location dependent, then it is unlikely to be a proton issue as it looks correct on my end.

Re: https://github.com/ValveSoftware/Proton/issues/6471#issuecomment-4997618189

Here's some pictures:

This is what the game looks like on Windows:

Also I'm on Mesa 26.2.0-devel - my mistake.

dmesg (DX11 renderer)
amdgpu 0000:0a:00.0: ring gfx_0.0.0 timeout, signaled seq=142762504, emitted seq=142762506
amdgpu 0000:0a:00.0: Process GRB.exe pid 384779 thread dxvk-submit pid 384870
amdgpu 0000:0a:00.0: Starting gfx_0.0.0 ring reset
amdgpu 0000:0a:00.0: Ring gfx_0.0.0 reset failed
amdgpu 0000:0a:00.0: GPU reset begin!. Source: 1
amdgpu 0000:0a:00.0: [drm] ERROR Failed to initialize parser -125!
amdgpu 0000:0a:00.0: MES(1) failed to respond to msg=REMOVE_QUEUE
amdgpu 0000:0a:00.0: failed to unmap legacy queue
amdgpu 0000:0a:00.0: [gfxhub] page fault (src_id:0 ring:24 vmid:5 pasid:9754)
amdgpu 0000:0a:00.0: Process GRB.exe pid 384779 thread dxvk-submit pid 384870
amdgpu 0000:0a:00.0: in page starting at address 0x00000040f4024000 from client 10
amdgpu 0000:0a:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x00501431
amdgpu 0000:0a:00.0: Faulty UTCL2 client ID: SQC (data) (0xa)
amdgpu 0000:0a:00.0: PERMISSION_FAULTS: 0x3
amdgpu 0000:0a:00.0: MODE1 reset
amdgpu 0000:0a:00.0: VRAM is lost due to GPU reset!
amdgpu 0000:0a:00.0: GPU reset succeeded, trying to resume
Environment

• OS: Arch Linux (CachyOS), Wayland/KDE
• CPU: AMD Ryzen 9 5900XT (16C/32T)
• GPU: AMD RX 9060 XT (RDNA4, Navi 44)
• Mesa: 26.2.0-devel (git-584a0997c8)
• Kernel: 7.1.3-1-cachyos
• Proton: ProtonGE 11-1, Proton CachyOS (SLR and Native)
  Notes
• Vulkan renderer works fine. Only DX11 triggers this crash.
• Root cause reportedly Denuvo anti-tamper — DX11 path triggers GPU faults that don't occur on Vulkan.
• GPU recovers via MODE1 reset but VRAM is lost.
• Same crash pattern observed across multiple Proton versions.

---

AMDGPU Frametime Spikes (Anvil Engine)
Division 2 and GR Breakpoint have 500ms frametime spikes caused by amdgpu driver fence timeouts. This is a kernel bug, not a vkd3d-proton issue (vkd3d-proton#1956 (https://github.com/HansKristian-Work/vkd3d-proton/issues/1956) closed). Related kernel bug: Bugzilla #216645 (https://bugzilla.kernel.org/show_bug.cgi?id=216645) (Oct 2022, status NEW).
Workaround: udev power profile rule at /etc/udev/rules.d/30-amdgpu.rules:
KERNEL=="card1", SUBSYSTEM=="drm", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="manual", ATTR{device/pp_power_profile_mode}="1"

• 1 = 3D_FULL_SCREEN, 5 = COMPUTE (try if 1 doesn't help)
• Hot-reload without reboot: sudo udevadm trigger --name-match=/dev/dri/card1
• Check: cat /sys/class/drm/card1/device/pp_power_profile_mode | grep '*'
  Tested on RX 9060 XT (RDNA4). Related: drm/amd#1503 (https://gitlab.freedesktop.org/drm/amd/-/issues/1503), drm/amd#1850 (https://gitlab.freedesktop.org/drm/amd/-/issues/1850).