sergio91pt commented 5 years ago

Compatibility Report

Name of the game with compatibility issues: Hitman 2
Steam AppID of the game: 863550

System Information

GPU: GTX 1050
Driver/LLVM version: 4.6.0 NVIDIA 415.23
Kernel version: 4.15.0-42-generic
Link to full system information report as Gist: https://gist.github.com/sergio91pt/306e805f428092cca14e8fbd0c5f2a1e
Proton version: 3.16-6 Beta (also happens in 3.7-8 and 3.16-4)

I confirm:

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

steam-863550.log

Symptoms

The launcher works but the game crashes a couple seconds after the game launches in fullscreen. The screen is always black when it crashes.

Reproduction

Always reproducible.

Solution

The problem seems to be caused by this bug, related to Nvidia prime/optimus and gdm3 on Ubuntu.

The solution is to run sudo vulkaninfo. It fails without sudo and the command needs to be run again after rebooting.

skeevy420 commented 5 years ago

Is anybody else experiencing controller issues after the last Proton and/or Hitman update? In particular, aiming down is a struggle and my controller gets un-calibrated by while playing.

OS: ubuntu 19.04 Proton: 4.11-6

And as a side note thank you @skeevy420 for the dll.

Yeah, but my controller issues are related to my DS4 right stick deadzone (it needs to be a hair bigger else looking tends to get stuck going slowly left unless I precisely center the right stick).

I had issues in the past with VSync and my right stick acting wonky with this game and setting dxgi.syncInterval = 1 in the game's dxvk.conf helped.

aeikum commented 5 years ago

@Dylan-Brotherston For what it's worth, I played a couple minutes with a wired Xbox One controller with Steam configuration both turned on and off and saw no problems. There weren't any changes between 4.11-5 and 4.11-6 that were directly related to controller support.

chriswere commented 5 years ago

The latest update borked my game. But adding the .conf into to /Retail folder fixed the issue for me.

dribbleondo commented 5 years ago

DXVK 1.4.1 has fixed the amd_ags_x64 issue now

viggy96 commented 5 years ago

Currently unable to launch any missions. Game crashes when trying to start a mission. Attached log for reference. steam-863550.log

tbe commented 4 years ago

Same here, game crashing after the mission loading screen. https://pastebin.com/jAyV871p

NoXPhasma commented 4 years ago

I tried to run the game with DX12 and Proton 4.11-8 (vkd3d), but it doesn't even launch.

steam-863550.log https://gist.github.com/NoXPhasma/9c4497ebcb8838352716c93460353eab

kisak-valve commented 4 years ago

Hitman 2 (with DX12 selected): game and benchmark both crash

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3196. @NotMrFlibble posted on 2019-11-09T03:14:58:

Compatibility Report

Name of the game with compatibility issues: HITMAN 2
Steam AppID of the game: 863550

System Information

GPU: RX 570
Driver/LLVM version: Mesa 19.2.3/7.1.0
Kernel version: 5.3.9
OS: Devuan beowulf
Proton version: 4.11-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.

Symptoms

Silent crash on launch. Log file says exception, code=80000003.

No problems if DX11 is selected.

Reproduction

In the launcher, select DX12: ‘“Options” → “Graphics API” → “Direct3D 12”. Then either save the settings and launch the game, or use benchmark mode. (In the latter case, the launcher will continue to run.)

Log

<Log omitted, please see #3196>

aqxa1 commented 4 years ago

Seems like there is some weirdness with the new VKD3D integration. The launcher now looks to be using WineD3D's GPU detection (which seems to use OGL, and detects an older card). This also breaks ReShade because it thinks the game is running with OGL (but the game itself does correctly use DXVK once launched).

See error:

EDIT: Just needed to use native DXGI: WINEDLLOVERRIDES="dxgi=n"

It wasn't working with winecfg for some reason.

doitsujin commented 4 years ago

It wasn't working with winecfg for some reason.

I think the Proton script itself sets WINEDLLOVERRIDES (but takes into account the value you already set, if any), which is why this doesn't work.

NoXPhasma commented 4 years ago

It does https://github.com/ValveSoftware/Proton/blob/proton_4.11/proton#L515

aqxa1 commented 4 years ago

Thanks, that confirms it. That's more convenient than using winecfg anyway, was just unaware of it.

Bumbadawg commented 4 years ago

With the WINEDLLOVERRIDES="dxgi=n" it now allows to start in D3D12 but immediately goes log

1197 warn: DxgiAdapter::QueryInterface: Unknown interface query^M

Running on Ubuntu bionic, Kernel 5 (futex), Nvidia 440.

aeikum commented 4 years ago

Yeah, D3D12 won't work with dxgi=n. That's actually why it's not the default anymore.

dribbleondo commented 4 years ago

This is probably one of those games that'll require a manual patch from within VKD3D to work, I'd expect.

jmshrv commented 4 years ago

Still not launching with DX12 on Proton 5.0-3

JWolvers commented 4 years ago

Screenshot_20200331_182459 Textures of leaves have this weird black border when using proton 5.0-5, but they are normal when using proton 4.11-13.

dribbleondo commented 4 years ago

Textures of leaves have this weird black border when using proton 5.0-5, but they are normal when using proton 4.11-13.

The black border is the texture alpha. For some reason, your game isn't accepting the alpha channel values and ignoring it. Cannot confirm on my end, as I've not had this issue. What GPU/ Mesa stack you using @JWolvers ?

JWolvers commented 4 years ago

Using a RX 5700XT and mesa 20.0.2 The weird thing is this only happens on moving objects like leaves, but static flowers are fine.

NotMrFlibble commented 4 years ago

RX 570, Mesa 20.0.2. Looks fine here; specifically, no transparency problems noticed.

JWolvers commented 4 years ago

I checked with AMDVLK but the issue remains.

viggy96 commented 4 years ago

I still can't play the game, it crashes when clicking play on any level, and also crashes when trying to run the benchmark. Excuse the zip file, apparently the log file was too large for GitHub.

steam-863550.zip

sinaflan commented 3 years ago

proton 5.13 dx12 crash on start

MurdoMaclachlan commented 3 years ago

Reaches launcher but crashes after briefly loading game window on 5.13-4. Runs perfectly on 5.0-10.

kisak-valve commented 3 years ago

Hello @MurdoMaclachlan, 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.

MurdoMaclachlan commented 3 years ago

Whoops, sorry about that. System info here Proton log here

kisak-valve commented 3 years ago

Thanks, looking at the log, audio failed to initialize for some reason:

ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
INFO: OpenAudioDevice failed: ALSA: Couldn't open audio device: No such file or directory
INFO: Assertion failed: 0 && "Failed to open audio device!"

then the game falls over with an unhandled access violation (c0000005).

Managor commented 3 years ago

So there's a weird blending issue on Haven Island 20210130121808_1 The spot can be found here and on the private island. 20210130121910_1

Is this a proton bug or a game bug?

dribbleondo commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/2121#issuecomment-770428558.

This is a game bug. The devs updated Hitman 2 just before christmas, and it broke the sand blending when they updated the sand textures.

cray12399 commented 3 years ago

Compatibility Report

Name of the game with compatibility issues: HITMAN 2
Steam AppID of the game: 863550

System Information

GPU: AMD Radeon RX 5700XT (Driver: Mesa 21.1.0-devel (git-b4d1764 2021-03-05 focal-oibaf-ppa)
CPU: Radeon R9 3900X
Linux Distro: Ubuntu 20.04
Kernel Version: 5.8.0-44-generic
Proton Version: 5.13-6 (also happens in every Proton version except 4.11-13)

Symptoms

Game wont launch on any Proton version, including GE and experimental, except for 4.11-13. However, when launched on Proton version 4.11-13, the audio doesnt work.
Launcher loads on every Proton version, but clicking "Play" immediately causes the game to crash.
A week or two ago, I was able to get the game to launch using version 5.0-10. However, despite nothing changing in my system configuration since then except for routine updates, this solution no longer works.

What I have tried:

Reinstalling the game
Reinstalling my graphics drivers
Resetting the wine prefix by deleting Hitman 2's pfx folder under compatdata
Switching between DX11 and DX12
Installing Proton-GE and trying to launch it with that.

Reproduction

Always reproducible.

kisak-valve commented 3 years ago

Hello @cray12399, I suspect you've encountered https://gitlab.freedesktop.org/mesa/mesa/-/issues/4396. Can you try temporarily disabling lavapipe with something like:

sudo mv /usr/share/vulkan/icd.d/lvp_icd.i686.json /usr/share/vulkan/icd.d/lvp_icd.i686.json.disabled
sudo mv /usr/share/vulkan/icd.d/lvp_icd.x86_64.json /usr/share/vulkan/icd.d/lvp_icd.x86_64.json.disabled

and see if that has an effect?

cray12399 commented 3 years ago

@kisak-valve Thanks for the quick response! Your solution fixed the launching issue! However, Hitman still doesn't have any audio for me on any Proton version.

It might be worth noting that I am using a Creative Sound Blaster Audigy FX sound card, but when I launched it previously a 2 weeks ago, I still had the card and the sound worked perfectly.

EDIT:

Additionally, it seems that the game still won't launch in DX12 mode, which isn't a big deal, but I find that it might be worth mentioning.

dsalt commented 3 years ago

Rendering bug. Can't usefully tell whether this is radv or dxvk.

“Three-Headed Serpent” – standing on the terrace outside Héctor Delgado's room, looking towards the water. There are some sheets, acting as a roof, over the area below. These are not rendered correctly; there is flickering as the viewing angle is changed. (Shadow bug?)

Mesa 21.0.0 & 20.3.x LLVM 11 (1fdec59bffc1, from apt.llvm.org) Linux 5.11.2 Steam build datestamp 1615510515 Proton 5.13-6 & experimental RX 5600 XT

Supersampling: 1.00 Texture filtering: anisotropic 4× Screen-space shadow: on Motion blur: off Dynamic sharpening: moderate Simulation quality: best Other settings: high

ZereoX commented 3 years ago

Hi @kisak-valve,

The AMD RADV / Mesa drivers label can be removed. I confirmed that the issue stated above is a Game Bug and can be reproduced on both AMD and Nvidia at any graphical preset (Confirmed on Linux and Windows with both DX11 & 12).

Both exhibit severe flickering on the awning drapes when the camera is moved. Nvidia has even worst shadow artifacting.

Windows Nvidia	Windows AMD

aufkrawall commented 3 years ago

With recent Proton-Experimental, mouse and keyboard input doesn't work correctly for me, as it erroneously expects gamepad controller input, and such a device isn't even connected.

kisak-valve commented 3 years ago

Hello @aufkrawall, about how long ago (what date) do you know it was behaving like it was supposed to? Can you check how the game behaves with Proton 5.13-6 and 6.3-2?

aufkrawall commented 3 years ago

It seems all Proton versions are affected, I've tested from Experimental to 5.0-10. So this is probably an issue of the runtime (e.g. SDL)? The cursor always jumps back to the middle of the screen and also keyboard input isn't correctly recognized, thus I can't navigate the game's main menu. It was still working 2-3 weeks ago, also with Experimental.

One less severe issue: It would be nice if it wasn't required anymore to specify WINEDLLOVERRIDES="dxgi=n" in order to make it start with D3D12/VKD3D-Proton, as it has gotten much faster in CPU bound scenes than the game's D3D11 renderer + DXVK.

aufkrawall commented 3 years ago

Turns out it was due to a hardware change, the RGB controller of my new mainboard confuses input device handling. This udev rule has solved the issue for me: https://bbs.archlinux.org/viewtopic.php?pid=1948148#p1948148

Edit: Better solution: https://www.reddit.com/r/ASRock/comments/kax86r/asrock_led_controller_as_joystick_recognized/gi3s58u/?utm_source=reddit&utm_medium=web2x&context=3

kisak-valve commented 3 years ago

hitman 2 (863550) doesnt start

Issue transferred from https://github.com/ValveSoftware/Proton/issues/4962. @CrCrate posted on 2021-07-12T08:29:41:

upon pressing play after a few seconds it just goes back to play, no windows opens and nothing happens. PROTON_LOG is extremely unhelpful as theres pretty much nothing in it experimental

======================
Proton: 1625839307 experimental-6.3-20210709
SteamGameId: 863550
Command: ['/media/dumbass/ext/SteamLibrary/steamapps/common/HITMAN2/Launcher.exe']
Options: {'forcelgadd'}
SteamLinuxRuntime: v0.20210317.0-0-ge09b2e6
pressure-vessel: 0.20210415.0+srt1 scout 0.20210415.0
soldier: 0.20210415.0 soldier 0.20210415.0
======================

3.16-9

======================
Proton: 1554732609 proton-3.16-9
SteamGameId: 863550
Command: ['/media/dumbass/ext/SteamLibrary/steamapps/common/HITMAN2/Launcher.exe']
======================

kisak-valve commented 3 years ago

Hello @CrCrate, the short logs hints that Proton is failing to initialize, before it tries to run the game launcher.

Maybe your issue is filesystem related? What filesystem are you using with /media/dumbass/ext/SteamLibrary/?

CrCrate commented 3 years ago

it was, turns out I was using a drive formatted ntfs. used ext4 and it works perfectly now, thanks :D

bernharl commented 3 years ago

This game worked two weeks ago on Proton 6.3 (I think it was 6.3). Now it crashes my entire GPU and I need to restart my graphical session (It freezes, monitors flash to black and back again to a frozen image. Sound still plays.).

I'm running a Ryzen 5900x, RX 6800 XT. Arch Linux on kernel 5.12.15. Running SwayWM (Wayland compositor). I have attached logs.

steam-863550.log Edit: log pasted twice for some reason.

Managor commented 3 years ago

We got a regression. The game is unable to contact Hitman servers with Proton Experimental but the connection works perfectly fine with 6.3-6

kisak-valve commented 3 years ago

Hello @Managor, 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.)

Managor commented 3 years ago

I retract that statement. Changing back to experimental and it allows me to connect normally again.

gardotd426 commented 3 years ago

I'm actually unable to connect to the Hitman 2 servers using Proton Experimental.

gardotd426 commented 3 years ago

PROTON_LOG=1 log:

https://gist.github.com/gardotd426/fa6f5ee08a9b69b6131e9b469ae99692

gofman commented 3 years ago

The failure to connect should be fixed in today Experimental update.

farukr1 commented 2 years ago

Crashes on DX12, no problems with DX11. Using Fedora 35 with everything up-to-date on R5 3600 + RX 580 system.

Here's the log.

kisak-valve commented 2 years ago

Hello @farukr1, info: Driver: 2.0.210 in your log suggests that you're using AMDVLK. Can you also test if the same behavior happens with mesa/RADV?

ValveSoftware / Proton

Hitman 2 (863550) #2121

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction

Solution

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction

Log

Compatibility Report

System Information

Symptoms

What I have tried:

Reproduction