VR mode fails similarly here (log). There's no OpenXR crash.

The issue is that the game is rendering to its own window (the initial desktop window) rather than using the proper API.

I can't get the game to use VR without SteamVR running, and I haven't been able to get SteamVR to “let go” of the headset display (i.e. not be able to claim the DRM lease) for long enough to be able to set up the headset as part of the desktop (via xrandr) and move the window to the headset display (which I've not successfully done as yet).

Seems to me that application of an appropriate cluebat to IOI is needed. Which is unfortunate…

There might be a regression with Proton that breaks Hitman 3.

When starting the game today, Steam downloaded a small update. I don't think it was one for the game but rather Proton (there's none that I'm aware of for the game and both Hitman 3 and Proton were listed together in the download manager).

When starting the game with Proton Experimental or Proton GE, the launcher displays fine but when clicking on "Play game", it doesn't start and Steam's "Play" button goes back from blue to green.

Using Proton 7.0-2 seems to work fine, the game starts properly, so I would assume that the issue comes from a recent change (upstream?) that occured in both Proton Experimental and Proton GE.

I've put both in the same gist: https://gist.github.com/terzag/91fc7b6d147bcc74054afa83df0884cc
(System infos are in french as my Steam is in that language, tell me if it's an issue and need it in english.)

If that matters, I use Steam as a flatpak (on Ubuntu 22.04, flatpak version is recent enough to use the original Proton Experimental and regular version, they're not the flatpak packages). As you can see in the log, Hitman 3 is installed on a secondary partition, it's an EXT4 one.

I think I see: on Ubuntu 22.04, I have Mesa 22.0.1 but from what I understand, the flatpak Steam package use its own Mesa package/runtime which is currently at 21.3.8, so that would explain the issue.

Out of curiosity, is that a recent change in the VKD3D build? The game worked fine yesterday with Proton Experimental, it broke with an update today.

Edit: this issue was fixed by updating Mesa drivers!

There's one radio upstairs in soldier barracks room "The Ark Society" mission that crashes my GPU. Nothing else does that. Really weird. Happens both wayland and x11.

System info:

Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.11-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15,6 GiB of RAM
Graphics Processor: AMD DIMGREY_CAVEFISH

Edit: sorry I wasnt clear enough, following happens:

1. Activate the HAM radio on table in The Ark Society mission. It's in upstairs of the castle in one of the guard barrack rooms.
2. The game plays sounds but both of my screens freeze the last seen frame. Nothing moves.
3. I can open another TTY screen and kill the game from there.
4. Switch back and the screens stay frozen, still showing the game screen.

Now that I think of it, this may be related to something else too because my RDP clients can crash my GPU in similar way sometimes...

What do you mean by "crash your GPU"? There seems to be issues where the game freezes randomly since the last update (not specific to Linux/Proton), is it what you're experiencing?

I udpated my earlier post

Since the May update, Hitman 3 hangs, apparently at random, with the following log messages:

22255.557:0120:0130:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
22258.899:0150:01bc:err:sync:RtlpWaitForCriticalSection section 00000003BD9B5E40 "?" wait timed out in thread 01bc, blocked by 01b8, retrying (60 sec)
22258.899:0150:0230:err:sync:RtlpWaitForCriticalSection section 00000003BD9B5F60 "?" wait timed out in thread 0230, blocked by 01bc, retrying (60 sec)

This can happen almost immediately on launch, or after many minutes of normal play. It appears to be more likely to happen when tabbing out of the game, but does not require it.

(Is it appropriate to report this as a comment on this issue, or should it be a separate issue?)

Compatibility Report

• Name of the game with compatibility issues: HITMAN 3
• Steam AppID of the game: 1659040

System Information

• GPU: GeForce RTX 2080
• Driver/LLVM version: NVIDIA 515.49.05
• Kernel version: 5.18.6.1
• Link to full system information report as Gist: https://gist.github.com/Unser395/174d15233a473dcac059c68e02a35ba7
• Proton version: Proton 7.0.3 and Proton 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

With proton 7.03, The game freezes in the main menu or during the loading screens when the game is launched. The sounds keeps on working but the image freezes.
With proton experimental, it will occur during gameplay.
Proton 7.0.3 log :
steam-1659040.log
Proton experimental log :
steam-1659040.log

As it is, the game is unfortunately unplayable for me.

Reproduction

Launch the game. The freeze will always come.

Game appears to be rather unstable and crashes consistently or at random either in-game or in menus.

Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ASUSTeK driver: nvidia
    v: 515.48.07 arch: Pascal bus-ID: 01:00.0
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2 driver: X:
    loaded: nvidia gpu: nvidia resolution: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.48.07 direct render: Yes

steam-1659040.log

System Information

GPU: GeForce GTX 1070ti
Driver version: NVIDIA 470.129.06
Kernel version: 5.15.50-1
Working Proton 6.3-7
Current Proton 6.3-8

Symptoms

Before a recent Hitman 3 and Proton 6.3 Update it (6.3-7) worked perfectly while 7.X gives me constant graphical glitches and Experimental Crashes on load (no popup). Now 6.3-8 gives me a crash (possibly related to SteamVR (not installed, but also the VR Mode is not activated and i don't even have a VR device connected)) when starting the game after the initial popup
Full log: Gist

I am currently trying:

• Installing SteamVR
• Different Nvidia Driver
• Commandline options to disable VR
• Different Kernel
  And combinations

Edit: with a Combination of newer drivers and SteamVR i got it working again, i will test what made the difference and come back with a solution that hopefully works for @Unser395 too
Edit 2: No idea. Used it with the newest NVIDIA Drivers, Proton 6.3-8 and "-vrmode none" as command line arguments, sometimes it works, sometimes it doesnt. Pressing play 2-3 times before it works happens. Make sure to disable Exclusive Fullscreen (in the pregame launcher) or Alt-Tabbing will crash the game. Then it works pretty well (80% of the time it works all the time)

I tried something out with not being able to Alt+Tab away from the game which involves adding a Registry Key. I believe this RegKey should be included in Proton for future releases, because this appears to fix the Alt+Tab issue outright.

Open RegEdit with Protontricks and add the following;

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"UseTakeFocus"="N"

This stops the games from stealing focus and allows the user to Alt+Tab away without issue. While that's one side of an issue fixed, it's still broken in terms of stability and performance as per my previous post. The game seems incapable of running in DX11 or DX12 because it says it can't find the specific DLL files for running it.

As a data point, I'm here to report that neither Proton GE 7-27 nor the July Patch helped the freezing issue.

So, I've been having crashing issues as well since the May update. I'm on KDE Neon.

But lately I've been testing the game out on my Windows 10 setup (latest Windows updates installed and latest Nvidia driver installed), and it actually seems to crash randomly there sometimes too. Although it seems worse on certain maps... On Chongqing for example, I get consistent crashes on that map. Other maps seem fine though. I played the new Ambrose Island map for like 6 hours straight without any crashes.

So I guess perhaps it is a deeper issue than just Proton...

The most frustrating thing is I haven't even seen any acknowledgement of the issue from IOI. Nothing on the known issues page, no mentions of it in the patch notes, nothing. So we don't really know if they are even aware of the issue right now.

They're aware of it and have mentioned this on Reddit I think. Basically, their stance is "all the reports of crashes we have since the may update are from PC players using Windows 11 and the requirements on the store page list Windows 10, it's the only version we support."

This, despite other reports (e.g. PS4 and a few Windows 10 −and of course Linux, though they don't support it so won't care) but they probably consider they're specific cases with faulty installs or hardware.

EDIT: and indeed, there's probably nothing that can be done with Proton to address this.

When I emailed support of these freezing/crashing issues this is the response I got from them;

I'm Adrian from the HITMAN 3 Support team.

I understand that you are attempting to play HITMAN 3 on Linux. If this is the case, it means that your computer does not meet the minimum system requirements in order to play the game, which at this time include Windows 10. While we would like as many players as possible to enjoy the game, we cannot guarantee a smooth performance or functioning of the game on a machine that does not meet these minimum system requirements (as they can be seen on the game's store page).

I know this is probably not the resolution you were hoping for, but technological limitations are definitive and they are not something that can be altered. With that in mind, do let me know if there is anything else I might assist you with.

All the best,
Adrian
HITMAN 3 Player Support

regardless of the "You PC does not meet the minimum recommends" jargon, completely dismisses the fact that this is STILL an issue with the game itself, despite being a "Steam Deck Verified" title, which should still extend to working on Linux as a whole. Most users report that the game runs fine on Steam Deck, but running on mainline Linux desktop does not work properly. It's this kind of abysmal support from game dev studios who have this kind of attitude towards Linux that really brushes the wrong way. You don't have to fully support Linux just for a game to work, but make changes to Windows specific DLLs that the game uses and in-game engine thats the main issue for these games when they don't work.

@alkaris2 Yeah, even mentioning Linux is a bad idea. That will shut down any possible support right from the start. It seems it is an issue with Windows in general anyway so no need to mention Linux really.

I just read the August roadmap and they don't even mention a game update in it, so that definitely doesn't bode well for a fix anytime soon. :(

I just read the August roadmap and they don't even mention a game update in it, so that definitely doesn't bode well for a fix anytime soon. :(

The next big update will probably be with the release of the Freelancer mode, later this year (no ETA).

Now I'm curious about one thing alkaris2 mentioned:

Most users report that the game runs fine on Steam Deck, but running on mainline Linux desktop does not work properly.

Are there any reports of similar freezes on the deck? If not, any idea of what would differ that could explain that the game freezes on desktop?

@terzag See the reports on ProtonDB - Hitman 3, I notice other reports saying crashes also happen on Windows, so it's not Proton issue specifically, and it's to do with the ray-tracing support that was added to the game.

Yeah, I know it's not a Proton issue but if there are no freezes on the Deck (on ProtonDB there are only two reports, which isn't relevant), there might be some setting, hardware config, or even software versions on SteamOS that at least mitigates the issue.

There was one section in H3 where there was consistent crashing on Proton Experimental (Haven Island Server Room going up stairs in back left near the window). I used Proton 7.04 Testing and it didn't crash and I was able to finish that level. However 7.04 does crash when there's a PIP notification when detected by cameras. The crashing is way worse on 7.04 since its a system crash and requires a reboot.

The crashing is way worse on 7.04 since it's a system crash and requires a reboot.
That sounds like a graphics driver bug.

Is there anything relevant from the time of any of these crashes in the kernel log (/var/log/kern.log or wherever systemd puts it)? (If it's a hard hang then you'll need to use netconsole to have a chance of getting anything.)

Got some time to test this again after some updates to HoloISO and Hitman 3 have come out, but still having the issue. Attaching some logs and my journalctl output if it helps: steam-1659040.zip

Launching from the Steam Deck UI (gamescope?) causes the game and the mangohud output to freeze almost instantly. I tried switching to desktop mode and was able to launch the game from there and got into a level, but it still froze after about 15 minutes.

I also briefly tried on another PC (R9 3900X, RX 580, 32 GB RAM) running Manjaro and using a KDE-wayland session, and was playing for a bit, but maybe it wasn't long enough to cause a freeze. The next time I get the chance I'll try again.

Still having crashes with Proton-Experimental here's the output of my Steam log steam-1659040.zip

Saved at a portion of the game right before it crashes in the cellar in Sapienza.

Using Experimental-BleedingEdge it looks like crashing is at acceptable levels if not completely gone. No longer crashing every play session.

Not for me. Even with Experimental-BleedingEdge I'm still getting crashes as usual pretty much. Running KDE Neon with all the latest updates available, Steam with all updates, etc.

I have noticed though that running on Windows 10 mostly works lately. It only crashes in specific situations, like when wearing the Analyst disguise on Chongqing. So it does seem to be a Proton issue when it comes to Linux.

@Mezentium Did you do anything else special on your setup besides just switching Proton to Experimental-BleedingEdge? Like do you have certain launch parameters, etc?

@jamesdimick looks like latest update to experimental led to a regression, its crashing again. At least on Haven Island. I was pretty much able to play all weekend without a crash on levels that previously had crashed often like Dubai and Carpathian Mountains (to the point of getting full Mastery). I've also tried non bleeding edge and that still crashes a few minutes in. I'll try the levels that didn't crash and see if they're crashing with current bleeding edge.

FWIW I'm running Artix Linux 5.19.2 with AMD CPU and an AMD 5500XT. No launch params.

Tested again today on HoloISO after downgrading the mesa and radeon drivers with sudo pacman -S jupiter-main/mesa jupiter-main/lib32-mesa jupiter-main/vulkan-radeon jupiter-main/lib32-vulkan-radeon. I also installed an update for wayland and wayland-32 from 1.20.0 to 1.21.0.

Hitman 3 no longer freezes right away, but froze 2/3 times about 10 minutes into playing. The session that didn't freeze, I played for maybe 30 minutes.

Seems there are few issues if using AMD, but if using Nvidia crashes are more common and frequent where the game will completely freeze hang, but everything else like game audio still plays as normal as if nothing is wrong. Would be useful if a cause is found for these freeze crashes other than just blaming Proton. There has to be an underlying issue with the games code to trigger the crash in the way it does. Can't play Introduction stage without crashes, couldn't play any other stage for that matter either without the freeze crash, not even Proton logs are all that helpful at pointing at what causes it, which would lead to believe it's not a Proton issue.

To me it's clearly an issue with the game, as it appeared after a specific patch (end of may). Never happened before that in 200+ hours.

I've had problems with vanilla Experimental, I've been using Experimental Bleeding Edge and so far its been good. Just finished the elusive target and didn't crash.

The game is still as unplayable as it was months ago for me, even on Bleeding Edge.
From what I've seen here and on Proton DB, it does seems like the game works better for people with an AMD GPU/CPU. There's probably an issue with the game as well, as @terzag mentioned.

Does Valve ever give feedback on what is happening with these kind of issue? Do they ever ask players to do another log, or are we usually in the dark until the problems are fixed?

FWIW I've been able to play long sessions recently without freezes (with AMD CPU and GPU) but they're still there, happening at random. I've always been under the impression that they happen more in specific maps (for me, Paris mostly, Sapienza a bit and Berlin occasionally; I'm not sure I've had freezes in other maps). And maybe when doing specific things, like triggering some animations, or when looking at a specific angle in some rooms.

For people who have frequent freezes and can usually trigger them quickly, do they happen if you start a mission (let's say in Paris) and just do nothing, just wait at the start without moving (not even the camera)?

There's no feedback from Valve on this issue AFAIK but given that the logs don't seem to provide relevant information on the freezes, it would be difficult to get feedback.

Just some additional data: At least for me, the recent October update doesn't fix it. Tried Proton GE7 37 and Proton Experimental.

Actually, for me the Update made Proton 6.8 very unstable (bad performance, weird resolution etc) but 7.x works pretty well

Am 09.10.2022 um 18:32 schrieb Félix Pelletier @.***>:


Just some additional data: At least for me, the recent October update doesn't fix it. Tried Proton GE 37 and Proton Experimental.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

I had the same issue as some other users here where the game would freeze mid-game frequently but the audio is still running, and I think I have found a fix (at least without any freeze so far). I am using the following configuration:

Steam launch options:
VKD3D_CONFIG=dxr11 PROTON_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% -dx12

Proton version:
Proton 6.3-8

Nvidia GPU Driver:
520.56.06

In-game Graphics Settings:
Fullscreen, V-Sync, Adaptive Supersampling Technique: Off, Ray Tracing

I am running Pop!_OS 22.04 with Linux kernel 6.0.3 on Ryzen 5600X and RTX 3060. Please do comment and update if this list of settings works for you, and I will also comment whether freeze has happened again.

Replying to https://github.com/ValveSoftware/Proton/issues/5536#issuecomment-1304601144

I've tried these settings, adapting them a bit as I don't have a nvidia GPU (so, removed the last two env vars for NVIDIA-GPU and NVAPI) and while I've been able to play long sessions in the recent days, the issue just happened again.

I might also add that I've recently changed my GPU, went from a Radeon RX 560 to a RX 6500 XT and since then, when Hitman 3 crashes, it does not only freeze as before but completely crashes my GPU: I have to switch to a TTY where I get a series of "amdgpu_cs_ioctl failed to initialize parser -125" errors that continue indefinitely even after killing hitman3.exe, can't go back to the desktop session (black screen), I have to reboot.

I can confirm that the freeze is back again (though without the GPU crash part) for about a week or more even though it worked perfectly before.

Haven't had any time to investigate further, but since it's independent of the GPU driver or model, I can only suspect it has to do with Proton, Hitman or Steam. It seems Hitman was last updated on 30 October for me, so that mostly rules out Hitman, and Proton 6.3-8 was released ages ago so that's out too.

However, I have also upgraded my linux kernel to 6.0.6. @terzag Would you care to share your linux kernel version? Cheers

However, I have also upgraded my linux kernel to 6.0.6. @terzag Would you care to share your linux kernel version? Cheers

Using Xubuntu 22.10 with kernel 5.19.0.23 from its repos.

I have done a bit more digging around using sudo nvidia-bug-report.sh and found that every time the same error message pops up in the log:

Nov 21 13:25:40 pop-os-dekstop kernel: NVRM: Xid (PCI:0000:06:00): 109, pid=74450, name=hitman3.exe, Ch 00000023, errorString CTX SWITCH TIMEOUT, Info 0x11c00c
Nov 21 13:30:21 pop-os-dekstop kernel: NVRM: Xid (PCI:0000:06:00): 109, pid=78054, name=hitman3.exe, Ch 00000023, errorString CTX SWITCH TIMEOUT, Info 0x13c011
Nov 21 13:41:58 pop-os-dekstop kernel: NVRM: Xid (PCI:0000:06:00): 109, pid=82504, name=hitman3.exe, Ch 00000023, errorString CTX SWITCH TIMEOUT, Info 0x1bc011
Nov 21 14:11:12 pop-os-dekstop kernel: NVRM: Xid (PCI:0000:06:00): 109, pid=87930, name=hitman3.exe, Ch 0000004b, errorString CTX SWITCH TIMEOUT, Info 0x24c020

However I have not been able to find any information on CTX SWITCH TIMEOUT nor XID error code 109. Does anyone know what kind of error this is.

I might also add that I've recently changed my GPU, went from a Radeon RX 560 to a RX 6500 XT and since then, when Hitman 3 crashes, it does not only freeze as before but completely crashes my GPU: I have to switch to a TTY where I get a series of "amdgpu_cs_ioctl failed to initialize parser -125" errors that continue indefinitely even after killing hitman3.exe, can't go back to the desktop session (black screen), I have to reboot.

That's nothing to do with HITMAN 3. It appears to be a bug in amdgpu which causes the GPU reset. which I know confuses X.

The fact that you can switch to another VT is good – you can kill the desktop session from there (sudo killall -HUP Xorg, probably); or, from the desktop session, you should be able to log out blindly – I've done that a few times…

Have a look back through the kernel log (you may need to examine /var/log/kern.log* or use journalctl) for something like

[drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!

(you may also see some L2 protection fault status – also relevant). See https://gitlab.freedesktop.org/drm/amd/-/issues/2068#note_1459270 for example kernel log text. There are other, similar bug reports.

I also have the freezing issue. I have an nvidia gpu, and have tried using various version of Proton (Current, Experimental, and latest GE version), as well as various launch options I've seen in this thread. The freezes happen really randomly, sometimes I can go for hours without issues, other times it starts freezing within 10 min of launching. I tried turing on Proton Logging and next time it froze I checked the logs. There where a lot of warnings, but I saw a certain error level log close to the end of the log. Not sure if it has anything to do with the freeze, but I thought I would put it here in case it does and can help identify the issue:

53241.943:015c:0224:err:sync:RtlpWaitForCriticalSection section 00000003BD9C80A8 "?" wait timed out in thread 0224, blocked by 0220, retrying (60 sec)

53241.945:015c:0298:err:sync:RtlpWaitForCriticalSection section 00000003BD9C81C8 "?" wait timed out in thread 0298, blocked by 0224, retrying (60 sec)

I have finally found the reason for my freezes (woo-hoo)! The CTX SWITCH TIMEOUT error is caused by me over-overclocking the GPU offset frequency using GreenWithEnvy.

I discovered this as I was trying to push the limit of my GPU by incrementing another 5MHz, and then it would start to crash in less than 5 minutes rather than 15. After I lowered it from +175MHz to +160MHz, the freeze has completely disappeared, and I have finally been able to play a mission from start to finish lol. Interestingly, it didn't actually cause any issue in Unigen Heaven during stability testing, but since Hitman 3 is the most graphic intensive game I have, that makes sense.

For now, my configuration is now using VKD3D_CONFIG=dxr11 PROTON_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% -dx12 with GE-Proton7-42 (though I would expect normal proton would work just fine too, and RTX is still only available in version 6 not 7 for some reason) and Nvidia driver 525.

I think I finally solved my freezing issue. I tried a solution I found for random Crashing to Desktop, despite that not being exactly what happened, and I didn't have a single freeze in 2 game sessions of several hours each. I found a guide detailing solutions to frequent crashing with error 0x80000003, and one of them involved adding a new registry value, so I used Proton Tricks so I could access regedit on the prefix and added the value, and after that I haven't had crashes so far. Here is the value it said to add:

"Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"
Create a Key of type DWORD there named "TdrDelay", and give it the value "10" as it's Decimal value

According to the guide this increases the time the Driver has to respond, as the issue might be due to the driver randomly taking to long to respond and hitting a threshold.

Granted, I could be getting lucky with the last 2 gaming sessions, so there is a chance this didn't fix things. If the freezing comes back I'll update this, but it seems promising as I had been getting the freeze almost every hour for the past week while I tried to play, and haven't gotten it once with 2 3+ hour gaming sessions.

I am having really poor performance despite having a 6900 :cry:

Full specs and log of the game can be found here

Issue

• Performance for Hitman 3 is between 30-40 fps despite having a 6900 XT, the expectation being that it runs at least 60fps.
• Changing resolution of the game doesn't seem to change FPS much (windowed 1080p -> 1440p -> 5120x1440)
• Changing graphical settings doesn't seem to change FPS much either
• Exclusive fullscreen / fullscreen / windowed seems to make no difference
• Looking at the floor / sky gives ~5 fps more
• Different proton versions had no noticeable effect (used GE 7-43 (log file), experimental, various other versions)

Rough specs

• CPU: AMD Ryzen 7 5800 X
• GPU: AMD Radeon 6900 XT
• GPU drivers: Mesa 22.2.5
• Monitor: 5120x1440 (but I want to run the game at 2560x1440)
• OS: NixOS 23.05 (64 bit)
• Kernel: 6.1.1

The deadlock issue mentioned by many people here that manifests itself as a "frozen screen with continuing audio" and the following error in steam-1659040.log as:

1477672.177:0140:01d0:err:sync:RtlpWaitForCriticalSection section 00000003BD9C7838 "?" wait timed out in thread 01d0, blocked by 01d4, retrying (60 sec)
1477672.177:0140:0248:err:sync:RtlpWaitForCriticalSection section 00000003BD9C7958 "?" wait timed out in thread 0248, blocked by 01d0, retrying (60 sec)

Appears to have been fixed in Proton Experimental (as of 01/06/2023) due to the inclusion of fixes present in vkd3d-proton release 2.8.

The vkd3d-proton 2.8 Changelog notes:

Fixes a spurious hang in Hitman III where game relies on asynchronous present in order to not lock up.

I have tested this a bit and it appears to resolve the issue. The upgrade to vkd3d-proton 2.8 is not present in Proton 7.0-6 (current Proton Next). Fix will probably be in Proton 7.0-7 (or whatever version comes after 7.0-6), provided it is not reverted. One can only guess. Currently in Proton Experimental.

Would be interested to hear if other people experiencing this issue can verify resolution by testing the current Proton Experimental.

Refs:
https://github.com/ValveSoftware/Proton/wiki/Changelog
https://github.com/HansKristian-Work/vkd3d-proton/releases/tag/v2.8
https://github.com/HansKristian-Work/vkd3d-proton/issues/1248

I've been seeing this bug since I bought the game recently, the Dubai map being the most consistent offender for the crash, I just played that map for an hour without incident thanks to your tip.

Since I commented on this that it was working for me things took a turn, I don't have a current log at the moment but the game no longer runs at all with Experimental, it won't even start the launcher.

System info https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02
Proton log from Proton 7.05
steam-1659040-p705.log
Proton log from Experimental
steam-1659040.log

Any ideas on what I screwed up would be appreciated.

Sorry I've taken so long to get back, real world issues, vkbasalt was broken, I was using the script to install it & failed to notice a compilation error that stopped it working even though it still installed. I've got that fixed now but the Vulkan render paths you pointed out are still pooched, I've purged & reinstalled the nvidia drivers as well in case it was them.

Gamemode was also in a poor state so I rebuilt that while I was feeling industrious. new logs to follow.

Haven't read through the entire thread but this game is basically unplayable for me. Sometimes I can get in to watch intro cutscenes. Most of the time the game will freeze in a menu and then just crash out.

Just tried to play Hitman 3 after the recent update. Using Proton Experimental, still crashing.

I'm not sure this is the same issue or a new one, though, as I've tried to play in the new Freelancer mode and the game crashes as soon as I want to start a mission. Seems to be reproducible. I hear some plane take off audio when it crashes (but with image frozen in the gameplay part), so I assume it's playing a cutscene.

Also, as I've said in a previous message, with my current CPU I get a series of "amdgpu_cs_ioctl failed to initialize parser -125" errors, I'm not sure if that's a different crash that's specific to my hardware and if there's something I should try about it (updating the kernel? Mesa? I'm using Ubuntu, so I'm a bit reluctant on using 3rd-party repos for this kind of stuff).

Can somebody confirm if they can play the Freelancer mode or if it crashes when starting a mission too?

I've been able to play the Freelancer mode no crashes and decent frame rates. Not using any 3rd party repos or command line arguments when starting the application. Using Proton experimental (non-beta) I haven't had any crashes since September 2022. Framerates are surprisingly good at 50fps average (vs 30fps on Hitman 2). Note: Using Mesa 22.3

neofetch

                 'ooo'                    OS: Artix Linux x86_64 
                'ooxoo'                   Kernel: 6.1.6-artix1-1 
               'ooxxxoo'                  Uptime: 42 secs 
              'oookkxxoo'                 Packages: 993 (pacman) 
             'oiioxkkxxoo'                Shell: bash 5.1.16 
            ':;:iiiioxxxoo'               Resolution: 3840x1080 
               `'.;::ioxxoo'              DE: Plasma 5.26.5 
          '-.      `':;jiooo'             WM: KWin 
         'oooio-..     `'i:io'            WM Theme: plastik 
        'ooooxxxxoio:,.   `'-;'           Theme: Artix-dark [Plasma], Artix-dark [GTK2/3] 
       'ooooxxxxxkkxoooIi:-.  `'          Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] 
      'ooooxxxxxkkkkxoiiiiiji'            Terminal: konsole 
     'ooooxxxxxkxxoiiii:'`     .i'        CPU: AMD Athlon X4 845 Quad (4) @ 3.500GHz 
    'ooooxxxxxoi:::'`       .;ioxo'       GPU: AMD ATI Radeon RX 5500/5500M / Pro 5500M 
   'ooooxooi::'`         .:iiixkxxo'      Memory: 970MiB / 15938MiB 

vulkaninfo --summary

Devices:
========
GPU0:
        apiVersion         = 1.3.230
        driverVersion      = 22.3.3
        vendorID           = 0x1002
        deviceID           = 0x7340
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon RX 5500 XT (RADV NAVI14)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 22.3.3
        conformanceVersion = 1.2.7.1
        deviceUUID         = 00000000-0300-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000

My Mesa version is a bit older (22.2.1, there's 22.2.5 in the repos since a few hours, currently upgrading to test) but more than that, my kernel is quite older (5.19) and I'm wondering if it's recommended (or required) to use kernel 6.x for proper management of navi14 GPUs.

Looking at Distrowatch, Artix moved to 6.x around the time my crashing issues were resolved.

No change with Mesa 22.2.5 anyway. I'll try to upgrade the kernel to see, then.

EDIT: nope.

First tried to install kernel 6.1.8 → still freezing + GPU reset when starting a Freelancer mission.

Then tried to upgrade to Mesa 22.3.4 (most recent version I can get using a somewhat stable repo) → same, except that now the GPU somewhat recovers from its crash as I get back to the login screen without having to kill Xorg.

I've put a Proton log there in case someone can spot something wrong: https://pastebin.ubuntu.com/p/CK5yncXqry/

From the output it looks like you're using Radv instead of amdgpu (kernel driver). You can know for sure by running:
lspci -k | grep -EA3 'VGA|3D|Display'

AFAIK, I've always used amdgpu, seems to still be the case with the current configuration:

09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 24 [Radeon RX 6400 / 6500 XT]
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

One more thing, do you have vulkan-radeon and lib32-vulkan-radeon installed?

These don't exist as such on Ubuntu. I have Vulkan packages installed as well as a libdrm-radeon1 package and a xorg one (xserver-xorg-video-radeon). All packages are installed as 32 + 64 bit except for the xorg one which doesn't have a 32 bit build.

ah you're right I guess for Ubuntu the equivalent is: apt install libvulkan1 mesa-vulkan-drivers vulkan-utils

Yeah, they're installed, 32 and 64 bit. In theory, everything is fine regarding packages installed.

@terzag is your Steam client beta participation on, that broke H3 for me a while back:

No, regular version, no beta.

I've made a couple of changes to my setup, I switched to the nvidia 520 drivers & using Proton next 7.06 the game is running pretty much perfectly for me at the moment.
https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02

steam-1659040.log

I currently have a massive slowdown with experimental compared to Proton Next (7.0-6). Next is usually ~60 FPS while experimental is averaging less than 20 FPS.

System information: https://gist.github.com/uristdwarf/43f90f9147edef5fc3fa73417b2625a3
Experimental logs
steam-1659040-experimental.log
Next logs
steam-1659040-next.log
(Tested on the Dartmoor interactive benchmark)

vulkaninfo output
vulkaninfo.log

Hello @uristdwarf, your system is configured to use AMDVLK. Can you check how the game behaves with mesa/RADV?

That seems to have put it back to 60 FPS (even better than the performance on next with AMDVLK)

steam-1659040-experimental-radv.log

In any case, thank you for the advice to use RADV, I wasn't too familiar with vulkan drivers so I picked the one supported by the manufacturer.

I've been having the issue with the game freezing on Linux for several months now, and nothing I've tried (mostly from this thread) has worked. I confirmed when freelancer came out that it still froze frequently. However, I just upgraded from an Intel i5-9400F to an AMD 5800X3D, and now the game doesn't freeze (I've played a few syndicates with no problems.) It is possible that the CPU change fixed it. It is also possible that an OS/game/driver/Proton update fixed the issues. If you've been having freezing issues, you might want to run all updates and try again. If that doesn't work maybe it's something Intel-specific.

Other details:

• GPU: RTX3060
• OS: Ubuntu 20.04

For anyone who's having issues with abnormally low FPS, I've found that running the game with Plagman's gamescope solves it. Not the most elegant fix - Steam now hangs "waiting for the game to shut down" - but at least I can actually play the game now.

It is also possible that an OS/game/driver/Proton update fixed the issues. If you've been having freezing issues, you might want to run all updates and try again. If that doesn't work maybe it's something Intel-specific.

Well, in my case the freezes happen with an AMD CPU (Ryzen 5 1500X) + GPU (Radeon RX 6500 XT), so definitely not Intel-specific.

@terzag have you disabled SMT? I saw recently that was an issue and SMT should be disabled for some CPU loads. My setup doesn't have SMT.

@terzag have you disabled SMT? I saw recently that was an issue and SMT should be disabled for some CPU loads. My setup doesn't have SMT.

What's SMT and how do I disable it?

@terzag It should be in your bios.

Hitman 3 has a DLSS problem where enabling it results in severely incorrect behavior like this:

System Info Gist

@Mezentium So, I've checked in the BIOS (sorry, didn't have time to do it until now) and SMT was likely enabled (auto) so I forced disabling it but no change for Hitman 3, still the exact same crash.

Re: the greyed out RT options, I found this: https://github.com/HansKristian-Work/vkd3d-proton/issues/1148#issuecomment-1570914021

After setting vendor id to something bogus via dxvk.conf, e.g dxgi.customVendorId = ffff then I can enable both RT reflections and shadows in the game and they render correctly. This of course locks out enabling DLSS.

4070 Ti, driver 535.86.05
Nobara 38, kernel 6.3.12
Proton 8.0-103 (default)

frozen-sea:

This of course locks out enabling DLSS.

Can someone explain why setting the VendorId to ffff disables DLSS, but enables rt? Why does the stock 10de that dxvk sets here disable rt?

Oh and any idea why cyberpunk2077 has both rt and dlss, without adding a dxvk.conf file, but hitman3 doesnt, even though both games use directx12? Did the Cyberpunk devs do something on their side?

frozen-sea:

This of course locks out enabling DLSS.

Can someone explain why setting the VendorId to ffff disables DLSS

dxvk-nvapi checks that it's 10de

Why does the stock 10de that dxvk sets here disable rt?

Got no clue, but the commit that does it pre-dates Hitman 3 even having RT. FWIW, spoofing 1002 (AMD) instead of ffff has the same result for me, but might be different in actual AMD hardware. Could also be that AGS (AMD GPU Services) works just fine now and this is all outdated.

Oh and any idea why cyberpunk2077 has both rt and dlss, without adding a dxvk.conf file, but hitman3 doesnt, even though both games use directx12? Did the Cyberpunk devs do something on their side?

I have tested dozens of RT enabled games and no other has behaved like this, so it's more like Hitman 3 does something odd. Could be that Dirt 5 is also affected since it has RT and AGS workaround in dxvk, but I can't test that.

Would be interested to hear if other people experiencing this issue can verify resolution by testing the current Proton Experimental.

Sadly this one is still an issue for me @tshack: audio continues but video freezes. Log shows the same error as you've got there. Running Proton Experimental 8.0-20230822 and proton-vkd3d 2.9.0 (although I've tried on GE and stable too). I tried dropping all graphics settings to the lowest possible and still experienced this issue. Proton logs::

7720.410:0138:01d4:err:sync:RtlpWaitForCriticalSection section 000000039CD0CA98 (null) wait timed out in thread 01d4, blocked by 01d0, retrying (60 sec)
7720.440:0138:01a4:err:vkd3d-proton:dxgi_vk_swap_chain_submit_blit: Failed to wait for fence, vr -4
7720.440:0138:01a4:err:vkd3d-proton:dxgi_vk_swap_chain_present_signal_blit_semaphore: Failed to submit present discard, vr = -4.

Hitman 3 currently doesn't work for me, it'll show the Launcher and I hit Play, and then the game immediately exits. I have tried the -skip_launcher and the game immediately exits when it tries to run, so basically can't run the game at all.

I've tried running the game with DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12 %command% -dx12 and it does nothing. Created dxvk.conf with the dxgi.customVendorID = 10de set, I ensured I also had dxgi.nvapiHack = true and still doesn't work at all. Tried with multiple versions of Proton with no luck at all. It was last previously known working with GE-Proton7-42, but that is not the case anymore, even later versions did nothing, as it either results in game launcher popping up but hitting Play immediately crashes the game, or launcher never appears and runs indefinitely without doing anything but being hung up in a zombie process state.

The following log file shows for running under GE-Proton7-42, one extra thing I had to throw into the Launch Options was LD_PRELOAD="$LD_PRELOAD:/usr/\$LIB/libgamemode.so.0" because it wasn't properly detecting libgamemode.so.0 library file and would throw errors saying;

gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory

steam-1659040.log

Hitman 3 has a DLSS problem where enabling it results in severely incorrect behavior like this

DLSS works with no more artefacts (4070 Ti and GE-proton8-20). However, it seems the framerate has been capped to 60, while FSR can deliver 100-120fps.

VR still doesn't work on the latest version of Proton (tested on Experimental and 8.0-4). The game switches to VR mode, and responds to the movement of the headset, but there's no video in the headset.

Proton version: 8.0-4
SteamVR version: 2.0.9 beta

Attaching the log file.
steam-1659040.log

I just got my Steam Deck OLED and was disappointed to see that the HDR option in this game doesn't show up. The HDR option is there in the launcher but doesn't do anything, in-game the option just doesn't appear. I tried with the default Proton 8 and changing to Experimental but neither work.

@Mar2ck This seems to be a game bug, the HDR functionality does not work for me on Windows either.

It has the same symptom of it creating a HDR swapchain for the first frame and then going back do aRGB for the rest.

You have to be in Exclusive fullscreen for HDR to appear as an option in-game, but otherwise it works fine on my Windows PC for both my HDR monitor and TV.

https://github.com/ValveSoftware/Proton/assets/6759254/f10f8474-d484-4d80-a75a-456dc02beb1b

Edit (2024-07-09): HDR now works with Proton Experimental! Not sure when this happened but I'm glad it's been fixed.

Am I the only one who noticed physics issues playing Hitman? The problem is with rebounds: when I throw an object (like a coin) on the floor, it will rebound several meters in the air with huge force, which makes it impossible to predict where it will end up. The issue happens with any object, including bodies but to a lesser extent.

I've seen this issue since day 1 playing Hitman 3. It does not make the game unplayable but it sure is annoying. Hitman 2016, which had a native Linux port, did not have this problem.

Playing on Steam on Ubuntu 23.10 with amdgpu drivers.

While HDR works for me, I can't see the dark box in the gamma settings for HDR. It only shows a white box:

Logfile: steam-1659040.log
Sysinfo: https://gist.github.com/NoXPhasma/b8596ea576a20d55d687f3bd0de79e17

I found something interesting when messing around with the settings.
If V-Sync is turned off while a level is being loaded, and no other software is limiting the framerate, the load times are super fast. It also stops the textures from flickering. If I then turned on V-Sync after the level had loaded, it ran perfectly.

Is this of use for anybody? I'm using a 3080 Ti and SSD btw. Is there a way to automatically disable V-Sync while a level is being loaded and then re-enable when the level has loaded?

seemingly at random the game will freeze and crash my whole computer, i am using Proton GE 21 and here is some bits of the log i am using a Gigabyte Radeon RX 7600xt

I've also observed this. Most crashes are freezes in which the game's audio will continue playing for a short time, and maybe an extra frame also appear after a short delay, but this leaves the game stuck. Closing it freezes my system entirely for an short period. Some crashes (maybe 1 in 6) will lock up my system altogether.

Potentially similar reports at https://www.reddit.com/r/HiTMAN/comments/1hfw92o/the_game_constantly_freezes/ (including replies).

I myself am using Arch Linux with default proton, latest game version, KDE Plasma 6.2.5 and an RTX 2070.

Experiencing the same thing as @olib14 and that Reddit thread. Radeon RX 6800, Linux Mint 21.3, Proton Experimental

https://www.reddit.com/r/HiTMAN/comments/1i26l0a/possible_workaround_for_random_freezes_on_linux/

A suggested fix is to limit the framerate, and can be done in-game simply by enabling V-sync. It seems to be effective.

vsync was on

On Wed, Jan 22, 2025 at 11:57 AM Oliver Beard @.***>
wrote:

https://www.reddit.com/r/HiTMAN/comments/1i26l0a/possible_workaround_for_random_freezes_on_linux/

A suggested fix is to limit the framerate, and can be done in-game simply
by enabling V-sync. I have not extensively tested it but it seems to be
effective.

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

Not sure if it's just me (or if it's even really Proton), but I sometimes get issues where the game just disconnects from the servers during gameplay or when trying set hidden stashes for missions. :/

It doesn't always happen, but I've run into it consistently for the last hour when attempting to set a dead drop for Mumbai - Illusions of Grandeur specifically.

@ThisNekoGuy That will be issues with IOI servers. It happens from time to time where some things are inaccessible.

You should refer to https://hitmanstat.us for server issues which tracks the server status, they are not run by or affiliated with IOI and is just a public community site that is able to track this stuff.

Encountering a freezing issue when running Hitman World of Assassination, kwin with KDE Plasma freezes up and system becomes unresponsive temporarily, the game is still technically running, but everything is frozen and takes a while to unfreeze when Alt+Tabbing away from the game on start up. KWin will eventually crash and restart, I have it so when Steam launches games, it automatically disables Desktop Compositing, and only enables after the game exits.

It's of course NVIDIA driver related issue the NVAPI becomes unresponsive because it fails to initialize sometimes for unknown reasons despite driver being free and available for use, no other application is using it or taking priority. Reboots don't necessarily help either, because it still fails to initialize after startup.

Steam Launch Option:

PROTON_LOG=1 PROTON_LOG_DIR="/home/$USER/SteamLogs/" DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 PROTON_HIDE_NVIDIA_GPU=0 VKD3D_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=11  %command% -dx11

Steam Log: steam-1659040.log

Possibly related issue: (https://github.com/ValveSoftware/gamescope/issues/1247) except I'm not using gamescope here.

I was playing on the Haven Island map where I found that, upon picking up a remote explosive device found in the security room located in the center of the map, the game can crash. If I had to guess the reason why, I think it might have been audio related because normally a sound plays when picking objects up but it didn't play in this case and the crash followed immediately after. What I find odd, though, is that this crash seems inconsistent: this crash doesn't always happen when picking up the item. I'm not sure if it's a consequence of picking it up, restarting the level from the pause menu later, then coming back for it again afterwards but this crash is vaguely familiar because I think I've run into it before. 🤔

Distro: Gentoo Linux (OpenRC + 100% LLVM-built)
GPU: AMD RX 7800 XT (XFX MERC 319 BLACK)
Driver/LLVM version: Mesa 24.3.4 (LLVM19 w/ libc++)
Kernel Version: 6.10.9-tkg-eevdf-gentoo-llvm18-generic_v3
Proton Version: 9.0-4d
Proton Log: steam-1659040.log.zip
System Info Report: Gist

@huupoke — I see this line in your steam log err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\winebth": c0000142

I recently encountered this error myself, I'm surprised the game even loads to the main menu for you, as when I got this error it was just black screen.

However I fixed the issue using Protontricks --> https://github.com/Matoking/protontricks selected the game from the list, select default prefix and ran winecfg with this app, and in the Libraries tab came across library entries that has (??) you want to make sure there are no entries with that by setting them to Native, then Builtin then click Apply and Close, and try launching the game again.

Incorrect details on performance stats for Hitman World of Assassination for the in-game Steam Overlay doesn't get a proper read on what the game is actually using.

The setting for Performance Detail Level is set to FPS, CPU, GPU and RAM Full details, however when I look at the performance stat counters for Hitman WoA it's reading GPU usage at 0% and VRAM usage at 0.00/0.00 MB. I can open up nvtop in Terminal and I can see the game is actually using 48% GPU and 3.505 GB VRAM.

Game randomly freezes/hangs using Proton versions > 8.0-5, using versions <= 8.0-5 causes a "Failed to initialize Steam." error to appear with the Eminem Vs. Slim Shady patch.

steam-1659040.log

There is a memory leak in Proton versions > 9.0-4.

Steps to reproduce:

In any Proton version above 9.0-4 just idling in the main menu is enough to see the ram continuously climb up.

I also have the memory leak issue with version > 9.0-4.
I have attached a cut down log of a play session with version 10.0-4. The original logfile is 6.7 GB from just ~30 minutes of playtime. The error message 2239.794:01ac:02d8:fixme:amdxc:AmdExtStub1_QueryInterface2 unknown guid {4bbcaf68-eaf7-4fa4-b653-cb458c334a4e} repeats infinitely, causing the massive file size.

steam-1659040-cut.log

Has anyone experienced continuous crashes in Freelancer mode loading screens? For me it gets to a point where I simply cannot continue the freelancer campaign, because even after relaunching the game it will still crash every time when loading the level.

Has anyone experienced continuous crashes in Freelancer mode loading screens? For me it gets to a point where I simply cannot continue the freelancer campaign, because even after relaunching the game it will still crash every time when loading the level.

@kristaps777
Try switching to Proton 9.0-4 and disable ntsync (eg.: sudo rmmod ntsync).

Has anyone experienced continuous crashes in Freelancer mode loading screens? For me it gets to a point where I simply cannot continue the freelancer campaign, because even after relaunching the game it will still crash every time when loading the level.

@kristaps777 Try switching to Proton 9.0-4 and disable ntsync (eg.: sudo rmmod ntsync).

Turns out I am already running it with Proton 9.04, I guess no other version worked, and disabling ntsync made no difference.
Some sort of exception is logged in proton log; at best I guess it is not gpu driver related, those usually contain something with "amd", I suppose.
9406.761:016c:020c:warn:seh:dispatch_exception backtrace: --- Exception 0x80000101. 9406.761:016c:020c:trace:seh:dispatch_exception code=80000101 flags=1 addr=00007F3DA3E9A29C ip=7f3da3e9a29c 9406.761:016c:020c:warn:seh:dispatch_exception EXCEPTION_WINE_ASSERTION exception (code=80000101) raised 9406.761:016c:020c:trace:seh:dispatch_exception rax=0000000000000000 rbx=000000000000ed65 rcx=00007f3da3e9a29c rdx=0000000000000006 9406.761:016c:020c:trace:seh:dispatch_exception rsi=000000000000ed65 rdi=000000000000ed30 rbp=00000001027fde40 rsp=00000001027fde10 9406.761:016c:020c:trace:seh:dispatch_exception r8=00000000ffffffff r9=0000000000000000 r10=0000000000000022 r11=0000000000000246 9406.761:016c:020c:trace:seh:dispatch_exception r12=00000001027fdf80 r13=00007f3d99153000 r14=0000000000000006 r15=0000000000000000 9406.761:016c:020c:trace:seh:call_vectored_handlers calling handler at 00006FFFFCF70680 code=80000101 flags=1 9406.761:016c:020c:trace:seh:call_vectored_handlers handler at 00006FFFFCF70680 returned 0 9406.761:016c:020c:trace:seh:call_vectored_handlers calling handler at 00006FFFFD2EC060 code=80000101 flags=1 9406.761:016c:020c:trace:seh:call_vectored_handlers handler at 00006FFFFD2EC060 returned 0 9406.761:016c:020c:trace:seh:call_vectored_handlers calling handler at 00006FFFFB44B190 code=80000101 flags=1 9406.761:016c:020c:trace:seh:call_vectored_handlers handler at 00006FFFFB44B190 returned 0 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind function 7f3da3e9a29c base 0x7f3da3e9a190 cie 0x7f3da3fc7420 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip 9406.761:016c:020c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f3da3e9a29c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x9a29c. 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a190: DW_CFA_def_cfa %rsp, 8 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a190: DW_CFA_offset %rip, -8 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind fde 0x7f3da3fd2288 len 24 personality (nil) lsda (nil) code 7f3da3e9a190-7f3da3e9a2f3 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a190: DW_CFA_advance_loc 1 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a191: DW_CFA_def_cfa_offset 16 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a191: DW_CFA_offset %rbp, -16 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a191: DW_CFA_advance_loc 3 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a194: DW_CFA_def_cfa_register %rbp 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a194: DW_CFA_advance_loc 7 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a19b: DW_CFA_offset %r14, -24 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a19b: DW_CFA_offset %rbx, -32 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a19b: DW_CFA_advance_loc1 165 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a240: DW_CFA_remember_state 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a240: DW_CFA_def_cfa %rsp, 8 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a240: DW_CFA_advance_loc 8 9406.761:016c:020c:trace:unwind:execute_cfa_instructions 7f3da3e9a248: DW_CFA_restore_state 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind next function rip=00007f3da3e3e7d0 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind rax=0000000000000000 rbx=0000000000000006 rcx=00007f3da3e9a29c rdx=0000000000000006 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind rsi=000000000000ed65 rdi=000000000000ed30 rbp=00000001027fde60 rsp=00000001027fde50 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind r8=00000000ffffffff r9=0000000000000000 r10=0000000000000022 r11=0000000000000246 9406.761:016c:020c:trace:unwind:dwarf_virtual_unwind r12=00000001027fdf80 r13=00007f3d99153000 r14=0000000000001000 r15=0000000000000000 9406.761:016c:020c:err:seh:call_stack_handlers invalid frame 00000001027FDE10 (0000000059622000-0000000059720000) 9406.761:016c:020c:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. 9406.926:00e0:075c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 9406.972:0030:0760:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 9406.973:0030:0764:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 9406.973:0030:0768:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 9406.974:0030:076c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" 9406.974:0030:0770:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker" pid 60610 != 60609, skipping destruction (fork without exec?)

I'm getting a crash when launching VR, tried with Proton 9, 10, 11, & Experimental(and GE variants). Flatscreen seems to be working okay.

SteamVR beta, 4090, BSB2e, Knuckles Controllers

Full System Info
Proton Experimental Log

I'm getting a crash when launching VR, tried with Proton 9, 10, 11, & Experimental(and GE variants). Flatscreen seems to be working okay.

SteamVR beta, 4090, BSB2e, Knuckles Controllers

Full System Info Proton Experimental Log

Someone in LVRA discord found the fix - use the bleeding edge branch of Proton Experimental:

1. Proton Experimental
2. Properties
3. Game Versions & Betas
4. bleeding-edge

After setting the Hitman WoA compat tool to Proton Experimental, I was able to launch the game directly in VR without a crash.