Game doesn't start on 3.15.5 #1519
Comments
|
if you know how to compile gamescope does latest master solve it for you? includes this: 6eaee77 |
|
Thanks, it didn't occur to me to try the git version. The game starts and works fine for the most part but it now freezes after an in-game video is played/skipped. There are a few more warnings and errors in the system log though: These lines seem to be of interest, though I'm not sure if some were caused by me terminating the process: |
|
what xwayland version? I have seen that one before, and it was when my xwayland version was too old. |
|
I'm using xwayland 24.1.2 and wayland 1.23.0. I recompiled gamescope this morning based on the latest commit, did a full system upgrade and then tested with both the latest Arch distribution kernel and my custom kernel. Oddly enough everything works fine when I use Steam proton 9.0-2 and experimental (after installing the missing codecs to the prefix). Switching back to proton GE 9-12 (with a new prefix and cleared shader cache) and the freezing issue still happens. I'm not sure what to make of this; without gamescope everything works fine no matter the kernel or proton version used, but only proton GE seems to be affected by whatever changed in the 3.15 gamescope versions. |
|
hmm, my guess is that if you opted into the proton experimental bleeding-edge branch you'd very likely start to run into the same issue as GE 9-12 and GE 9-13, since those both build off that specific branch. i'll see if i can make it happen again on my end although I only have a Nvidia dGPU rig and not a hybrid system |
what does this command show for you? Might also be worth trying in gamescope for your NVIDIA gpu and see if there is any difference in behavior. Right now it looks like gamescope is using your Intel Tiger Lake iGPU. Of course, NVIDIA in gamescope is an entirely different beast and has its own issues, but this may help narrow down the problem you're running into currently. |
|
That command returns these devices: Assuming I'm using it correctly: Produces the same result as before, the game doesn't start. I'll try compiling and using proton experimental bleeding-edge and confirm if it's indeed an upstream issue. |
|
@TintedKiwi you can just search for "proton experimental" in your steam library and opt into it in the entry's settings, like you would for a normal game beta. look for "bleeding-edge" edit: even downloaded the same VN and still not seeing that issue on GE 9-13 when using my NVIDIA dGPU as a compositor like you did with the vk device select option :/ maybe since I don't have an iGPU? not sure... |
|
Oh cool, I wasn't aware that you could do that. I tested using bleeding edge - latest and can confirm everything's working fine. The video that causes the freeze is the one that plays at the end of the prologue, possibly the epilogue as well. edit: I guess the reason it works despite vulkan selecting the iGPU is because I'm connected to an external screen via HDMI which is wired to the dGPU. I also run steam using prime-run so the game subsequently also runs on the dGPU. |
|
okay thanks, I think I finally managed to repro in Sabbat of the Witch on my AMD running Arch proton log to me looks like an issue with how the mf videos are being decoded... in the process of debugging this, I also found a second way to make repro the specific |
|
Ok cool, thanks; I appreciate the help. Ah, the protonmediaconverter errors is a known issue that I have already reported to the umu-protonfixes project. Based on the feedback I’ve received it seems to be a build issue with the proton GE 9-13 release. The game runs fine on GE 9-12 and on a GE 9-13 version I compiled from the git tag as was suggested by umu-protonfixes. |
|
okay, I'll focus on the other way I get the same error then (changing window state), since this one happens even when I don't use Proton-GE, and work from there. |
|
Does using wined3d avoid the issue? |
|
@layercak3 in my case yes, passing WINED3D does seem to avoid the issue I was seeing. I still haven't figured out what makes SteamOS so special in this regard though to work OOTB |
|
@TintedKiwi Do you have a after changing both of those things and running the game with EDIT: realizing now Arch doesn't even package |
|
Try using (enter/exit scene, etc.) other d3d9 KiriKiri-based applications. Installing and using a lib32 WSI seems to prevent it in some places but not others. |
|
@layercak3 happen to know any titles off hand that are on steam? not sure I own any more than this... maybe resident d3d9 expert @Joshua-Ashton can take a look. |
|
@matte-schwartz I've recompiled gamescope from the latest git commit and installed the lib32-gamescope package you mentioned. I tested with my self-compiled proton GE 9-13 build and ran the game with The crash at startup, switching to windowed -> fullscreen -> windowed crash and the game freezing after the prologue video is played/skipped don't happen anymore. However there are now some visual issues with certain confirmation prompts like when opening settings -> Title Screen, and Quit from the home screen. It flashes the prompt rapidly for a few milliseconds before displaying it, the same happens when the prompt closes. This happens regardless of WSI layer enabled or not. After the prologue video is played/skipped the flashing is worse as it flashes with some white background as well. I've tried without lib32-gamescope installed, the prompt flashing is gone but then the freeze issue returns. I also tried running with wined3d (with and without lib32-gamescope installed) but that reintroduces the freezing issue as well. |
|
Thanks for the detailed info @TintedKiwi sounds like this will be a fun issue for a dev to pick apart... |
|
@matte-schwartz the plot thickens unfortunately. Using my usual gamescope + mangohud launch options with lib32-gamemode installed and WSI layer enabled/disabled introduces a new issue. My launch options are: Immediately following startup this window is shown and the game freezes:
Without lib32-gamemode installed the game crashes the moment the prologue video is played. edit: the |
|
The MANGOHUD=1 may be causing issues there, the layer does not play nicely with that method of using it sometimes. Does `--mangoapp` alone change anything?
…On Wed, Sep 11 2024 at 1:33 PM, TintedKiwi < ***@***.*** > wrote:
@matte-schwartz ( https://github.com/matte-schwartz ) the plot thickens
unfortunately. Using my usual gamescope + mangohud launch options with
lib32-gamemode installed and WSI layer enabled/disabled introduces a new
issue.
My launch options are:
GAMESCOPE_ENABLE_WSI=1 LD_PRELOAD="" MANGOHUD=1 gamescope --expose-wayland
-f -W 2560 -H 1440 -r 144 --mangoapp %command%
Immediately following startup this window is shown and the game freezes:
Screenshot_20240911_214831.png (view on web) (
https://github.com/user-attachments/assets/1c55c9af-e4b0-4c15-bd3f-1aba9b181316
)
Proton Log (
https://gist.github.com/TintedKiwi/8d2a292470ee4c193cfe9233d1ac92bf )
System Log (
https://gist.github.com/TintedKiwi/52717855c2ffd42974c7f79f001f3f87 )
Without lib32-gamemode installed the game crashes the moment the prologue
video is played.
Proton Log (
https://gist.github.com/TintedKiwi/b3dc96bab2f6dee59111d7d62307e855 )
System Log (
https://gist.github.com/TintedKiwi/f9c483dd2f457f375e7e51d505410ec2 )
—
Reply to this email directly, view it on GitHub (
#1519 (comment)
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/BAP22TVY3BC77YFYRNXTSU3ZWCSKBAVCNFSM6AAAAABN5RBWYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBUGY2DSNBTG4
).
You are receiving this because you were mentioned. Message ID: <ValveSoftware/gamescope/issues/1519/2344649437
@ github. com>
|
|
Seems that the |
|
@TintedKiwi probably worth a re-test with ddf0d76 to see if it fixes any of the weird behavior for you. also, |
|
@matte-schwartz I've been unable to run anything at all using gamescope (3.14) on my dGPU the past few days. I rebuilt my gamescope-git package and tried that but still no luck with and without the WSI layer enabled. Using these launch options: System log shows 3 Vulkan errors: |
|
@matte-schwartz nevermind, rebuilding the nvidia dkms modules fixed it. |
I'm using a hybrid Intel/NVIDIA system on Arch Linux KDE Wayland using gamescope version 3.15.5.
Launched from Steam the game doesn't start, downgrading to 3.14.29 and everything works fine again.
I have
export ENABLE_GAMESCOPE_WSI=0set in my .bashrc file.I'm running Steam on the NVIDIA GPU and using the following launch options:
Even a simplified launch options still doesn't work:
Here's the relevant log entries:
And for comparison, the relevant log entries for version 3.14.29:
The text was updated successfully, but these errors were encountered: