search

ValveSoftware / Proton

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

Marvel's Avengers (997070) #4168

Open NTMan opened 4 years ago

NTMan commented 4 years ago

Compatibility Report

System Information

I confirm:

steam-997070.log

Symptoms

The game immediately crashes after launch. Screenshot from 2021-04-02 00-47-22 Screenshot from 2021-04-02 00-47-58 Screenshot from 2021-04-02 00-46-05 Screenshot from 2021-04-02 00-46-21

Reproduction

Always.

gardotd426 commented 4 years ago

This looks like it might be the offending part: 

23386.338:00c0:00c4:trace:seh:call_teb_handler handler at 0x7b475d00 returned 1
23386.338:00c0:00c4:warn:seh:virtual_unwind exception data not found in L"avengers.exe"
Unhandled exception: page fault on read access to 0x15ce08000 in 64-bit code (0x00000001416147c0).

Followed by a dump

DadSchoorse commented 4 years ago

So it's interesting that the game doesn't load d3d*.dll or dxgi but vulkan-1.dll gets loaded. Can somebody make a log with WINEDEBUG=+vulkan?

NTMan commented 4 years ago

So it's interesting that the game doesn't load d3d*.dll or dxgi but vulkan-1.dll gets loaded. Can somebody make a log with WINEDEBUG=+vulkan?

steam-997070.zip

Screenshot from 2020-09-06 17-56-42

gofman commented 4 years ago

I've tested the game. Attached patches fix the crashes regularly encountered on start (I tested that with mainstream Wine, that should probably work with Proton 5.0.x too but I didn't try). The game was playable for me on Nvidia with the following additional workarounds:

On AMD the game I was hitting Mesa issues (with the current git Mesa and 20.3.0), so no luck yet (maybe it will work with some other Mesa version or GPU, I tested with RX 580) : SPIR-V parsing FAILED: In file ../src/compiler/spirv/vtn_cfg.c:261 b->block && b->block->branch == NULL 39824 bytes into the SPIR-V binary

patches.zip

fsyy commented 4 years ago

Hi,

here the game doesn't start. I compiled proton with your patches, run protonricks and installed d3dcompiler_47 and set it to native, i also put the dxvk.conf with dxgi.nvapiHack = True in the game dir.

I attached the proton log ( last time i tried it got denuvo kick in).

https://gist.github.com/fsyy/2d271e49817a3ad7cd59620e626f46b4

EDIT: i see winedxgi in the top of the log, maybe that is the wrong one.

fsyy commented 4 years ago

here's the log with PROTON_USE_WINEDXGI=0, but still denuvo could now be the issue. i guess i have to wait to try it again.

https://gist.github.com/fsyy/e67594be24bfc34a6390f00273789f14

fsyy commented 4 years ago

today i tried it again, no denuvo this time, but still crashing:

https://gist.github.com/fsyy/6b8799bcea21d866ec88a0b1e5bc4ee8

fsyy commented 4 years ago

if i use PROTON_USE_SECCOMP=1 i get to the launcher, which tells me i have no gpu installed, gpu is shown in the settings, but after i hit play it still crashes.

NTMan commented 4 years ago

I am able to launch the game with proton-5.9-GE-7-ST but when I launch the campaign, after loading (splash screen with heroes) the game crashes

or if the game did not crash I have time to run a hundred meters with stutters before the game hanged or crashed again.

So which logs could be useful?

I use Mesa from git and AMDVLK from git

gardotd426 commented 4 years ago

I use Mesa from git and AMDVLK from git

Which one are you using? You can't use both at the same time, I mean you can have both installed, but when you run the game, you're either using mesa, or AMDVLK. Which one is it?

NTMan commented 4 years ago

You can't use both at the same time

I know. I installed AMDVLK and several times launched the game:

then uninstalled AMDVLK and several times launch the game with RADV (ACO)

NTMan commented 4 years ago

Disappeared face texture on Abu, and hairs on Kamala. Demonstration: https://youtu.be/qakardXQ2-g Proton log: steam-997070-proton-5.9-GE-7-ST-amdvlk-05-crashed.zip

This is happening with both AMDVLK and Mesa drivers. It a driver issue or Wine/Proton? @hakzsam ^^^

GloriousEggroll commented 4 years ago

@NTMan the DirectX11 implementation in the game is not meant to be used and is incomplete. There are no options to select it anywhere in the game or the launcher, and happened to be found existing only by chance. Therefore we cannot validate if it is a game bug or graphics bug. If this is happening on both amdvlk and mesa it's even more so likely to be a game bug. As mentioned in my release notes the game is still very broken, and you should wait until DX12 support works.

ErikReider commented 3 years ago

For anyone else looking, the game now works out of the box using Proton-6.9-GE-1

Edit: The game always crashes when stepping out of the bus in the beginning

mwprado commented 3 years ago

I could play for 3 times when I set VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command% in launcher. Proton was 6.3-4 and I have a Radeon WX4100 running GamerOS 24.

alosarjos commented 3 years ago

Also crasing in the same spot as @ErikReider

Arch Linux (5.15.6-zen) AMD 5700XT Mesa 21.1.5

steam-997070.log

mwprado commented 3 years ago

I could play for hours on chimeraos. However, after Wakanda War update, the game shut off in disclaimer screen. I deleted the game and install it again and now I can't see disclaimer the game came back to steam screen.

Selmack commented 3 years ago

I am having issues trying to launch this game at all in Linux after Wakanda update. This is also after I installed to freshly installed machine. No matter the proton build, or launch option or options I try, this game will not start.

NTMan commented 3 years ago

The game crashes after "Warning read before playing" information. And does not matter which Proton is selected GE or Valve. steam-997070-experimental-6.3-20211011b.log steam-997070-6.19-GE-2.log

20211013145735_1

Selmack commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4168#issuecomment-942131146

Wanted to update my report: This has been my exact experience.

mwprado commented 3 years ago

After last proton experimental update, the game is running again.

NTMan commented 3 years ago

I also can confirm that the game stop crashing with Proton experimental-6.3-20211020 steam-997070-experimental-6.3-20211020.log

Selmack commented 3 years ago

I can also confirm that Marvel Avengers is working with Proton Experimental now!

hakzsam commented 3 years ago

Any RADV related issues with this game or can we drop the label?

dantob commented 3 years ago

Played around 6 hours using RADV no problems, medium settings, does require proton-GE, no other workarounds.

RX 6600XT kernel: 5.14.18 mesa: 21.2.5 proton: Proton-6.21-GE-1

tux-rampage commented 2 years ago

Test results

Played for about 6 hours. Sometimes it freezes the whole system otherwise just some minor glitches:

Workarounds

Environment

GPU: nVidia Geforce RTX 3090 nVidia Driver: 495.44 Proton: 6.3-7 (Steam)

ruineka commented 2 years ago

The game crashes at the loading screen and the game is unplayable. Tested with 6.3.8 with the same results and tried to hide the NVIDIA GPU. Pop OS 20.04 Nvidia GTX 1650 i5 9400f 8GB Ram nVidia Driver: 470.86 Proton: 1641823616 experimental-6.3-2022011 steam-997070.log

EwokExile commented 2 years ago

Tried this out for the first time in months and I'm getting some serious graphical bugs. RX 6600XT Ryzen 1600AF 16gigs Ram Game installed on SATA SSD Latest Nobara Tested on 7.0-4, Experimental and GE 7-31

From one angle I get this, perfectly normal Screenshot from 2022-09-08 13-17-05

Then I turn the camera slightly and this happens Screenshot from 2022-09-08 13-17-18

steam-997070.log

https://gist.github.com/EwokExile/999ff860e37bba6e572596bfa37defce

kisak-valve commented 2 years ago

Hello @EwokExile, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

EwokExile commented 2 years ago

Hello @EwokExile, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Done

hakzsam commented 2 years ago

@EwokExile It looks like you are using Mesa Git, can you please try again after pulling your repo? It might have been a recent regressions that I just fixed in main.

EwokExile commented 2 years ago

@EwokExile It looks like you are using Mesa Git, can you please try again after pulling your repo? It might have been a recent regressions that I just fixed in main.

I'm trying to avoid tinkering with things too much on this machine, so I'll have to wait until @GloriousEggroll pushes an update on Nobara, but that usually happens fairly often. I'll report back as soon as it happens

EwokExile commented 2 years ago

Sad to report that updated Mesa did not fix the issue

NTMan commented 2 years ago

@hakzsam

I can confirm this issue. I used commit https://gitlab.freedesktop.org/mesa/mesa/-/commit/dcc52618952d0e0f2745c0ee443b620cea37ac68 for testing.

Screenshot from 2022-09-11 14-45-29

Unfortunately adding renderdoc capture cause game crashing.

Screencast from 2022-09-11 15-04-57.webm

hakzsam commented 2 years ago

Could you maybe bisect if it's a Mesa or vkd3d-proton regression?

hakzsam commented 2 years ago

Ok, I bisected myself to 1762e6b5406bf6c0ebec84a21fa8eb62f812dd2b

NTMan commented 2 years ago

Could you maybe bisect if it's a Mesa or vkd3d-proton regression?

Unfortunately, I won't be able to build mesa anytime soon due to a change llvm version in my distribution. https://gitlab.freedesktop.org/mesa/mesa/-/issues/7282

hakzsam commented 2 years ago

This RADV regression should be fixed in main, now. Please re-test.

EwokExile commented 2 years ago

This RADV regression should be fixed in main, now. Please re-test.

Tested using 22.3.0-git.20220922.672a1a9.fc36 and the issue is gone

jcc10 commented 1 year ago

I just wanted to provide a update: I'm running on the steam deck and the game runs fine for me, however the steam input generates issues in that it doesn't show correct button prompts for the game. Current fix below:

  1. Connect a controller to the Steam Deck (via blutooth is OK)
  2. Select the game icon (do not launch)
  3. Click on the controller icon to open the controller settings
  4. Set controller type to Gamepad with Joystick Trackpad
  5. Press the LB/RB bumper button to select the newly selected controller
  6. Next to Edit Layout, click on the gear icon
  7. Click on Disable Steam Input > The controller can now be disconnected

(Note: I have not tested this but multiple others have and it seems to work.)

While not directly related to proton, it is a issue that other games might have and it might be nice to have a easy way to "forcibly trick" a game into treating steam input as a specified controller, X-Box or Play Station, as a "escape hatch" for icons not working properly. A simple command line toggle would work. (But again, this is a steam input issue, not a proton issue. So not expecting a fix, but it would probably be a good QOL improvement.)