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:
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
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).
Weird, so a stub for mfplat makes the game crash, and since Proton 5.13-6 doesn't have this stub, it works?
@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!
I confirm, with the latest Proton Experimental bleeding edge, installed from a clean prefix, the game now works perfectly. Thank you, @alasky17.
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.
@opal1974 The latest experimental release should have the fix now :)
@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'
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.
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.
Ok checking back on this, works great in the 6.3 release, so I think this can be converted to a whitelist request now.
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:
ghost_d3d11.log
ghost_dxgi.log
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.
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
@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 :)
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
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.
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.
Actually, the issue has been addressed on the DXVK side.
Thanks and best regards!
With Proton 10.0-1 beta, I'm encountering a regression where the game window fails to gain focus upon launch. As a result, the game does not respond to keyboard or gamepad inputs. Mouse input does work, but clicking inside the game window does not shift focus to it.
It appears that the system retains focus on the last active window prior to launching the game. For example, pressing Alt+F4 while the game is running closes the previously focused window, at which point the game finally receives focus and starts accepting keyboard/gamepad input.
Additional Observations:
On XFCE (xfce 4.20.2), the desktop panels (xfce4-panel) remain visible and above the game window.
MP4 video playback in-game sometimes shows a green bar at the bottom. This behavior is inconsistent.
These issues do not occur with Proton 9.0-4 (however, under Proton 9.0-4, MP4 playback fails entirely, and the game falls back to playing lower-resolution OGV videos). As an additional note, when testing video playback in this game, please ensure that the MP4 files are actually being used, not the fallback OGV versions, it's easy to mistake one for the other.
Logs (Proton 10 Beta, including green bar issue):
Proton_10.0-1_(beta)_steam-1449280.log
I also tested with Proton Experimental and Bleeding-edge, but the game fails to launch at all in these versions, reporting a lack of D3D11 support.
Logs (Proton Experimental/Bleeding-edge):
Proton_Experimental_(bleeding-edge)_steam-1449280.log
Please let me know if you require further information or testing to help investigate and resolve these issues.
After further testing, it seems these issues are not isolated to this single game (Ghostbusters: The Video Game Remastered).
I reproduced the same problems, lack of window focus and desktop panels staying on top, when running Spyro Reignited Trilogy with Proton 10.0-1 beta.
Additionally, with Proton Experimental and Bleeding-edge, the game fails to launch entirely, citing missing DX11 feature level 10.0 support.
Given that this behavior affects multiple games, it appears to be a broader issue with Proton 10 and Experimental rather than a game-specific one.
Please consider moving this report to a more appropriate category.
I've identified the cause of the window focus issue, it was due to a custom Compiz window rule (No focus) I had set a while ago to work around a Steam client bug where menus would randomly close. With Proton 10, that rule now also matches game windows, which prevented them from receiving focus. After removing the rule, game windows now receive focus correctly again. Unfortunately, this brings back the original Steam menu issue, where menus intermittently close on their own.
Remaining Issues:
I've resolved the issue where games wouldn't launch under Proton Experimental or Bleeding-edge, throwing errors about missing DX11 support.
The root cause is the outdated NVIDIA driver shipped with Debian (actually 535.247.01).
After upgrading to NVIDIA's officially recommended driver (570.144) via the upstream .run installer, the issue was resolved, games now launch correctly.
So, the problem lies with Debian currently shipping an old NVIDIA driver that lacks proper support.
A few days ago, suspecting this was driver related, I submitted a proposal to the Debian NVIDIA maintainers. If you're interested in the discussion or want to contribute, you can find it here.
proton experimentalx7 2025-05proton 10.0x1 2025-05proton 10.0-1x1 2025-05proton 9.0-4x1 2025-05proton 6.3-8x1 2024-05proton 5.13x2 2024-05proton 9.0x1 2024-05proton 5.13-6x3 2024-05proton 6.3x1 2021-11
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