search

ValveSoftware / Proton

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

Marvel's Guardians of the Galaxy (1088850) #5250

Open CaptainDerank opened 2 years ago

CaptainDerank commented 2 years ago

Compatibility Report

System Information

I confirm:

Symptoms

The Launcher opens and after clicking "Play" in the Launcher the Game will start, but crashes after a few seconds.

Reproduction

Start the Game and click "Play" in the Launcher.

steam-1088850.log

NTMan commented 2 years ago

System Information

steam-1088850.log

Symptoms

The game crashes immediately after start.

Reproduction

Always.

NalianNalis commented 2 years ago

the game now works, i have compiled vkd3d with the latest pull requests and replaced the dll it still has performance issues that need to be resolved, low inconsistent fps. here a video at 1080p, https://streamable.com/nb8zco

ruineka commented 2 years ago

the game now works, i have compiled vkd3d with the latest pull requests and replaced the dll it still has performance issues that need to be resolved, low inconsistent fps. here a video at 1080p, https://streamable.com/nb8zco

It works on AMD, but it isn't working on Nvidia even with the latest 495.44 driver.

mikeant42 commented 2 years ago

I'm on AMD and the game is working for me, but the performance is bad. It also crashes every time we try to warp away for the first time, tried new save, new proton version etc. So I'm stuck and can't make it past essentially the intro, not sure.

Also would recommend using WINE_FULLSCREEN_FSR=1, and running the game at a lower resolution, especially if you're above 1080. Upscales pretty well. Only available on proton GE.

bundyo commented 2 years ago

With the aforementioned vkd3d-proton patch, the game works fully with Proton 6.20-GE-1, but crashes on specific places, like entering the code for the Nova field in the beginning. Updated to latest patch, GE still crashes, but switching to Proton Experimental (with the same vkd3d-proton dll) allows passing through the crash and landing without problems. However, all menus and subtitles are invisible and the game hard to navigate.

bundyo commented 2 years ago

The fix is merged in vkd3d, and now the ball is in this issue, as all menus and subtitles in the game with Proton Experimental are invisible. Proton 6.20-GE-1 has them working, but crashes on specific places probably connected with text again.

ofcaah commented 2 years ago

The fix is merged in vkd3d, and now the ball is in this issue, as all menus and subtitles in the game with Proton Experimental are invisible. Proton 6.20-GE-1 has them working, but crashes on specific places probably connected with text again.

Either Proton Experimental was updated very recently or there's something strange going on. I have black screen on 6.20-GE1, and on Proton Experimental game starts, menu is working, but game crashes a second or two after Marvel logo.

bundyo commented 2 years ago

The fix is merged in vkd3d, and now the ball is in this issue, as all menus and subtitles in the game with Proton Experimental are invisible. Proton 6.20-GE-1 has them working, but crashes on specific places probably connected with text again.

Either Proton Experimental was updated very recently or there's something strange going on. I have black screen on 6.20-GE1, and on Proton Experimental game starts, menu is working, but game crashes a second or two after Marvel logo.

Even though changes in vkd3d were merged, that doesn't mean that PE was updated with it. ;)

Also the fix was AMD only.

NalianNalis commented 2 years ago

the game works with latest proton experimental, al least on amd rdna2, menu shows up and you can start playing after the cinematics. i didnt test further if there are some game breaking bugs like the ones we had at the start, in the discussion on VKD3D-Proton github. now i have compiled mesa 22. git. to test performance. the game does not enable Raytracing, after i use VKD3D_CONFIG=dxr11 RADV_PERFTEST=rt. options stay grayed out.

bundyo commented 2 years ago

Seems PE still crashes on the same places.

SveSop commented 2 years ago

Yeah, seems nVidia users are still stuck with a crash right after the Marvel into logo...

01b4:warn:vkd3d_is_linear_tiling_supported: Attempting to create linear image, but not supported.
usage: 0x17, flags: 0x20, fmt: 98, image_type: 2
01b4:err:d3d12_resource_create_placed: Failed to bind image memory, vr 1.
01b4:fixme:hresult_from_vk_result: Unhandled VkResult 1.

Issue is "closed" on vkd3d-proton git tho, so dunno if it is deemed a "driver issue/wontfix" or something?

bundyo commented 2 years ago

New update today. Among the release notes:

Also some crash fixes.

bundyo commented 2 years ago

Seems there are no visible changes to FPS I can see, except when Dynamic Resolution Target is on (which I didn't notice working at all before). However it started better, then went kaboom:

Screenshot_20211123_230133

ruineka commented 2 years ago

Edit: Same error on Windows still as well.

I tested using the NoLauncher option using Intel Iris Xe graphics and it still says no compatible d3d12 device found. Bummer. About to test on Windows next.

tfks commented 2 years ago

Just got a new update of the game 11/23/2021 containing some stability related issues:

bundyo commented 2 years ago

Yeah, I was talking about that one. The round log thing no longer crashes, so my guess is that all the rest similar crashes are also fixed. No performance gains on my RX 6800 though. If I'm reading properly the benchmark up there, seems the game doesn't use CPU and GPU very efficiently.

bundyo commented 2 years ago

Edit: Same error on Windows still as well.

I tested using the NoLauncher option using Intel Iris Xe graphics and it still says no compatible d3d12 device found. Bummer. About to test on Windows next.

I think someone mentioned, that 4GB RAM is required, not sure if Xe has that.

The official requirements: https://www.systemrequirementslab.com/cyri/requirements/marvels-guardians-of-the-galaxy/20969

ruineka commented 2 years ago

It's much like the AMD apus, it has shared memory. So if I have 16GB of ram that is the pool that is shared. This game runs on Vega 10 graphics, but not on Intel. Games like Red Dead Redemption 2, Cyberpunk, Witcher 3, and more to name a few run just fine on Iris Xe and AMD integrated graphics.

On Tue, Nov 23, 2021, 4:01 PM Bundyo (Kamen Bundev) < @.***> wrote:

Edit: Same error on Windows still as well.

I tested using the NoLauncher option using Intel Iris Xe graphics and it still says no compatible d3d12 device found. Bummer. About to test on Windows next.

I think someone mentioned, that 4GB RAM is required, not sure if Xe has that.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/Proton/issues/5250#issuecomment-977206661, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD42HD6XBAUJAIXC54KMGVLUNQFNHANCNFSM5GYNMBMA .

bundyo commented 2 years ago

It's much like the AMD apus, it has shared memory. So if I have 16GB of ram that is the pool that is shared. This game runs on Vega 10 graphics, but not on Intel. Games like Red Dead Redemption 2, Cyberpunk, Witcher 3, and more to name a few run just fine on Iris Xe and AMD integrated graphics.

It doesn't really work like that - the video memory is set aside for video in the BIOS and is not used as normal memory afterwards. So check if you can share more video memory to Xe in there. Also I think Wine/Proton can lie to the game about how much really the video memory is, although I don't remember where this is configured.

ruineka commented 2 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/5250#issuecomment-977552848

I'm pretty sure it does, half the system memory available is allocated to GPU memory on newer Intel graphics. https://www.intel.com/content/www/us/en/support/articles/000020962/graphics.html

In my case I'd have a maximum of 8GB since I have 16gb of ram in my device. It's all dynamic and in most cases the bios option that we used to see with older integrated graphics are no longer available because its not static like it used to be in the past.

bundyo commented 2 years ago

I'm pretty sure it does, half the system memory available is allocated to GPU memory on newer Intel graphics. intel.com/content/www/us/en/support/articles/000020962/graphics.html

In my case I'd have a maximum of 8GB since I have 16gb of ram in my device. It's all dynamic and in most cases the bios option that we used to see with older integrated graphics are no longer available because its not static like it used to be in the past.

This seems like a new development in Win10+, that I've missed. Then again, if Windows is using half the RAM for video, then Xe might be completely not supported by the devs.

ChaosBlades commented 2 years ago

Xe drivers are not anywhere near as mature as AMD/Nvidia/Old Intel GPUs. So don't rule that out as well. Xe is completely new from the ground up if I am not mistaken and the base for Intels foray into high end dedicated GPUs. I would guess it would be Xe driver issue over Windows. It would not be my choice of stable testing platforms is all I am saying.

kisak-valve commented 2 years ago

Hello, the VKD3D-Proton devs have noted here that there hasn't been any been any testing against Intel graphics, so it wouldn't be surprising if there are hardware limitations that are not accounted for in the translation layer or if VKD3D-Proton stresses mesa/ANV in ways that the driver devs have not seen before.

ruineka commented 2 years ago

Hello, the VKD3D-Proton devs have noted here that there hasn't been any been any testing against Intel graphics, so it wouldn't be surprising if there are hardware limitations that are not accounted for in the translation layer or if VKD3D-Proton stresses mesa/ANV in ways that the driver devs have not seen before.

I'm thinking it's almost guaranteed to be this, nobody is testing on Intel so things at a driver level and at a game engine/compatibility layer level aren't looked at. So although the hardware is more than capable the drivers/software just isn't. I've shared my experiences with Mesa and with DXVK to let them know that gaming devices do exist now that use Intel and it's not the old-school intel HD graphics days anymore, Iris Xe packs a serious punch much like how the AMD APU does in the Steam Deck and similar devices.

vaslabs commented 2 years ago

The benchmark works pretty well, but when starting the story, it crashes before the first mission starts, just as gamora says the code is 0451. the screen opens Drax starts to speak, then game crashes, every time. Both with 6.3-8 and experimental, I also tried the latest mesa drivers and latest vkd3d

steam-1088850.log

20211130001758_1

Update: I started a new game and moves around the ship before the crashing scene. You can interact to an item next to the radio in the main room, if doing so the game crashes there too.

bundyo commented 2 years ago

The overall slowness might be caused by this issue:

https://github.com/ValveSoftware/Proton/issues/5346

By adding PROTON_NO_FSYNC=1, my game started using my CPU more and FPS doubled. Still can't run it on pure 4K, but using AMD FSR on 3200x1800 now produces ~60 FPS on RX 6800.

vaslabs commented 2 years ago

I've built this https://github.com/ValveSoftware/Proton/releases/tag/experimental-6.3-20211106 and got passed the initial issue (no dialogs/ui so you have to guess the keystrokes), then continued with proton 6.3-8 , I'll put more updates here. It seems the issue is in vkd3d since swapping it in from recent builds I have the same crashing issues

Edit: during the first mission there's a donut looking hologram, crashes there too with proton 6.3-8

Edit2: doing sound=pulseaudio via winetricks solves the issue for me crashed after a while :/ Edit 3: waiting for the dialogs before picking these log items also seems to help I'll update here as I go through the game

bundyo commented 2 years ago

Okay, waiting for dialogs pointed me in an interesting direction - at first I thought it was audio only, but after nothing helped (overriding xaudio dlls, etc.), I got an idea - we already know that PE without any text/UI works and passes through the crash. And audio is connected to text - the subtitles. :) Stopped all subtitles and the donut log devices started working! Radio and code entry in the beginning still crashes though, so donuts and other crashes might turn out unrelated...

vaslabs commented 2 years ago

Nice find

vaslabs commented 2 years ago

After a lot of trial and error (couldn't proceed to chapter 5) I found the area of the code that crashes, this is related to vkd3d https://github.com/HansKristian-Work/vkd3d-proton/issues/937#issuecomment-986076002 I have a build that just removes the lines that cause the crashes I encountered, so far so good, I'll keep updating if I find something else (This is not my area of expertise, even though the build works for me, use at your own risk)

Edit: reached chapter 10 with no crashes, end of chapter 7 when exploring the videos there's some background breakage, could be the game's , still video is clear to watch

Edit 2: after a while (on my system about a couple of hours) the game slows down, a restart fixes the frame rate

Edit 3: just finished the game with that workaround, no crashes. At the credits there's some breakage on the edges, maybe mfplat related

bundyo commented 2 years ago

I usually change the resolution and the frame rate gets fixed.

alosarjos commented 2 years ago

Hi there! Just tried the game with an AMD 5700XT. Performance is HORRIBLE, is there anything that can be done about it?

bundyo commented 2 years ago

Hi there! Just tried the game with an AMD 5700XT. Performance is HORRIBLE, is there anything that can be done about it?

You can use Proton-6.21-GE-2 and WINE_FULLSCREEN_FSR=1 PROTON_NO_FSYNC=1 %command% as command-line arguments. Make sure to switch exclusive fullscreen option on and use resolution less than your desktop resolution, so thatWINE_FULLSCREEN_FSR=1 can kick in (this is not yet available in Proton Experimental). The second option is to avoid the high CPU usage bug I mentioned 8 days ago, that may also steal some fps from the game. In game settings you can switch off vsync and boost max refresh rate and dynamic resolution target to max. This way I'm getting ~75 FPS on title screen with 3200x1800 upscaled to 4K (of course with 6800). At least for FullHD, you should be able to get similar FPS with your card. Don't upscale too much or it will become blurry.

bundyo commented 2 years ago

Also, make sure to check this comment by @vaslabs, as his build fixes all game crashes, including the code entry one in the beginning. Just replace the dlls in your GE folder.

alosarjos commented 2 years ago

@bundyo Thanks a lot. It has improved a bit, but still it's like half the framerate I have on Windows...

vaslabs commented 2 years ago

@bundyo Thanks a lot. It has improved a bit, but still it's like half the framerate I have on Windows...

I have the exact same gpu and it's playing great, I'm on fedora 35 with Wayland

NalianNalis commented 2 years ago

@vaslabs do you experience framedrops? like you have 100+ fps and you move around and it goes don to 50?

i have tested that on F35 Wayland / X11 and on Manjaro X11 RX 6800 and it is the same issue. i think Hans-Kristian from VKD3D-Proton said that he has not bein able to resolve this issue.

vaslabs commented 2 years ago

Hm, I didn't notice during gameplay, but my screen is 60Hz and I have the frame rate limit on 60. I'll try to test in the weekend with some profiling and see

Can you share your system info, for instance I have 16 cores, just to see if there's CPU bound computation and what are the differences

If it's an issue with vkd3d or Mesa there's not much we can do but report and wait I guess, but I finished the game without any noticeable issues

NalianNalis commented 2 years ago

@vaslabs Ryzen 5800x 16GB ram RX6800 F35 wayland Gnome, Proton Experimental - Bleeding Edge, 3440x1440 144hz, Mesa 21.3.1 and also locally compiled mesa folder (it does not interfere with the rest of the system) mesa-dev 22. i use a scrip for that in the launch options.

vaslabs commented 2 years ago

Thanks more or less the same apart from ram (64GB) but I don't think I'd notice the kind of frame rate drop (like from 60 to 50), so I'll remove the limits and run it with profiling and see. I'll let you know in a few days, I can't test today

bundyo commented 2 years ago

@vaslabs do you experience framedrops? like you have 100+ fps and you move around and it goes don to 50?

i have tested that on F35 Wayland / X11 and on Manjaro X11 RX 6800 and it is the same issue. i think Hans-Kristian from VKD3D-Proton said that he has not bein able to resolve this issue.

I had sudden framedrops - usually get fixed if you change the resolution, then revert back. Make sure to use PROTON_NO_FSYNC=1 as it improved my frame rate considerably (I'm with the same GPU). Also use GE-6.21-2 and FSR, as I mentioned earlier.

vaslabs commented 2 years ago

Ah I have these too yeah, but it wasn't sudden (well not during interactive play I guess) , just seemed something was being triggered after cinematic scenes and getting heavy

NalianNalis commented 2 years ago

@vaslabs here an example, it is old mesa 21.2 but this is how the game still behaves even on newer mesa, i will try the fsync option later

https://streamable.com/nb8zco

NalianNalis commented 2 years ago

Ok i did some further tests pulled latest mesa-dev,

with mesa 21.3.1 is the same issue as in the video above. GE and proton experimental Bl.-edge FSR and no fsync ( enabeld and disabled those options)

with mesa 22 -dev same setup as above there are no frame drops game stays above 130 fps even after removing all launch options and using only proton experimental bleeding edge , except mangohud and of course the mesa22-dev script

alosarjos commented 2 years ago

Ok, was just a matter of using mesa-git instead of latest stable on Arch. Now game is running amazing.

bundyo commented 2 years ago

I'm on dev mesa from probably half an year, so they probably fixed it recently, as I for sure had frame drops before.

bundyo commented 2 years ago

Something changed in the latest dev mesa, and I'm suddenly able to run the game on full 4K with minimum 80 FPS (6.21-GE-2).

image

SveSop commented 2 years ago

Yeah yeah.. rub it in for us poor sob's that are stuck with nVidia :smiling_face_with_tear:

NalianNalis commented 2 years ago

@bundyo are you experiencing flickering in the game? we have an open issue at Mesa Github.

https://streamable.com/zt0qne

bundyo commented 2 years ago

@bundyo are you experiencing flickering in the game? we have an open issue at Mesa Github.

https://streamable.com/zt0qne

Yes, mainly in Peter's house.