HITMAN 3 (1659040)

[AirstrikeIvanov]

Compatibility Report

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

System Information

• GPU: GeForce RTX 2080 Super
• Driver/LLVM version: nvidia v495.46
• Kernel version: 5.16.4-zen1-1-zen
• Link to full system information report: System Information report
• Proton version: 6.3-8

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 attached here: steam-1659040.log

Symptoms

The game itself seems to work well in 2D, but when the user attempts to enable VR mode, it does not seem to work in the HMD display.
The game also needs SteamVR running before it recognizes the device in my case (Rift CV1 with OpenHMD), but I am also using a relatively unsupported device and wasn't sure if this was a bug or a feature.

Reproduction

1. Start SteamVR, and then start HITMAN 3.
2. Enable VR mode.
3. Watch as the display image in the application window works just fine in VR mode, but is not sent to the HMD.

(Note, This is my first time submitting a compatibility report here, I'm not sure if it's appropriate to submit one for JUST the VR mode of a game, please let me know if I'm not supposed to submit reports for things like this!)

[kisak-valve]

Hello @AirstrikeIvanov, your log hints that OpenXR failed to intialize for some reason. From the log:

Error [GENERAL |  | OpenXR-Loader] : RuntimeManifestFile::FindManifestFiles - failed to determine active runtime file path for this environment
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : RuntimeInterface::LoadRuntimes - unknown error
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : RuntimeInterface::LoadRuntimes - failed to load a runtime
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : Failed loading runtime information
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
[...]
err:openxr:get_vulkan_extensions Error getting openxr_vulkan_instance_extensions, status 0.

For the note at the bottom of the opening post, we're using one issue report per unofficially supported game title, so this compatibility report is a good place for all feedback related to running HITMAN 3 on Proton.

[dsalt]

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

[dsalt]

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…

[terzag]

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.

[kisak-valve]

Hello @terzag, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[terzag]

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.

[kisak-valve]

Thanks, info: Driver: 21.3.8 and 0148:err:vkd3d_init_device_caps: KHR_dynamic_rendering is not supported by this implementation. This is required for correct operation. are the lines that matter in the log. The build of VKD3D-Proton in Proton Experimental requires mesa 22.0 or newer and this specific failure is expected and not a bug.

[terzag]

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.

[kisak-valve]

The change in VKD3D-Proton is from about 2 months ago, HansKristian-Work/vkd3d-proton#905 / HansKristian-Work/vkd3d-proton@095a36c, but Proton Experimental and point releases were being held back for a while to let driver updates propagate into some common distros.

[Akselmo]

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

[terzag]

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?

[Akselmo]

I udpated my earlier post

[BCMM]

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"
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?)

[Unser395]

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:

• that I haven't found an existing compatibility report for this game.
• 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.

[alkaris2]

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

[ghost]

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)

[alkaris2]

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.

[kisak-valve]

Hitman 3 Freezing/Crashing

Issue transferred from #6013.
@ecameracci posted on 2022-07-19T22:36:18:

Compatibility Report

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

System Information

• GPU: RX 6400
• Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 22.1.2
• Kernel version: 5.13.0-valve21-2-neptune-02209-g2a5bdc1102a0
• Link to full system information report as Gist: System Information
• Proton version: proton-7.0-3 (also tried with experimental, but logs are captured with 7.0-3)

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.
  steam-1659040.zip

Symptoms

When launching Hitman 3, I get the launcher screen. After selecting "Play" I see the "ioi" splash screen and then the game freezes. Attempting to launch the game again sometimes causes a crash or the freezing again. I have managed to get into game once after changing from exclusive fullscreen to fullscreen and from disabling vsync, but the freeze just happens later. The game is frozen, but alt+tab (or exiting the game from the steam deck overlay menu) still works.

Reproduction

• Launch the game
• Select "Play" on the splash screen.
• Observe game is frozen

Notes

This is with a PC with HoloISO installed on it. This is the relevant output from neofetch:

OS: SteamOS Holo x86_64
Host: OptiPlex 3060
Kernel: 5.13.0-valve21-2-neptune-02209-g2a5bdc1102a0
Packages: 875 (pacman), 6 (flatpak)
Shell: bash 5.1.16
Resolution: 2560x1440
DE: Plasma 5.23.5
CPU: Intel i5-8400 (6) @ 4.000GHz
GPU: AMD ATI 03:00.0 Device 743f
GPU: Intel CoffeeLake-S GT2 [UHD Graphics 630]
Memory: 1816MiB / 7774MiB

This happens when launching in both the gamescope session and the desktop mode. The game is installed on the same ext4 formatted drive as the OS. Verified that the game runs under Windows to rule out a potential hardware issue.

[felixpelletier]

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

[jamesdimick]

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.

[terzag]

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.

[alkaris2]

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.

[jamesdimick]

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

[terzag]

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?

[alkaris2]

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

[terzag]

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.

[Mezentium]

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

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

[Mezentium]

@terzag It should be in your bios.

[ThisNekoGuy]

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

System Info Gist

[terzag]

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

[frozen-sea]

Re: the greyed out RT options, I found this: HansKristian-Work/vkd3d-proton#1148 (comment)

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)

[Aegeontis]

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]

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.

[willthong]

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.

[alkaris2]

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

[kisak-valve]

Hello @alkaris2, err:steamclient:create_win_interface Don't recognize interface name: SteamUser023 followed by an access violation hints that the third party build of Proton is too old to be used with the game.

SteamUser023 looks like it's part of Steamworks 1.57, which should work with Proton 8.0-3 (or newer). (a33bbf1) Please retest with Proton 8.0-3 and share and updated Proton log.

[my4ng]

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.

[morali]

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

[Mar2ck]

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.

[misyltoad]

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

[Mar2ck]

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.

Hitman.3.2023.11.28.-.00.18.18.10.mp4

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

[oliwer]

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.

[huupoke]

I'm having problem when setting graphic at "Fullscreen" mode (as "Exclusive Fullscreen" crashes the game when alt-tabbing). The game window is being pushed up and right slightly, as shown in the picture below (I can't screenshot this bug). I'm using Proton 8.0-5 and NVIDIA RTX 3050Ti Mobile with driver 545.29.06 on Fedora Workstation 39, GNOME 45.3 on Xorg server.

Seems like the problem only happen when running under Xorg server. Doesn't happen on Wayland.

[NoXPhasma]

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

[MarcPG1905]

I am completely unable to launch the game.
When launching over steam, it just shows the "Launching" and then returns back to the "Play" button.

These are the errors I get in the proton logs:

12263.046:0120:0124:err:module:loader_init "d3d12.dll" failed to initialize, aborting
12263.046:0120:0124:err:module:loader_init Initializing dlls for L"E:\\SteamLibrary\\steamapps\\common\\HITMAN 3\\Launcher.exe" failed, status 80000100

and this is the complete log.
I'm running Arch with an RTX 4070 on the 555.58.02 NVIDIA drivers.

[drabgaol]

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?

[Rob4096]

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

10544.735:01bc:044c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
10551.908:01bc:0268:err:sync:RtlpWaitForCriticalSection section 000000014934D630 (null) wait timed out in thread 0268, blocked by 0264, retrying (60 sec)
10551.908:01bc:02e4:err:sync:RtlpWaitForCriticalSection section 000000014934D750 (null) wait timed out in thread 02e4, blocked by 0268, retrying (60 sec)
10560.329:01bc:023c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:023c:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:023c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:023c:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:023c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:023c:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.329:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.329:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
10560.349:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.349:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.349:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.349:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.349:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.349:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.350:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.350:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0240:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.351:01bc:0240:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.351:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0238:err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
10560.351:01bc:0238:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.351:01bc:0234:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.351:01bc:0234:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
10560.352:01bc:023c:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4.
10560.352:01bc:023c:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 0000000050560080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
pid 111410 != 111409, skipping destruction (fork without exec?)

[olib14]

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.

[rmg-x]

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

[olib14]

I believe the following journal log extract around the time of the freeze might be relevant:

03:33:48 kernel: NVRM: Xid (PCI:0000:26:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: Class 0xc5c0 Subchannel 0x0 Mismatch
03:33:48 kernel: NVRM: Xid (PCI:0000:26:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x4041b0=0x108c5c0
03:33:48 kernel: NVRM: Xid (PCI:0000:26:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x404000=0x80000002
03:33:48 kernel: NVRM: Xid (PCI:0000:26:00): 13, pid=68577, name=hitman3.exe, Graphics Exception: ChID 00af, Class 0000c597, Offset 00000000, Data 00000000

[olib14]

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.

[Rob4096]

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 <#5536 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMYWAEJK3CVHNM3G6IQKAML2L7EZPAVCNFSM5NLFHKR2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TENRQG43TONRUGA2Q> . You are receiving this because you commented.Message ID: ***@***.***>

[ThisNekoGuy]

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.

[alkaris2]

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