search

ValveSoftware / Proton

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

Little Busters! English Edition (635940) #1802

Open Jdenki opened 6 years ago

Jdenki commented 6 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Most of the time, the game will open and immediately freeze. When it does, minimizing and reopening the game will allow it to run for a few seconds. The longer it's minimized, the longer it works, up to about a minute. Sometimes the game doesn't launch at all, and I haven't figured out why.

steam-635940.log

Reproduction

Launch the game.

nsivov commented 6 years ago

gnutls integration issue probably:

6189.219:0008:002b:trace:module:MODULE_InitDLL (0x7cff0000 L"bcrypt.dll",PROCESS_ATTACH,(nil)) - CALL 6189.219:0008:002b:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption 6189.219:0008:002b:trace:module:MODULE_InitDLL (0x7cff0000,PROCESS_ATTACH,(nil)) - RETURN 1 6189.219:0008:002b:trace:module:process_attach (L"bcrypt.dll",(nil)) - END 6189.219:0008:002b:trace:module:process_attach (L"crypt32.dll",(nil)) - START 6189.219:0008:002b:trace:module:MODULE_InitDLL (0x6df20000 L"crypt32.dll",PROCESS_ATTACH,(nil)) - CALL 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6df20000,PROCESS_ATTACH,(nil)) - RETURN 1 6189.221:0008:002b:trace:module:process_attach (L"crypt32.dll",(nil)) - END 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6f050000 L"rsaenh.dll",PROCESS_ATTACH,(nil)) - CALL 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6f050000,PROCESS_ATTACH,(nil)) - RETURN 1 6189.221:0008:002b:trace:module:process_attach (L"rsaenh.dll",(nil)) - END 6189.221:0008:002b:trace:module:LdrUnloadDll (0x6f050000) 6189.221:0008:002b:trace:module:LdrUnloadDll (L"rsaenh.dll") - START 6189.221:0008:002b:trace:module:MODULE_DecRefCount (L"rsaenh.dll") ldr.LoadCount: 0 6189.221:0008:002b:trace:module:MODULE_DecRefCount (L"bcrypt.dll") ldr.LoadCount: 1 6189.221:0008:002b:trace:module:MODULE_DecRefCount (L"crypt32.dll") ldr.LoadCount: 0 6189.221:0008:002b:trace:module:MODULE_DecRefCount (L"bcrypt.dll") ldr.LoadCount: 0 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6f050000 L"rsaenh.dll",PROCESS_DETACH,(nil)) - CALL 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6f050000,PROCESS_DETACH,(nil)) - RETURN 1 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6df20000 L"crypt32.dll",PROCESS_DETACH,(nil)) - CALL 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x6df20000,PROCESS_DETACH,(nil)) - RETURN 1 6189.221:0008:002b:trace:module:MODULE_InitDLL (0x7cff0000 L"bcrypt.dll",PROCESS_DETACH,(nil)) - CALL 6189.221:0008:002b:trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) ip=00000000 tid=002b

Jdenki commented 6 years ago

Is there a way of fixing it? A step by step guide of what to test would be helpful and I will report back with my results.

Jdenki commented 5 years ago

Little Busters still has the same issues it had back in Proton 3.16. Is there anyone that can help to fix it?

Jdenki commented 5 years ago

Compatibility Report

System Information

I confirm:

steam-635940.log

Symptoms

Game freezes on startup. Minimizing the game allows it to "run", a few seconds after opening again the game will freeze. This process can be repeated to reach gameplay, but is impractical for actually playing the game.

Reproduction

Launch Game.

trenton4k commented 3 years ago

this game is now running without issues for me

Kyuunex commented 3 years ago

For me, it still does not work. I can see the difference between Proton 5.0 and 5.13. In 5.13, I can at least launch the configuration tool, and it will not freeze unlike with 5.0. But when launching it normally, it literally just crashes before even the window pops up. In past, when trying to launch it normally, this game used to launch and hang half the time, the other half it just errored and crashed like right now. Today, it always errors.

I am very curious why this game does not work, not that I'll play it any time soon but for just technical reasons.

Here is my log attached. steam-635940.log.gz

I'm on Arch / KDE / Kernel 5.10 (LTS) / RX 480 (amdgpu) / Ryzen 2700 EDIT: My MESA is 20.3.4-3 EDIT2: Upgrading MESA to 21 devel did not fix the issue

trenton4k commented 3 years ago

i'm on fedora 33 / KDE / Kernel 5.10 tkg / RX6800 (amdgpu) / Ryzen 3900 Driver Version: 4.6 (Compatibility Profile) Mesa 21.1.0-devel useing ACO

kisak-valve commented 3 years ago

Hello @Kyuunex, err:ole:CoGetClassObject class {f447b69e-1884-4a7e-8055-346f74d6edb3} not registered looks like a relevant line from your log, which might have been fixed in upstream wine 5.10 with https://source.winehq.org/git/wine.git/commit/d45d34cdf5c2fc4b73aa6c07ff04079cdb9fe752.

Maybe try configuring the game to use Proton 5.13 and move/remove the game's wineprefix (which should be in ~/.local/share/Steam/steamapps/compatdata/635940 or equivalent if you installed the game to a second Steam Library) and see if a newly generated wineprefix gets further. NOTE: If the game doesn't cloud save, then this could delete your game progress.

Kyuunex commented 3 years ago

@kisak-valve I already tested with Proton 5.13. In fact, I tested with various versions of Proton and every time I switch to a different Proton version, I always delete the wineprefix and let Proton make a new one.

That log is generated with Proton 5.13 and unfortunately, I can't get any further than what the log says.

ipr commented 3 years ago

With most recent Proton experimental game starts and works fine, including opening movie. I had issues on starting before (like mentioned already here) but now it works fine. Mesa 21.2.3, kernel 5.14.12

kisak-valve commented 2 years ago

Little Busters! English Edition (635940)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5389. @myronas34 posted on 2021-12-08T00:28:51:

Compatibility Report

System Information

I confirm:

Symptoms

  1. The game will not start after restarting my computer.
  2. The game will only start again at random if I launch it enough times. After it launches, there are no problems. Restarting the game itself after it begins to start again poses no problems until I restart my computer.
  3. There is no pattern to when the game will decide to run again other than to install a completely new Proton version, but it will eventually stop working on the other Proton version too. Re-installing steam doesn't work, re-installing proton doesn't work, installing new kernel does until the game fails again much like it does with a newer proton version.

This ZIP file has two logs, one of when the game starts successfully, and of when it doesn't. littlebusters_logs_double_log.zip

Reproduction

Try starting the game. It will likely work the first time.

kisak-valve commented 2 years ago

Hello @myronas34, it looks like if you jump to cImage::Open PARTS/PC_BUTTON in both your logs, things start to get interesting. In the failure to start log, this appears:

err:ole:com_get_class_object class {f447b69e-1884-4a7e-8055-346f74d6edb3} not registered
err:ole:com_get_class_object no class object {f447b69e-1884-4a7e-8055-346f74d6edb3} could be created for context 0x1

and an access violation (c0000005) where the game fails.

It's not clear why this would be influenced by a system restart. I'd expect something like that to always behave or always fail. It looks like you switched from Proton 6.3-8 to Proton Experimental between test iterations where you gathered a log. Can you confirm that the same symptoms happens with the same Proton version in both the working and broken state?

myronas34 commented 2 years ago

Hi @kisak-valve, thanks so much for replying.

Like I explained in my post, the reason I switch Proton versions is because it causes the game to work. But only if I newly install that newer or older Proton version for the very first time, and even if I do this, the game will stop working once I restart and output the same error log just like it did with the previous Proton version I was using. If I switch between already-installed working Proton versions, it makes no difference, so the more Proton versions I install, I so-call "exhaust" them. I've ran out of "new" proton versions to install at this point.

The reason the logs are on a different Proton version is simply because that was what I was using at the time. When the game was working, I quickly captured a log so I could have it for reference. The game wasn't working last night when I made this issue report and provided the logs above, but when I woke up today morning to your message and tried again with Proton 6.3 to provide another log identical to the non-working version for your convenience, it did.

However, to prove that the Proton version doesn't matter beyond "newly installing one for the very first time", here is the log with Proton 6.3 showing the game to work, so now, you have two logs identical in terms of Proton version showing the game to work. No changes made to the system, I just woke up and tried it. But I did notice that when I tried it, a message briefly popped up saying "Processing Vulkan Shaders".

steam-635940.log

So yes, the violation you mentioned varies by a weird unknown factor that changes completely at random, so it's not constant. The company who made this game, Key VisualArts, used their Siglus engine. I have another game of theirs utilising the same engine, and it has no such problems. I'm not sure this matters but I thought it was worth mentioning.

ipr commented 2 years ago

Like I explained in my post, the reason I switch Proton versions is because it causes the game to work. But only if I newly install that newer or older Proton version for the very first time, and even if I do this, the game will stop working once I restart and output the same error log just like it did with the previous Proton version I was using. If I switch between already-installed working Proton versions, it makes no difference, so the more Proton versions I install, I so-call "exhaust" them. I've ran out of "new" proton versions to install at this point.

One thing that comes to mind if something does not exit cleanly and is still hanging in a state that is not fully operable but not finished stopping either. In my case it works every time now but I've seen that behaviour with old versions with some other games in the past.

I would suggest upgrading the distribution if there's a newer one, it might be windowing system or something else that is the culprit.

ipr commented 2 years ago

Another thing that might be behind this: are you using automounted drive for the game which might change paths? Or are you maybe using NTFS, which isn't working well (known issue)?

I think these might explain why it only works right after install.