search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.9k stars 1.04k forks source link

HITMAN 3 (1659040) #5536

Open AirstrikeIvanov opened 2 years ago

AirstrikeIvanov commented 2 years ago

Compatibility Report

System Information

I confirm:

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 commented 2 years ago

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 commented 2 years ago

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

dsalt commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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

Akselmo commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

I udpated my earlier post

BCMM commented 2 years ago

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 commented 2 years ago

Compatibility Report

System Information

I confirm:

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 commented 2 years ago

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 commented 2 years ago

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:

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 commented 2 years ago

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 commented 2 years ago

Hitman 3 Freezing/Crashing

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6013. @ecameracci posted on 2022-07-19T22:36:18:

Compatibility Report

System Information

I confirm:

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

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 commented 2 years ago

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

jamesdimick commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

@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 commented 2 years ago

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 commented 2 years ago

@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 commented 2 years ago

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 commented 2 years ago

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.

dsalt commented 2 years ago

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

ecameracci commented 2 years ago

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.

Mezentium commented 2 years ago

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.

Mezentium commented 2 years ago

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

jamesdimick commented 2 years ago

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?

Mezentium commented 2 years ago

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

ecameracci commented 2 years ago

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.

alkaris2 commented 2 years ago

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.

terzag commented 2 years ago

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.

Mezentium commented 1 year ago

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.

Unser395 commented 1 year ago

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?

terzag commented 1 year ago

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.

felixpelletier commented 1 year ago

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

ghost commented 1 year ago

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.

my4ng commented 1 year ago

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.

kisak-valve commented 1 year ago

Hitman 3 missing DLSS ingame menu and raytracing in both launcher and ingame menu

Issue transferred from https://github.com/ValveSoftware/Proton/issues/6327. @Tarch1 posted on 2022-11-18T17:45:35:

Hitman 3 v3.130.0

System Information

I confirm:

Symptoms

terzag commented 1 year ago

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.

my4ng commented 1 year ago

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

terzag commented 1 year ago

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.

my4ng commented 1 year ago

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.

dsalt commented 1 year ago

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.

Inveli commented 1 year ago

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)

my4ng commented 1 year ago

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.