search

ValveSoftware / Proton

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

Ghostbusters: The Video Game Remastered (1449280) #5087

Open opal1974 opened 3 years ago

opal1974 commented 3 years ago

Compatibility Report

System Information

I confirm:

Symptoms

After the copyright screens, the game crashes for me. Others have been able to get it to work but I cannot, and I tried it on a couple of different Linux installs

Reproduction

Install, play

steam-1449280.log

Patola commented 2 years ago

Same thing for me, and I'm on AMD (RX 6800 XT). Game crashes after copyright screen. A recent protondb report (one month ago) says it worked out of the box, which is weird. My proton log says there's an unhandled exception:

30179.461:0140:0144:trace:seh:call_teb_handler calling TEB handler 000000007BC68410 (rec=000000000063EDE0, frame=000000000063FEA0 context=000000000063E330, dispatch=000000000063E200)
wine: Unhandled page fault on read access to 0000000000000000 at address 0000000140504030 (thread 0144), starting debugger...
(...)
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000140504030).
Register dump:

steam-1449280.log

Patola commented 2 years ago

Ok... Game doesn't work with Proton-GE 6.x and Proton Experimental, but it works with Proton 5.13-6 (clean prefix install). Just in case, I'm uploading the log with Proton 5.13-6 in hopes it is of any help. steam-1449280-proton-5.13-6-working.log

kisak-valve commented 2 years ago

Hello @Patola, looks like a hint is a bit earlier in your log with fixme:mfplat:MFCreateDXGIDeviceManager stubbing out, which is immediately followed by an access violation (c0000005).

Patola commented 2 years ago

Weird, so a stub for mfplat makes the game crash, and since Proton 5.13-6 doesn't have this stub, it works?

alasky17 commented 2 years ago

@Patola We are in a weird place where some games still need the stub and crash with the "semi-complete" implementation and some games crash with the stub ... we already have a hack to avoid the stub for the games that need to and so I added this one to that hack list - it should be working in the next experimental release and also the next main 6.3-x release :) Thank you for the report!

Patola commented 2 years ago

I confirm, with the latest Proton Experimental bleeding edge, installed from a clean prefix, the game now works perfectly. Thank you, @alasky17.

opal1974 commented 2 years ago

In light of this recent discussion, I am going to retest this later today, since I was the one who originally filed this report. I've never been able to get it to work so I am looking forward to it.

EDIT: I still get the crash in the same spot. Must really be bleeding edge whatever proton experimental you're using.

alasky17 commented 2 years ago

@opal1974 The latest experimental release should have the fix now :)

opal1974 commented 2 years ago

@opal1974 The latest experimental release should have the fix now :)

Confirmed 👍🏻 I had to force the update and now it seems flawless.

This report can be changed to a 'Whitelist request'

kisak-valve commented 2 years ago

Hello @opal1974, the workaround added to Proton Experimental means we're on the right track to clearing the regression status once it reaches Proton 6.3. If we're knowingly missing video content in game, it's not ready for a whitelist.

opal1974 commented 2 years ago

At least for me, the cut scenes played fine. I guess I am not sure what's missing? Nothing obvious, but it's been awhile since I played this (either the remix or the original 2009 version).

Or do you mean because it only works in the Experimental version and not a full release, it can't be added to whitelist yet? I remember you saying I couldnt use E for reports before.

opal1974 commented 2 years ago

Ok checking back on this, works great in the 6.3 release, so I think this can be converted to a whitelist request now.

kisak-valve commented 1 year ago

Ghostbusters: The Video Game Remastered - Settings Aren't Saved After Exiting

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7003. @RedSoxFan04 posted on 2023-08-10T19:09:49:

Compatibility Report

System Information

I confirm:

ghost_d3d11.log ghost_dxgi.log

Symptoms

Settings aren't being saved to disk. Consequently, they have to be modified every time the game is launched. Well, unless you're happy with the base settings. Personally, I like to use the highest settings.

Reproduction

  1. Launch Game
  2. Change Graphics Settings
  3. Close Game
  4. Re-Open Game
  5. Check Graphics Settings to See if They Have Changed

Solution

Through research and trial & error, I have found a solution which works: `mkdir ~/.steam/steam/steamapps/compatdata/1449280/pfx/drive_c/users/steamuser/Documents/GHOSTBUSTERS ; mkdir ~/.steam/steam/steamapps/compatdata/1449280/pfx/drive_c/users/steamuser/AppData/Local/GHOSTBUSTERS

alasky17 commented 1 year ago

@RedSoxFan04 Believe it or not, it turns out this is a Windows bug and the game does not create the Local/GHOSTBUSTERS folder by default. I will reach out to attempt to inform the game devs, but if you have a way to leave feedback on the steam page etc for them, feel free to do so :)

KeyofBlueS commented 4 months ago

Dear Valve Proton Team,

I'm experiencing an issue with this game using Proton. When running the game with Proton versions 8 and 9, there are severe and unpleasant artifacts on the characters' face, neck, and chest.

In this report, 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.

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!

https://github.com/ValveSoftware/Proton/assets/45725677/8b03a8a9-ced2-491d-8ea5-1489dacda1c7

steam-1449280_proton-5.13-6.log

steam-1449280_proton-9.0-1.log

kisak-valve commented 4 months ago

Hello @KeyofBlueS, there's multiple years worth of changes between Proton 5.13 and Proton 9.0. Can you test some Proton versions between them and see if you can narrow down the time frame of the regression? Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

KeyofBlueS commented 4 months ago

Thank you so much @kisak-valve for the prompt reply! It's really appreciated.

I've tested the game with Proton 6.3-8 and 7.0-6, but unfortunately, the artifacts persist in those versions as well. It seems that 5.13-6 is the last version unaffected by this issue.

I've attached the Steam Runtime Diagnostics as requested.

Thanks again for your help and support.

KeyofBlueS commented 4 months ago

Actually, the issue has been addressed on the DXVK side.

Thanks and best regards!