Proton 6.3-5
30579.865:00fc:0108:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFA, 01EDFEF8
30580.092:00fc:0104:fixme:winsock:server_ioctl_sock Unsupported ioctl 4004747b (device=4004 access=1 func=d1e method=3)
30580.092:00fc:0104:fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (SIO_IDEAL_SEND_BACKLOG_QUERY)
30610.918:00fc:0100:fixme:font:RemoveFontMemResourceEx (873942E9) stub

It freezes at the end of the loading bar:

My System:
Betriebssystem: openSUSE Tumbleweed 20210729
KDE-Plasma-Version: 5.22.4
KDE-Frameworks-Version: 5.84.0
Qt-Version: 5.15.2
Kernel-Version: 5.13.4-1-default (64-bit)
Grafik-Plattform: X11
Prozessoren: 12 × AMD Ryzen 5 3600 6-Core Processor
Speicher: 15,5 GiB Arbeitsspeicher
Grafikprozessor: NVIDIA GeForce GTX 1650/PCIe/SSE2

I'm using the latest driver for my GTX 1650
Downloaded the supported Script from Suse Community: https://www.opensuse-community.org/
https://www.nvidia.com/Download/driverResults.aspx/145182/en-us

https://pastebin.com/H2PLg3UV

Game does not even start anymore
Proton 6-3-8 Log:https://gist.github.com/McMarius11/0bbbdb6531f49234c5913f16494a9020

with ProtonGE EAC will pop up and freeze at the end.
https://gist.github.com/McMarius11/5cfec24bcd8f3d69196de7d696ffe494

OS: Manjaro Linux
KERNEL: 5.10.88-1-MANJARO
CPU: Intel Core i5-7600K @ 3.80GHz
GPU: NVIDIA GeForce GTX 1070
GPU DRIVER: NVIDIA 495.46
RAM: 24 GB

Any updates on EAC support for this game?

Issue with Easy Anti Cheat, game not work!

• GPU: RTX 3070
• Driver/LLVM version: nvidia 525.60.11
• KERNEL: 6.1.0-1-MANJARO
• Link to full system information report : https://gist.github.com/AceroRomano/8b44b8735407c4eb0130c1dfd12ead5d
• Proton version: Any version, experimental-bleeding-edge-7.0-31405-20221217
• Proton log: https://gist.github.com/AceroRomano/5cf187c99b62e1737eb06629b14cec9f

the devs add EAC support , it works pretty well, but i notice two issues with game

1. LODs system in game not work correctly
2. changing brightness not working in xorg and wayland

sys info - https://gist.github.com/koloved/e5e9ebde78c84383d87dedee54e4679b
logs - steam-594650.log

with RADV_DEBUG=nodcc nothing changes , the bug still there

In my case, game still won't start because of eac.
Tested with Proton GE 49, 42, Experimental 7.0 and 6.3.
Also tested it on the steam deck with same results.
steam-594650.log

Here are the parts which might be interesting:
897.849:0130:0134:trace:module:load_dll looking for L"EasyAntiCheat/easyanticheat_x64.dll" in L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\bin\win_x64;Z:/home/arne/.local/share/Steam/steamapps/common/Hunt Showdown;C:\windows\system32;C:\windows\system;C:\windows;C:\Program Files (x86)\Steam;C:\windows\system32;C:\windows;C:\windows\system32\"...
897.850:0130:0134:trace:module:get_load_order looking for L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll"
897.850:0130:0134:trace:module:get_load_order got hardcoded b for L"Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll", as the eac unix library is present
897.850:0130:0134:warn:module:find_builtin_dll cannot find builtin library for L"\??\Z:\home\arne\.local\share\Steam\steamapps\common\Hunt Showdown\EasyAntiCheat\easyanticheat_x64.dll"
897.850:0130:0134:warn:module:load_dll Failed to load module L"EasyAntiCheat/easyanticheat_x64.dll"; status=c0000135

@arne-fuchs hello! Did you install EAC from your library? EAC should be installed from library like any other games in steam

@koloved Yes I did installed it over steam
Edit: no I did not. Though you meant the game.

@koloved Thanks! It workes now. Will post performance results soon

Some areas looks a bit weird but overall it runs great especially with FSR enabled!

Edit: Setting graphics settings higher and vram target higher resolved the problem with the textures. It can be, that textures might still "pop" in.
Running on a RX 5700 XTX

@arne-fuchs set Video Memory usage target >90% and the bug fixed , nice! thanks!

I have the issue that I can't connect to any region. Hunt says it blocked some areas because of connection issues. So I can't play any online game
Found this in the logs:
1672.418:0130:027c:warn:seh:dispatch_exception Thread 027c renamed to "Network"

@arne-fuchs set Video Memory usage target >90% and the bug fixed , nice! thanks!

This doesn't fix the LOD/Texture loading issue for me. I've tried various combinations of Mem Usage target and graphical settings.

@kisak-valve Actually this original issue was solved because it was an EAC problem. But EAC support was enabled by Crytek 2 days ago. So, maybe it's better to close this old outdated issue and create a new one? I feel that it's kinda important to focus on fixing it as fast as possible to make this anticheat support as successful as possible.

I only have the issue with connection to regions, otherwise the game seems to mostly run fine:
Attaching log for debugging help
steam-594650.log

@WebsiteDeveloper You can work around that if you just join a party.

Hi,
Update regarding the online functionality, it seems it's a Debian related issue. Game works online, can start a match, the latency indicators are present on network region dialog, with Fedora 37 and Proton Experimental on the same hardware and internet connection.

Update 2: Solution for Debian found, it's related to ICMP sockets. Specifically for Debian, one needs to configure: net.ipv4.ping_group_range="0 1000", here 1000 is my current user gid.

Steps:

1. id (note the number after gid=, example gid=1000)
2. sudo sysctl -w net.ipv4.ping_group_range="0 1000" (changes the setting for runtime, temporary)

for persistent config, sudo /etc/sysctl.d/local.conf, put the line net.ipv4.ping_group_range="0 1000" there, save the file. After restarting your computer, check with sudo sysctl net.ipv4.ping_group_range, it should show the value configured.

1. start Steam normally and then launch the game, Region dialog should have latency indicators and colors and work normally. Starting an online match should also work OK.

Current Debian discussion about changing this setting: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027773
And Fedora 's default is: "net.ipv4.ping_group_range=0 2147483647"

Voodoo time!

@kisak-valve Maybe Steam could check and issue a console warning message regarding this setting, "your user is not in the net.ipv4.ping_group_range allowed groups, no ICMP functionality" ?

Compatibility Report

Hunt: Showdown (594650)

System Information

• GPU: RTX 3070 TI
• Driver/LLVM version: nvidia-525.89.02_1
• Kernel version: 6.1.14_1
• Full System Info Gist
• Proton version: Proton Experimental or 7.0-6 (and GE-Proton-49 and Proton 6.3 etc)

I confirm:

• [x] that I have checked whether there are updates for my system available.

steam-594650.log

Symptoms

Upon launching the game, it immediatly goes to a popup that says: Easy Anti-Cheat Hash Catalogue not found.

Troubleshooting steps already taken:

Reinstalled the game
Installed Proton EAC from steam library
Verified Gamefiles

Reproduction

Launch the game

Setting VRamUsage to 100 in steamapps/common/Hunt Showdown/user/profiles/default/attributes.xml seems to solve the LOD issue.

Source https://www.protondb.com/app/594650#wb666TbhAF

seems to solve the LOD issue.

@grego9
It's just postponed it a bit by adding 10% more VRAM. But generally it fixes nothing. Maybe on some setups with 6+ gb of VRAM it can make the issue not so painful but it is still there.

seems to solve the LOD issue.

@grego9 It's just postponed it a bit by adding 10% more VRAM. But generally it fixes nothing. Maybe on some setups with 6+ gb of VRAM it can make the issue not so painful but it is still there.

This matches up with my findings I'm running a GTX 1660 Super with 6GB VRAM and I've tried all the suggested fixes/tweaks.

Sometimes it takes a while to happen other times it happens as soon as you go into a building or traverse the map to a different compound.

It's a visual nightmare on my 1060 3GB

Can confirm excessive VRAM usage with Nvidia GTX 1660 Ti using driver 525.85.05. Game looks like TF2 running on Pentium 4.

Started happening to me after a system update the other night. https://pastebin.com/q6vJfrtT

It's the same issue that was actual from the start. But now it is reproducible on any gpu with any VRAM amount.
Here I was add the new info about the possible reasons: https://github.com/doitsujin/dxvk/issues/3265#issuecomment-1468879110

Seems like all LOD problems are fixed by the latest dxvk commits. Probably the only problem it has right now is the gamma slider.

Anyone else seem to have random issues with in game audio chat as well?

Seems like all LOD problems are fixed by the latest dxvk commits. Probably the only problem it has right now is the gamma slider.

Yep tested again last night for a few hours and no texture/LOD problems

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1452452118

It seems to be working for other users, anyone got any pointers what i might have to do?

Hi @larsgrah

Some basic steps:

• Make sure you don't have any other EAC workarounds, like for example entries in your /etc/hosts file etc.
• In Steam make sure you have Proton EAC Runtime and uninstall the game.
• With Steam closed (not running), delete the directories from your steamlib path: steamapps/compatdata/594650 and steamapps/Hunt Showdown if leftover.
• Then start Steam, install the game again, make sure it uses Proton 7.0-6 before starting it first time.
• If the game starts and you can not select a region or start a multiplayer game, make sure your group id range is in ping_group_range, see https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1446474166 above.

Probably the only problem it has right now is the gamma slider.

The gamma slider problem is much likely caused by CRYENGINE: https://docs.cryengine.com/display/CRYAUTOGEN/CONSOLEPREFIXR#AnchorRGAMMA

It changes the gamma at hardware-level only, not software-level. The option is called "r_gamma" in the game.cfg file.

Hi @SamPurple22

thanks for those steps. I have tried the following steps:

Made sure EAC runtime is installed. Uninstalled the game using steam closed steam, deleted /home/$USER/.steam/steam/steamapps/compatdata/594650.

Started steam again and downloaded the game. Unfortunately it has the same behaviour as before.

EDIT: It works when running steam through Conty, so i assume its something to do with my linux configuration. Though other than running voidlinux (no systemd) its pretty standart.

3 days ago the game ran like a charm on my Arch manjaro xfce4. Then I think there was an update like 2 days ago, and now it's 100% unplayable, the game opens and runs, no crashes or anything, but the framerate is literally 0.1, about 1 frame every 30 seconds. What happened??? I tried reinstalling, updating everything and nothing works.

fixed by running it in steam runtime instead of snap steam and resetting my user settings

Not sure what changed but since the steam beta UI update the game is crashing constantly regardless of what version of proton I use. I'll try to catch logs at some point but is anyone else experiencing this?
System info https://gist.github.com/Nicknakin/abdb32c637900f0618934cf9e7a5cc72

I updated to the beta Steam client and noticed right away hunt was crashing when opening the Steam Overlay with the following error

Wine C++ Runtime Library
(X
Assertion failed!
^ *
Program: Z:\home\luke\STEAM\SteamLibrary
\steamapps\common\Hunt Showdown bin
(win_x64\HuntGame.exe
File: ../src-wine/dls/winevulkan/loader_thunks.c
Line: 5275
Expression: "Istatus"
Press OK to exit the program, or Cancel to start
the Wine debugger.
OK
Cancel

I opened an issue here too https://github.com/ValveSoftware/steam-for-linux/issues/9426

Hello @LukeDearden, please temporarily opt out of Steam's client beta, 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.

Hi,

I can't get the system info from steam beta or not at the moment. Seems something with the AMD GPU is crashing when I try. very similar to this issue

https://github.com/ValveSoftware/steam-for-linux/issues/9267

EDIT:

Some addition info

OS: Fedora Linux 38 (Workstation Edition) x86_64
Kernel: 6.2.13-300.fc38.x86_64
Resolution: 1920x1080, 1920x1080
DE: GNOME 44.1
CPU: AMD Ryzen 5 5600X (12) @ 3.700GHz
GPU: AMD ATI Radeon RX 6600/6600 XT/6600M
Memory: 2636MiB / 15889MiB

EDIT:

OK I got sys info from the flatpak version of Steam without the crash

https://gist.github.com/LukeDearden/b704a9ddf729ca78417f7aeb43762448

EDIT:

Just to confirm I tried the beta again using the flatpak version of Steam and still get the same Hunt crash with the overlay

Similar story here, but different game:

System information: https://gist.github.com/zetxx/2dac69e8fa5b04c15a8795a8f64e90f9

i forced usage of RADV as per docs https://wiki.archlinux.org/title/Vulkan and everything is working ... even better :)

I made the same experience as @LukeDearden with the Steam beta client. Opted out immediately. But nevertheless, the game is making constant trouble on my system sadly:

Compatibility Report

Hunt: Showdown (594650)

System Information

• GPU: RTX 2060
• 2 displays
• Driver/LLVM version: 525.116.03
• Kernel version: 6.2.14-300.fsync.fc37.x86_64
• Gnome on Wayland
• Link to full system information report as Gist
• Proton version: Tried/using various since a while (Experimental, 8, 7, GE 8/7)

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-594650.log (Gnome on Wayland)
steam-594650.log (KDE on Wayland)

Symptoms

1. Game looses mouse focus frequently depending on the ingame action (could not reproduce this behaviour when using only one display).
2. Crashes repeatedly after some time playing when setting it to fullscreen mode (Steam client crashes then, too; friends list [on second display] closes often before crash appears).
   Update: Crashes now also with borderless fullscreen mode.
3. Seems to crash somehow "reliable" on alt-tabbing after some time, too, but have been avoiding this for now by switching to another virtual desktop.
4. Gamma slider not working (as already known).

Reproduction

Somewhat difficult.

• For 1 this happens mostly when acting heavily with mouse (to dodge shots/wiggle around for example).
• For 2 it's easy: change to fullscreen option, play some time, crash appears.
• For 3 same like for 2. Alt-tab a couple of times, play some time, crashes.
• 4 needs no work as already known to being related to Cryengine and workarounds do exist.

Tried to "debug" it on my own by looking up on the internet for some of the reported errors/warnings/fix me messages. Tried to workaround with using various Proton versions and variables; Protontricks and winecfg options; using gamescope, vkBasalt and ReShade for issue 1 and 4 but that introduces more/other issues. Even been using a custom script for disabling Gnome extensions, animations and notifications.

Next step I will install KDE alongside Gnome and see if that makes a change.
Went to Windows yesterday again to be able to play "safely" again but I do not want to do that!!!

Kind regards and many thanks to everyone who is involved in developing this stuff!! =)

The UI redesign seems to have been forced today, which means that I can no longer play the game.

The UI redesign seems to have been forced today, which means that I can no longer play the game.

Hi,

For me I can play but it it crashes as soon as I open the Steam Overlay. Disabling the Overlay is an option but it restricts inviting players to the game.

Is the game not launching now for you now or is it just crashing while trying to use the Steam Overlay?

Looking for some advice from @kisak-valve on how we can help troubleshoot this issue?

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1592415395

Currently I'm only able to launch the game at all using proton GE 7-54, anything newer is launching with a crash reported by another user above. Once the game is open, like you've said, interacting with the overlay in any way causes the game to crash. I've mitigated that since yesterday by just disabling the overlay and accepting party invites externally, but you can't send them with the overlay disabled. Otherwise even just playing the game normally I would experience random crashes without interacting with the overlay, which seems to have been fixed by disabling it.

On a potentially related note, since the UI beta went live a while ago the game has been absolutely destroying my computer on launch, no audio for >30 seconds, other applications become somewhat unresponsive, and I can't do anything about it but wait. This continued even after reverting from the beta back to the stable branch, so it doesn't seem to be tied to the UI rework specifically, but I'm not sure how I could go about figuring out what's wrong.

I also want to confirm crashes while interacting with steam overlay and random crashes well (not sure if it is completely random, for example one time it crashed when I pressed F12 which is the steam screenshot button). Problem with overlay isn't constant on my side. For example once it was reproduced constantly (I launched the game few times) but fixed when I reopened steam.
UPD: sometimes it crash purely random.

Steam Runtime System Info: https://gist.github.com/Nicknakin/922a6b0010e1ab50e3a200090272ba9a
System Info: https://gist.github.com/Nicknakin/ce0b269882b7fe3c20030ecfa4d7fd04
Game Log: https://gist.github.com/Nicknakin/52542b3185993e368dec1f0a974c522b

I had/have the crash as well.

Workaround:
Disabled smooth web scrolling, gpu accelerated rendering and hardware video decoding.
Pretty sure I should not have disabled all three but I don't want to bother trying which option did it.

After all - Steam overlay works and no crash so far.

I was able to resolve the crashing by having the proper drivers configured. I was running vulkan-radeon and lib32-amdvlk, so steam was using the amdvlk driver and the game was using the vulkan-radeon driver. Installed lib32-vulkan-radeon and removed lib32-amdvlk and the issue as stopped happening.

I was able to resolve the crashing by having the proper drivers configured. I was running vulkan-radeon and lib32-amdvlk, so steam was using the amdvlk driver and the game was using the vulkan-radeon driver. Installed lib32-vulkan-radeon and removed lib32-amdvlk and the issue as stopped happening.

Could you link to somewhere explaining this?
This exceeds my knowledge by far and also has some feat with it altering my system failing.

Nothing helps on my side. Overlay even works as expected when I boot the game for the first time. But once I close it and open it start crashing again.

runs without any issue, i can open and close the new steam overlay

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 5.15.117-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7600K CPU @ 3.80GHz
Memory: 23,4 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2

I was able to resolve the crashing by having the proper drivers configured. I was running vulkan-radeon and lib32-amdvlk, so steam was using the amdvlk driver and the game was using the vulkan-radeon driver. Installed lib32-vulkan-radeon and removed lib32-amdvlk and the issue as stopped happening.

This seems to have been a fluke, still having the crash with the correct drivers configured.

@Milliw it looks like you're using an RTX 2060. I was fixing my AMD graphics drivers so it shouldn't be something you need to deal with. However if you want to make sure you only have the necessary drivers installed I would reference the Nobara equivalent of the packages listed under "Install" on this page. https://wiki.archlinux.org/title/Vulkan

Hi what runs?

Some games have problems others don't

AMD CPU/GPU here
Running Manjaro KDE
Since the steam overlay update get random crashes, even when I do not open the overlay for some reason other times the overlay works without issues.

Error states:
File: ../src-wine/dlls/winevulkan/loader_thunks.c Line: 5396
Expression: "!status && vkQueuePresentKHR"
I have verified the issue mentioned by @Nicknakin in the comment 5 days ago is not my issue. Only radeon drivers are present.

@Milliw it looks like you're using an RTX 2060. I was fixing my AMD graphics drivers so it shouldn't be something you need to deal with. However if you want to make sure you only have the necessary drivers installed I would reference the Nobara equivalent of the packages listed under "Install" on this page. https://wiki.archlinux.org/title/Vulkan

I ran that card but now I am on AMD Radeon 5700.

Disabling gameoverlay fixed the crashes. It wont make you able to invite friends, but you can accept invites alt-tabbing to the chat window.

Not that it matters to most but not having the overlay enabled also breaks the ability to buy in-game DLC and currency (blood bonds, battlepass, etc.).

Just use "gamescope" and there will be no problems with the overlay.

Just use "gamescope" and there will be no problems with the overlay.

As in within the launch options?

Or using big picture mode.

Overlay issues have been resolved for me. Gamma slider still not working, the game is too dark indoors.

OS: Debian 12
KERNEL: 6.1.0-9-amd64
CPU: AMD Ryzen 5 1600
GPU: AMD Radeon RX 580 Series
GPU DRIVER: Mesa 22.3.6
RAM: 16 GB

              .o+`                   -------------- 
             `ooo/                   OS: Arch Linux x86_64 
            `+oooo:                  Host: B550M-ITX/ac 
           `+oooooo:                 Kernel: 6.4.3-arch1-1 
           -+oooooo+:                Uptime: 1 hour, 8 mins 
         `/:-:++oooo+:               Packages: 737 (pacman) 
        `/++++/+++++++:              Shell: bash 5.1.16 
       `/++++++++++++++:             Resolution: 2560x1440 
      `/+++ooooooooooooo/`           DE: Plasma 5.27.6 
     ./ooosssso++osssssso+`          WM: kwin 
    .oossssso-````/ossssss+`         Theme: [Plasma], Breeze [GTK2/3] 
   -osssssso.      :ssssssso.        Icons: [Plasma], breeze-dark [GTK2/3] 
  :osssssss/        osssso+++.       Terminal: konsole 
 /ossssssss/        +ssssooo/-       CPU: AMD Ryzen 5 5600G with Radeon Graphics (12) @ 3.900GHz 

/ossssso+/:- -:/+osssso+- GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series +sso+:- .-/+oso: Memory: 5729MiB / 27931MiB

                          I  have this same problem with Wine C++                                     

Or using big picture mode.

it works! Thank you!

Overlay issues have been resolved for me.

How?
For me it sometimes works and sometimes not, instantly crashing the game.

Gamma slider still not working, the game is too dark indoors.

I do use a workaround atm which is working 99% of the time. I call a shell script which runs gnome-gamma-tool/gnome-gamma-tool.py -y -d 0 -g 1.2 at launch and same command with 1.0 gamma at game stop. Maybe this can be useful for you.

@Milliw I use big picture mode as temporary workaround.
Also I noticed that on gnome it works bad because no tearing protocol support (increased input lag, no expected smoothness even on 100+ fps and 144hz screen). I use openbox session for gaming and it works much much better. In future I probably will switch to KDE because it's ok with tearing.

As a workaround for gamma settings you also can use vkBasalt with some color shaders.

This is the error I've got today after enabling Steam Overlay. Disabling it seems to be the only work around.

i'm getting the same error as above, turning on logging seems to make it hang without that popup showing up

the log file is 2.5GB
i've uploaded a truncated version
steam-594650_truncated.log

Or using big picture mode.

That just seems to result in my game saying "You must enable the steam overlay" when I press the invite friend button. Does anyone actually have the invite button working under AMD/Mesa drivers?

Okay, after playing around with this longer ... for me, if I use Proton 8, the game works fine (including the overlay and the invite system). If I use proton experimental, I get the !status crash when trying to invite someone.

That just seems to result in my game saying "You must enable the steam overlay" when I press the invite friend button. Does anyone actually have the invite button working under AMD/Mesa drivers?

Sometimes my game does this too, simply relaunching it usually fixes it.

7900 XTX + mesa-git

On the first start of the game it crashes with the error message above. Afterwards the game runs stable as long I do not quit Steam or restart the computer.
Switching to Big Picture Mode also solves the issue but the Steam overlay seems to work totally different.

My specs are:
OS: Freedesktop.org SDK 22.08 (Flatpak runtime)
KERNEL: 6.5.0-arch1-1
CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: AMD Radeon RX 6600 XT (navi23, LLVM 15.0.7, DRM 3.54, 6.5.0-arch1-1)
GPU DRIVER: 4.6 Mesa 23.1.4 (git-8b0202e4b4)RAM: 32 GB

Okay, after playing around with this longer ... for me, if I use Proton 8, the game works fine (including the overlay and the invite system). If I use proton experimental, I get the !status crash when trying to invite someone.

Could you please get a log of this crash using PROTON_LOG=1 %command% in the launch options? By default, log will be located here: ~/steam-594650.log.

Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

For what little it's worth: I see the exact same crash in MS Flight Simulator 2020 (in the installation manager, after hours and hours and hours of downloading). I suspect the Hunt Showdown crash may be easier to replicate!

Okay, after playing around with this longer ... for me, if I use Proton 8, the game works fine (including the overlay and the invite system). If I use proton experimental, I get the !status crash when trying to invite someone.

I can second this. Works fine with Proton 8.0.3.
Though I would be really interested, if this has some other downsides I am not aware of?!

@Milliw @DarkArc I am also on AMD/mesa drivers, and I cannot reproduce this crash. Could you please get a log of this crash using PROTON_LOG=1 %command% in the launch options? By default, log will be located here: ~/steam-594650.log.

Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

@Milliw @DarkArc I am also on AMD/mesa drivers, and I cannot reproduce this crash. Could you please get a log of this crash using PROTON_LOG=1 %command% in the launch options? By default, log will be located here: ~/steam-594650.log.

Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

I can reproduce this every time in Hunt Showdown by just trying to invite someone to a game. I'll get back to you with the log etc

@Milliw @DarkArc I am also on AMD/mesa drivers, and I cannot reproduce this crash. Could you please get a log of this crash using PROTON_LOG=1 %command% in the launch options? By default, log will be located here: ~/steam-594650.log.

Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

As written earlier, I do not get crashes anymore.
I changed from Proton 8.0.3 to experimental again and even with this, it does not crash anymore.
But I can't tell since when it is working because I disabled the overlay since the big rework.

So, after today's update I had an issue with the game not wanting to open on both Proton 8 and Proton Experimental... That seemed to have gone away on its own.

I'm now simply seeing "Please enable the Steam Overlay in Steam Settings" when I try to invite someone:

However... as you can see the steam overlay is indeed enabled:

Here's the system diagnostic info:
https://gist.github.com/DarkArc/1bdd000d05e740a00fa36c4061f7dc29

and the log:
steam-594650.log

Ah yeah. Of course. Now I got crashes again.

What changed:

1. Disabled fullscreen mouse capture with winecfg
2. Game got an update

Tried:

1. Revoked my changes with winecfg (didn't work either)
2. Tried different Proton versions. Even on 8.0.3 it crashes.

Tried to enable proton log aswell but NOW this does not trigger the crash dialogue like it did before BUT instead the game freezes with some weird glitch on the mouse cursor and the log seems to write endlessly. It stopped around 928 MB as I force closed the game.

EDIT:
Somehow I accidently invited someone on my friends list in one of my test runs. Interesting...

@Milliw @DarkArc I am also on AMD/mesa drivers, and I cannot reproduce this crash. Could you please get a log of this crash using PROTON_LOG=1 %command% in the launch options? By default, log will be located here: ~/steam-594650.log.
Please also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.

I can reproduce this every time in Hunt Showdown by just trying to invite someone to a game. I'll get back to you with the log etc

Here's a gist of my system info/diagnostics
https://gist.github.com/LukeDearden/6294ab1135229ccb3b0db172f63ae96a

If I add PROTON_LOG=1 %command% my game hangs on startup and the log file grows quickly (1gb a minute or something)

Tried to start the game with PROTON_LOG=1 %command% and opened the Steam Overlay. The game freezes and floods the logfile until I forced it to quit. I have truncated the file to the point where it repeats itself.
steam-594650.log

OS: Freedesktop.org SDK 23.08 (Flatpak runtime)
KERNEL: 6.5.5-arch1-1
CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: AMD Radeon RX 6600 XT (navi23, LLVM 16.0.6, DRM 3.54, 6.5.5-arch1-1)
GPU DRIVER: 4.6 Mesa 23.1.8 (git-4baea976bb)
RAM: 32 GB

I'm seeing a new issue of CryDescriptor plugin failed to load on a friend's Proton install (both stable and experimental) after the latest update. This has happened after the latest event update a few days ago and didn't previously happen. Searching the issue has not yielded anyone else having the issue.

The Proton log doesn't mention anything out of the ordinary. I've attached their game's run log in case someone has any idea what might be going on. Since this seems to be an issue directly related to the CryEngine I've additionally reached out on the HUNT subreddit to see if anyone else is experiencing this issue.

BackupNameAttachment=" Build(3210) 07 Oct 23 (12 23 36)"  -- used by backup system

Log Started at Sat Oct  7 12:23:36 2023 (UTC+1)
Built on Sep 26 2023 13:28:42
Running 64 bit Windows version
Command Line: "[hunt game folder]\bin\win_x64\HuntGame.exe" +online_account_client_settings live +online_websvc_skip_tls_cert_validation 1
Executable: [hunt game folder]\bin\win_x64\HuntGame.exe
FileVersion: 1.0.0.3210
ProductVersion: 1.0.0.3210
Project Hunt: Showdown
Using Project Folder [hunt game folder]
Using Engine Folder [hunt game folder]/
Using Asset Folder [hunt game folder]/game_hunt

Total number of logical processors: 6
Number of available logical processors: 6
Total number of system cores: 6
Number of cores available to process: 6

Processor 0:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

Processor 1:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

Processor 2:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

Processor 3:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

Processor 4:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

Processor 5:
  CPU: Intel Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Family: 6, Model: 14, Stepping: 10, FPU: On-Chip
  Features: FP16, SSE, SSE2, SSE3, SSE4.2, AVX, AVX2, FMA3

<11:23:37> <ThreadConfigInfo>: Thread profile loaded: "pc_Common" (%engine%/config/engine_core.thread_config)
<11:23:37> <ThreadConfigInfo>: [XML Parsing] Thread with name "Main" already loaded. Overriding with new configuration
<11:23:37> <ThreadConfigInfo>: [XML Parsing] Thread with name "RenderThread" already loaded. Overriding with new configuration
<11:23:37> <ThreadConfigInfo>: Thread profile loaded: "pc_6" (%engine%/config/engine_core.thread_config)
<11:23:37> UDR initialization
<11:23:37> Windows 10 64 bit (build 10.0.19043)
<11:23:37> System language: English
<11:23:37> Windows Directory: "C:\windows"
<11:23:37> Local time is 13:23:37 10/07/23, system running for 50 minutes
<11:23:37> 32042MB physical memory installed, 16721MB available, 134217727MB virtual memory installed, 47 percent of memory in use
<11:23:37> PageFile usage: 314MB, Working Set: 369MB, Peak PageFile usage: 314MB,
<11:23:37> Current display mode is 2560x1440x32, (Unknown graphics card)
<11:23:37> IBM enhanced (101/102-key) keyboard and 3+ button mouse installed
<11:23:37> --------------------------------------------------------------------------------
<11:23:37> Stream Engine Initialization
<11:23:37> BuildTime: Sep 26 2023 13:28:42
<11:23:37> Physics initialization
<11:23:37> <Audio>: AudioSystem initialization
<11:23:37> Loading plug-in CryUQS_Core
<11:23:37> Loading plug-in CryGamePlatform
<11:23:56> Messagebox: cap: Plug-in load failed!  text:Plugin load failed, could not find dynamic library CryGamePlatform!

<11:23:56> Renderer initialization
<11:23:56> Logging video adapters:
<11:23:56> - AMD Radeon RX 6950 XT (RADV NAVI21) (vendor = 0x1002, device = 0x73a5)
<11:23:56>   - Adapter index: 0
<11:23:56>   - Dedicated video memory: 16384 MB
<11:23:56>   - Feature level: D3D 11_1 (SM 5.x)
<11:23:56>   - Displays connected: yes
<11:23:56>   - Suitable rendering device: yes
<11:23:57> Active GPUs: 1
<11:23:57>  Renderer ColorBits: 32
<11:23:57>  Display Resolution: 2560x1440
<11:23:57>  Render Resolution: 2560x1440
<11:23:57>  Output Resolution: 2560x1440
<11:23:57>  Window State: Fullscreen Window
<11:23:58> [Renderer] A display device has been connected to the system
<11:23:58> Font initialization
<11:23:59> [net] Socket IO management: External [iocp], Internal [iocp]
<11:23:59> network hostname: [Their hostname]
<11:23:59> [Network Version]: RELEASE PURE CLIENT
<11:23:59> Time initialization
<11:23:59> Input initialization
<11:23:59> Initializing Animation System
<11:23:59> Init 3D Engine
<11:23:59> Script System Initialization
<11:23:59> Schematyc initialization
<11:23:59> Entity system initialization
<11:23:59> LiveCreate initialization
<11:23:59> Dynamic Response System initialization
<11:23:59> AI initialization
<11:23:59> Initializing AI System
<11:23:59> Initializing additional systems
<11:23:59> CControlledRandomizationManager was seeded with: 1337
<11:23:59> [Discord] Successfully initialized Steam API, user_id=[Their User ID] build_id=12288039
<11:23:59> [GamePlatform] Attempting to automatically set user preferred language 'english'
<11:24:00> Initializing default materials...
<11:24:00> =============================================================================
<11:24:00> *ERROR
<11:24:00> =============================================================================
<11:24:00> CryDescriptor plugin failed to load.
<11:24:00> Windows 10 64 bit (build 10.0.19043)
<11:24:00> System language: English
<11:24:00> Windows Directory: "C:\windows"
<11:24:00> Local time is 13:24:00 10/07/23, system running for 51 minutes
<11:24:00> 32042MB physical memory installed, 16034MB available, 134217727MB virtual memory installed, 49 percent of memory in use
<11:24:00> PageFile usage: 835MB, Working Set: 903MB, Peak PageFile usage: 835MB,
<11:24:00> Current display mode is 2560x1440x32, (Unknown graphics card)
<11:24:00> IBM enhanced (101/102-key) keyboard and 3+ button mouse installed
<11:24:00> --------------------------------------------------------------------------------
<11:24:00> CryAudioImplWwise.dll Used in module:668568 Allocations:6571
<11:24:00> CryUQS_Core.dll Used in module:17720 Allocations:355
<11:24:00> CryRenderD3D11.dll Used in module:35429040 Allocations:161550
<11:24:20> Messagebox: cap: CRYENGINE FATAL ERROR  text:CryDescriptor plugin failed to load.

I had a new crash when starting Hunt. Launching Hunt with the overlay disabled in the game properties.

The game launched and played fine after this. Normally this doesn't happen but the info might be useful.

Problem reporting title : wine64-preloader quit unexpectedly

ccpp-2023-10-08-10:38:08.527057-7708.zip

It also seems to freeze, when trying to go to the external store, to buy blood bounds. Not sure if this was previously the case.

The steam overlay seems to play a part in the crashes for me, it seemingly coincides with getting an achievement in one instance.

Here's a log from a crash trying to invite a friend (with overlay enabled)

steam-594650.log

So, I stumble over https://www.reddit.com/r/HuntShowdown/comments/14l6xtt/any_nonsteam_way_to_buy_blood_bonds/ so it seems like the overlay has been causing problems for some time.

But I was able to successfully buy blood bounds (for testing I assure you) using the big picture mode, using the same PC that did not work/freeze, when trying to do it normally.

Here is a log of the Steam overlay crash. I started the game, pressed Escape key to go directly to main menu after the initial startup credit, and opened the overlay, it instantly crashes consistently on multiple retry:

steam-594650.log

As soon as you try to open the overlay, you crash, with this WINE error popup (which itself can't be closed by clicking the button (We can see the taskbar because of my screenshot tool I opened twice and change settings to only screenshot one monitor).

@razzeee @Zorrototo Thank you for the logs! I've reported this ... unfortunately, intermittent steam overlay crashes are exceedingly hard to investigate and fix, but hopefully this will lead towards finding the bug and fixing it :)

@razzeee @Zorrototo Thank you for the logs! I've reported this ... unfortunately, intermittent steam overlay crashes are exceedingly hard to investigate and fix, but hopefully this will lead towards finding the bug and fixing it :)

Not too "what about me" but I'd like to note my issue above where the invite system doesn't work despite the steam overlay working... Just to make sure it's getting the visibility.

Maybe it's the same underlying issue manifesting slightly differently? It's reproducible every time last I checked.

unfortunately, intermittent steam overlay crashes are exceedingly hard to investigate and fix

I can assure you I currently have a 100% reproducibility rate. But I have to note that initially on my first launch and maybe one or two other subsequent launches, the game was working with the overlay not crashing the game, then something happened and now, on a new prefix or not, it is 100% reproducibility rate.. Could it be related to some cache somewhere?

unfortunately, intermittent steam overlay crashes are exceedingly hard to investigate and fix

I can assure you I currently have a 100% reproducibility rate. But I have to note that initially on my first launch and maybe one or two other subsequent launches, the game was working with the overlay not crashing the game, then something happened and now, on a new prefix or not, it is 100% reproducibility rate.. Could it be related to some cache somewhere?

I think I noted above reseting the steam overlay cache (in the like "properties" in steam for the game -- away from my computer) changed things for me.

Can you elaborate? none of your post talk about that.

Deleting the in game overlay data from the game properties doesn't help for the overlay instant crash.

Deleting the in game overlay data from the game properties doesn't help for the overlay instant crash.

Yeah this is what I was talking about. If it didn't make a difference for you, it may have been a fluke, but I remember it changing things for me... I think from a crash to the "please enable the steam overlay"

It's honestly been a rollercoaster trying to get the invite system to work since valve updated the overlay. I can't keep it straight

@razzeee @Zorrototo Thank you for the logs! I've reported this ... unfortunately, intermittent steam overlay crashes are exceedingly hard to investigate and fix, but hopefully this will lead towards finding the bug and fixing it :)

Not too "what about me" but I'd like to note my issue above where the invite system doesn't work despite the steam overlay working... Just to make sure it's getting the visibility.

Maybe it's the same underlying issue manifesting slightly differently? It's reproducible every time last I checked.

I lumped it under the same issue because it is all trouble with the steam overlay (rather than Proton/Wine) ... if you are getting different behavior (eg not a full game crash), then uploading a log is worthwhile for devs to ponder. My hypothesis for now is that it is all related, which fits with the inconsistencies that folks are reporting (and that we have seen locally where the game will crash when using the invite system, and then "magically fix itself" and stop crashing).... I think it is safe to say there is at least one race condition involved here :(

Also, if you have a date/steam client version (eg were you on the beta branch or not) where the overlay suddenly got worse, it can't hurt to mention the specific date. Unfortunately, I suspect that it could easily be some timing change rather than an actual regression that was introduced, but a regression scenario would likely be easier to hunt down.

I lumped it under the same issue because it is all trouble with the steam overlay (rather than Proton/Wine) ... if you are getting different behavior (eg not a full game crash), then uploading a log is worthwhile for devs to ponder. My hypothesis for now is that it is all related, which fits with the inconsistencies that folks are reporting (and that we have seen locally where the game will crash when using the invite system, and then "magically fix itself" and stop crashing).... I think it is safe to say there is at least one race condition involved here :(

I already did a while ago https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1747988561

Also, if you have a date/steam client version (eg were you on the beta branch or not) where the overlay suddenly got worse, it can't hurt to mention the specific date. Unfortunately, I suspect that it could easily be some timing change rather than an actual regression that was introduced, but a regression scenario would likely be easier to hunt down.

All of these issues started when valve released the new steam UI and steam overlay. There were people reporting the issues here prior to launch but they unfortunately were never resolved.

I'm also seeing a rare system crash (it freezes completly, so I usually restart the system - to get back into the ongoing round)

I'm not sure, but the log reads, like my internet connection was lost and it doesn't fail safe in that case?

steam-594650_crash.log

the game does not working anymore, disconnecting every time when i tried to play (to menu)

See: https://www.reddit.com/r/linux_gaming/comments/17wtqu1/hunt_showdown_not_working_anymore/
And this: https://steamdb.info/depot/594651/history/?changeid=M:8890193140935823212

They updated some EAC files

See: https://www.reddit.com/r/linux_gaming/comments/17wtqu1/hunt_showdown_not_working_anymore/ And this: https://steamdb.info/depot/594651/history/?changeid=M:8890193140935823212

They updated some EAC files

Seems like they retried whatever they did in the 12th of October update which had the same effect for me.

FWIW

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1816951990

If I receive any further updates from Crytek support to my inbox, I will follow up with additional screenshots on here and the Discord server.

sad face

That is expected as they never supported Steam Deck or Linux in general.

It's back working, crytek announced it about an hour ago. I've also played a round without problems.

Nice, will do games tonight... just to confirm it works... :D

It appears this game is unfortunately impacted by #5794 which means the Steam overlay no longer works.

It appears this game is unfortunately impacted by #5794 which means the Steam overlay no longer works.

Looks like it is also the reason why the game now is crashing sometimes after volume change notification in Gnome (previously it was crashing for me when I used overlay).

It appears this game is unfortunately impacted by #5794 which means the Steam overlay no longer works.

Looks like it is also the reason why the game now is crashing sometimes after volume change notification in Gnome (previously it was crashing for me when I used overlay).

Might be helpful to grab a log of that

@seroperson what you quoted is not causing any crashes, so I don't see how it's connected. I also tried to trigger the bug you mentioned, muting and unmuting via the keyboard with hunt in the foreground in the main menu. I pressed the button a 50 ish times and it did not crash.

@seroperson what you quoted is not causing any crashes, so I don't see how it's connected. I also tried to trigger the bug you mentioned, muting and unmuting via the keyboard with hunt in the foreground in the main menu. I pressed the button a 50 ish times and it did not crash.

I will attach all the logs a little bit later

edit: It has been fixed automatically somehow; I haven't noticed it for a while now.

It appears this game is unfortunately impacted by #5794 which means the Steam overlay no longer works.

Looks like there is no way to invite friends at all? Or are there some workarounds?

It appears this game is unfortunately impacted by #5794 which means the Steam overlay no longer works.

Looks like there is no way to invite friends at all? Or are there some workarounds?

I think it works on the steamdeck, not sure if that qualifies as a workaround

@an9949an @razzeee
Does the workaround with using Steam Big Picture Mode not work anymore?
Haven't tested lately since I let me invite from my m8s using Windows.

@Milliw no, that's brokend as mentioned above, since they moved to the new eac and that issue linked above

@Milliw no, that's brokend as mentioned above, since they moved to the new eac and that issue linked above

Oh. I didn't notice that this was impacted as well.
The only thing that is left as a workaround is by using gamescope I guess. But besides reading frequently that it works (or at least has worked) it did never for me or at least introduce other issues.
Or is this also broken now and I didn't notice it, too? :D

EDIT:
Just tried and can't run the game with gamescope at all. Even no proton log gets created.... idk idk

Gamescope is broken on Nvidia couple latest driver release I think currently. But yeah I think Gamescope could be a potential workaround for the Steam overlay and the impossible invitation at the moment.

//EDIT: I will try to install an older Gamescope version from the AUR and test if it work (for sure currently it doesn't work on Manjaro because of Nvidia drivers.

//EDIT2: I did not have it to work properly it blocks at the start before the menu, it stays a black screen and it doesn't even show the startup credits at all. gamescope-git work with Nvidia 535.

I have fedora + nvidia laptop. I was able to run gamescope but with huge performance issues.
Also I have manjaro + amd desktop. I was not able to run gamescope at all. I tried 2 different versions, also even compiled the git master, all of them crashed with the different errors. I am not sure what was wrong, maybe something on my or manjaro side.

I have done some diagnosing on this issue using Ubuntu 23.10 (as gamescope is not available on 22.04 LTS) with the official Steam deb package, Fedora Silverblue 39 with the unofficial Flatpak package from Flathub and the Valve Steam Deck.

Here are my current notes in working to diagnose this and attempting to restore the overlay:

Proposed Workarounds:

• gamescope

  • This restores the Steam overlay's connection to the game, however the ability to invite friends is still borked and not restored using gamescope.
  • You are able to purchase the in-game premium currency and access other resources linked to Steam, however.

• Big Picture Mode

  • This is currently borked and does not function as a workaround to the overlay bug.

Tested Configurations:

• Official Steam .deb

  • Affected by overlay issue, easiest to link into gamescope if installed from the official repo.

• Steam Flatpak

  • Affected by overlay issue, gamescope can be installed from Flathub but requires a community/unsupported repackaging of Proton (that is outdated) or Proton-GE (that is outdated and unofficial) from Flathub which do not contain the pressure-vessel sandbox feature. I was not able to get this version of gamescope to work.

• Valve Steam Deck

  • In Steam Deck UI mode, NOT affected by overlay issue.
    • Full access is available from inviting other players to purchasing premium in-game currency.
  • In Steam Deck Desktop mode, affected by overlay issue.

My current theory is that after Steam launches the game executable which launches EAC, or the EAC executable launches the game executable, the Steam overlay hooks into EAC and closes before the game launches therefore removing the overlay from Hunt.

Just stumbled on this issue also. I managed to make gamescope work on nvidia with downgrading to version 3.12.5.
I can see the steam overlay ingame now, but the problem is still same. Can't invite friends. It thinks the Overlay is not enabled.

A friend of mine on Windows couldn't invite me yesterday, even him couldn't invite so there are issues anyway in this game invite system. He didn't have the error message about the Steam overlay though, just it wasn't working when he was trying to invite me. Not sure if this issue on Windows is common, but it was not the first time for him that we had the issue and canceled our play session (we usually have a third friend on Windows too creating the lobby).

A friend of mine on Windows couldn't invite me yesterday

It's something different from the issue we have on linux I guess.

Yes, Just pointing out this game invite system is already half broken on Windows.

The issue here is that there is no Steam overlay, so there is no invite system AT ALL as it 100% relies on the in game Steam overlay (which is totally idiotic, it restrains a lot who is able to invite, and forces you to enable the ingame Steam overlay).

Yes, Just pointing out this game invite system is already half broken on Windows.

The issue here is that there is no Steam overlay, so there is no invite system AT ALL as it 100% relies on the in game Steam overlay (which is totally idiotic, it restrains a lot who is able to invite, and forces you to enable the ingame Steam overlay).

It's worth noting Crytek is working on a new UI for the spring 2024 update. This may be resolved by that.

Yes, Just pointing out this game invite system is already half broken on Windows.

The issue here is that there is no Steam overlay, so there is no invite system AT ALL as it 100% relies on the in game Steam overlay (which is totally idiotic, it restrains a lot who is able to invite, and forces you to enable the ingame Steam overlay).

Well the overlay hooks correctly to the game when you use gamescope, but the invite still doesn't work. Its like missing some mechanisms to call the steam overaly. Game still thinks overlay is not there, even though i can open the overlay with the shortcut key steam has.

Does anyone have Steam Deck? It works on steam deck right? and steam deck also uses gamescope i think. I dont understand how it works there and not on general linux distros.

I think the Deck also uses the other Steam UI so maybe here lies the difference with the normal Steam UI.

Paul Gofman said it works on proton-experimental Bleeding Edge branch.
And what do you know... Just tested and I can invite friends!!
no need for gamescope either.
Happy days!

NICE! Will test and report back!

i tried with proton-experimental Bleeding Edge, the game won't launch

i tried with proton-experimental Bleeding Edge, the game won't launch

PROTON_LOG=1 %command% then i guess. Or try verifying files just in case

Works without issues here with RTX 3080 and 535.43.20 (vulkan dev drivers)

Can confirm, overlay works fine with that on AMD too

If you dont want constant bleeding edge updates you can copy the bleeding edge proton folder
put it into ~/.local/share/Steam/compatibilitytools.d

get a compatibilitytool.vdf file from Proton-GE folders for example and copy that into the same proton-experimental copy thats in
compatibilitytools.d and just edit that file to give a different name, so its nicely listed on steam as separate entry.
then switch the official proton-experimental back to normal branch

Same here, game just doesn't create the window properly, process is started but it doesn't create the window. Maybe it requires Steam BETA too?

Same here, game just doesn't create the window properly, process is started but it doesn't create the window. Maybe it requires Steam BETA too?

disable mangohud
seems it doesnt want to launch with mangohud enabled for some reason

I don't have MangoHud enabled for this game. I have GameMode though. I tried a fresh prefix and it didn't help, will update when I find what's causing an issue but I doubt it is GameMode.

Nvidia 445 here.

//EDIT: removed all Launch options, and verified Proton Experimental files, game properly launches, and I can invite friend in game! Great! Thanks to whoever patched it.

//EDIT 2: yep seems like it is GameMode that creates an issue on my side.

I had to disable gamemode to get it running with proton bleeding edge. Mangohud works

For me, it doesn't work even if I do disable gamemode and use bleeding edge. :/

With Proton Experimental [bleeding-edge] the overlay works as it should. I am able to invite people out of the game. With Proton 8.0-4 the overlay does not work but I am able to tab out and accept invites. I am using Arch Linux with GNOME 45.2.

OS: Freedesktop SDK 23.08 (Flatpak runtime)
KERNEL: 6.6.7-arch1-1
CPU: AMD Ryzen 7 5800X3D 8-Core
GPU: AMD Radeon RX 7700 XT (radeonsi, navi32, LLVM 17.0.6, DRM 3.54, 6.6.7-arch1-1)
GPU DRIVER: 4.6 Mesa 23.3.0 (git-1fbdd37d4c)
RAM: 32 GB

With Proton Experimental Bleeding Edge, inviting works but it seems like using any wrappers causes the game to hang for me after the anticheat's splash screen. The game reads my SSD like crazy and does nothing with the following launch args:
mangohud %command%
gamemoderun %command%
LD_PRELOAD="$LD_PRELOAD:/usr/\$LIB/libgamemodeauto.so.0" %command%

However for some strange reason mangohud works with the MANGOHUD=1 env var set like this:
MANGOHUD=1 %command%

Steam (Runtime)
KDE Plasma
OS: Arch
KERNEL: 6.6.7-zen1-1-zen
CPU: AMD Ryzen 7 4800H
GPU: Nvidia GTX 1660 TI
GPU DRIVER: 545.29.06 (AUR: nvidia-beta-dkms)
RAM: 32 GB

Indeed, any wrapper blocks the game from actually creating its window. I will have to test, but if I recall correctly, I think the overlay opens in the EAC splashscreen when you add a wrapper to startup command line, maybe it is related to the issue..

The launch failure with mangohud (and hopefully gamemode) should be fixed with the most recent bleeding-edge (thanks to @gofman again :D)

@ThisNekoGuy When you say "this doesn't work", is this any regressive behavior vs non-bleeding-edge Experimental? I'm not sure exactly what is failing for you.

@alasky17 What I meant was that, from Proton-8.0-4 to experimental bleeding-edge, attempting to use gamemode would prevent the game window from appearing; so, we appear to still be on the same page given what you said about mangohud possibly at least working

Can confirm, mangohud and gamemoderun wrappers work now with the new experimental bleeding edge update.

I have had a very strange issue for a long time and want to ask if somebody saw something like this.
Sometimes average FPS becomes ~30% lower and GPU usage becomes ~70% into the places it was constant 100% all the time. For example on the shooting range: I just load, do nothing, look at the exact same point. In the good case I see 116 fps, in the bad case I see ~85 fps. It happens periodically. For example, last month it worked perfectly. But now it runs bad. Previously I also had bad and good periods.

I have no idea what it relates to. Maybe upgrade of some system components, or update of hunt itself, or even something hardware related (but I did a bunch of stuff to exclude it).

My system: MSI laptop, fedora 38, intel i5 10500h, 32gb ram, rtx 3050 mobile. I use clear openbox session for gaming (but issue reproduced on any session).

There is the things I tried to do with no luck:

1. Installed other distro (on manjaro I saw the same behavior).
2. Checked cpu frequencies to exclude throttling. Cpu frequencies ok and same in both cases.
3. Disabled hyper threading, c-states and speed shift
4. Checked RAM frequency, timings and result bandwidth and latency. Bandwidth and latency same in both cases.
5. Tried different proton versions.
6. Tried different kernels.
7. Tried to tune kernel params based on archwiki
8. Disabled zram and swap
9. Disabled all vulnerability mitigations
10. Disabled steam overlay
11. Played with dxvk configuration (I don't know to much, just tried to enable/disable different things)
12. Checked other games to indirectly exclude hardware issues. I used Sea of Thieves because it can work with high FPS (120-140) and high cpu usage on my system which is more or less similar to the Hunt system load scenario. And it works fine.

So, I have no idea whats going on and why nobody report this. Maybe it's some issue that happens only on laptops with hybrid graphics.

Here is the log of bad scenario.
steam-594650.log

I also have FPS dips on Hunt, when it happens I also have sound issues like it crackle a bit and it is almost like on/off repeatedly multiple times a second, and when FPS goes back to 60 sound comes back OK. I guess it is the game itself.

Watch the VRAM usage, it might be that too.

I don't think I ever had that with hunt currently at 170 hours on linux amd.

What I have is very rare random freezes. Maybe once a week?

@Zorrototo The issue I described is completely different. In my case FPS becomes constantly lower CPU limited. If I look at Hunt HUD I see that MainThread time limits the total frame time. Also I am sure that it isn't a VRAM issue because VRAM usage is always under 100%. In the case of the shooting range it is much lower. Also if you play with 60 fps limit you will probably never see the issue I'm talking about. On my 10500h it's ~115 (gpu limited) in the good case and ~85 (cpu limited) in the bad case.

@razzeee Very strange indeed. Random freezes are something different, I also saw it sometimes.
Maybe my issue is something related to the hybrid nvidia graphics. Also it's possible to just not notice it if you are not too sensitive to the framerate changes and input lag.

The launch failure with mangohud (and hopefully gamemode) should be fixed with the most recent bleeding-edge (thanks to @gofman again :D)

@ThisNekoGuy When you say "this doesn't work", is this any regressive behavior vs non-bleeding-edge Experimental? I'm not sure exactly what is failing for you.

Overlay works now with regular Proton Experimental.
But I am not able to view player profiles. If I click on "open profile" it just opens the built in web browser with the default web page.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1869679614

Hm, I actually yesterday did see the player profile after clicking ingame
on profile option. It opened window which was blank few seconds then
properly loaded player's profile. This is on Fedora 38, Proton
experimental (bleeding-edge), and steam client 1702079146. Also my GPU is
AMD 6800 XT if that matters.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1870115580

https://github.com/ValveSoftware/steam-for-linux/issues/9386#issuecomment-1869454737

I found that not having Steam maximised and instead running in a Window seems to let you view profiles and prevents the blank store page

Wow! It certainly is case for me, I have Steam window docked right on main
stream (thus covering only right half of the screen).

On Wed, Dec 27, 2023 at 10:31 AM Luke Dearden @.***>
wrote:

Hm, I actually yesterday did see the player profile after clicking ingame
on profile option. It opened window which was blank few seconds then
properly loaded player's profile. This is on Fedora 38, Proton experimental
(bleeding-edge), and steam client 1702079146. Also my GPU is AMD 6800 XT if
that matters.
… <#m_-5489254772222406298_>
On Tue, Dec 26, 2023 at 6:29 PM Milliw @.> wrote: The launch failure
with mangohud (and hopefully gamemode) should be fixed with the most recent
bleeding-edge (thanks to @gofman https://github.com/gofman
https://github.com/gofman https://github.com/gofman again :D)
@ThisNekoGuy https://github.com/ThisNekoGuy
https://github.com/ThisNekoGuy https://github.com/ThisNekoGuy When you
say "this doesn't work", is this any regressive behavior vs
non-bleeding-edge Experimental? I'm not sure exactly what is failing for
you. Overlay works now with regular Proton Experimental. But I am not able
to view player profiles. If I click on "open profile" it just opens the
built in web browser with the default web page. — Reply to this email
directly, view it on GitHub <#3898 (comment)
https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1869679614>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFU45T556L6HZUN2JPXZL3YLMCRDAVCNFSM4NHQYMDKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHE3DOOJWGE2A
https://github.com/notifications/unsubscribe-auth/AAFU45T556L6HZUN2JPXZL3YLMCRDAVCNFSM4NHQYMDKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHE3DOOJWGE2A
. You are receiving this because you were mentioned.Message ID: @.>

ValveSoftware/steam-for-linux#9386 (comment)
https://github.com/ValveSoftware/steam-for-linux/issues/9386#issuecomment-1869454737

I found that not having Steam maximised and instead running in a Window
seems to let you view profiles and prevents the blank store page

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1870118551,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFU45SRMXSBC7HP7NM6RC3YLPTFLAVCNFSM4NHQYMDKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGAYTCOBVGUYQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Trying to map & { } ( to keys in game, but the button presses don't get recognized, so I can't map them in the settings. This works fine on windows due to my latest tests. Similar buttons work and also get shown normally in the menu/ingame.

Edit: Proton-GE doesn't help with this problem

2. changing brightness not working in xorg and wayland

I can confirm this is still an issue. One of the biggest for me as it's a major disadvantage compared to people that can see properly.

1. changing brightness not working in xorg and wayland

I can confirm this is still an issue. One of the biggest for me as it's a major disadvantage compared to people that can see properly.

Just setup VKBasalt with some gamma on it, that's what I do for it and dark and darker since my IPS monitor sucks for darks.

1. changing brightness not working in xorg and wayland

I can confirm this is still an issue. One of the biggest for me as it's a major disadvantage compared to people that can see properly.

Just setup VKBasalt with some gamma on it, that's what I do for it and dark and darker since my IPS monitor sucks for darks.

How exactly are you doing that? And I'm not so sure the game would support that action. They prevent matchmaking with ReShade, and this isn't very different than that after looking into it. Anyways I gave it an attempt and this game in particular I could not get to work with my vkBasalt.conf. I just wanna increase my gamma to the point where I see the logo above the gamma slider in game.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1963027155

As far as I know VKBasalt is fine, as it doesn't have access to a lot of the data that was being abused with reshade, and additionally, it doesn't have any modified DLL's present in the game folder it runs ontop of the game similar to something like Mangohud. I just used a global configuration, the only thing is it doesn't effect brightness when your out of the game, as it isn't properly detected as 3D yet. So in the main menu or settings it won't work, but once your in a game it works great! Try just using the default config file with a simple toggle key located in /home/.config/vkBasalt. You will need to download the reshade shaders, I personally use the tonemap one with the following config file:

toggleKey = Home
depthCapture = off
reshadeTexturePath = "/home/.local/share/reshade/Textures/"
reshadeIncludePath = "/home/.local/share/reshade/Shaders/"

effects=tonemap

tonemap=/home/.local/share/reshade/Shaders/Tonemap.fx
Gamma=0.8

If this isn't allowed though, please hunt devs clarify this. I assumed its fine since unlike reshade its impossible to see through walls or smoke or darkness since it doesn't have depth 3d data like reshade does, all it can do is act system gamma or recoloring.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1968927126

So, my issue was I thought reshade would work with only the Tonemap.fx file. I needed the base reshade files still. Thanks anyhow for your response. It's good to know I don't need to worry about it being considered some sort of cheat.

Replying to [#3898 (comment)](https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1968927126)

So, my issue was I thought reshade would work with only the Tonemap.fx file. I needed the base reshade files still. Thanks anyhow for your response. It's good to know I don't need to worry about it being considered some sort of cheat.

No problem, BTW while I'm sure enough to use it myself it's possible for something to happen, just like its possible for being banned just by using Linux so use at your own discretion, but it works quite differently to reshade so it should be safe IMO.

To be fair you are less likely to being banned using Proton than touching shaders and/or manipulating the game thing in memory and all.

Game don't have connection to the servers on kubuntu 24.04 after the clean installation (I checked 2 times on 2 different machines) with any proton version. It loads just fine but never shows the ping of the servers.
I can't enter the match, but if somebody else invite me I can join and play without any issues.

If I run steam from the terminal I see this:

[libprotobuf ERROR D:\Perforce\FRWP1LUXIANG_bootstrap\protobuf\3.17.3\src\google\protobuf\wire_format_lite.cc:577] String field 'FP.Hunt.LocaleInfo.system_country' contains invalid UTF-8 data when serializing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.

P.S. with manjaro on the same pc it works just fine

UPD: fixed by sudo sysctl -w net.ipv4.ping_group_range="0 2147483647", solution found here.
For some reason kubuntu 24.04 has ping_group_range value 1 0. On fedora default values is 0 2147483647.

System Information

• GPU: RX 6600
• Driver/LLVM version: Mesa 24.0.7 / LLVM 17.0.6
• Kernel version: 6.6.32_1
• Link to full system information report as Gist
• Proton version: 9.0-1

I confirm:

• [x] that I have checked whether there are updates for my system available.

Symptoms

Upon launching the game, I'm greeted by the greeter, followed by a black screen with the ingame mouse cursor. Eventually the following window pops up, and upon clicking the OK button the game either closes itself or lingers in the background until it's closed from the Steam client.

steam-594650.log

Reproduction

Proton Experimental exhibits the same behaviour.

Experiencing a crashing issue on Fedora 40 using Proton 9.0-1 with the 6.9.7 kernel, and also with the 6.6.37 longterm kernel from kwizart's COPR repo.

Hardware details:

• AMD Ryzen 3600XT
• Nvidia 3060ti (on Wayland session with proprietary 555.58.02 drivers)
• Fedora 40 (Kernels 6.9.7, 6.6.37 LTS)
• 32GB RAM

Possibly this is related to the Wayland session and Nvidia drivers? Haven't had a chance to test on Xorg yet. Crashing does not occur on Xorg GNOME session. Proton Experimental does not seem to solve the problem and the crashing can still be observed when using the proprietary drivers with Wayland in GNOME.

Crashes with the following critical error, pressing either button causes the game to force itself closed:

Editing to add:

It seems as though this is very likely related to an overzealous consumption of VRAM. All crashes seem to occur once the VRAM of the card is fully saturated; perhaps the overhead of DXVK + XWayland result in this crash where it does not occur on XOrg alone, and it may not be intrinsically related to the Nvidia beta drivers (but is probably down to the driver in no small degree). For the time being, telling Hunt to target only 70% (or even 80%) of the total available VRAM in the graphics options seems to prevent this crash.

The Hunt Showdown 1896 update is available on Steam now.

Although the game is still in maintenance until later today it looks like there's going to be problems running this with Proton

On Windows you can launch the game and get the splashscreen and a connection failed message in the new UI.

On Linux you just get a blank screen

Could be Easy Anti-Cheat related :/

After the update the game fails to launch and I can see there are memory dumps in the game files. From what I can tell the game tries to take a screenshot and fails, hence the crash.
I've reached out to the devs, awaiting their response.

crycrash_error.log
Game.log

can confirm this issue with latest version, friend on windows is still downloading to test if same issue happens however on linux currently it is crashing and black screen. Tried changing proton versions, x11 and wayland, gamescope none worked likely eac related?

Same behavior here. Using Proton Experimental and Proton Hotfix, the game shows a splash screen, opens a black window and closes after approx. 30 seconds of 100% CPU usage on one core.

Logs:

• game.log
• crycrash_error.log

I get the same screenshot error @TakinaLisa wrote about

friends windows download completed and they are now in game able to play, this is 100% linux specific.

There are some windows people describing the same issue tho...

Can someone on Windows post their USER/Game.log?

Can someone on Windows post their USER/Game.log?

do you want a working or non working windows log?

Can someone on Windows post their USER/Game.log?

do you want a working or non working windows log?

Preferably working Windows log, I want to cross-check it with my failed launch log on Linux

Can someone on Windows post their USER/Game.log?

do you want a working or non working windows log?

Preferably working Windows log, I want to cross-check it with my failed launch log on Linux

Game.log
@TakinaLisa here you are

As per Yuerino's request, here's a fully verbosed log, it says it has issues loading *.pak files
Game.log

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2291175673

Mine cuts off just before "Discovered layout comb", so I guess the Warnings when loading *.pak files might be connected to it

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2291195091

Can confirm, mine also cuts off before that point.

Arch 6.10.4-arch2-1
i5-12600K & RTX 3070Ti
plasmax11

Having a look at the verbose log it seems like its trying to access the pak files through home/user/.local/share/Steam/steamapps/common/HuntShowdown/ instead of home/user/.local/share/Steam/steamapps/common/Hunt Showdown 1896/

Having a look at the verbose log it seems like its trying to access the pak files through home/user/.local/share/Steam/steamapps/common/HuntShowdown/ instead of home/user/.local/share/Steam/steamapps/common/Hunt Showdown 1896/

I tried to move the game files into a directory with no spacebars in it, but it changed nothing. I have my game installed in "Hunt Showdown 1896" folder now and same results.

Can someone post a working Windows USER/Game.log with "+log_verbosity 4 +log_WriteToFileVerbosity 4 +sys_dump_type 3" launch options?

I noticed that the game tries to fetch the .pak-files from the .../Engine/-folder. It is called .../engine/, tho. Changing it to be the capitalized Engine doesn't change anything. Just for the sake of it, I also made all the .pak-files have chmod 777, which also didn't change anything.

I noticed that the game tries to fetch the .pak-files from the .../Engine/-folder. It is called .../engine/, tho. Changing it to be the capitalized Engine doesn't change anything. Just for the sake of it, I also made all the .pak-files have chmod 777, which also didn't change anything.

I tried the same to the USER/user folder but it looks like the game falls back to lower case names if upper/camel case names are not found.

User donated Windows verbosed log, notice how assets here load correctly:
game-1.log.txt

As it runs in WINE the case doesn't matter. I'm updating now, and the update is worth the whole game current size, in such case I would recommend to just reinstall the whole game instead of updating 56GB worth of files. Steam update isn't perfect and often for such huge updates there are failures.

//EDIT: by reinstalling you have a 68GB download instead of a 56GB update. Safer in my opinion.
Also recreating a new Proton prefix would be recommended.

As it runs in WINE the case doesn't matter. I'm updating now, and the update is worth the whole game current size, in such case I would recommend to just reinstall the whole game instead of updating 56GB worth of files. Steam update isn't perfect and often for such huge updates there are failures.

I did this 2h ago and still have the same issue. Only thing that really changed was the folder name inside .../common/. I uninstalled and removed the remaining files manually, before reinstalling.

Just realised, Crytek said they will be using DirectStorage in this version of Hunt. Considering there are asset loading issues maybe here's the culprit?

Just realised, Crytek said they will be using DirectStorage in this version of Hunt. Considering there are asset loading issues maybe here's the culprit?

hmm that's an interesting theory, it could also explain why some users aren't able to launch on windows as they might not have gen3 nvme hardware or have it installed to another storage device. this is assuming my quick 1 minute google search about what it is, is correct..

Only thing I can see is the screenshot error. But that seems to be after some sort of other error occurs but the logs are inconclusive. How can I help by contributing? Log file? Should I try anything else?

Can someone post a working Windows USER/Game.log with "+log_verbosity 4 +log_WriteToFileVerbosity 4 +sys_dump_type 3" launch options?

Log from the win10 x64
game.log

Just realised, Crytek said they will be using DirectStorage in this version of Hunt. Considering there are asset loading issues maybe here's the culprit?

hmm that's an interesting theory, it could also explain why some users aren't able to launch on windows as they might not have gen3 nvme hardware or have it installed to another storage device. this is assuming my quick 1 minute google search about what it is, is correct..

I tried to run Hunt off an USB 3.0 stick on a different Windows PC and it launched, so DirectStorage theory is either false, or Hunt has a fallback for it but is not using it on Linux/Proton.

Can someone post a working Windows USER/Game.log with "+log_verbosity 4 +log_WriteToFileVerbosity 4 +sys_dump_type 3" launch options?

Log from the win10 x64 game.log

<16:23:59> DX12: SwapChain supports tearing

I don't have that line in my logs, maybe Hunt fails to create a SwapChain?

Here is my log, the game starts and i see the ingame mouse and after the black screen it closes.

https://gist.github.com/McMarius11/d0b16b80f068bab982eabbac4f6799cf#file-steam-594650-log

Game Log tells me
<17:38:39> Taking a screen shot
<17:38:39> Failed to take a screen shot even before starting!

Operating System: Manjaro Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.6.44-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 62,4 GiB of RAM
Graphics Processor: AMD Radeon RX 7800 XT
Manufacturer: ASRock
Product Name: B650E PG-ITX WiFi

Can someone post a working Windows USER/Game.log with "+log_verbosity 4 +log_WriteToFileVerbosity 4 +sys_dump_type 3" launch options?
game.log

Here's my logs from a successful launch on Windows, let me know if you need anything else

Just to make you aware, there's no additional link on your comment @YoSoyMuzzy

Did anybody try with Nvidia driver 560.31.02 BETA ? Heard that users have black screen with old driver on Windows.

Did somebody try with Nvidia driver 560.31.02 BETA ? Heard that smdy had black screen with old driver on Windows.

Yes, I'm running 560.31.02 and have the same black screen issue.

Just to make you aware, there's no additional link on your comment @YoSoyMuzzy

I screwed up the comment but I just double checked. The quoted file is my logs but just in case, here it is again.
game.log

So current progress recap,

• Both AMD & Nvidia GPUs are affected (not sure about Intel cards) so issue is vendor agnostic and with the game itself.
• The Direct Storage theory isn't right as it isn't integrated into the game yet per this video from Crytek: https://www.youtube.com/watch?v=hpIimnVGUbw&t=129s
• Appears to affect official Proton, both Experimental & Stable 9.0.
• Unofficial forks like GE-Proton also affected, so no workaround at this time.
• Easy AntiCheat is not the cause either, as it successfully loads and would present a different error.

I haven't tested extensively, but launching with Proton versions 9 through 3, only 4 had different results, where not even EAC started.

I saw that the test server had a few updates today so I gave it a try and it launches past the splash screen but I'm not sure if its running the new engine/update etc but its something work taking note of I guess

I saw that the test server had a few updates today so I gave it a try and it launches past the splash screen but I'm not sure if its running the new engine/update etc but its something work taking note of I guess

test build is a pre-update version. test serves are shut down anyway right now.

Game shows a black screen and closes after a minute or two.

• Proton Experimental
• Garuda Linux x86_64
• Linux 6.10.4-zen2-1-zen
• AMD Ryzen 9 7900X
• NVIDIA GeForce RTX 4090 nvidia-dkms 555.58.02

Proton Log: steam-594650.log
Game's Custom Logger: crycrash_error.log

⚠️⚠️⚠️

People who are giving game.log, this is not the correct file to be providing. Please follow Valve's instructions on using launch options: PROTON_LOG=1 %command% thank you. This log is critical, then provide other logs.

Anyone attempt removing the shaders folder?

Anyone attempt removing the shaders folder?

I did a clean reinstall, didn't help.

The universally reproducible crash on game start should hopefully be fixed in the just updated Proton Experimental ([bleeding-edge] branch (experimental-bleeding-edge-9.0-112786-20240815-p569828-wdcc9ab-d02d8fa-v89f640).

Not sure if there are further issues in game or not.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2292200971

same issue for me

• AMD Ryzen 7 5800x
• AMD Radeon RX 6800xt
• Archlinux (Linux 6.10.4-zen2-1-zen)
• KDE Plasma 6.1.4 (Wayland)

steam-594650.log

The universally reproducible crash on game start should hopefully be fixed in the just updated Proton Experimental ([bleeding-edge] branch (experimental-bleeding-edge-9.0-112786-20240815-p569828-wdcc9ab-d02d8fa-v89f640).

Not sure if there are further issues in game or not.

Eh, the initially observed issue is understood and should be fixed in Experimental [bleeding-edge] branch now, so probably not much use in posting more confirmations. It would be interesting to check with that [bleeding-edge] if there are more issues seen deeper in game.

[bleeding-edge] branch is available to select in Proton Experimental tool's properties, Betas tab. Proton Experimental should be selected as Compatibility tool in game's properties. Also, if Steam is running already, best to restart to make sure the just updated version is picked up.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2292225435

sorry - you managed to post your comment before i was finished with mine.. ;)

Starts perfectly using the bleeding edge branch. Thanks a lot! :tada:

So just for information, is it: https://github.com/ValveSoftware/Proton/commit/569828dc8c18bf67ab746065b0e0ce48513a5d4a that fixed it ? Or the submodules update ?

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2292225435

I can confirm that Proton Experimental, bleeding edge, build ID: 15386549 has solved the issue. The game loaded through just fine, and was allowing me to navigate properly. Current proton experimental not in the beta (at least on my machine) appears to be build id: 15306265

So just for information, is it: 569828d that fixed it ? Or the submodules update ?

https://github.com/doitsujin/dxvk/commit/02d8fa593b45390a72d1bc43bc5ddb46d7ee469f

I would like to add why this thread is being looked at. The gamma slider in game does not work.

I've just played a whole game on Proton experimental with the most recent bleeding-edge branch build and everything works fine, big thanks to everyone that contributed in fixing the issues that came up by the recent update!

When is the fix expected to be in the main proton experimental branch?

Can confirm it working, there are some oddities with assets popping in and out on first render. But I will guess those will be fixed by the shader cache.

I would like to add why this thread is being looked at. The gamma slider in game does not work.

I guess you know, but it never did. There was a reason, but I think I will get it wrong, without searching for it.

Experimental [bleedin

how would I install it?

https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

Im having a weird issue with post processing where if I put it above the minimum, i get a rainbow effect in the top half of my screen.

For people who wonder what to do:
Enter your Library, search for Proton, find Proton Experimental (Bleeding edge)
Right-click Proton, properties, Betas, Beta Participation - Select Bleeding Edge 8
Click update on Proton Experimental
Right-click Hunt, properties, Compatibility - Select Proton Experimental

Im having a weird issue with post processing where if I put it above the minimum, i get a rainbow effect in the top half of my screen.

Christmas lights effect? Had this too, restart. But otherwise game is extremely laggy and unplayable for me on 3080

Im having a weird issue with post processing where if I put it above the minimum, i get a rainbow effect in the top half of my screen.

Christmas lights effect? Had this too, restart. But otherwise game is extremely laggy and unplayable for me on 3080

It reminded me of oil on water. I've only had one issue, in the last game I played as we were running to extract, my frame rate dropped to about 10. If I looked at the ground it shot up to 120. I've been playing Solo survivor too with little issues. I'd highly recommend going into the shooting range and messing with settings.
3080ti btw.

Was facing a black screen on launch. Even Bleeding Edge 8 did not work. I had to use "bleeding-edge - latest and untested dxvk, vk3d-proton..."

First launch crashed on the splash screen, my next attempt ran amazingly well. The game ran at 100-160fps. Was able to play half a game and then suddenly while just running along, my game completely froze. Could still hear Discord for a few seconds and then the display crashed and I was logged out to my login screen.

I didn't have proton logs enabled at the time, but here is the relevant journalctl error log for the crash, if it is of any help.
hunt_journalctl.log

• ArchOS
• AMD Radeon RX 6750 XT
• Wayland / Hyprland

Same issue here as devinjc213
Bleeding Edge 8 did not work, "bleeding-edge - latest and untested dxvk, vkd3d-proton and wine changes; backup your prefixes before using"... did.

No issues so far. Framerate seems good, no visual glitches.

OS: Nobara Linux 40 (KDE Plasma) x86_64
Kernel: 6.10.2-200.fsync.fc40.x86_64
Resolution: 2560x1440
DE: Plasma 6.1.3
WM: kwin
CPU: AMD Ryzen 5 5600 (12) @ 4.468GHz
GPU: AMD ATI Radeon RX 7700 XT / 7800 XT

Can confirm it working, there are some oddities with assets popping in and out on first render. But I will guess those will be fixed by the shader cache.

I would like to add why this thread is being looked at. The gamma slider in game does not work.

I guess you know, but it never did. There was a reason, but I think I will get it wrong, without searching for it.

assets popping is present on windows, too, so that is not and environment issue.

Im having a weird issue with post processing where if I put it above the minimum, i get a rainbow effect in the top half of my screen.

Experienced the same. Setting Post Processing to at least Very High made it disappear for me.

In my case I can get rid from rainbow by setting Post-Process quality to Low.

I had some stability issues too. In general it runs fine with bleeding edge, but it can happen that the game freezes.
Had it once in 4 games.
Would be nice if someone would provide an log if that happens.
May be fixed if it comes to the experimental branch though.

I heard from a Hunt streamer I watch that his game (on Windows) crashes every now and then too, especially when opening the map.

For people who wonder what to do: Enter your Library, search for Proton, find Proton Experimental (Bleeding edge) Right-click Proton, properties, Betas, Beta Participation - Select Bleeding Edge 8 Click update on Proton Experimental Right-click Hunt, properties, Compatibility - Select Proton Experimental

Small correction. If you never selected any beta for Proton Experimental, it will not have remark [bleeding-edge], so it's just Proton Experimental.

Seems to work on Mint 21.2 + 1060M, but only launched and started shooting range yet.

I heard from a Hunt streamer I watch that his game (on Windows) crashes every now and then too, especially when opening the map.

Ah okay I see. Then it is general instability.
So I guess from wine side there is not much to do anymore for now.

As @davernos described,
"bleeding-edge - latest and untested dxvk, vkd3d-proton and wine changes; backup your prefixes before using"
works fine after one fix:
I had Christmas lights on the top half of my screen.
After setting Post-Process Quality to "Very High" it disappeared.

Game runs now smooth as butter. A lot better than on my Dual Boot Windows 10, which i used yesterday, where i had more frame drops and inconsistencies.

I played 2 Soul Survivor and 2 Bounty Hunts now on Linux.

On both Windows and Linux, some assets take a few miliseconds before they appear (Throwing Axe e.g.).

System Info:
CPU: AMD Ryzen 5600x
GPU: Nvidia RTX 4070Ti
OS: CachyOS
Kernel: Linux 6.10.5-2-cachyos
GPU Driver: Nvidia Proprietary 560.31.02

For people who wonder what to do: Enter your Library, search for Proton, find Proton Experimental (Bleeding edge) Right-click Proton, properties, Betas, Beta Participation - Select Bleeding Edge 8 Click update on Proton Experimental Right-click Hunt, properties, Compatibility - Select Proton Experimental

Just to be clear, these instructions are wrong. Do not select bleeding-edge-8.0, select bleeding-edge

Just to be clear, these instructions are wrong. Do not select bleeding-edge-8.0, select bleeding-edge

True, bleeding-edge-8.0 is just the last "bleeding-edge" existed on Proton 8 lifecycle and is never updated, the new stuff goes to just "bleeding-edge" which is dev branch, totally untested.

I had some stability issues too. In general it runs fine with bleeding edge, but it can happen that the game freezes. Had it once in 4 games. Would be nice if someone would provide an log if that happens. May be fixed if it comes to the experimental branch though.

It's not linux problem. Servers feel bad right now. Me and my mates (on windows) have lags and frame drops at the same time.

I still can't get it to work. I click play and after a moment the Hunt initializing window appears and then disappears. Nothing more.

Here's the proton log:

steam-594650.log

Do the basics:

• Make sure system is fully up to date
• Delete the prefix ~/.local/share/Steam/steamapps/compatdata/594650/ (//EDIT: or wherever you have your library for this game)
• Reboot
• Start Steam, verify the game files
• Start the game

I'm experiencing a game breaking bug where my fps drops to single digits within seconds after a banish. Distance to the banish doesn't matter, or who started it. Sometimes it happens with a few seconds late, sometimes immediately. The only 'fix' I've been able to come up with is restart the game and reconnect, which naturally has resulted in many losses due to having to afk. It doesn't happen for the roaming boss, only compound bosses.

System Info:
CPU: AMD Ryzen 7 7700x
GPU: Nvidia RTX 3070
OS: Kubuntu 24.04
Kernel: 6.8.0-40-generic (64-bit)
GPU Driver: Nvidia Proprietary 555.58.02 (no 560 listed in ubuntu-drivers list)
RAM: 62 GiB
Graphics platform: X11
Proton: Experimental

Things I've tried:
Verifying game files, deleting prefix, turning my graphics settings all the way up and all the way down. Updated from nvidia 550 to 555. Currently reinstalling the game.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2295348015

I have the same issue. Temporary fix for me was to set all graphics to as low as possible. I can play this way and I don't get the drop to 10fps after a banish.

I'm experiencing a game breaking bug where my fps drops to single digits within seconds after a banish. Distance to the banish doesn't matter, or who started it. Sometimes it happens with a few seconds late, sometimes immediately. The only 'fix' I've been able to come up with is restart the game and reconnect, which naturally has resulted in many losses due to having to afk. It doesn't happen for the roaming boss, only compound bosses.

That also happens on windows and should be a known issue at least did i heard it from a few streamers. My game also freezes sometimes when a banish is going on and i open the map. I also need to restart and reconnect.

I'd highly recommend going into the shooting range and messing with settings. 3080ti btw.

Game has issues with network layer, the single player maps works great without lags, all issues are because of network. Network layer is synchronized with graphics and gives lag.

Replying to [#3898 (comment)](https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2295348015)

I have the same issue. Temporary fix for me was to set all graphics to as low as possible. I can play this way and I don't get the drop to 10fps after a banish.

I'll try that again as well.

I'm experiencing a game breaking bug where my fps drops to single digits within seconds after a banish. Distance to the banish doesn't matter, or who started it. Sometimes it happens with a few seconds late, sometimes immediately. The only 'fix' I've been able to come up with is restart the game and reconnect, which naturally has resulted in many losses due to having to afk. It doesn't happen for the roaming boss, only compound bosses.

That also happens on windows and should be a known issue at least did i heard it from a few streamers. My game also freezes sometimes when a banish is going on and i open the map. I also need to restart and reconnect.

Given this comment I might wait for a week of hotfixes before booting up the game again...

Just to add my two cents: I was able to play the game without hiccups or any (non-expected crashes) for the last few days. No problems so far other than the occasional crash on map opening. That happened once or twice in 20 hours of gameplay. Other than that it was smooth sailing with bleeding-edge 👌

I managed to run game on my machine. My problem is that there is insane fog indoors. I play on lowest settings normally but when I tried high nothing changed.

System Info:
CPU: Intel i7-9750H
GPU: NVIDIA GeForce GTX 1650
OS: Manjaro Linux
Kernel: 6.1.102-1-MANJARO (64-bit)
GPU Driver: Nvidia Proprietary 555.58.02
RAM: 15 GiB
Graphics platform: x11
Proton: Experimental

Will we ever get working gamma on Linux? I hoped Crytek will do something with engine update, but they are good only in creating new bugs so only Proton can do this I guess...

Will we ever get working gamma on Linux? I hoped Crytek will do something with engine update, but they are good only in creating new bugs so only Proton can do this I guess...

you can temporarily workaround (change your outputs yourself) by

DISPLAY=:0 /usr/bin/xrandr --output DP-0 --gamma 1.20:1.20:1.20

or even put it into xrandr config

Will we ever get working gamma on Linux? I hoped Crytek will do something with engine update, but they are good only in creating new bugs so only Proton can do this I guess...

you can temporarily workaround (change your outputs yourself) by

DISPLAY=:0 /usr/bin/xrandr --output DP-0 --gamma 1.20:1.20:1.20

or even put it into xrandr config

If you're on Wayland you can do something similar with wlsunset

wlsunset -o DP-9 -g 1.2

Will we ever get working gamma on Linux? I hoped Crytek will do something with engine update, but they are good only in creating new bugs so only Proton can do this I guess...

you can temporarily workaround (change your outputs yourself) by

DISPLAY=:0 /usr/bin/xrandr --output DP-0 --gamma 1.20:1.20:1.20

or even put it into xrandr config

I am currently running it in my launch options, which is also viable:

xrandr --output <your output> --gamma 1.xx:1.xx:1.xx; <other things like mangohud> %command%; xrandr --output <your output> --gamma 1.00:1.00:1.00

This way it only sets it when running the game, and resets it when closing the game. :)

I have been experiencing a strange issue since the update. The game is crashing specifically in the "Deadfall Timbre" compound. Otherwise performance is excellent, game runs smooth, and I have had NO other problems. However, upon even approaching the Deadfall Timbre compound, there seems to be a GPU crash. I suspect this because the whole system freezes and displays turn off, requiring hardware reboot. Unfortunately I do not know how to find the relevant logs files.

Just tried the game out again, and I have the same problem as before. As soon as a banish happens, my fps completely tanks.

I changed the settings to the game's lowest, and just had a banish happen that didn't tank my fps. Instead, the game froze when I opened the map.

Edit: Apparently had a stroke partway through that comment so I had to fix it.

Just tried the game out again, and I have the same problem as before. As soon as a banish happens, my fps completely tanks.

I changed the settings to the game's lowest, and just had a banish happen that didn't tank my fps.

This is the workaround for it, for the moment it seems. I have the exact same issue.

Instead, the game froze when I opened the map.

This is an unrelated issue and not just a Linux one. Crytek addressed this in a Reddit post and iirc it is set to be fixed this week.

With your settings set to low, you should be good to go for now, when it comes to performance.

I'll try upping settings until it starts tanking my fps again. Is it known which setting or settings is causing it?

The game doesn't look particularly good on lowest settings. Surprisingly I only went from 110 to 130 fps going from middling settings to lowest...

I have been experiencing a strange issue since the update. The game is crashing specifically in the "Deadfall Timbre" compound. Otherwise performance is excellent, game runs smooth, and I have had NO other problems. However, upon even approaching the Deadfall Timbre compound, there seems to be a GPU crash. I suspect this because the whole system freezes and displays turn off, requiring hardware reboot. Unfortunately I do not know how to find the relevant logs files.

I have resolved this issue. It seems to be a problem with the amdvlk drivers on Arch Linux. Forcing radeon-vulkan fixes the issue.

As others have suggested here and elsewhere, I changed the drivers for this game to RADV, however I still crash around the Deadfall Timber area. This is a snippet of the logs I got:

4712.439:01a4:0298:warn:vkd3d-proton:vk_image_aspect_flags_from_d3d12: Invalid plane index 0 for format 0.
4712.439:01a4:0298:warn:vkd3d-proton:vk_image_aspect_flags_from_d3d12: Invalid plane index 0 for format 0.
4712.645:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
4712.645:01a4:02a4:err:vkd3d-proton:vkd3d_memory_transfer_queue_flush_locked: Failed to submit command buffer, vr -4.
4712.645:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
4712.645:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
4712.645:01a4:02a4:err:vkd3d-proton:vkd3d_memory_transfer_queue_flush_locked: Failed to submit command buffer, vr -4.
4712.645:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
4712.653:01a4:0298:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 2560 x 1440 x 1, 1 levels, 1 samples, fmt #2c, flags #2).
4712.653:01a4:0298:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 2592 x 1472 x 1, 1 levels, 1 samples, fmt #2c, flags #2).
4712.656:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
4712.656:01a4:02a4:err:vkd3d-proton:vkd3d_memory_transfer_queue_flush_locked: Failed to submit command buffer, vr -4.
4712.656:01a4:02a4:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000220c0080 is lost (reason 0x80004005, "Failed to execute pending memory clears.
").
XIO:  fatal IO error 110 (Connection timed out) on X server ":0"
      after 59 requests (57 known processed) with 0 events remaining.

To add to that, not only does the game crash, but the whole GPU locks and my PC resets.

I have been experiencing a strange issue since the update. The game is crashing specifically in the "Deadfall Timbre" compound. Otherwise performance is excellent, game runs smooth, and I have had NO other problems. However, upon even approaching the Deadfall Timbre compound, there seems to be a GPU crash. I suspect this because the whole system freezes and displays turn off, requiring hardware reboot. Unfortunately I do not know how to find the relevant logs files.

I have resolved this issue. It seems to be a problem with the amdvlk drivers on Arch Linux. Forcing radeon-vulkan fixes the issue.

Did only changing the drivers really help with the issue? I tried it, but it still happens every time I get near Deadfall Timber.

I've been able to increase most settings to medium or high and keep decent performance, but it seems like texture quality is the culprit for the banish FPS loss. I can only keep it on the lowest possible setting.

I suspect it might have something to do with the ram target usage setting, because despite the fact that I upped it to 90%, the "progress bar" for that looks the same. However, that could just be bad UX/UI.

I'm curious, is anything fixed in Proton, or it bugged for years without any fixes?
https://github.com/ValveSoftware/Proton/issues/4571
I reported similar issue for hunt

It did actually happen to me recently that I had about half a second input delay. I clicked to shoot, and the game shot some time later. Still, it's very rare.

It has accumulating effect, the more you play the bigger delay

Do you guys have low FPS and/or Vsync enabled? What desktop environment?

Upper limit is set to 144, usually sit at 80-110 fps, vsync disabled, KDE Plasma. My full stats are further up.

https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2295348015

It doesn't related to FPS/Vsync, I have same issue with Deadlock, which doesn't require Proton I believe, so it could be problem somewhere else, but I also heard that Proton used even if game has native build...
Could be Plasma bug btw, since I got this issue only after 6. release, seems so

I don't think Deadlock is a native Linux game, why do you think it doesn't use Proton?

Because I don't use Proton for it explicitly

FPS issue is partially related to Texture quality setting - if you set it High or more (and you have 8Gb VRAM or less) it somewhat "leaks". The more you play - the more you lag and less your fps. Restart "solves" the problem. Win users suffer the same.

Because I don't use Proton for it explicitly

Like probably all games in my library I don't configure anything specifically in the game properties. So what?
Deadlock has no Linux depot from what I can see on SteamDB. https://steamdb.info/app/1422450/depots/

Found out interesting things, when huge input delay happened again I tried to use my touchpad and it worked without any delay, then I switched to random Fujitsu mouse I had and it also got no delay, so maybe problem is Logitech mouses, my was G102

Check your mouse polling rate. It is a known old bug that 1000Hz polling rate on mouse causes issues often in WINE/Proton (a bug that was deemed a "NOTOURBUG" from the old bug reports on WINE side https://bugs.winehq.org/show_bug.cgi?id=46976).

Reduce it to 250Hz (either with manufacturer tool if available, or other means like a boot option) and see if the issue occurs again. https://wiki.archlinux.org/title/Mouse_polling_rate (for Arch but basically universal for most part).

To check your current mouse polling rate, use evhz tool.

• for me (Arch + KDE + rtx3080ti) it's just 2 inconvenient issues with Hunt:

1. if you have multiple monitors - hunt settings ignores selection and always runs on main one.
   for example if you have
   primary 1080p + secondary 1440p
   dragging windowed and maximizing doesn't remember + resolution on secondary will be is 1080p max (it thinks that's on primary monitor).

2. with mangohud game runs black screen + cursor, so it's not working with.

If I set the game video setting to FULLSCREEN and configure the preferred monitor there, it sticks.

Also MangoHud is working fine here, using 0.7.2-1.

If I set the game video setting to FULLSCREEN and configure the preferred monitor there, it sticks.

Also MangoHud is working fine here, using 0.7.2-1.

unfortunately doesn't work for me and 2 friends of mine (one of them with AMD 6700xt video), all of us with X11 - maybe that's it.

X11 with AMD RX 68OO (//EDIT: on KDE too) here. Not to be a dick, maybe you all doing it wrong? I didn't drag a window or whatever, I configure the game from its menus.

For me on KDE the game doesn't remember the correct screen (KDE Wayland, 7900 XTX). However, I fixed that with a KDE window rule to force it to the secondary monitor.

For me on KDE the game doesn't remember the correct screen (KDE Wayland, 7900 XTX). However, I fixed that with a KDE window rule to force it to the secondary monitor.

tried that, but it seems it doesn't work if your secondary screen has higher resolution (got FHD instead of 2k) :(

@hcwf I haven't gotten any crashes in this area, I tried in soul survivor mode but assuming all modes have the same map this shouldn't be a factor. Does it crash every time for you or is it random? What are your graphics settings

@hcwf I haven't gotten any crashes in this area, I tried in soul survivor mode but assuming all modes have the same map this shouldn't be a factor. Does it crash every time for you or is it random? What are your graphics settings

Yes, it crashes every time in that area for me. I play on high settings, no extra tweaks.

@StellarHarbour @Moghul did you try what I wrote about mouse polling rate? It most likely is the issue you encounter.

https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2329481960

Yes, seems it helped, but it's strange that bug exist for so long and wasn't fixed

Haven't tried it, hope I remember next time I play, whenever that is.

I think I encountered this issue on some Unreal Engine games in the early Proton years, it is very old yes. From what I remember, because someone affected by the issue fixed it by updating his BIOS, the WINE team said "yep, not to us to fix, it is hardware issue, put the issue under the carpet". But I just noticed the issue I linked has been "REOPENED" and not a "NOTOURBUG" issue anymore :D so maybe they will fix it in the future. To be fair it is inconsistent, you sometimes not have the issue so tracking it and fixing it may be challenging.

//EDIT: archive.org just showed me it was reopened many years ago, so not so hopeful now, at least it is not "CLOSED NOTOURBUG" anymore :P

New bug since the last update; this appears to be Linux specific (I can't reproduce it on my windows box).

The items that "flash" are flashing incorrectly and getting this almost like "spider web" effect instead of getting outlined (a few pictures of it):

I have the same issue AMD GPU 7800XT I think it might be related to FSR

Not game breaking but this candle in the Chapel on Stillwater was really wild.

If you think it is related to FSR, disable it and confirm, it is very simple to test, instead of guessing and reporting.

I don't use FSR and I have the 'spider web flashing' instead of the normal flashing of interactive items.

If you think it is related to FSR, disable it and confirm, it is very simple to test, instead of guessing and reporting.

I don't use FSR and I have the 'spider web flashing' instead of the normal flashing of interactive items.

I did mention that I have the same issue (spider web flashing)

Seems like you just confirmed its not FSR related yourself. Fair enough. But a little hostile IMO

I mean you say you think it is FSR, it is one click to confirm that, you could confirm it isn't before reporting it may be it. Yet again you didn't test and confirm, but "complain" I'm hostile. Can you test and confirm you have the issue again without FSR enabled? That would help discard FSR as a supposed reason for the issue. You see what I mean now? It is important to be thorough before reporting something that's all.

On 7900 XTX I'm having the same outline issue as others. Turning FSR on/off makes no difference, so I'm pretty sure it's not related to it. Also, the glitch is making strange patterns if I move the camera.

Video:
https://github.com/user-attachments/assets/227cf210-c89d-47c5-8637-302da40797e0

Edit: changing the graphics settings to full low makes no difference either

Are nvidia users affected by this glitch as well?

I have the same issue on my PC with rx 6700xt (checked on Manjaro and Fedora). I also checked it on my laptop with nvidia rtx 3050 and it has the same issue. So, looks like it's something vkd3d related, am I right?

Cannot start the game anymore with Proton Experimental Bleeding Edge since today's update.
Base Proton 9 works, but we have the old issues of no overlay in this version so you can not invite people.

I had the following error trying to launch Hunt after the latest update.

Switched to Proton Experimental (from bleeding edge) and it works fine now. Overlay working too.

I'll get some logs later if needed

Normal Proton Experimental works indeed.

@kisak-valve

Here is a log from multiple hours session on Proton Experimental, 50MB, nothing weird:
steam-594650-experimental.zip

Here is a log from just a startup with Proton Experimental BLEEDING EDGE and me forcing killing the game after 10 seconds, 1.5GB, big problem:
steam-594650-experimental_BLEEDING_EDGE.zip

Here is the block that keeps repeating in the log before I force killing the process from the Library:

240251.571:018c:021c:warn:seh:dwarf_virtual_unwind backtrace: 0x7a050056649c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x11949c.
240251.571:018c:021c:trace:unwind:execute_cfa_instructions 7a0500566495: DW_CFA_def_cfa %rsp, 8
240251.571:018c:021c:trace:unwind:execute_cfa_instructions 7a0500566495: DW_CFA_offset %rip, -8
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind fde 0x7a05006249a4 len 10 personality (nil) lsda (nil) code 7a0500566495-7a05005664a6
240251.571:018c:021c:trace:unwind:execute_cfa_instructions 7a0500566495: DW_CFA_undefined %rip
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind next function rip=00007a050056649c
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=00007a05004e0ff0 rcx=0000000000000001 rdx=0000000000000000
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind   rsi=00007a04501048e0 rdi=0000000000000000 rbp=0000000000000000 rsp=00000001013c3c68
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind    r8=00007a04500008e0  r9=0000000000000007 r10=0000000000000000 r11=97790d621b055aab
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind   r12=0000000100aff6c0 r13=ffffffffffffff88 r14=000000000000003d r15=00000001000ff870
240251.571:018c:021c:trace:unwind:dwarf_virtual_unwind function 7a050056649c base 0x7a0500566495 cie 0x7a050060f820 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip

Runtime Diagnostic: https://gist.github.com/Zorrototo/153ba169fccb220bc1c454ac62a99c68

Anyone else not hearing the sounds added in the current event? Shredder, ballons, ursa and so on.
Integrity check did not help and looking around on reddit there does not seem to be others with this problem, assuming Windows players.

Arch with Proton Experimental

Fedora seems fine

The only issue I've seen so far is that I sometimes have issues with alt-tabbing and coming back to a black screen following the update.

It was an integrity issue. It also seems I didn't have/had corrupted more things then just sounds but didn't notice it - the new subsonic bullets didn't render in-game at all, for example when reloading.

Deleted ~3 .pak files files at random in steamapps/common/Hunt\ Showdown\ 1896/game_hunt/, mainly targeting the ones that have audio in the name, run integrity check again and now it seems to be alright, even the missing models.

Edit: @DarkArc I haven't had "alt-tabbing" problems for some time but that might be because of using tiling DE (AwesomeWM) and if I switch to a different program or virtual desktop then Hunt automatically minimizes (for better or worse). Though I did have the same problem before, who knows what changed though.

I am experiencing the alt-tab issue as well since the last game update. KDE, Wayland, borderless fullscreen, Proton experimental. Instead of a black screen, though, the game irrecoverably freezes when alt-tabbing back to it. Sometimes it works fine, though, I haven't been able to consistently reproduce it yet.

You could try the UseTakeFocus registry trick (I guess through protontricks) on the hunt compatdata.

https://askubuntu.com/a/1202472/954964
https://bugs.winehq.org/show_bug.cgi?id=48121

I am experiencing the alt-tab issue as well since the last game update. KDE, Wayland, borderless fullscreen, Proton experimental. Instead of a black screen, though, the game irrecoverably freezes when alt-tabbing back to it. Sometimes it works fine, though, I haven't been able to consistently reproduce it yet.

I'm also on KDE, I have a window rule for hunt to force the desired screen:

I'm also using VRR (variable refresh rate) monitors which do cause the screen to go black when full screen applications are refocused.

Otherwise, I don't believe there are any special factors in play.

Fedora seems fine

Do you mind sharing what you did to make it work? I'm currently testing on Fedora Silverblue and I'm either getting crashes on launch, or persisting black screen on launch. I've tried proton experimental, proton experimental with bleeding edge beta, proton 9, and proton 7. None have actually gotten me into the game.

Fedora seems fine

Do you mind sharing what you did to make it work? I'm currently testing on Fedora Silverblue and I'm either getting crashes on launch, or persisting black screen on launch. I've tried proton experimental, proton experimental with bleeding edge beta, proton 9, and proton 7. None have actually gotten me into the game.

I'm also on Fedora... No manual set up required other than using Proton Experimental (and actually I think the latest version of 9 may also work). Silverblue might be a different story; but I'd be surprised.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2544155943

Thanks for confirming I should be looking to use Proton Experimental (with no beta opt-in).

This is a fresh Silverblue install with Budgie desktop and x11. My only concerns were that Silverblue containerizes things a lot, but I don't think thats the issue. I haven't installed the flatpak version of Steam, instead opting for the package from the official rpm-ostree repos.

Maybe it could be GPU driver related? I have an RTX 3070 Ti and I've set to using the proprietary Nvidia drivers. If you have an nvidia card, are you using nouveau?

I am experiencing the alt-tab issue as well since the last game update. KDE, Wayland, borderless fullscreen, Proton experimental. Instead of a black screen, though, the game irrecoverably freezes when alt-tabbing back to it. Sometimes it works fine, though, I haven't been able to consistently reproduce it yet.

For anyone experiencing freezing when alt-tabbing, gamescope works as a band-aid.

I am experiencing the alt-tab issue as well since the last game update. KDE, Wayland, borderless fullscreen, Proton experimental. Instead of a black screen, though, the game irrecoverably freezes when alt-tabbing back to it. Sometimes it works fine, though, I haven't been able to consistently reproduce it yet.

I can second this. Same setup, same problem.

I can second this. Same setup, same problem.

I can at least confirm that, like the previous commenter said, gamescope works as a band-aid. Without the --force-grab-cursor flag, though, instead of the game freezing, the in-game camera would start spinning endlessly. With the flag, everything seems to work fine.

Seems like the game gets confused about the cursor position somehow?

I have the same problem since the 2.2 update of freezing. Not only when alt-tabbing, but also most of the times when i click on the trait menu.

Absolutely no issues with Manjaro KDE and Proton Experimental (no BETA) and an AMD card.

I am experiencing the alt-tab issue as well since the last game update. KDE, Wayland, borderless fullscreen, Proton experimental. Instead of a black screen, though, the game irrecoverably freezes when alt-tabbing back to it. Sometimes it works fine, though, I haven't been able to consistently reproduce it yet.

For anyone experiencing freezing when alt-tabbing, gamescope works as a band-aid.

Also having in game freezing when alt+tabing or loading screens. What are the steam launch options for using gamescope? Thanks!

Also having in game freezing when alt+tabing or loading screens. What are the steam launch options for using gamescope? Thanks!

gamescope -W 3440 -H 1440 -r 144 -f --force-grab-cursor gamemoderun -- %command% in my case. Replace width, height, and refresh rate as needed. Also, if you're using KDE and fractional scaling, make sure you have the latest version of Gamescope, otherwise there might be a crash issue on cursor reaching the border.

Ever since update 2.2, the game crashes frequently on my PC, often when alt-tabbed, but sometimes for no apparent reason. The sound of the game continues until I force quit the game.

When I use Gamescope the game crashes more often and more abruptly, it's just gone without any sound or message. This has been a problem for me since the engine update, so I have avoided using gamescope. I'd like to use gamescope with HDR, but it's unplayable.

I have tried Proton Experimental, Proton Next, Proton-GE and I still get both types of crashes.
Gamescope works perfectly fine in other games without crashing. (CS2, Sea of Thieves, Dead by Daylight)
I am running openSUSE Tumbleweed-Slowroll and my GPU is a AMD RX 6950 XT.

I am still wrangling some missing/broken models (front half of lemat pistol, carbine, ...) and integrity (even filesystem) checks say everything is alright.

Could someone please give me the output of this command?

# enter the game directory, usually in home but change accordingly
cd "$HOME/.steam/steam/steamapps/common/Hunt Showdown 1896"
find game_hunt -type f | parallel sha256sum {} > /tmp/checksums.sha256

Alternatively rhash --sha256 --recursive game_hunt > /tmp/checksums.sha256 but slower.

I want to really rule out this is not some weird integrity bug.

My output of find game_hunt -type f | parallel sha256sum {} > /tmp/checksums.sha256:
https://pastebin.com/PEQGy2rn

I have no issues like you mentioned.

Thanks a lot @HereticWay, for better or worse the hashes all came out alright, so something between proton and the game itself just refuses to load/render the specific models correctly.
Interestingly enough, in the testing range the missing parts of weapons still cast correct shadows.

I've noticed that there was a Hunt specific commit in vkd3d-proton https://github.com/HansKristian-Work/vkd3d-proton/commit/2848a18edf45ba3f5fc72fb8b91826352c08c68a from issue https://github.com/HansKristian-Work/vkd3d-proton/pull/2171
but trying VKD3D_CONFIG=skip_application_workarounds did not help.

I don't know what else to try except complete system reinstall, maybe it's some caching issue but then I would expect deleting Hunt and redownloading completely would cover that but no luck.

Edit: For posterity's sake this is how the Carbine 1865 looks

@wereii what hardware are you using? I believe some rendering issues like this are still happening to some folks on Windows, so this may be down to more of a game + hardware specific bug than anything to do with Proton or your particular system.

Arch 6.12.7-arch1-1, Nvidia 3090 (nvidia-open-dkms 565.77-2) with i9-13900kf, X11.
First thing I did was look around on reddit if there are other people with this problem but coudn't find any (tried "missing model", "missing weapon"), that is how I arrived to the conclusion that it must be mostly "me" problem.

Edit: This is the only thread I could find https://old.reddit.com/r/HuntShowdown/comments/1fn2jkl/hunt_not_loading_weapon_models_textures/
Thing is, it's a bit aged now and I did encounter the same thing (in soul survivor too), back then just restarting the game fixed it, nothing seems to affect it now though and it's the same weapons.

Arch 6.12.7-arch1-1, Nvidia 3090 (nvidia-open-dkms 565.77-2) with i9-13900kf, X11. First thing I did was look around on reddit if there are other people with this problem but coudn't find any (tried "missing model", "missing weapon"), that is how I arrived to the conclusion that it must be mostly "me" problem.

Edit: This is the only thread I could find https://old.reddit.com/r/HuntShowdown/comments/1fn2jkl/hunt_not_loading_weapon_models_textures/ Thing is, it's a bit aged now and I did encounter the same thing (in soul survivor too), back then just restarting the game fixed it, nothing seems to affect it now though and it's the same weapons.

Hm... Yeah, I remember from one of the videos they published prior to the engine update the game does asynchronous loading of the models (so that not working for some reason is the source of this problem). For some folks it's slow, for some it doesn't seem to work at all, and for some it's barely noticeable if at all. Nvidia + Linux may be related to your issue (I suspect most of us are running on AMD hardware at this point).

That said; I wonder if your shader or dxvk cache might be the problem. I can't find any good information on how to clear it / how applicable that is to Nvidia hardware though.

I don't know what else to try except complete system reinstall, maybe it's some caching issue but then I would expect deleting Hunt and redownloading completely would cover that but no luck.

Did you also delete the Proton prefix or is that getting dropped automatically now?

@razzeee I did multiple times manually, though unsure if I completely purged both game data and compat at the same time

All Proton versions are giving me random crashes since last patch, specially when looking for team mates. Tried the gamescope suggestion, or gamemode without luck. Any suggestions?

Delete the prefix, verify game files (I play with Proton Experimental no issues).

Also having in game freezing when alt+tabing or loading screens. What are the steam launch options for using gamescope? Thanks!

gamescope -W 3440 -H 1440 -r 144 -f --force-grab-cursor gamemoderun -- %command% in my case. Replace width, height, and refresh rate as needed. Also, if you're using KDE and fractional scaling, make sure you have the latest version of Gamescope, otherwise there might be a crash issue on cursor reaching the border.

I'm experiencing the same issue on Arch Linux with KDE Plasma on Wayland. When I press ALT+TAB, the game ends up crashing.

Using gamescope with the command you provided seems to fix the problem, but limiting the FPS causes occasional stuttering, so I removed that parameter and enabled the in-game frame limiter.

The truth is that I would prefer not to use gamescope, especially considering that the game was working perfectly before the update.

KDE Plasma on Wayland

Just for the sake of it, next time you boot can you login to an X11 session instead of Wayland, to confirm the issue is related to Wayland please, so we know better where to look to help fix it.

KDE Plasma on Wayland

Just for the sake of it, next time you boot can you login to an X11 session instead of Wayland, to confirm the issue is related to Wayland please, so we know better where to look to help fix it.

After starting a session with X11 in KDE, I can confirm that the issue is gone. I can press ALT + TAB as many times as I want, and the game won't crash.

I've uninstalled gamescope and left the following launch options for the game:

mangohud gamemoderun %command%

But otherwise, everything is at its default settings. I'm not using any particular version of Proton beyond the one recommended by Steam by default.

So yeah, we can say with reasonable certainty that the problem comes from Wayland after the latest game update, since I didn't experience any issues before, despite using Wayland.

Thank you very much for the suggestion.

The "gamescope -W 3440 -H 1440 -r 144 -f --force-grab-cursor gamemoderun -- %command%" is working fine for me, after last patch on latest Proton-GE. Only thing missing is Steam overlay. Thanks!

Is anyone else experiencing frametime issues? I am frequently getting random frametime spikes on both X11 and wayland. I have tried mesa drivers on arch, bazzite, and nixos with different versions of proton, and there is zero difference. My friend who has a very similar system (we both have a 6700xt) reports smoother frametimes (and lower framerate) on the proprietary drivers. Gamescope mangoapp looks better, but doesn't feel any better.

Is anyone else experiencing frametime issues? I am frequently getting random frametime spikes on both X11 and wayland. I have tried mesa drivers on arch, bazzite, and nixos with different versions of proton, and there is zero difference. My friend who has a very similar system (we both have a 6700xt) reports smoother frametimes (and lower framerate) on the proprietary drivers. Gamescope mangoapp looks better, but doesn't feel any better.

I haven't noticed any issues in this area. I play with VRR on though given the game's general variance in FPS area to area, so that might be a factor.

Hunt can be very CPU sensitive as well, so that's another thing to consider when comparing you and your friend's machines. The AMD "X3D" chips in particular tend to work wonders.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2581842982

Interesting... I've tried with and without VRR, and it's still more stuttery than Windows. As for CPU, I've got a 5700x and my friend an intel one (I can not remember which), and yet we both have this issue using mesa. I'll try to record my issue soon.

Only thing missing is Steam overlay

No issue with Steam overlay in Proton Experimental (NO BETA).

Is anyone else experiencing frametime issues?

No issue perfect smooth experience locked at 75FPS with a Ryzen 5 3600 CPU and a RX 6800 video card. You might want to check your video settings maybe you're setting too high parameters (I can show my in game settings for reference if needed later).

Is anyone else experiencing frametime issues? I am frequently getting random frametime spikes on both X11 and wayland. I have tried mesa drivers on arch, bazzite, and nixos with different versions of proton, and there is zero difference. My friend who has a very similar system (we both have a 6700xt) reports smoother frametimes (and lower framerate) on the proprietary drivers. Gamescope mangoapp looks better, but doesn't feel any better.

Thank you everyone who has already help. Here is a video demonstrating my issue (compressed for size):

Mine (medium preset with no upscaling, and a VRAM target of 90):

https://github.com/user-attachments/assets/439153a0-a6d9-436d-8b97-2b03f5b6fbd2

My friend's:

https://github.com/user-attachments/assets/41aab8a9-2915-4cee-a44e-8f39300cb079

Lowering the settings doesn't stop the stutter, and capping FPS somehow makes it worse in some cases.

Just a note @LachlanS7 your first video is hevc encoded - not all browser on not all platforms are going to natively play that (h264 is better for compatibility), for example my Firefox on Arch does not.
I don't see anything out of ordinary though (downloaded and playing with mpv) in the video? Well except for not using gamemode but your friend seems to not either.

Hi @wereii, thank you for your comment regarding the video encoding, I wasn't sure what the issue was.

I have tried gamemode and it never seemed to make a difference. So far the only thing I've found to help is setting a frame cap (via mangohud), but that still isn't perfect, but it's good enough for now.

Thanks again

For a few months now, hunt has been crashing for me, and many others, when the game is not focused on Wayland. I recently found what seems to be a workaround, and that is by running the game in Wayland-native proton. I presume this is to do with the game still being rendered when not-focused.

To use Wayland-native proton:

1. Download wine-tkg-git and grab the most recent wine master proton nightly build. You will need to be logged in to do this.
2. Extract the downloaded zip to your compatibilitytools.d folder in your steam directory.
3. Restart steam and under compatibility select to use the new proton-tkg. Then unset the DISPLAY environment variable (e.g. DISPLAY= %command%).

A few things to note:

• Wayland-native proton is currently under development and is experimental, expect some bugs / quirks. One of these is that, at least with KDE plasma, screen scaling causes issues as it trying to scale the game. So far the only fix for this is just disabling screen scaling while I play.
• I cannot seem to be able to rotate my hunters or weapons in the preview, however this is a minor issue.
• If you are playing at a lower resolution than native (this does not include FSR, I mean something like 1080p on a 4k screen using basic up scaling), you might experience some issues when running in fullscreen. Using window borderless seems to fix these for me.

Do the basics, verify integrity of game files, EAC Runtime files, give proper system information about your setup that might not be common, because the game definitely works on Proton Experimental without issues, AMD or NVIDIA. Try other LTS kernel.

I would guess the way you installed Steam breaks things for Proton.

I would guess the way you installed Steam breaks things for Proton.

Yeah, I figured...
Seems like it was probably the flatpak, couldn't find another build of steam for OpenSUSE so I just swapped to Debian and it works fine.
Performance hit compared to windows is quite minimal.

Proton should work fine in flatpak, that would be very surprising. Did your system install the flatpak nvidia driver?

Problem is probably Flatpak permission, if you look at the error from WINE log.

steam-594650.log

the 2.3 update today it seems Linux users can no longer connect to the servers

Fedora 42 - Proton Experimental

Ah yup, booted up the game and all seemed fine, but when I actually went to try and queue into something, that's when I got hit with the region not being available and ping to all regions being 0.

FYI, you can still play with friends, if you accept their invite the game lets you queue up as normal. Still hoping to see a workaround in proton.

FYI, you can still play with friends, if you accept their invite the game lets you queue up as normal. Still hoping to see a workaround in proton.

I wouldn't be surprised if that comes with the caveat that the corresponding party is then put into the "high ping" match making queue though; so that's not ideal for multiple reasons 🥲

Thanks for the information though, it's good to know Linux players aren't totally locked out (assume we have friends 🙂)!

FYI, the "Region is currently unavailable" popped up for me as a windows user. So I think that error message is just happening for a lot of people. Obviously the 0ms ping issue appears to be Linux specific though.

I wouldn't be surprised if that comes with the caveat that the corresponding party is then put into the "high ping" match making queue though; so that's not ideal for multiple reasons 🥲

I just played a game and it seemed fine, I myself had a ping of around 7 which is my usual.

I wouldn't be surprised if that comes with the caveat that the corresponding party is then put into the "high ping" match making queue though; so that's not ideal for multiple reasons 🥲

I just played a game and it seemed fine, I myself had a ping of around 7 which is my usual.

It wouldn't be client observable: https://www.huntshowdown.com/news/developer-insight-high-ping-separation

It's about who you're matched with. Your ping might be 7, but if they can't get a proper ping reading, they might be putting you with people that have 200ms ping.

We've pushed a tentative fix for that to Proton Experiental [bleeding-edge branch] (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions , "Proton Bleeding Edge" part for the hints on how to select it).

No issue on Proton BLEEDING EDGE regarding the ping of servers/regions.

I can also confirm that the Bleeding Edge version fixes the reported latency for server/regions.

The Bleeding Edge version fixes the server/regions issue for me

Of note, the alt-tab issue seems to have been fixed by this update.

Can confirm, bleeding edge fixed the region/server issue for me too

Can also confirm it to fix the region issue. Can somebody link to the commit, that fixed this?

Can also confirm it to fix the region issue. Can somebody link to the commit, that fixed this?

I believe it was this one: https://github.com/ValveSoftware/wine/commit/c591734b72cfb0b606418136dc201ec88876cead

Saw that and assumed it wasn't the fix, as it talks about crashes, which were not the case

The Polaris glitches seem to be a regression in Mesa 24.2.0, so I've filed an issue report for it here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13082

You can not bind some keys with FRENCH keyboard layout anymore on Proton 10, for example the [é2] (secondary weapon) key doesn't bind at all. the [&1] and ["3] (before and after) are able to be bound, and work.

In Proton 10 beta and experimental, the game no longer holds the mouse focus in the same way. The mouse cursor is moving over my second monitor

Proton Hotfix is working OK

@LukeDearden What window manager are you using? Could you explain a bit more detail - does the problem happen on the menus or only in-game? Is your second monitor on the right or left hand side?

@LukeDearden What window manager are you using? Could you explain a bit more detail - does the problem happen on the menus or only in-game? Is your second monitor on the right or left hand side?

I’m using Niri WM and xwayland-satellite

The second monitor is on the left

I’m using borderless. But the same thing happens in full screen too

This happens in the game. If you try and look left all the way the movement stops and the mouse appears on the other monitor. Then the keyboard input kind of gets stuck so you’d keep sliding right while moving etc. At this point there’s nothing you can do to play normally.

As mentioned proton hotfix is working fine

@LukeDearden Thank you for the details! I'll take a look :)

FWIW - Proton Hotfix is only updated when infrequently when needed and is intended to be "short lived" as it is almost immediately older than bleeding-edge (see https://github.com/ValveSoftware/Proton/wiki/Proton-Versions). We haven't needed hotfix since shipping Proton 10, so it is still a Proton 9 based build, which explains the lack of regression. For now, you can use Proton 9.0-4 and we are also keeping an experimental-9 branch around (on the same beta dropdown menu as bleeding-edge) to avoid the regression :)

@alasky17 thanks I tried the last regular proton 9 but that still has the issue where all regions have 0ms ping

Proton Experimental-9 working fine

Tested the beta Proton 10, after about 20 minutes in-match I've got a crash, the game freezes and locks up the PC for a few seconds, alt+f4 the window just closes it but the process keeps running in background as I can still hear the last sounds going, had to press stop in steam.

Proton Experimental-9 seems to work ok.

[104314.314419] traps: VizCompositorTh[228107] trap int3 ip:649bc9c3494d sp:746cad3e3fc0 error:0 in electron[8a5294d,649bc2aeb000+9b71000]
[119787.199288] NVRM: VM: invalid mmap
[119787.199298] NVRM: VM: invalid mmap
[119787.199411] NVRM: VM: invalid mmap
[119787.199422] NVRM: VM: invalid mmap
[119787.199453] NVRM: VM: invalid mmap
[119787.199475] NVRM: VM: invalid mmap
[119787.199485] NVRM: VM: invalid mmap
[119787.199490] NVRM: VM: invalid mmap
[119787.199594] NVRM: VM: invalid mmap
[119787.199604] NVRM: VM: invalid mmap
[119787.199606] NVRM: VM: invalid mmap
[119787.199613] NVRM: VM: invalid mmap
[119787.199615] NVRM: VM: invalid mmap
[119787.199621] NVRM: VM: invalid mmap
[119787.199728] NVRM: VM: invalid mmap
[119787.199744] NVRM: VM: invalid mmap
[119787.199795] NVRM: VM: invalid mmap
[119787.199815] NVRM: VM: invalid mmap
[119787.199843] NVRM: VM: invalid mmap
[119787.199859] NVRM: VM: invalid mmap
[119787.199896] NVRM: VM: invalid mmap
[119787.199952] NVRM: VM: invalid mmap
[119787.200018] NVRM: VM: invalid mmap
[119787.200025] NVRM: VM: invalid mmap
[119787.200068] NVRM: VM: invalid mmap
[119787.200071] NVRM: VM: invalid mmap
[119787.200129] NVRM: VM: invalid mmap
[119787.200163] NVRM: VM: invalid mmap
[119787.200174] NVRM: VM: invalid mmap
[119787.200191] NVRM: VM: invalid mmap
[119787.200261] NVRM: VM: invalid mmap
[119787.200320] NVRM: VM: invalid mmap
[119787.200328] NVRM: VM: invalid mmap
[119787.200331] NVRM: VM: invalid mmap
[119787.200655] NVRM: VM: invalid mmap
[119787.203645] traps: MediaPD~oder #3[275884] general protection fault ip:7a8a5237db41 sp:7a8a4a25c280 error:0 in libnvcuvid.so.570.144[17db41,7a8a52200000+f71000]
[132226.432537] traps: ThreadPoolForeg[300890] trap int3 ip:5c01766d7278 sp:76cc681f81d0 error:0 in electron[66d8278,5c0171908000+9b71000]
[135786.367400] x86/split lock detection: #AC: CHTTPClientThre/311965 took a split_lock trap at address: 0x568d030f
[135866.213601] x86/split lock detection: #AC: CJobMgr::m_Work/309573 took a split_lock trap at address: 0xeb3f459f
[135886.135321] nvidia 0000:01:00.0: Using 39-bit DMA addresses
[135886.468205] x86/split lock detection: #AC: CGameStreamVide/313460 took a split_lock trap at address: 0x99cc0ad3
[135886.469483] x86/split lock detection: #AC: CGameStreamVide/313218 took a split_lock trap at address: 0x99d7c95a
[135886.760746] x86/split lock detection: #AC: CGameStreamVide/313464 took a split_lock trap at address: 0x99d7c95a
[136657.268710] NVRM: GPU at PCI:0000:01:00: GPU-49efb36f-4915-36b4-2144-67de63192c4f
[136657.268714] NVRM: Xid (PCI:0000:01:00): 69, pid=313470, name=Main, Class Error: ChId 0027, Class 0000c797, Offset 00000dcc, Data 000000e4, ErrorCode 00000004

Arch, 6.14.4-2-cachyos kernel
nvidia-open-dkms - 570.144-3
RTX 3090
X11 (AwesomeWM)

@kisak-valve will do when it gets into Arch repos, not there yet

In Proton 10 beta and experimental, the game no longer holds the mouse focus in the same way. The mouse cursor is moving over my second monitor

Proton Hotfix is working OK

I'm not having any issues using Proton Experimental w/ KDE Wayland.

You can not bind some keys with FRENCH keyboard layout anymore on Proton 10, for example the [é2] (secondary weapon) key doesn't bind at all. the [&1] and ["3] (before and after) are able to be bound, and work.

Here you can see on Proton 10, the keys associated with the weapons/items/consumables which are not working are having these weird texts "@cc_2" (when it should be "é"), or "@cc_7" or "@cc_9" or "@cc_0":

basically the weapons/consumables/items are bound to 1 / 2 / 3 / 4 / 5 / 6 / 7 / 8 / 9 / 0 (which for a FR keyboard the main characters are & / é / " / ' / ( / - / è / _ / ç / à, not the actual numbers like on a QWERTY keyboard). With Proton 10, the keys é2 / è7 / ç9 / à0 can not be bound and do not work if previously bound, probably there are more issues with keys.

I switched to Proton Experimental Bleeding Edge 9, and my previous key bindings work and show properly the correct character, and I can assign all the keys.

//EDIT: I have similar issue on Rising Storm 2 Vietnam, where ALL the keys are recognized as NUM LOCK key when I try to rebind them. https://github.com/ValveSoftware/Proton/issues/2726#issuecomment-2848721547

As of Proton 10, I seem to be having some new minor issues related to cursor capture, window focus, and alt+tab behavior, using KDE 6.3.4 on Wayland, Arch Linux

This is easiest to reproduce in borderless fullscreen mode with a multi-monitor setup, but I can reproduce it in a small window on a single monitor as well.

After going into a match (e.g., the shooting range), where the game captures the cursor:

• On Proton 10:
  When I press alt+tab to change focus to another window on a different screen, the cursor remains invisible. I can blindly move it off Hunt's window, but the in-game camera continues to follow the cursor as if it’s still captured.

• On Proton 9.0.4:
  Pressing alt+tab causes the cursor to visibly appear. I can then move it normally, and the camera no longer tracks it.

Additionally, I noticed that the option to mute the game in the background (Settings > Audio > "Play sound in background" set to off) no longer works reliably.
However, the game does mute properly if I switch focus specifically to the Steam client, but not when focusing other windows.

Interestingly, the cursor issue also does not occur when switching focus to a Steam window.

Hopefully this help narrow it down.

I, as well as a friend, have instability with this game, it randomly freezes, sometimes on the first game, sometimes after 4 hours session, completely random. I have a RX 6800, the friend has a RX 7800 XT. Here are two logs, one small where it froze at the first game, and the other one where it froze after a long session:

steam-594650.tar.gz

System info: https://gist.github.com/Zorrototo/eb139f17775a275ffcaf08f977a77ec3

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2848323148

not being able to map some keys always was a problem, but proton 10 seems to change something. See https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-1893152394 for the old problem.

I also was on proton experimental and lost all my keybindings - then reverted to normal (9) and had to redo the keybindings again. So the switch over seems to cause this.
I faintly remember, that something was fixed with keys in wine.https://www.gamingonlinux.com/2025/01/windows-compatibility-layer-wine-10-out-now-bringing-wayland-and-arm64ec-support-new-ffmpeg-multimedia-back-end/
Think might just have been the dvorak improvements

I have clean new prefix for Hunt Showdown and Rising Storm Vietnam for Proton 10, and I have two similar issues with key binding not working properly. On Hunt Showdown only a few key do not work, but on Rising Storm Vietnam, every key I try is seen as NUM LOCK.

No issue on Hunt showdown on Proton Experimental 9 Bleeding Edge regarding key bindings.
Did not try for RS Vietnam yet on this Proton version but my guess is that it works properly, will edit this post after testing.

//EDIT: for RS Vietnam switching to Proton Experimental 9 Bleeding Edge doesn't help, still the same issue so I guess the game is just borked on Proton completely.

Seems like beta has had a fix added - I've not tested it, only saw the patch note https://github.com/ValveSoftware/Proton/releases/tag/proton-10.0-1d

Yes it fixed the issue with the keybinding with FR keyboard layout key not working https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2848323148

The assigned keys seem to show up correctly ingame now.

I still can't map most of my "number keys" with programmer dvorak having the number row replaced with brackets and such. Out of the left half of my keyboard I can only map [ and =, at least &, {, } and ( don't work.

Report maybe here https://github.com/ValveSoftware/Proton/issues/8658

@razzeee Thank you for noticing! Yes - the fix is in the 10.0-1d bump. Is the remaining issue with dvorak for just Hunt: Showdown or all/most games? If it is impacting many games, please comment on https://github.com/ValveSoftware/Proton/issues/8658 as I'm still going to keep investigating the remaining issue with Rising Storm 2 as well there 👍

Continuing my bug report from there: https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2848541380 , I have some new findings

It seems like it's not just switching focus to a Steam window that is the "exception" to this issue, but to any Xwayland window. Otherwise, the problem remains the same.

It also affects every game that I tested on proton 10, not just Hunt: Showdown, and in some games it can get more annoying than just some unwanted camera movement.

It happens on both my AMD and Nvidia PCs, so that doesn't seem to be the problem.

Any idea where I would go about reporting this regression? is it an xwayland issue, a wine issue, or is it specific to proton?

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2866336914

I’m still having this same problem.

@Maselkov If the behavior differs when switching to Xwayland windows, we might have a fix coming next week. We know of at least one issue that fits that description that we are trying to fix in Proton, although yes - it is caused by a combination of Proton and Wayland interacting strangely ... Since this is happening in multiple games, you can feel free to file a separate meta-issue in this tracker so that other folks can have better visibility rather than getting a lot of similar reports. Please tag me so I can keep track if you do :)

Switched to GE-Proton 10.1 today to try native Wayland.

I have to say that this works exceptionally well for me! At least for two round quickplay watching.
Have HDR and VRR enabled on Gnome as well. Discord streaming quick test worked well, too! Did not before (pixelated).
The bug with wrong keyboard layout seems to not apply for me, too.

Only the steam overlay is broken now and I can't remember if I read about a fix for this somewhere or not.

I'm using PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 in the game options and LD_PRELOAD= LD_LIBRARY_PATH= in a launch/stop script (to execute a flatpak command). My guess is, that this "LD_PRELOAD=" breaks the overlay as I've read about that but it did not with GE-Proton 9.27. Not gamebreaking for me though.

Just mainly wanted to let people know about that as I'm very excited about all this working now!

Oh - and gamma slider works now, too (with HDR disabled of course) - yeay!

Gnome 48 Wayland, AMD RX6700, 3 Displays, Nobara 42

EDIT:
Nope - it's not the LD stuff. It's enabling wayland what breaks the overlay.

This is the status for my last Gaming session (2 hours):
I can confirm that the Gamma Slider works now, i have no Alt-Tabbing issues and no Screen focus issues.
The game runs buttery smooth with no felt Input Lag.
The Steam Overlay is NOT working

My setup:
CachyOS KDE Plasma 6 on Wayland
Kernel: Linux 6.14.6-2-cachyos
AMD Ryzen 5600X
NVIDIA 4070Ti with Driver 570.144
One 1440p 144Hz Monitor with VRR active
Proton: 10.0-200 (Looked this up in steamapps/compatdata/594650/version)

Game Launch options:
DXVK_FRAME_RATE=137 LD_PRELOAD="" LD_LIBRARY_PATH="" PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1dlss-swapper game-performance %command%

In-Game i have not activated HDR.

Nice work guys and see you in the Bayou :-)

EDIT: i added the Proton version (i hope this is correct)
Thanks @Zorrototo for pointing that out so nicely :-)

You didn't even mention the Proton version you used..

EDIT: I mean without the Proton version the info provided is not really helpful in any way. It could be Experimental, HotFix, Old Proton version (not really as you talk about Wayland now working), a custom one, and so on. It is not about asking nicely, whatever that means to you, it is just to provide relevant info, if you want to report something.

Guys, does anyone experience problems with Steam's Game Recording with Hunt and any Proton based Wine 10.x? issues both X11 and Wayland

Wine9-based - Proton 9 and GE-Proton 9.27 - okay

Wine10-based - Proton 10 and GE-Proton 10.x - only splash-screen (with EAC logo and "initializing" message) recorded with sound? sometimes with multiple static cursor "trailing" over it.

vanilla Arch 6.15
KDE Plasma 6.3.5
NVIDIA GeForce RTX 3080 Ti
nvidia-dkms 575.57.08-3

cmd in Steam (checked - does not affect the issue) for image clarity:
ENABLE_VKBASALT=1 %command%

Latest game update does not work with Proton Experimental Bleeding Edge.
It loads but can not connect to Cry Cloud.

steam-594650.log

Not a proton issue, servers are just down

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2985309703

This is not a proton issue.
The Game's servers are down right now.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-2973500320

This seems to have something to do with the way EAC is implemented, as it happens on many games using EAC. At one point, bleeding edge of Experimental worked, and also it was said that whatever hack was put into Experimental to fix this was placed in 10.0-1 Beta, but as of today, I can confirm that neither 10.0-1 Beta or Experimental work right now to fix Steam Recording for Hunt.

@codywlsmith I don't know if I misunderstood, but I thought you were complaining that you're unable to use steam game recording with the hunt, but I was able to use it on proton experimental bleeding edge and also proton 10 beta. If I understood correctly and it isn't working for you, does it work in other ones? if so, which games?

@simifor I should clarify: it's not that Steam Recording does not work, it's that what Steam Recording actually records is the EAC splash screen when starting the game. Hunt is the only game that I play that has this issue. But that is just my small sample size. I have heard it happens on other games that use EAC such as The Finals and New World Aeternum.

For me, it doesn't matter if I am on bleeding edge or the 10 beta, when I look at the recording, it's just this.

@codywlsmith I'm not seeing this on my end. I had previously recorded manually after the game started and the recording just showed the same thing I saw. Now I tried to set it to background recording and the eac prompt showed at the start of the launch (seconds 5 through 21 in the recording) but switched to the game window as the game loaded proper. What desktop environment are you using?

@simifor I am on Nobara 42, using KDE.

@codywlsmith I was using kde plasma 6.3.5 with a wayland session

Hunt Showdown has, overtime, completely degraded for me and I am now missing various parts of weapon models, or missing complete vegetation/objects, as well as various glitched parts (specifically the sparks with fast fingers trait, last screen)

I am out of options to try except for trying a completely different distro.
If anyone here has any other ideas please send it, anything is appreciated.

See print screens at the end of how it looks.

Timeline, about 7 months ago at the end of 2024, when the clown update dropped was the first time some weapons just did not load or loaded only partially, some sounds were missing too. While the sounds and some things did fix itself (I believe the following patch fixed some of this), from that moment on I still don't see full models of some weapons, Carbine 1896, LeMat pistol, a bit of Derringer Pennyshot and Silenced Bornheim, this has never improved since (I was hoping this is an intermittent hunt/proton/driver issue).

Now, after a little bit more fiddling last few days - I've completely reset the in-game settings and reinstalled the game to give it another chance - instead I've got another model bug: graphical fidelity of hunter models went down the drain and no in-game setting seem to affect it at all, this also caused some in world objects to vanish, when I encounter these I sometimes get kicked/disconnected, probably because of too many desyncs.

Setup:

OS: Arch Linux 6.15.3-arch1-1
Processor: Intel 13900kf
GPU: MSI Suprim X 3090 (24GB vram), nvidia 575.64-2 (no difference between nvidia-open-dkms)
RAM: 64G 6400MHz
Proton version: does not seem to matter, tried 9, 10.1 beta, Experimental, Experimental [Experimental-9], Hotfix, and even various 3rd party like GE
Env: X11, Awesome WM without compositor, no difference with wayland
Disks: The game disk is 2TB nvme with btrfs, healthy. Home disc is btrfs and nvme too.

Proton log from the same run as the screenshots:

steam-594650.log

UPDATE 25-07-03:

• I've tried completely fresh install of Linux Mint 22.1, then through their driver manager tested nvidia versions 575,550 and 535 - no difference, can't test 470 as the game just crashes (with proton 9, something about the system not supporting dx12 of some spec, which I believe translates to the driver not implementing needed vulkan apis).
  No change with either version.
• I've got my hands on an RX 7900 XTX, removed anything nvidia specific, verified everything else works, and tested again - nothing has changed. Bone Doctor hunter still looks like Lara Croft from TR1 and lemat is missing it's front half.

I am starting to believe this is some kind of sorcery :D

With new Hunt update 2.4.0.2 the easy anti cheat doesn't load.

I can also confirm this as well.
I tried a few proton versions: Experimental [Bleeding Edge], Hotfix, GE-10-9, 10.0-2 Beta.
Tried even changing the Proton Easy AntiCheat runtime to the test branch and it didn't work.
Integrity checks on the proton instances as well as the game ended in the same place.

I too can confirm this.
As @Shoklan I tested multiple proton versions (Experimental, Experimental Bleeding Edge, GE-10-10, proton-cachyos) and all proton versions produced the exact same error prompt as that of @Arisa-Snowbell.
Well, gg

Anyone tried the update on the Flatpack version of Steam?

@LukeDearden Yes, same there. Tried several proton versions, too.

Same here, Experimental, TKG, 10, and Hotfix all give the same issue. Possible EAC side update bricked it.
Can we get any information regarding other games running newer EAC to possibly narrow down the issue?

steam-594650.log
Here are my steam logs if anyone is interested in looking into it
There are some process handling/fork errors. Something with mismatched pid's. So propably the EAC spawns unexpected.

Game.log says clearly:

Game.log

<22:00:33> [Error] [EAC] [EOS][LogEOSAntiCheat] [AntiCheatClient] Anti-cheat client not available. Result code 21 (EOS_VersionMismatch). This version of the EOS SDK requires a newer anti-cheat client module version. Check the EOS Developer Portal for updates.

The file is attached. Log can be found in steamapps/common/Hunt Showdown 1896/USER/

Edit: Judging by the timestamp from Proton Easy AntiCheat Runtime files, it seems like the last time it was updated was in the Hunt's engine update (15/8/2024).

Maybe the devs forgot to push the EAC Linux version.

It's fixed now, they somehow fixed it without update. Hunt works now

steam-594650.log
Game doesn't allow to override DLSS versions anymore. I used to sucessfully override DLSS version using this launch options set: PROTON_ENABLE_NGX_UPDATER=1 DXVK_NVAPI_DRS_SETTINGS=NGX_DLSS_RR_OVERRIDE=on,NGX_DLSS_SR_OVERRIDE=on,NGX_DLSS_FG_OVERRIDE=on,NGX_DLSS_RR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_latest,NGX_DLSS_SR_OVERRIDE_RENDER_PRESET_SELECTION=render_preset_latest DXVK_NVAPI_SET_NGX_DEBUG_OPTIONS=DLSSIndicator=1024,DLSSGIndicator=2 %command%
Now game just starts and stays on a black screen with in-game cursor. Proton-stable, Proton-Experimental-Bleeding Edge, Proton-GE, every proton version i tried doesn't change anything. Overriding still works in other games.

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-3181362580

That is a lot of commands. What do they all do?

I just use the following for FSR4 and HDR

PROTON_FSR4_UPGRADE=1 PROTON_ENABLE_WAYLAND=1 ENABLE_HDR_WSI=1 PROTON_ENABLE_HDR=1 DXVK_HDR=1 mangohud %command%

Replying to [#3898 (comment)](https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-3181362580)

That is a lot of commands. What do they all do?

I just use the following for FSR4 and HDR

PROTON_FSR4_UPGRADE=1 PROTON_ENABLE_WAYLAND=1 ENABLE_HDR_WSI=1 PROTON_ENABLE_HDR=1 DXVK_HDR=1 mangohud %command%

It overrides every DLSS component to the latest version and createas a small window with dlss version in the bottom left corner. Problem is that even without all the messy long command, game doesn't even start just with PROTON_ENABLE_NGX_UPDATER=1, which just enables this feature. Also i've got nothing to do with FSR4 upgrade, because it's only supported by AMD cards.

UPD: Looks like the problem was on my side. Adding PROTON_HIDE_NVIDIA_GPU=0 fixed my problem

That's odd, haven't had any crashes (at least lately, can't remember when hunt last crashed maybe with hunt 2.0 and the map bug) and I have the same graphics card. But I'm not using Proton GE but normal Proton.

Try the basics, remove startup parameters in Steam, delete the prefix folder ~/.local/share/Steam/steamapps/compatdata/594650/, delete (or rename to keep old files) the profile folder inside the game files folder ~/.local/share/Steam/steamapps/common/Hunt Showdown 1896/USER/ start all fresh with the Proton Experimental Bleeding Edge version or other 10.0 official Steam version.

@Anaerobic-ai when uploading logs, you should always go for stock proton instead of third party builds. I'm not sure if I found the pond you mention in ash creek, but the other two I did and didn't cause any issues on my end. Do you have amdvlk installed, by any chance? and if so, can you try uninstalling it and see if it has an effect?

I just want to say a huge thank you! @simifor
For about 9–10 months I wasn’t able to play properly — I had to completely avoid Deadfall and other affected areas because of the constant crashes.
During that time I tried everything: different kernels (LTS and rolling), multiple Proton versions, various launch options with commands, even clearing caches. Nothing helped.

And now, simply removing amdvlk finally solved the problem. Honestly, I didn’t even know what amdvlk was or that it was installed on my system in the first place.

It feels almost unbelievable after such a long time of trial and error. I’m really grateful you pointed me in the right direction — now the game runs stable and I can finally enjoy it again. Thanks a lot!🙏 ✌️😁

Hi,
since a few weeks (even before the 2.5 update) i have random crashes in Hunt Showdown on various spots on the map and also various maps. I have already done a lot of steps to figure out why. Among others i reinstalled the game, deleted shaders, changed graphics settings, used NTSYNC, tried Wayland session. But i can't mitigate or reproduce the crashes consistently. But first things first:

Description:
Random application crashes during games of Hunt: Showdown. Sometimes it happens on the first game or also after several games.
The image will freeze, but some sound of the game is still audible (e.g. breathing of the character. Gunshots and other players are not audible anymore). It is possible to Alt-Tab out of the game and close it in Steam. I can also start it again without initial hiccups although it sometimes stem validates game files after such a crash.

System information:
Ryzen 5600x
Nvidia RTX 4070Ti using Nvidia 580.95.05
CachyOS on KDE Plasma 6.4.5 with Kernel 6.17.0-3-cachyos
Proton versions used, but crashes still happen:
Proton Experimental, Proton-GE, Proton-cachyos, Proton-cachyos-slr

Log file: "crycrash_error.log":

`
----- FAILED TO GET SCREENSHOT -----
Exception Code: 0xC0000005
Exception Addr: 0x0033:0x00000001414FA3F4
Exception Module: [unknown]
Exception Description: EXCEPTION_ACCESS_VIOLATION, Attempt to read from address 0x0000000000008000

The memory could not be "read"
Memory in use: 5538.0MB
Debug Status: 05:19
Out of Memory: 0
MainThread Id: 384
RenderThread Id: 604
[Crashed] Thread Id: 848
[Crashed] ThreadName:

[Crashed] Call Stack: ["ThreadNameUnknown" [848]]

=============================================================================

1. function = [unknown]+0x1414fa3f4
   =============================================================================
   Logged at Thursday, October 02, 2025 10:50:44
   FileVersion: 2.5.0.45
   ProductVersion: 2.5.0.45
   LogFile: Game.log
   GameDir: game_hunt
   Executable: Z:\home\User.local\share\Steam\steamapps\common\Hunt Showdown 1896\bin\win_x64\HuntGame.exe

Exception Code: 0xC0000005
Exception Addr: 0x0033:0x00000001414FA3F4
Exception Module: [unknown]
Exception Description: EXCEPTION_ACCESS_VIOLATION, Attempt to read from address 0x0000000000008000

The memory could not be "read"
Memory in use: 5538.0MB
Debug Status: 05:19
Out of Memory: 0
MainThread Id: 384
RenderThread Id: 604
[Crashed] Thread Id: 848
[Crashed] ThreadName:

[Crashed] Call Stack: ["ThreadNameUnknown" [848]]

1. function = [unknown]+0x1414fa3f4
   `

Does someone have a similar issue or does know what to do?
Thanks ahead!

No issue at all with the game on full AMD system and Proton Experimental Bleeding Edge. Maybe try a LTS kernel. Maybe monitor system (RAM, temperatures, and so on). Maybe disable all Launch Options in Steam. Maybe check for hardware failure/issues (tested your RAM already?). Maybe delete the Proton prefix and start over. Also try various game settings preset for the video, maybe one parameter creates issues.

@DiggerTigger Most likely issue with the nvidia driver (maybe in combination with kernel) Try upgrading/downgrading nvidia driver first before upgrading/downgrading the kernel

@DiggerTigger does it reliably happen on specific spots? if so could y ou point them out?

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-3360024763

Not sure how relevant this is, but I consistently experience intermittent crashes when I have a controller plugged in. I bring this up because the timespan you've mentioned lines up with the release of Silksong, and I imagine many of us have left our controller plugged in while switching from that game to this one. I find that Hunt is substantially more stable if I unplug my controller before launching.

Running on AMD and Linux Mint it's still like this, it can take up to 10 min for stuff to load in and sometimes it straight up doesn't

Random application crashes during games of Hunt: Showdown. The game will freeze and it is usually when entering a compound or building. I have copied @DiggerTigger's description to an extent below it is so similar to what I see. I am not seeing crashes like this in other games that I've been playing regularly like Helldivers 2 and Deadzone Rogue for example.

The image will freeze, but some sound of the game is still audible (e.g. breathing of the character and gunshots.) This sometimes freezes the screen and I can't alt tab out of the game. A lot of the time this happens it requires me to hard reboot my PC. Discord will still let me chat to my teammates while the screen is frozen, so it's not a complete crash. In fact when trying to alt tab out of the game my teammates can hear me in Hunt. I've also had it eventually kick back to KDE after several minutes with an error that the graphics were reset. So it seems like Hunt is crashing my graphics.

I've run memory tests on both my ram and vram, both turned up without any issues. I actually think the ram mentioned in the errors above is vram, not system ram BTW. I'm also not seeing the frequency of crashes that I do in Hunt in any of the other games I have installed or have tested since this issue popped up when I started playing Hunt again in September.

I have found I can replicate the crash at will loading into the shooting gallery and following the path I have outlined in the screenshot below.

System Info:

• CPU: AMD Ryzen 5 5600G
• GPU: AMD Ryzen RX 7900 XTX
• Ram: 32GB DDR4
• DE: KDE Plasma 6.3.5
• WM: Kwin (Wayland)
• OS: PikaOS
• Kernel 6.18.2

Steps to reproduce:

1. Make sure v-sync is off in the settings
2. Go to shooting Gallery
3. Run to the left of the box with the shredder on it
4. Turn right and attempt to enter the fort
5. Game crashes usually by the time you're in the door.

The game still crashes with vsync on, but not every time like it does when it is off for me. I also have found that using an older kernel, 6.14.7 doesn't cause as many crashes either. However the game still crashes when using these options. No amount of fiddling with settings in game seems to change the frequency outside of setting v-sync on. I still crash basically every time I play the game for any length of time.

I also tested @Nicknakin's theory regarding it being a controller plugged into my system. I saw no change if my controller is plugged in or not.

Still need to get my logs up on my github to share. Sadly the game.log that Hunt produces doesn't have any valuable info in it, but my proton.log is filled with the same warning over and over again when I am in a match, including the shooting gallery.

Warnings that repeat endlessly in a match:

1405.898:017c:02b0:warn:vkd3d-proton:d3d12_device_GetResourceAllocationInfo3: Invalid resource desc.
1405.898:017c:02b0:warn:vkd3d-proton:d3d12_resource_validate_texture_alignment: Invalid resource alignment 0x1000 (required 0x10000).

Then sometimes it hits this before repeating the above until I am out of a match. Then it stops producing a bunch of warnings.

1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 16 x 16 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 16 x 16 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 8 x 8 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 8 x 8 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 4096 x 4096 x 1, 1 levels, 1 samples, fmt [#27](/issue/ValveSoftware/Proton/27), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 4096 x 4096 x 1, 1 levels, 1 samples, fmt [#27](/issue/ValveSoftware/Proton/27), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 5120 x 5120 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 5120 x 5120 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 3692 x 3692 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 3692 x 3692 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 8 x 8 x 1, 1 levels, 1 samples, fmt [#27](/issue/ValveSoftware/Proton/27), flags #2).
1405.908:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 8 x 8 x 1, 1 levels, 1 samples, fmt [#27](/issue/ValveSoftware/Proton/27), flags #2).
1405.910:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 512 x 512 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.910:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 512 x 512 x 1, 1 levels, 1 samples, fmt [#13](/issue/ValveSoftware/Proton/13), flags #2).
1405.911:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 2048 x 2048 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).
1405.911:017c:02b0:warn:vkd3d-proton:vkd3d_get_image_allocation_info: Padding allocation requirements. Requested alignment 65536 < 131072 (dim 3, 2048 x 2048 x 1, 1 levels, 1 samples, fmt [#35](/issue/ValveSoftware/Proton/35), flags #2).

@jonstump no luck here, either from that route in shooting range nor from bounty hunting. Grahpics set to high, sync off, proton experimental, linux 6.18.2, plasma 6.3.5. But I have a 9060 XT.
Last time there were some game freezes it was caused by people having both radv and amdvlk at the same time. Can you check if you have both? and if so, uninstall amdvlk

@simifor amdvlk is not installed on my system. I checked both apt and vulkaninfo. Apt says it isn't installed and vulka shows the radv drivers are being used.

WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -9 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_dzn.so. Skipping this driver.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.309


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 13
---------------------------
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64)               1.3.221  version 1
VK_LAYER_INTEL_nullhw              INTEL NULL HW                                                1.1.73   version 1
VK_LAYER_MANGOHUD_overlay_x86      Vulkan Hud Overlay                                           1.3.0    version 1
VK_LAYER_MANGOHUD_overlay_x86_64   Vulkan Hud Overlay                                           1.3.0    version 1
VK_LAYER_MESA_anti_lag             Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303  version 1
VK_LAYER_MESA_device_select        Linux device selection layer                                 1.4.303  version 1
VK_LAYER_MESA_overlay              Mesa Overlay layer                                           1.4.303  version 1
VK_LAYER_MESA_screenshot           Mesa Screenshot layer                                        1.4.303  version 1
VK_LAYER_VALVE_steam_fossilize_32  Steam Pipeline Caching Layer                                 1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64  Steam Pipeline Caching Layer                                 1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32    Steam Overlay Layer                                          1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64    Steam Overlay Layer                                          1.3.207  version 1
VK_LAYER_VKBASALT_post_processing  a post processing layer                                      1.3.223  version 1

Devices:
========
GPU0:
        apiVersion         = 1.4.328
        driverVersion      = 25.3.2
        vendorID           = 0x1002
        deviceID           = 0x744c
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon RX 7900 XTX (RADV NAVI31)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 25.3.2 - PikaOS YellowBirb Mesa Stable (git-3848a08053)
        conformanceVersion = 1.4.0.0
        deviceUUID         = 00000000-0300-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000
GPU1:
        apiVersion         = 1.4.328
        driverVersion      = 25.3.2
        vendorID           = 0x10005
        deviceID           = 0x0000
        deviceType         = PHYSICAL_DEVICE_TYPE_CPU
        deviceName         = llvmpipe (LLVM 19.1.7, 256 bits)
        driverID           = DRIVER_ID_MESA_LLVMPIPE
        driverName         = llvmpipe
        driverInfo         = Mesa 25.3.2 - PikaOS YellowBirb Mesa Stable (git-3848a08053) (LLVM 19.1.7)
        conformanceVersion = 1.3.1.1
        deviceUUID         = 6d657361-3235-2e33-2e32-202d20506900
        driverUUID         = 6c6c766d-7069-7065-5555-494400000000

Select Proton Experimental Bleeding Edge in the game Compatibility options (to set Proton Experimental on the Bleeding Edge branch, check its own settings in Steam).
Reset everything by renaming these folders (for safekeeping in case):

~/.local/share/Steam/steamapps/common/Hunt Showdown 1896/USER/ -> ~/.local/share/Steam/steamapps/common/Hunt Showdown 1896/USER_OLD/
~/.local/share/Steam/steamapps/compatdata/594650/ -> ~/.local/share/Steam/steamapps/compatdata/594650_OLD/

Verify game files integrity in Steam.

Start the game to regenerate the Proton prefix with latest Proton, and regenerate the game USER profile.

See if it works now with everything fresh, and if so you had something corrupted somewhere in your files.

I wanted to come back and give an update that I believe I have found the setting that has resolved my crashing after a couple weeks now without seeing any. Hunt has also seen updates so it is possible that also helped.

After some testing I found if I use a frame limiter to keep the game one frame per second under my monitor's refresh rate I don't seem to see crashes. I suspect this was why I saw less crashing with vsync but didn't see it go away. Not sure why this was resulting in crashes the way it did, but I haven't had a crash in a couple weeks since testing frame limits under my monitor's refresh rate.

Hunt has also seen updates so it is possible that also helped.

Revert what you have done and see if crashes are back, this way you know what helped.

The game sometimes goes to a black screen when I alt tab on KDE Wayland. Audio still works but I can't see anything so I have to restart it. I have an RX 6600 XT. Anyone else experience this?

After the 2.7 update I'm no longer able to run the game with PROTON_USE_WAYLAND=1

The game hangs on the Crytek loading screen and I can just hear sound

Previously I'd been running the following commands

WINEDLLOVERRIDES="winepulse.drv=d" WINEALSA_CHANNELS=2 gamemoderun LD_PRELOAD=$LD_PRELOAD:/usr/libgamemodeauto.so.0 PROTON_FSR4_UPGRADE=1 PROTON_ENABLE_HDR=1 PROTON_USE_WAYLAND=1 ENABLE_HDR_WSI=1 DXVK_HDR=1 PROTON_USE_NTSYNC=1 %command% -USEALLAVAILABLECORES

The attached log running with just PROTON_USE_WAYLAND=1

Without PROTON_USE_WAYLAND=1 I have to switch focus to get the menu showing

been using Proton-GE Latest

steam-594650-proton.zip

@LukeDearden this issue tracker is for upstream proton, issues with forks should be reported to their corresponding support channels

When running Hunt after the 2.7 Update it appears that xalia is causing issues. With it running I can't use my keyboard, but if I kill the process my keyboard starts working again.

Hmm I've tried a few versions of Proton, including older ones that I didn't see xalia start up and it didn't seem to resolve the issue when booting the game. I think Crytek changed something related to inputs that seems to be breaking on Proton.

After trying 8, 9, 10, Experimental, and Hotfix versions of Proton non of them worked. Either the game wouldn't boot normally or I wouldn't get inputs until I killed all xalia processes running. Just to see if there was any version of Proton I could find that resolves this issue I tested several forks as well. CachyOS's fork, and those based on it, appear to be the only working solutions that don't require me having to kill the xalia processes in order to get inputs working on Hunt Showdown.

@jonstump Interesting - I'm getting no keyboard input on launch, but as soon as I alt+tab to lose/regain focus, it fixes the keyboard input. Do you have any peripherals plugged in (controller, etc)? If so, which ones?

Also, what is "Window Mode" set to in your graphics settings? And could you also copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report?

Edit: in the meantime, in theory you can use PROTON_USE_XALIA=0 to disable xalia.

I had absolutely no issue for multiple hours.

Full AMD system, on Manjaro KDE, Proton Experimental Bleeding Edge.

I had absolutely no issue for multiple hours.

Full AMD system, on Manjaro KDE, Proton Experimental Bleeding Edge.

I guess you're not using PROTON_USE_WAYLAND=1 though right?

Indeed I use X11.

//EDIT: after many more games, I notice on launch often that I have no keyboard input, but if I lose focus and get focus back inputs work. Similar issue then I guess.

@jonstump

I’m experiencing the exact same issue, but on an NVIDIA GPU. The game freezes during gameplay (most often when entering compounds or buildings), while audio continues playing. In many cases, I have to do a hard reboot. My logs also show the same repeating vkd3d-proton warnings related to resource alignment.

I tried several things (different Proton versions, graphics settings tweaks, kernel versions, etc.), but none of them reliably fixed the problem.

What fixed constant freezes for me was changing NVIDIA settings:

Switched from On-Demand to Performance mode
(NVIDIA Settings → PRIME Profiles → NVIDIA Performance Mode)

Disabled OpenGL Flipping
(OpenGL Settings → uncheck “Allow Flipping”)

Maybe this will help someone else.

@alasky17 - Alt tabbing seems to be working on its own for me. No need for flags or killing processes.

@serhiidankovych - I haven't had this issue in a while and what seemed to fix it for me was using Mangohud to set a fame limit 1 fame per second lower than my monitor's refresh rate. Not exactly sure why that fixed it for me, but that's what seemed to do it in my case.

There's a keyboard input problem appearing on Wayland with newer versions of Proton. Linking here for visibility:

[Wine-Wayland] Hunt: Showdown 1896 does not register any keyboard input
https://github.com/Etaash-mathamsetty/Proton/issues/109

[Compat]: In Hunt Showdown 1896, in a version newer than proton-cachyos-10.0-20260425-slr-x86_64_v3, not a single keyboard key works.
https://github.com/CachyOS/proton-cachyos/issues/169

@CoenTurk hmm so far I haven't had this happen in several (solo) matches with my 9070, borderless and fullscreen behaved the same on my end with plasma wayland. Do these issues also happen when in practice mode?
Also, just a FYI, but protontricks is a separate project made by third parties, when asked about proton version, what you were using in this case was experimental.

I'm curious if trying experimental again but with a new prefix (you can just delete the existing folder) still has the issue for you.

@simifor I havent seen this happening in practice mode. Im not sure what you mean by a new prefix. Could you go into more detail so I can try it out for you? And do you want me to test further in practice mode? or in competitive modes?

@CoenTurk a prefix is just a folder with the basic file structure expected by most windows programs, proton makes a prefix for each game, in this case yours should be at /home/coen/.local/share/Steam/steamapps/compatdata/594650, and when the folder is missing it's just remade from scratch by proton when you next run the game

Yeah, it was the kernel. Downgrading to 7.0.12-1-cachyos and using GE-Proton11-1 seems to have solved the stuttering issue for me.

@CoenTurk a prefix is just a folder with the basic file structure expected by most windows programs, proton makes a prefix for each game, in this case yours should be at /home/coen/.local/share/Steam/steamapps/compatdata/594650, and when the folder is missing it's just remade from scratch by proton when you next run the game

Excuse me for my late reply, I have been a little busy but I found some time today to do some testing.

• First I tested with 11 again, oddly enough the freezes appeared again. Maybe I need to downgrade for that like @HereticWay mentioned.
• Then I used experimental again and deleted the folder. My first game was flawless. I will try some more. If anything happens I will let you know.

Just played a couple other matches in bounty clash with experimental. Sometimes I experience a little bit of stuttering, but its not something I would be bothered about.

Let me know if I can do anything else for you.

I see that you are all using cachy's build of the kernel, and there was a report of marvel rivals issues that turned out to be specific to cachy's build. I'd recommended using 7.1.3 but from arch itself and see if the performance issue goes away

Replying to https://github.com/ValveSoftware/Proton/issues/3898#issuecomment-4979421220

@kisak-valve is there anything I can do to help solve this problem?

I see that you are all using cachy's build of the kernel, and there was a report of marvel rivals issues that turned out to be specific to cachy's build. I'd recommended using 7.1.3 but from arch itself and see if the performance issue goes away

Tested the game with the arch kernels (linux; linux-zen) and they also do not have the stuttering issue.