Hunt: Showdown 1896 (594650)

[r3l0c]

Compatibility Report

• Name of the game with compatibility issues: Hunt Showdown
• Steam AppID of the game: 594650

System Information

• GPU: AMD Radeon HD5700
• Driver/LLVM version: Mesa 20.2
• Kernel version: 5.6.0-050600-generic
• Link to full system information report as Gist:
• Proton version: Any version

I confirm:

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

PROTON_LOG=1 %command% steam-594650.log

game.log game.log

Symptoms

If proton version lower 4 then black screen and process info in task manager: kernel wait "pipe_read"
if proton version > 4 then Easy Anti Cheat cannot run with message box ERROR: Failed to create EAC game client interface.

Reproduction

Game not run any times, no need special reproducer

[KinLux]

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

[McMarius11]

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

[mercifulboss]

Any updates on EAC support for this game?

[JCDentonCore]

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

[koloved]

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

[arne-fuchs]

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

[koloved]

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

[arne-fuchs]

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

[arne-fuchs]

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

[arne-fuchs]

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

[koloved]

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

[arne-fuchs]

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"

[LukeDearden]

@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]

Hunt Showdown (594650)

Issue transferred from #6549.
@LukeDearden posted on 2023-02-18T07:16:59:

Compatibility Report

• Name of the game with compatibility issues: Hunt Showdown
• Steam AppID of the game: 594650

System Information

• GPU: GTX 1660 Super
• Driver/LLVM version: NVIDIA 525.89.02
• Kernel version: 6.1.11-200.fc37.x86_64
• Link to full system information report as Gist: https://gist.github.com/LukeDearden/ce60bf094640431cd332c0597f32d030
• Proton version: Experimental

I confirm:

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

Symptoms

Game starts out looking fine but then textures stop loading and the graphics look blobby. Some kind of LOD issue

Adjusting graphics settings (memory usage target/texture quality) doesn't help

Reproduction

Play a round of Bounty Hunt and traverse the map

---

@LukeDearden commented on 2023-02-18T07:30:47:

I'm unable to attach files to this issue for some reason

---

@an9949an commented on 2023-02-18T08:03:03:

The same on my RTX3050 mobile. Issue start happens when vram usage go close to the maximum (2 minutes of gameplay on minimal textures). Also I can see that VRAM usage is much much higher than on windows (~1.4gb more on the same settings).

[an9949an]

@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.

[WebsiteDeveloper]

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

[arne-fuchs]

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

[kisak-valve]

Hunt: Showdown (594650)

Issue transferred from #6569.
@SamPurple22 posted on 2023-02-25T12:39:37:

Compatibility Report

• Name of the game with compatibility issues: Hunt: Showdown
• Steam AppID of the game: 594650

System Information

• GPU: Radeon RX 7900 XTX
• Driver/LLVM version: Mesa 23.3.3
• Kernel version: 6.1.13-x64v3-xanmod1
• Link to full system information report as Gist:
• Proton version: Proton Experimental or 7.0-6 (and GE-Proton-49 and Proton 6.3 etc)
• Distro: Debian 12 (bookworm/testing)

I confirm:

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

Proton log: steam-594650.tar.gz

Symptoms

Game starts and works for offline play, like Tutorial mission or Trial mission. Does not work for online play, Bounty or Quickplay. When trying to play online you always need to choose your network regions, and it does not move forward from there.
The choose your network region dialog is also missing the ping, latency indicators on the buttons.

Reproduction

Install the game, start it, try to play online. Cannot see latency indicators on select network region dialog. Cannot start online game.

Additional info found in game.log:
<11:53:34> [Hunt Online] [Account] Initializing.
<11:53:34> [Hunt Online] [Online Account] Platform initializing: waiting for authentication token.
<11:53:35> [Hunt Online] [Account] Initializing online services for client with 'live' settings
<11:53:35> [Hunt Online] CProfileInboxService::Init: successfully initialized
<11:53:35> [CryCloud] Trying to establish connection with 'capi1-lv-lw-wc.huntshowdown.com:61088' open
<11:53:35> [CryCloud] Connection Succeeded
<11:53:41> [CryCloud] Sending request: Invoke (0x01000000) remotely on server with messageId = 1, grainId = 0, bodysize = 528
<11:53:41> [CryCloud] [Warning] Obtaining RTT of TCP connection is not supported
<11:53:42> [CryCloud] RECV messageid: 1
<11:53:42> [CryCloud] [Client Session] Authentication succeed

gamelog.tar.gz

[SamPurple22]

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.

3. 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" ?

[larsgrah]

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:

• 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

[grego9]

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

[an9949an]

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.

[LukeDearden]

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.

[supertriodo]

It's a visual nightmare on my 1060 3GB

[jclc]

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

[Nicknakin]

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

[runar-work]

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

[Zorrototo]

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.

[LukeDearden]

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

[alasky17]

@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]

@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

[alasky17]

@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 :)

[LukeDearden]

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

[LukeDearden]

Proton Experimental-9 working fine

[wereii]

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.

dmesg:

[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]

Hello @wereii, can you check if the NVIDIA 575 series driver has the same behavior? NVIDIA XID 69 is categorically a hardware or video driver issue.

[wereii]

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

[DarkArc]

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.

[Zorrototo]

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. #2726 (comment)

[Maselkov]

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.

[Zorrototo]

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

[razzeee]

Replying to #3898 (comment)

not being able to map some keys always was a problem, but proton 10 seems to change something. See #3898 (comment) 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

[Zorrototo]

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.

[razzeee]

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

[Zorrototo]

Yes it fixed the issue with the keybinding with FR keyboard layout key not working #3898 (comment)

[razzeee]

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.

[Zorrototo]

Report maybe here #8658

[alasky17]

@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 #8658 as I'm still going to keep investigating the remaining issue with Rising Storm 2 as well there 👍