Open marlyn-x86 opened 5 years ago
Game launches fine for me with Proton 4.11-7, and I can play through the tutorial, but it freezes (not crashes) whenever I attempt to play the first world of the story mode with Boki (the first character). Waited for 60 seconds, never responded, so I had to close it. I couldn't close it from the actual window X button and ended up having to force close it from System Monitor. Seems like this indicates it's stuck in a loop somewhere in such a way that even the event system can't proceed...? Also doesn't seem to indicate anything if I attempt to run Steam in a terminal and the game from that; I'm not aware of any way to run the game through a terminal while also from Steam through Proton to gather any more information.
Doesn't seem to matter whether I run in fullscreen or windowed mode, also doesn't matter if I have a controller connected or not. I also tried with Proton 4.2-9 with the same result. Tried changing effects and turning off / on VSync from the graphics menu; no change. Endless mode seems to work fine, though. When running using Proton 3.16-9 or 3.7-8, the game simply doesn't launch at all.
Running Solus, fully updated, tried both with the Steam integration and without; no change.
Computer Information:
CPU Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD FX(tm)-6350 Six-Core Processor
Speed: 3900 Mhz
Operating System Version:
"Solus" (64 bit)
Kernel Name: Linux
Kernel Version: 5.2.20-130.current
Video Card:
Driver: NVIDIA Corporation GeForce GTX 660/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 430.50
OpenGL Version: 4.6
Memory:
RAM: 24104 Mb
Please let me know if you need any more information. Thank you!
Hello @SolarLune, please add PROTON_LOG=1 %command%
to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Whoops, I forgot all about PROTON_LOG. Sorry about that, and thank you for the reminder!
Here's the log file: steam-349250.log
I should add some details myself - for prefixes created at the present time the game seems to freeze upon attempting to load the thumbnail for each level. I have an old prefix from earlier versions of steam that is able to pass this thumbnail loading step, but something changed since then that induces this softlock. Is there a good way to isolate a difference between wine/proton prefixes?
I looked into this and it seems to be the same issue as https://github.com/ValveSoftware/Proton/issues/4271, mono traces end at FNA3D_CreateTexture2D and the main thread entering mono_monitor_enter_v4_internal.
FNA3D_FORCE_DRIVER=Vulkan is a workaround but even at first glance corrupts the launch window graphics.
You could also try WINE_MONO_OVERRIDES=Microsoft.Xna.Framework.*,Gac=y
which will force it to use MS XNA from the redist instead of FNA.
Compatibility Report
System Information
I confirm:
Symptoms
The game is unable to run due to the following two missing frameworks: dotnet40 xna40
Treatment:
Consult #18 for details on installing custom frameworks to a compatibility prefix
The game should now be able to be run at any time with the following caveat: During installation, you may see a message saying that a framework is missing. This message can seemingly be ignored with no other negative impact.