Marvel's Guardians of the Galaxy (1088850)

[CaptainDerank]

Compatibility Report

• Name of the game with compatibility issues: Marvel's Guardians of the Galaxy
• Steam AppID of the game: 1088850

System Information

• GPU: Nvidia Geforce RTX 3070
• Driver/LLVM version: nvidia 470.74-10
• Kernel version: linux-zen-5.14.14.zen1-1
• Link to full system information report as Gist: https://gist.github.com/CaptainDerank/aadf1f4d999e74b0a863aa48969a45b9
• Proton version: Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

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]

System Information

• GPU: AMD Radeon 6900XT
• Driver/LLVM version: Mesa 22.0-git/13.0.0
• Kernel version: 5.15-rc6
• Link to full system information report as Gist
• Proton version: experimental-6.3-20211020

steam-1088850.log

Symptoms

The game crashes immediately after start.

Reproduction

Always.

[NalianNalis]

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]

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]

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]

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]

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]

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]

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]

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]

Seems PE still crashes on the same places.

[SveSop]

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]

New update today. Among the release notes:

• Fix for refresh frequency issue with exclusive Fullscreen
• Addition of -NoLauncher command line option to suppress launcher
• CPU performance optimizations for RT
• GPU performance optimizations, particularly at higher resolutions

Also some crash fixes.

[bundyo]

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:

[ruineka]

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]

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

• General stability improvements
• Multiple improvements to stability with Ray Tracing enabled
• Fix for refresh frequency issue with exclusive Fullscreen
• Fix for a few rare crashes during combat
• Fix for a rare visor crash
• Fix for a rare crash when using Drax's wrecking ball ability
• Fix for a rare crash during dog fight

[bundyo]

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]

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]

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 <#5250 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD42HD6XBAUJAIXC54KMGVLUNQFNHANCNFSM5GYNMBMA> .

[bundyo]

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]

Replying to #5250 (comment)

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]

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]

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]

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]

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]

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

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]

The overall slowness might be caused by this issue:

#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.

[bundyo]

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]

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).

[SveSop]

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

[NalianNalis]

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

https://streamable.com/zt0qne

[bundyo]

@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.

[selektionsrest]

Is there an easy way (because i am new to linux) to get the Game working on AMD? (5800x & 6800xt) Runs fine till the point where i have to enter the Code.

[vaslabs]

Is there an easy way (because i am new to linux) to get the Game working on AMD? (5800x & 6800xt) Runs fine till the point where i have to enter the Code.

you can find the proton directory used to run your game, let's say for example it's proton 6.3

right click on it and do browse local files.

Follow this path

to see

Then replace the d3d12.dll with the one from here

(in the x64 folder)

if you want to reset your proton as it was, right click again on it, properties, local files, click verify integrity

bare in mind that if it gets updated the changes will also be lost

[howels]

Any possible fix for nvidia cards?

[zixaphir]

Is there any further steps that can be taken to improve things on the nvidia side? On AMD, the game appears to be working at least in a playable state, but on nvidia, it still crashes with the same error present in the original first post of this issue.

Last message before trace is

01d8:warn:vkd3d_is_linear_tiling_supported: Attempting to create linear image, but not supported.
usage: 0x17, flags: 0x128, fmt: 98, image_type: 2
01d8:warn:vkd3d_get_image_create_info: Linear image not supported, attempting without EXTENDED_USAGE as a workaround ...
01d8:warn:vkd3d_is_linear_tiling_supported: Attempting to create linear image, but not supported.
usage: 0x17, flags: 0x28, fmt: 98, image_type: 2
01d8:warn:vkd3d_get_image_create_info: Linear image not supported, forcing OPTIMAL tiling ...
01d8:err:d3d12_resource_create_placed: Failed to bind image memory, vr -1000011001.

System Information

GPU: Nvidia Geforce GTX 1080 TI
Driver/LLVM version: nvidia 510.68.02
Kernel version: 5.17.5-76051705-generic
Link to full system information report as Gist: https://gist.github.com/zixaphir/12dca73e30b37ccfb0a17fe77492a27e
Proton version: Experimental [bleeding-edge]

Symptoms

Game starts, plays intro videos, but crashes with a black screen while music plays where the main menu should be.

Reproduction

Run the game on a system with the proprietary nvidia driver stack

steam-1088850.log

[joethefox]

With latest nvidia beta drivers 515.43.04 the game starts, looks playable and doesn't crash anymore after the intro movie with the marvel logo. Needs further test due the limited time I had.

[howels]

With latest nvidia beta drivers 515.43.04 the game starts, looks playable and doesn't crash anymore after the intro movie with the marvel logo. Needs further test due the limited time I had.

Which proton version?

[joethefox]

GE-Proton7-17

with proton 7.0.2 there were graphical glitches

[SveSop]

With latest nvidia beta drivers 515.43.04 the game starts, looks playable and doesn't crash anymore after the intro movie with the marvel logo. Needs further test due the limited time I had.

@joethefox What GPU is that? And possibly what config settings did you use (Eg. any custom user_settings.py stuff or commandline). I did not get further than the start of the intro-music with same driver + GE-Proton-7-17 on my RTX2070, but we might not be using the same settings otherwise...

[joethefox]

It's a 3060ti running on 5.15 kernel (latest xubuntu). No special config file. The command used to start is:

PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 gamemoderun %command%

[SveSop]

Interesting... I ran it with DXVK_ENABLE_NVAPI=1 aswell, and thus being able to select DLSS in the "settings window" that pop up before launching the game... and that seems to mess things up. Dropping that, and it seems to fire up and atleast be able to run the benchmark.

I guess that little settings window uses DX11 and dxvk then, and there is some nvapi setting that does not play nice with the game. Setting DLSS from the display settings when ingame seems to work fine tho (when running without the aforementioned DXVK setting), so i am not sure whats going on there. Time to investigate i guess 😄

[SveSop]

Right - so after a bit of testing, it seems vkd3d chooses a different codepath if it detects a real NVIDIA adapter (DXVK_ENABLE_NVAPI=1), and that is the reason the game bugs out.

Found the following to be the smoothest way to set things as of now: (Cleaning steam prefix 1088850 is always nice for a fresh start)

First time - start the game with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_ENABLE_NVAPI=1 %command% This way you are able to set graphics options + DLSS in the launcher/config app. Set that, hit apply and just choose QUIT to close it.

Then you run the game with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% and just press "play" in the launcher, and you have your DLSS setting++ configured in game.

Game seems to run rather well.. have seen a couple of artifacts here and there, but i believe from the little i have played so far it is working.

[Bitwolfies]

Using a GTX3080, the game will run just fine on its first boot, after that though, if you quit and restart the framerate is absolutely destroyed, and the only fix is to restart my computer itself.

[howels]

Still crashes to desktop on RTX 2080ti with 515 driver and Proton experimental or ProtonGE 7.24. Tried adding the PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% launch option but although I can get the initial window up and then click play, after the intro videos play the game quits every time.

[thebobbyboy420]

NVIDIA GeForce RTX 2060 SUPER
Driver Version: 515.65.01

Still crashing after the marvel intro movie :(

[SveSop]

A recent commit to vkd3d made it bork for some unknown reason on my NVIDIA adapter. I made it work like this, but it requires compiling vkd3d yourself.
HansKristian-Work/vkd3d-proton#1216 (comment)

It should not fail like this according to vkd3d dev´s so it might be only me and a few select thousands of other NVIDIA users perhaps 😏

[ruineka]

Using VKD3D_FEATURE_LEVEL=12_0 you are able to launch the game without the direct3d adapter not compatible error, but it closes after the initial intro movie on a Intel A750 Arc GPU.

Running with Mesa 22.3.1 - kisak-mesa and kernel 6.0.6-76060006-generic on Pop OS.
steam-1088850.zip

[mbriar]

@ruineka this game won't run on Intel until the features mentioned in this bug are implemented in anv: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5003

[der-eismann]

The game's performance is great on my AMD 6900XT, however I experience heavy flickering whenever I'm in a darker area like Peter's house or the caves on Maklu IV. Tried different shadow settings, but the flickering never stops.

[Blisto91]

@der-eismann You mean this kinda flicker?

Screenshot

[der-eismann]

Hmm, I think it looks a bit different. However I finished the game and forgot to make a good savegame where I'm in the basement, can you share it? I only got this scene from the start of chapter 9: https://imgur.com/iYv75LF
Funny thing is that when I take a screenshot with F12, the flickering stops for a short moment.
System is Fedora 37, kernel 6.1.11, Mesa 22.3.5, Proton 7.0-6

[Blisto91]

can you share it?

Haha no i played for like an hour to get here and then found i couldn't save 😁

Ah Proton 7. I'm guessing it's this bug then that has been fixed a while ago and is available in experimental HansKristian-Work/vkd3d-proton#1147
Proton 7 has quite a outdated vkd3d-proton due to backwards compatibility. Proton 8 stable should include it tho (not out yet).

[der-eismann]

I just did a quick test with Proton Experimental and it seems indeed like it was fixed. It's about time they release Proton 8 🙂 Experimental always sounds so buggy and unfinished.

[hjpaul7]

Is there a command prefix needed to get DLSS working? It was working at one time about two years ago.

[SveSop]

Is there a command prefix needed to get DLSS working? It was working at one time about two years ago.

The simplest way i know of enabling DLSS on GotG is to edit the proton file (assuming you are using proton 9 or similar), and then hash out the line with Guardians of the Galaxy like this:
# "1088850", #Marvel's Guardians of the Galaxy

However, note that this probably will be reverted every update (atleast if you do not use GE or copy it to compatibilitytools.d folder)!

Then you start the game, and open the "Options" in the launcher, and select your settings including NVIDIA DLSS quality. IF it is grayed out, you could try to launch the game with PROTON_ENABLE_NVAPI=1 %command% but you should not have to.

Once you have set your config in the launcher, click "Apply" and QUIT so it closes!

Then, go into the game folder (typically something like: SteamLibrary/steamapps/common/Marvel's Guardians of the Galaxy/bin (depending on where your actual library is), and create a file called dxvk.conf
This file should contain only this line:
dxgi.customVendorId = 1002

Next, launch the game and click PLAY (do NOT enter the Config part again!).

This should launch the game with DLSS.

You can change DLSS mode ingame, and comparing between quality and ultra performance for me showed quite a difference in image quality and cpu "time" when running the benchmark, although not so much in fps as i suspect the test machine i am using is somewhat cpu limited i guess.

[turin331]

The flickering bug seems to be back for me. Tried every proton version from 8 to experimental. And a few of the GE version. The flickering did not stop. Heavy in the menu, game and the benchmark. Has there been a regression with that vkd3d bug?

Linux Mint 21.3 (64 bit)
AMD AMD Radeon RX 6700 XT (navy_flounder, LLVM 13.0.1, DRM 3.42, 5.15.0-117-generic)
Driver Version: 4.6 (Compatibility Profile) Mesa 22.0.5

EDIT: Ok turns out my drivers were very old due to having an old kisak PPA source. Updating the drivers to 24.x fixed it. Never noticed before as i had no glitches with other games. Will leave this here in case anyone else missed it similarly.