ValveSoftware / Proton

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

Muv-Luv (802880) & Muv-Luv Alternative (802890) #1760

Open aljelly opened 6 years ago

aljelly commented 6 years ago

Compatibility Report

System Information

Log: steam-802880.log (basically, it was missing mfc140u.dll before the 3.16-4 beta)

I confirm:

Symptoms

The visual novel now launches as of 3.16-4 beta. There may or may not be any additional compatibility issues but I haven't started reading the visual novel yet.

Before 3.16-4 beta If you just download the visual novel and launch it, nothing shows up. The visual novel stops showing as running almost immediately after it's run. However, I got it working. It needs the 32-bit version of `mfc140u.dll` (from Visual C++ Redist 2015). ~~I installed it (into Proton's wine prefix) but that wasn't enough for it to work, I had to then go to the syswow64 folder and copy the required dll into the visual novel's folder.~~ (I installed it into the default prefix, and Steam creates new prefixes for each app... see the script below!) Once that's done, the visual novel launches as expected (yay!). ## Reproduction ~Download the game and click Play.~
aljelly commented 6 years ago

(As of 3.16-4 beta workaround isn't needed anymore)

Previous comment (also posted this in #72, but this version is different) If anyone wants a quick way of getting `mfc140u.dll` without trying to run the installer through Proton's Wine (this one will only work for Muv-Luv, the file version at the end of this post will work for other games): 1. Open the terminal and install `cabextract` from your package manager (e.g. `sudo apt install cabextract`). 2. Install the game if you haven't already. 3. Copy paste and run the following in the terminal: ```bash cd "/home/$USER/.local/share/Steam/steamapps/common/Steamworks Shared/_CommonRedist/vcredist/2015" && cabextract vc_redist.x86.exe --filter a11 && cabextract a11 --filter mfc140u.dll && mv mfc140u.dll "/home/$USER/.local/share/Steam/steamapps/common/Muv-Luv/" && rm a11 ``` Run the game, it should now work. --- Here's a file version if anyone wants to automate this, put in the game's folder: ```bash #!/usr/bin/env bash pwd=$PWD redist_dir="_CommonRedist/vcredist/2015" shared_dir="../Steamworks Shared/" if [ -d "$redist_dir" ]; then mfcdir=$redist_dir elif [ -d "$shared_dir/$redist_dir" ]; then mfcdir="$shared_dir/$redist_dir" else echo "Couldn't find Redist dir" exit 1 fi cd "$mfcdir" && cabextract vc_redist.x86.exe --filter a11 && cabextract a11 --filter mfc140u.dll && mv mfc140u.dll $pwd && rm a11 ```
nsivov commented 6 years ago

The issue comes from "Microsoft Visual C++ 2015 x86.cmd", installer is started using "vc_redist.x86", actual file name is vc_redist.x86.exe. Name is not expanded properly, because .x86 considered an extension. This is probably start.exe fault.

aljelly commented 6 years ago

@nsivov I was going to ask if I should report this on the WineHQ bug tracker but I see you've already fixed it in Wine 3.19!

Everyone else: Once Proton's version of Wine is updated to 3.19, VC2015 will install correctly and this game won't need any workarounds to launch it. Thank you nsivov!

nsivov commented 6 years ago

@aljelly should be fixed in 3.16-4 now, please test.

Enerccio commented 5 years ago

Same bug affecting muv luv alternative and is fixed by latest beta!

aljelly commented 4 years ago

Not working as of Proton 5.0-5, but still works fine if you use Proton 4.11-13 instead.

kisak-valve commented 4 years ago

Hello @aljelly, 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.

aljelly commented 4 years ago

Strangely I just tried it again (redownloaded) and now it's working fine in Proton 5.0-5 for some reason. Not sure why.

kekkoudesu commented 10 months ago

I get a Wine C++ Runtime error when I try to launch the game on Proton Experimental, Proton 8, and Proton 3.16. steam-802880.log image

Looks like DXVK is failing. I tried with PROTON_USE_WINED3D=1 %command% and it launches/plays fine with wined3d.

kisak-valve commented 10 months ago

Hello @kekkoudesu, 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.

kekkoudesu commented 10 months ago

@kisak-valve Here you go: https://gist.github.com/kekkoudesu/795d2dd379a62751f7149403354b1689

kisak-valve commented 10 months ago

Thanks, https://gist.github.com/kekkoudesu/795d2dd379a62751f7149403354b1689#file-steam-rt-diag-txt-L82-L97 is the section to focus on. Your 32 bit Vulkan render path might be broken, but it's not immediately clear why. I'd double check that the lib32-vulkan-intel system package is approximately the same version as the rest of your mesa package set.

kekkoudesu commented 10 months ago

I restarted my computer just in case I had updated some of these packages and never restarted before, but the game still fails to launch. These are the local packages I currently have installed:

local/glu 9.0.3-1
    Mesa OpenGL utility library
local/lib32-glu 9.0.3-1
    Mesa OpenGL utility library (32 bits)
local/lib32-mesa 1:23.3.1-1
    An open-source implementation of the OpenGL specification (32-bit)
local/lib32-vulkan-intel 1:23.3.1-1
    Intel's Vulkan mesa driver (32-bit)
local/mesa 1:23.3.1-1
    An open-source implementation of the OpenGL specification
local/mesa-utils 9.0.0-3
    Essential Mesa utilities
local/vulkan-intel 1:23.3.1-1
    Intel's Vulkan mesa driver

But I have an update for vulkan-intel and other vulkan packages pending:

Packages (6) cython-3.0.7-1  lib32-vulkan-icd-loader-1.3.274-1  libraw-0.21.2-1  python-pipx-1.3.3-2  vulkan-headers-1:1.3.274-1  vulkan-icd-loader-1.3.274-1

So I'll install the updates and report back whether that makes any difference. Incidentally, Gamescope works fine on my system and I was able to get games running on Lutris with DXVK enabled.

kekkoudesu commented 10 months ago

Okay, it seems to launch with DXVK after updating...I don't remember completing a partial upgrade, but I suppose that must have happened at some point.

Thanks for the help, @kisak-valve !