search

ValveSoftware / Proton

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

GRIP: Combat Racing (396900) #2050

Open kartoffelsup opened 5 years ago

kartoffelsup commented 5 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Trying to start the Game from Steam: steam-396900.log

ERROR: ld.so: object '/home/kartoffelsup/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. wine: /mnt/Games/Steam/steamapps/compatdata/396900/pfx is not owned by you ERROR: ld.so: object '/home/kartoffelsup/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object '/home/kartoffelsup/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. wine: /mnt/Games/Steam/steamapps/compatdata/396900/pfx is not owned by you

Trying from command line yields: env WINEESYNC=1 WINEDLLOVERRIDES="dxgi=n;d3d11=n" WINEDLLPATH="/mnt/Games/Steam/steamapps/common/Proton 3.7/dist/lib64/wine:/mnt/Games/Steam/steamapps/common/Proton 3.7/dist/lib/wine" WINEPREFIX="/home/kartoffelsup/.proton/pfx/" wine64 /mnt/Games/Steam/steamapps/common/Grip/Grip.exe

000b:fixme:winediag:start_process Wine Staging 3.20 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 002a:err:module:import_dll Library dxgi.dll (which is needed by L"Z:\mnt\Games\Steam\steamapps\common\Grip\Grip\Binaries\Win64\Grip-Win64-Shipping.exe") not found 002a:err:module:import_dll Library d3d11.dll (which is needed by L"Z:\mnt\Games\Steam\steamapps\common\Grip\Grip\Binaries\Win64\Grip-Win64-Shipping.exe") not found 002a:err:module:LdrInitializeThunk Importing dlls for L"Z:\mnt\Games\Steam\steamapps\common\Grip\Grip\Binaries\Win64\Grip-Win64-Shipping.exe" failed, status c0000135 0009:fixme:ver:GetCurrentPackageId (0x60fd30 (nil)): stub

Reproduction

Trying to start the game via steam or command-line

Any help is highly appreciated. :)

nsivov commented 5 years ago

wine: /mnt/Games/Steam/steamapps/compatdata/396900/pfx is not owned by you

That's not good. If you're using external storage for your Steam library, try to install or your main filesystem first. Is /mnt/Games using NTFS?

kartoffelsup commented 5 years ago

Is /mnt/Games using NTFS?

Yes. Is that bad as well?

nsivov commented 5 years ago

Likely yes. We've got a number of reports that NTFS partitions don't work well.

kartoffelsup commented 5 years ago

After repartitioning my /mnt/Games to ext4 (and making myself the owner), I am able to start the Game - Thank you! :) Unfortunately, the performance is unbearable :(

kisak-valve commented 5 years ago

Hello @kartoffelsup, please add a new proton log after seeing the poor performance for a short while.

kartoffelsup commented 5 years ago

Hi, thank you so much for your help thus far! It seems I jumped to conclusions. After playing a bit more, 2/3 (RUST, HAZE) Maps that I played were totally playable. Just that 1 Map (SPEEDBOWL) that I had played initially had a 10fps maximum. The other 2 were quite fine to be frank. (around 80fps). Is there anything else I can provide?

In the log, I played the low fps map (SPEEDBOWL) for a bit. (I had to .zip it since it was too big otherwise) steam-396900.zip

kisak-valve commented 5 years ago

The log suggests the degraded performance is nvapi related. Please retest with Proton 3.16-4.

kartoffelsup commented 5 years ago

It unfortunately gets stuck at the loading screen with Proton 3.16-4: steam-396900.log

kartoffelsup commented 5 years ago

Also gets stuck with Proton 3.16-5-beta: steam-396900.log

alasky17 commented 5 years ago

@kartoffelsup I tried to reproduce your failure, but everything ran well for me. Is it getting stuck at the very first loading screen on launch or when you try to start a race?

Also, could you run Steam from the terminal (just typing "steam" in a terminal and hitting enter is enough) and post the output from the terminal? I wonder if a Proton upgrade messed up your game files rather than a regression on Proton's end.

kartoffelsup commented 5 years ago

@alasky17 It gets stuck at the very first loading screen and 'reverting' back to Proton 3.7-8 'solved' it. Would you like the output from the terminal after launching the game or after launching steam?

alasky17 commented 5 years ago

@kartoffelsup After launching the game. However, I'm not sure it will be useful if all you have to do is switch back to Proton 3.7 to "fix" it.

kartoffelsup commented 5 years ago

@alasky17 Yes that 'fixes' the crash but does not solve my initial problem (incredibly low fps in certain maps) which is why I was using the newer version of proton in the first place. I've attached the steam log. Thank you for your help! steam.log

zzhiyi commented 5 years ago

GPU: Intel UHD 630 Driver/LLVM version: Mesa 18.2.5 Kernel version: 4.18 Proton version: 3.16-4/3.16-6beta

Works fine on my PC. Could be driver specific.

kisak-valve commented 5 years ago

Hello @kartoffelsup, can you test Proton 3.16 with nvidia 415.22 or newer?

kartoffelsup commented 5 years ago

Hi @kisak-valve, after upgrading my kernel to 4.20 and nvidia to 415.25 it now works perfectly. The previously troublesome low fps map now also works great. Thanks so much! :smiley:

kartoffelsup commented 5 years ago

A note for those interested, I still struggled with the game not starting initially (completely freezing at the loading screen). I found that setting the PowerMizer Settings in ǹvidia-settings to Maximum Performance would fix this.

minisori commented 5 years ago

It's working great with 4.2-3.

minisori commented 5 years ago

I spoke too soon...

I almost completed the game without any problem and high fps in UW 1440p until the last duel. After the introduction of your opponent a black rectangle pop ups covering most of the screen, the game doesn't freeze but you can't continue no matter what you press and i'm being forced to exit pressing alt+f4. Multiplayer is working too.

Full system report steam-396900.log

Myrddin-Wyllt commented 5 years ago

I've found a regression in the update from Proton 4.11-1 to 4.11-2. Disabling fsync (& esync) doesn't help. In Proton 4.11-1 the game worked perfectly, but after the update & when loading a map, Unreal Engine 4 crashes. The main menu still works (with intermittent crashes), but the game is now unplayable. I've reverted to Proton 4.2-9 until this issue is resolved & I recommend others do the same. Levels won't load anymore in Proton 4.11-2.

leinardi commented 5 years ago

Can confirm the same issue that @Myrddin-Wyllt reported: 4.11-2 crashes but 4.2-9 still works.

System Information

Proton log of the crash: steam-396900.log

alasky17 commented 5 years ago

I believe that this is the same issue affecting MORDHAU #2629 and Deep Rock Galactic #284 and is understood and being worked on.

zandeez commented 5 years ago

Same issues as @minisori , black rectangle over the screen on final duel and cannot progress. https://imgur.com/a/fjk4zLA

aeikum commented 5 years ago

Proton 4.11-3 should fix the regression. Please retest.

Myrddin-Wyllt commented 5 years ago

Retested & it works flawlessly again with Proton 4.11-3 (as for the last level of campaign, I couldn't tell you; this game has deleted my saves more than once...). I've been benchmarking with GRIP for Fsync; performance seems very similar with esync, fsync, and none on this title. Low settings were too inconsistent; I'm looking into setting up the Phoronix Test Suite for more accurate benchmarking & more data.

mimattr commented 4 years ago

~Unfortunately no in-game HUD is displayed/rendered within the HMD when using SteamVR, similar to a separate issue reported by the developer (tested on Ubuntu 19.10 with the Valve Index)~ UPDATE: The VR issue appears to be resolved using Proton 5.13-2 RC3 and SteamVR 1.15.7

@aeikum This behaviour has also been observed in other UE4 titles, perhaps something special is required for handling VR Stereo Layers?

System Information

I confirm:

Reproduction

  1. Select the title within your Library using the Steam client and press the Play button
  2. Launch GRIP: Combat Racing in Steam VR Mode
  3. Select SINGLE PLAYER > RACE > CLASSIC RACE > RACE from the title screen and wait for the race to start
frostworx commented 4 years ago

Grip VR worked some days after it was released on linux via proton. Just tried it again and it both doesn't work with proton-5.0-7 and 4.11-13 The game itself got a depot update, so maybe they broke it with that update for us.

GPU: NVIDIA GeForce RTX 2080
Driver/LLVM version: nvidia-440.82-12
Kernel version: 5.6.11-arch1-1
Proton version: 5.0-7

Attached is the steam-396900.log created with

WINEDEBUG="+steam,+vrclient" PROTON_LOG=1 %command% steam-396900.log

EDIT: Desktop mode still works. The UE4 crash window when starting VR mode shows:

LowLevelFatalError [File:E:\UnrealEngine-4.17.x\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 233] 
Result failed  at E:\UnrealEngine-4.17.x\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Viewport.cpp:289 
 with error 887A0020
zandeez commented 4 years ago

Last level of the campaign, the Borderlands 3 video resolution works...

mimattr commented 4 years ago

Grip VR worked some days after it was released on linux via proton. Just tried it again and it both doesn't work with proton-5.0-7 and 4.11-13

@frostworx VR now appears to work, can you re-test with the latest Proton (5.13-2 RC3) and SteamVR? (1.15.7)

frostworx commented 4 years ago

Thanks for the heads up, @mimattr I can confirm that the game works very good with proton-5.13-2 (some minor flickering in menu 2d textures) Afair it also looked worse last time I tried (must have been in May), but the reason could be me switching to AMD GPU since then.

Flone-dnb commented 3 years ago

I'm unable to launch the game in proton-6.3-3 (same as @kartoffelsup said: "It gets stuck at the very first loading screen"). Worked great on proton-5.0-10b and before - does work in proton-6.3-3.

System Information

GPU: GeForce GTX 1060
Driver version: NVIDIA 460.73.01
Kernel version: 5.8.0-50-generic
Proton version: 6.3-3

steam-396900-proton-6.3-3-not-launching.log

frostworx commented 3 years ago

Just tried it with proton-6.3-3, and it still works fine here.

AMD Radeon RX 6900 XT
5.12.1-xanmod2-2
mesa-21.0.3-3

(only tried with disabled SteamLinuxRuntime via SteamTinkerLaunch)

Flone-dnb commented 3 years ago

I'm just running it from Steam without launch options. I'm trying out your tool right now, it shows me a bunch of errors on start (using Ubuntu).

Just tried it with proton-6.3-3, and it still works fine here.

AMD Radeon RX 6900 XT
5.12.1-xanmod2-2
mesa-21.0.3-3

(only tried with disabled SteamLinuxRuntime via SteamTinkerLaunch)

frostworx commented 3 years ago

Probably some missing dependencies. SLR can simply be disabled via checkbox.

Flone-dnb commented 3 years ago

Probably some missing dependencies. SLR can simply be disabled via checkbox.

Where? I can't find it. :D

frostworx commented 3 years ago

I assume you've found it meanwhile as it is not hidden and also documented. Anyway this is off topic here.

Flone-dnb commented 3 years ago

I assume you've found it meanwhile as it is not hidden and also documented. Anyway this is off topic here.

I'm probably blind but I literally can't find it. Help. XD

frostworx commented 3 years ago

Heh, ok. Go into the "Game Menu", then find "Use Steam Linux Runtime" under the Proton Options category. Alternatively open directly the Proton Category and find it there. Or set USESLR to "0" manually in ~/.config/stl/gamecfgs/id/396900.conf For further help please use the discussion board or issue tracker from the project page directly :)

Flone-dnb commented 3 years ago

Heh, ok. Go into the "Game Menu", then find "Use Steam Linux Runtime" under the Proton Options category. Alternatively open directly the Proton Category and find it there. Or set USESLR to "0" manually in ~/.config/stl/gamecfgs/id/396900.conf For further help please use the discussion board or issue tracker from the project page directly :)

Did not helped. SLR is 100% disabled but I still can't pass the very first loading.

Flone-dnb commented 3 years ago

Found the solution: WINEDLLOVERRIDES=dxgi=n %command%. Now working on the latest Proton. :)

oblitum commented 3 years ago

On latest Proton (6.3-5) this game didn't load for me due to a weird Unread Engine 4 error: It was unable to find the "APEXFramework_x64.dll" from PhysX and gave a fatal error. I end up realizing it was due to filesystem case sensitivity, so I went to /mnt/data/Steam/steamapps/common/Grip/Engine/Binaries/ThirdParty/PhysX/Win64/VS2015 and mv ApexFramework_x64.dll APEXFramework_x64.dll, which fixed the problem and the game then worked flawlessly.

The same thing happened with the "Redout: Enhanced Edition" game, which is based on the same version of the Unreal Engine.

wereii commented 3 years ago

Putting up custom music (placing .mp3 file(s) into .steam/steam/steamapps/common/Grip/Grip/Custom\ Jukebox/) completely kills any music even the "built-in" songs at least in race, outside main menu (which seems to have the same pre-set song).

~~I found this line in the produced log: INFO: Assertion failed: pDSPSettings->DstChannelCount == ChannelCount && "Invalid channel count, DSP settings and speaker configuration must agree"~~

According to this https://github.com/Frogging-Family/wine-tkg-git/issues/61 it also seems to be a problem for broken mic with Deep Rock Galactic. Either way it seems like some problem with Faudio? https://github.com/FNA-XNA/FAudio/blob/398ca114c04343e41068c6f10990464fac7de489/src/F3DAudio.c#L349

EDIT: Scratching the last two paragraphs, it's definitely not the same problem as with DRG, and pretty much not a problem with Faudio as the DSP assertion fails seemingly randomly with no connection to if there is a custom song or not.

Though I found that Grip ships with itself it's own music player common/Grip/Grip/Binaries/Win64/Music\ Player.exe that is not loaded unless you put .mp3|.ogg file into the Custom Jukebox directory, running that program directly with wine runs ok, it prints information about itself and stays running but that's about it.

ranplayer commented 2 years ago

The game hangs after the intro logo is played with Proton 7.0-2 and Experimental.

Logs: steam-396900.tar.gz

Specs: O.S: Manjaro Kernel: 5.15.38 (fsync patched) CPU: Ryzen 7 5700G GPU: GTX 970 4Gb (Driver: 510.68.02)

spinktvis commented 2 years ago

By removing the intro movies as described on https://www.pcgamingwiki.com/api/appid.php?appid=396900

Fixes the hang for me right at the start. The game now starts and loads without issues. Game is running fine with latest Proton and GE.

Kalmaro4152 commented 5 months ago

Though I found that Grip ships with itself it's own music player common/Grip/Grip/Binaries/Win64/Music\ Player.exe that is not loaded unless you put .mp3|.ogg file into the Custom Jukebox directory, running that program directly with wine runs ok, it prints information about itself and stays running but that's about it.

Did you ever find a solution to this problem? I know I found a solution years ago, but I can't remember what I did, nor where I found it. Please let me know! Thank you!