ValveSoftware / Proton

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

Viscera Cleanup Detail (246900) #672

Open Cuddlypuff opened 6 years ago

Cuddlypuff commented 6 years ago

When starting Viscera Cleanup Detail, at step 1 of 4(or 6) ('installing: Epic Redist Package), I get a popup for Microsoft .NET installation that seems to start fine but eventually freezes at: 'Downloading windows6.1-kb958488-v6001-x64.msu' I tried letting it run overnight but it never finished.

Terminal dump: GameAction [AppID 246900, ActionID 3] : LaunchApp changed task to ShowLaunchOption with "" GameAction [AppID 246900, ActionID 3] : LaunchApp waiting for user response to ShowLaunchOption "" GameAction [AppID 246900, ActionID 3] : LaunchApp continues with user response "0" Loaded Config for Local Override Path for App ID 246900: /home/cuddlz/.local/share/Steam//controller_base/empty.vdf GameAction [AppID 246900, ActionID 3] : LaunchApp changed task to ProcessingInstallScript with "" Proton: Upgrading prefix from None to 3.7-2 (/media/3TB/SteamLibrary2/steamapps/compatdata/246900) GameAction [AppID 246900, ActionID 3] : LaunchApp changed task to RunningInstallScript with "" p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

Steam System Information: https://gist.github.com/Cuddlypuff/a518019d119623d9a1b7552e284c1f6d

JeffLabonte commented 6 years ago

Same thing happens for Smite on Fedora 28. I tried to use the Proton beta as well and it still doesn't work!

Cuddlypuff commented 5 years ago

tried again with 3.7-6 - this time the .net installation doesnt seem to be needed, but the game fails to launch silently. Going through the log, these seem to be the relevant lines:

158765.627:0037:0038:fixme:mscoree:ConfigFileHandler_startElement Unknown element L"generatePublisherEvidence" in state 4 158765.627:0037:0038:fixme:mscoree:parse_probing privatePath=L"Editor/Release" not implemented 158765.627:0037:0038:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed 158765.627:0037:0038:trace:module:LdrShutdownProcess ()

P4NCH1 commented 5 years ago

Same thing happens with Viscera Cleanup Detail: Shadow Warrior (255520)

I've tested it before and is not that the .net installations isn't needed @Cuddlypuff Seems to be that on the 2nd run it assumes that it's already installed.

2nd run launch: steam-255520.log

With Launch 60 bit option: steam-255520.log

System Information

geekaia commented 5 years ago

I have the same problem.

steam-246900.log

jvschiavo commented 5 years ago

I have the same problem with Viscera Cleanup Detail: Santa's Rampage (265210)

captura de tela de 2018-09-14 23-25-23

System info

By the way, shouldn't this installation (.NET framework) be silent?

lucifertdark commented 5 years ago

Compatibility Report

* Name of the game with compatibility issues: Viscera Cleanup Detail

* Steam AppID of the game: 246900

https://gist.github.com/lucifertdark/584c14275612e8e3c4a8070d428d8a02

I've managed to get this game working with Steam Play, here's how to do it......

1. Install the game.

2. find & remove the redist folder & anything that has dotnet in it's name, run the game & wait for it to crash, should take a second or so, if you forget this delete the pfx folder & start again from here.

3. Use Protontricks to install dotnet452 (takes about 5 minutes). at the end click restart now button. "protontricks 246900 dotnet452"

4. download the 64bit vcruntime2012.exe from here https://www.microsoft.com/en-us/download/details.aspx?id=30679

5. use protontricks run taskmngr & use that to run the exe you downloaded. it may seem like nothing happens, just wait a few seconds then shut taskmngr & winetricks.

6. run the game but choose 64bit & only 64bit.

7. enjoy the game.
   ps. This also works for both the extras, Santa's Rampage & Shadow Warrior.
lucifertdark commented 5 years ago

The technique I used above no longer works with the latest Proton 3.16 Beta dotnet40+ refuses to install at all even after multiple attempts.

geekaia commented 5 years ago

steam-265210.log

Cuddlypuff commented 5 years ago

same issue in 3.16-4, tried normal launch and 64-bit launch - doesnt have any issue installing anymore but fails to start

steam-246900.log

Should I change the issue title to better reflect current state?

kisak-valve commented 5 years ago

err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed in the log points towards #18.

RavyuS commented 5 years ago

image Same error as of 3.16-6 Beta!

geekaia commented 5 years ago

it's working, but you need to click on Steam menu and check for updates.

jolty1 commented 5 years ago

It now installs now in proton 4.2-3 and reaches the games splash screen, but crashes when launching.

2224.498:000c:000d:trace:module:MODULE_InitDLL (0x7bc20000 L"ntdll.dll",PROCESS_DETACH,0x1) - CALL 2224.498:000c:000d:trace:module:MODULE_InitDLL (0x7bc20000,PROCESS_DETACH,0x1) - RETURN 1 pid 9206 != 9205, skipping destruction (fork without exec?) crash_20190418231826_11.dmp[9270]: Finished uploading minidump (out-of-process): success = yes crash_20190418231826_11.dmp[9270]: response: Discarded=1 crash_20190418231826_11.dmp[9270]: file ''/tmp/dumps/crash_20190418231826_11.dmp'', upload yes: ''Discarded=1'' pid 9270 != 9269, skipping destruction (fork without exec?)

steam-246900.log

NoXPhasma commented 5 years ago

With Proton 4.2-4 the game now works out of the box. The first installation of dependencies complains once about a missing file, but doesn't have any negative impact. There are some stutters here and there but generally it works pretty nice.

Was also able to improve the performance a lot by using D9VK 0.11.

https://gist.github.com/NoXPhasma/d3ee077b33da13dcf7761c76c40e2a79

jolty1 commented 5 years ago

Can confirm its working out the box now. Performance isn't great though.

Cuddlypuff commented 5 years ago

As I'm the original reporter I figured I should chime in - tried again with 4.2-4 and it worked 100% for me, no performance issues at all anywhere. I'm running a GTX 1070 with 430.14.

Since others are still having issues I'll leave my issue open.

techmouse commented 5 years ago

I don't have the base game of VCD (yet), but I do have the stand alone Shadow Warrior version and it also installs and works great now. Best 2 hours I've spent in a long time. But bad performance seems to be directly linked to how many props are cluttering the map. The more that were removed, the smoother the frame rate got. Reducing shadow and other graphical effects improved performance. But still, with my hardware, shadows shouldn't be a problem. Some improvements can definitely be made here.

techmouse commented 5 years ago

I now have VCD and I've spent a lot of time on it. I can say for sure now where a lot of performance issues are coming from. They appear to be related to the "decals", such as blood splatters, dirt smudges, burn marks, bullet holes, bloody foot prints, and so forth. For some reason they are causing the biggest performance issues. By turning off bloody foot prints in the rules menu just before starting a new level, I'm able to keep the number of decals from increasing too much and this helps keep the framerate above 30.

How to easily reproduce this yourself: Load a level and find a corner with some body parts. Walk to the other side of the map, look in the direction of that corner, and make a note of the FPS. It's at a comfortable 60. Screenshot_20190702_224220

Then go back and start making a mess. All I had to do was walk in circles for about 2 minutes and push the body parts in random directions with the broom. This tiny 2 minute mess dropped the frame rate from 60 down to 30. Screenshot_20190702_224600

Then go back to the other side of the map, look at the corner, and make a note of the current FPS. You'll notice the frame rate stays the same; 30 FPS. So the "decals" will always be a problem whenever you look in their direction, regardless if you can see them or how far away they are. Screenshot_20190702_224637

Then go back and clean up all of the blood. Do not throw away or destroy any of the props. Only remove the blood splatters. You'll notice the frame rate has returned to normal. Screenshot_20190702_225157

Finally, go back to the opposite side of the map one more time and look at the FPS. Again, the frame rate is at 60. Screenshot_20190702_225235

I've done this test multiple times with different graphical settings and nothing impacts the frame rate like the decals. At the highest graphical settings, the difference in the frame rate is negligible. At the lowest settings, the decals will still dramatically affect performance and decrease your frame rate.

I never would have guessed decals could affect performance like this, but there it is. I'm hopeful someone with a better understanding of decals and the Unreal engine can find a better solution here. Removing blood splatters from this game undermines the whole experience, and the fact this is happening could possibly hint at a larger problem with Proton and the Unreal engine. Maybe this issue is specific to VCD, or maybe many other games are suffering from performance issues simply because of the decals. I think exploring this issue in other Unreal engine games could possibly help improve Proton. I would do it myself but I can't think of any off the top of my head where I can easily add and remove them.

Liemaeu commented 3 years ago

The game itself works fine, but the editor (Unreal Development Kit version 10907) crashs on launch.

Proton 5.13-5, Kubuntu 20.04

Any way to fix this?

Proton log:

steam-246900.log