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

Issue with Ghostbusters: The Video Game Remastered #4045

Closed
KeyofBlueS opened this issue Jun 1, 2024 · 6 comments · Fixed by #4046
Closed

Issue with Ghostbusters: The Video Game Remastered #4045

KeyofBlueS opened this issue Jun 1, 2024 · 6 comments · Fixed by #4046

Comments

@KeyofBlueS
Copy link

KeyofBlueS commented Jun 1, 2024

Dear dxvk developers,

Hi! after reporting an issue on Valve's Proton github about a problem I'm experiencing with Ghostbusters: The Video Game Remastered on Proton, I was redirected to this repo, so I'm reporting it here as well:

When running the game with Proton versions 8 and 9, there are severe and unpleasant artifacts on the characters' face, neck, and chest.

In that report on Valve's Proton, someone mentioned using Proton 5.13, so I decided to give it a try. While my controller isn't correctly detected and the performance is significantly worse compared to the latest Proton versions, the artifacts are not present in 5.13. This indicates a serious regression in the newer Proton versions.

Further tests reveals that even Proton 6.3-8 and 7.0-6 are affected, so Proton 5.13-6 is the last version unaffected by this issue.

I've attached a video that demonstrates these artifacts, along with logs from Proton 5.13-6 and 9.0-1.

Furthermore, the game won't play high-quality MP4 videos, defaulting instead to lower-resolution OGV videos. Is it truly impossible to fix this issue also?

I hope someone can investigate this problem and looking forward to hearing from you soon.

Thank you and best regards!

Software information

Ghostbusters: The Video Game Remastered

System information

  • GPU: nvidia GTX970
  • Driver: 535.161.08
  • Proton version: 6.3-8; 7.0-6; 8.0-5; 9.0-1
  • DXVK version: The one included within Proton I guess? sorry I don't know how to check

Apitrace file(s)

Log files

simplescreenrecorder-2024-05-31_23.27.06.mp4

steam-1449280_proton-5.13-6.log

steam-1449280_proton-9.0-1.log

@Blisto91
Copy link
Contributor

Blisto91 commented Jun 1, 2024

Hi there and thank you for the well made issue. The PR above should work around the problem

@KeyofBlueS
Copy link
Author

KeyofBlueS commented Jun 2, 2024

Hi, thank you for your quick reply!

I tried your patch, but unfortunately, the flickering is still there.

I've never compiled and installed DXVK before, so I might have made a mistake, but I don’t think so. Here’s what I did following the DXVK readme:

  • Cloned the DXVK repo
  • Edited the file ./src/util/config/config.cpp as per your PR
  • Compiled
  • Installed the DLLs in the game prefix
  • Added DLL overrides with Protontricks
  • Started the game

@mbriar
Copy link
Contributor

mbriar commented Jun 2, 2024

Installing the dlls to the prefix doesn't work with proton because they will be overridden again on every launch by the proton launch script. You need to replace the dlls in the proton distribution or put them next to the game's .exe. There's no need to add dll overrides because those are done by default anyways.

@KeyofBlueS
Copy link
Author

KeyofBlueS commented Jun 2, 2024

I didn't know that, thanks for the clarification!

I tried placing the DLLs next to the game's .exe, but that didn't work for some reason.

However, I managed to get it working by setting the DXVK_CONFIG_FILE=/xxx/dxvk.conf environment variable in Steam. This points to the dxvk.conf file where, as in the PR, I added d3d11.longMad = True!

Or, simply DXVK_CONFIG="d3d11.longMad = True".

This shows that the logic of @Blisto91's PR is confirmed. Thanks again, Blisto91, thanks @mbriar and thank you all.

I've also learned a couple of new things.

@mbriar
Copy link
Contributor

mbriar commented Jun 2, 2024

I tried placing the DLLs next to the game's .exe, but that didn't work for some reason.

probably didn't work because it's an Unreal Engine game and the real exe is in Whatever/Binaries/Win64/Whatever-Shipping.exe

@KeyofBlueS
Copy link
Author

No it's not. It's on Infernal Engine, and there is only one exe in the game.

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

Successfully merging a pull request may close this issue.

3 participants
  翻译: