Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hitman 2 not detecting DirectX 11 #1201

Closed
WillHaRSI opened this issue Sep 24, 2019 · 13 comments
Closed

Hitman 2 not detecting DirectX 11 #1201

WillHaRSI opened this issue Sep 24, 2019 · 13 comments
Labels

Comments

@WillHaRSI
Copy link

Hitman 2 was updated this on 9/24 and now start up does not detect DirectX 11.

This game is rated platinum on ProtonDb.

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.

Important: When reporting an issue with a specific game or application, such as crashes or rendering issues, please include log files and a D3D11 Apitrace (see https://github.com/apitrace/apitrace) so that the issue can be reproduced. In order to create a trace, run wine apitrace.exe trace -a dxgi YOURGAME.exe. DO NOT use DXVK together with apitrace!

Software information

Name of the game, settings used etc.

System information

  • GPU: AMD RX 560
  • Driver: Mesa 19.2
  • Wine version: Proton 4.11-6
  • DXVK version: 1.4

Apitrace file(s)

  • Put a link here

Log files

  • d3d11.log:
  • dxgi.log:
@skeevy420
Copy link

Are you using ACO?

I'm in the middle of testing something else with Hitman 2 right now, but both the update came in and I was testing a patch for ACO on mesa master so I switch from mesa from git master to mesa with ACO based on a git diff patch and was thinking that was the reason for my error. Thought it might have been due to using dxvk-ags, but that was reverted when I validated all the game files and the issue still occurred so it's very doubtful dxvk-ags is responsible.

Gonna test plain ACO in about 20 minutes (PC is busy at the moment) followed by a recompile of mesa from master and test that.

The error I'm seeing has something about GfeSDK.dll in it. I've rebooted since seeing that and didn't get a copy/paste of my terminal output. Sorry, thought it was related to other stuff I've been doing and didn't think it relevant to get.

@K0bin
Copy link
Collaborator

K0bin commented Sep 24, 2019

The error I'm seeing has something about GfeSDK.dll in it.

Make sure Nvapi is disabled in your wine prefix. As far as I know, GfeSDK.dll is part of Nvidias Geforce Experience.

Did you change anything in the dxvk config file?

@skeevy420
Copy link

The error I'm seeing has something about GfeSDK.dll in it.

Make sure Nvapi is disabled in your wine prefix. As far as I know, GfeSDK.dll is part of Nvidias Geforce Experience.

Did you change anything in the dxvk config file?

It is which is why that had me scratching my head.

That's a possibly in regards to the config file....gotta check....

 d3d11.maxTessFactor = 64
 dxgi.syncInterval = 1
 d3d11.samplerAnisotropy = 16

@K0bin
Copy link
Collaborator

K0bin commented Sep 24, 2019

The config file seems alright. I was just wondering if you had changed the vendor id to Nvidia but thats not the case.

@skeevy420
Copy link

skeevy420 commented Sep 24, 2019

Just tested with mesa-aco and it has the issue. Started compiling mesa-master, waiting on the 32-bit part to finish, and about to reboot and test that.

Tested mesa-aco with both a Proton-Tkg build from last night with dxvk from f37d4b5 (one commit after 1.4) and Proton 4.11-6 with the dxvk 1.4 they include.

UPDATE: Same issue with mesa-master and the same tkg build and 4.11-6. Gonna build a TKG Proton based on dxvk 1.3 and see how that fares.

The game was also updated this morning and it's likely that update is cause of the problem. The 1.4 + 1 commit in my Proton TKG build was working perfectly fine this morning until I updated Hitman 2.

EDIT: Restarted Steam to test the 1.3 build and Hitman 2 got a 10GB update. Hopefully that fixes this issue.

@doitsujin
Copy link
Owner

doitsujin commented Sep 24, 2019

This is not my bug. I don't know what they changed in the game but it just errors out for absolutely no reason; the same thing happens with wined3d.

Please report this on the Proton bug tracker instead.

@skeevy420
Copy link

The 2nd update didn't fix it and I tested that with both 1.3.4 and master with an up-to-date TKG Proton and 1.4 with Proton 4.11-6 and both of those with both Mesa versions. There's a issue over at the Proton tracker as well.

What did fix it was using dxvk-ags with the header set to 5.1

@doitsujin
Copy link
Owner

What did fix it was using dxvk-ags with the header set to 5.1

Interesting; for me the game just crashes if I do that.

@skeevy420
Copy link

skeevy420 commented Sep 24, 2019

aufkrawall noticed it was only working with with proton-tkg and not with Proton 4.11-6.

EDIT: With proton 4.11-6 the error I'm getting using dxvk-ags is
Unhandled exception: unimplemented function amd_ags_x64.dll.agsGetCrossfireGPUCount

@doitsujin
Copy link
Owner

doitsujin commented Sep 24, 2019

Turns out there was an entry point missing from my AGS DLL:
doitsujin/dxvk-ags@224dbba

With the latest code, this works now.

@skeevy420
Copy link

Thanks.

@WillHaRSI
Copy link
Author

WillHaRSI commented Sep 24, 2019

Thanks @doitsujin @skeevy420

@skeevy420
Copy link

skeevy420 commented Sep 24, 2019

Should I start an issue over at dxvk-ags for this?

That dxvk-ags update works just fine for me with proton-tkg but not with proton 4.11-6. I'm not sure if that's an actual issue with anything here or if Tk-Glitch adds some special sauce for ags possibly making it a proton issue.

EDIT: Disregard that. Just saw the one you posted at the Proton issue and it works just fine with tkg and valve protons. I'm probably doing something wrong in the build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants