Marvel's Spider-Man 2 (2651280)

[hjpaul7]

Compatibility Report

• Name of the game with compatibility issues: Marvel's Spider-Man 2
• Steam AppID of the game: 2651280

System Information

• GPU: Nvidia 4090
• Video driver version: 565.77
• Kernel version: 6.12.10
• Link to full system information report: Gist here
• Proton version: Experimental

I confirm:

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

Proton Log: steam-2651280.log

Symptoms

• Nvidia DLSS Frame Generation option isn't listed even though using Proton Experimental
• With gamescope controller input only works in menus, it doesn't register the input from a controller in the actual game or show controller prompts. (Tested PS5 Dualsense and a 8bitdo Ultimate)
• Enabling/Disabling FSR Frame Generation crashes the game
• Enabling/Disabling HDR crashes the game

Reproduction

• Launch game
• No DLSS Frame Gen option listed
• Enable/Disable FSR FG or HDR

[hjpaul7]

Just to add, running the game without gamescope fixes the controller input.

I was running with: gamescope -e -f -r 120 -W 3840 -H 2160 --hdr-enabled -- %command%

Edit: I'm also consistently getting a crash after being able to switch to Miles for the first time. Here's an updated proton log: steam-2651280.log

[alosarjos]

Some feedback:

Arch + Gnome + AMD 7800XT + Proton Experimental

Game runs fine and I don't get crashes toggling HDR or Framegen

But HDR is not showing the right colors (HDR in Gnome is still on testing, so I guess that's something on it)

And when I started playing I also tried a bit enabling and disabling raytracing and at some point the game memory leaked on the VRAM over 16 GB

I have then disabled RT, since it's not worth it for me and played for a couple of hours without any issue and I kept tweaking Framegen and upscaling while playing those 2 hours.

[Niedzwiedzw]

the game launches but the screen is completely black

[SimpleHeuristics]

To add to this thread. Distro: Bazzite GPU: RTX 4090 (Driver 570.86.15) Environment: Embedded Gamescope (Gamescope session) Proton: Experimental Bleeding Edge Launch Options: SteamDeck=0 %command%

Issues:

• HDR Slider for Max Luminance causes the screen to black out every change
• DLSS Frame Generation can't be toggled. Despite proton experimental (works for other games) and WINEHAGS=1 I've tried
• DLSS Ray Reconstruction cannot be toggled. Same proton works for other games like CP2077

[Saancreed]

• DLSS Frame Generation can't be toggled. Despite proton experimental (works for other games) and WINEHAGS=1 I've tried
• DLSS Ray Reconstruction cannot be toggled. Same proton works for other games like CP2077

Yeah, about that…

If you want to "fix" this, go the the game's directory, make a copy of Spider-Man2.exe and then run sed -i 's/WINELOADER/FROGLOADER/' ./Spider-Man2.exe. I don't know yet if messing with the game's Wine detection has other consequences so try this at your own risk. Hopefully this won't be needed in some future game update once at least Proton Experimental has the fix.

For anyone else who wants to give this a try, Proton Experimental bleeding-edge is currently required to avoid the crash, same as with Cyberpunk 2077.

[hjpaul7]

Is anyone able to get a Controller to work while using gamescope?

DLSS Frame Generation can't be toggled. Despite proton experimental (works for other games) and WINEHAGS=1 I've

If you want to "fix" this, go the the game's directory, make a copy of Spider-Man2.exe and then run sed -i 's/WINELOADER/FROGLOADER/' ./Spider-Man2.exe.

This technically worked, but something is not right. Causes extreme frame drops and is very laggy.

[SimpleHeuristics]

Is anyone able to get a Controller to work while using gamescope?

DLSS Frame Generation can't be toggled. Despite proton experimental (works for other games) and WINEHAGS=1 I've

If you want to "fix" this, go the the game's directory, make a copy of Spider-Man2.exe and then run sed -i 's/WINELOADER/FROGLOADER/' ./Spider-Man2.exe.

This technically worked, but something is not right. Causes extreme frame drops and is very laggy.

My Xbox controller is working via steam input without any issues under Gamescope session

[hjpaul7]

My Xbox controller is working via steam input without any issues under Gamescope session

Strange, my 8bitdo Ultimate in 2.4gz mode, which Steam recognizes as an Xbox controller does not work in a Gamescope window. I tried with Steam Input enabled and disabled.

Edit: Same issue with PS5 controller.

[SimpleHeuristics]

@Saancreed no luck with that command, frame Gen still can't be toggled and ray reconstruction is still greyed out

[Hadrianneue]

Symptoms Game has serious CPU under utilization issues, in fact this issue affects all 3 marvel spider-man games on linux, this one seems to be the worse overall, any help on how to debug this further? i've even tried using different syncing methods like NTsync, but it runs the same as Fsync mostly

Very High settings, 1440p with FSR3 performance to induce cpu bottleneck

No Sync - 42 FPS	Esync 41 FPS	Fsync 48 FPS	NTSync 48 FPS	Windows 62 FPS

System Information

• RX 6700 XT
• Endeavour OS - 6.13
• 5700X3D
• Proton experimental (cachy-proton to test ntsync, with vkd3d-git)

[kisak-valve]

Marvel's Spider-Man 2 (2651280)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/8512. @DistantThunder posted on 2025-03-10T12:57:46:

Compatibility Report

• Name of the game with compatibility issues: Marvel’s SpiderMan 2 with Raytracing
• Steam AppID of the game: 2651280

System Information

• GPU: AMD Radeon RX 7900 XTX
• Video driver version: Mesa 24.3.4-arch1.1 (amdgpu)
• Kernel version: 6.13.2-zen1-1-zen
• Proton version: Experimental / 9.0.4

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.
• [x] I have verified the game & Proton's files.

Symptoms

Marvel’s SpiderMan 2 previously supported Raytracing, but after an update around two weeks ago, enabling Raytracing no longer works. The game displays a Wine error: "status & "&"vkCreateRayTracingPipelinesKHR"". Other games using Raytracing are unaffected.

The game can work with Raytracing disabled but it removes significant visual fidelity.

• Game version: v1.307.0.0

Reproduction

1. Ensure the latest updates for your system (kernel, drivers) have been applied.
2. Launch Marvel’s SpiderMan 2 with Proton Experimental version or 9.0.4 via Steam.
3. Enable Raytracing in-game settings or just start the game with Raytracing previously enabled.
4. Observe if the error message appears.

Additional Context

• Logs: I have enabled PROTON_LOG=1 for debugging but the log file is now 400 MB and the game still hasn't started.
• The issue started occurring after an update to the game most probably, approximately 1 week ago or less.

Please let me know if there is additional information needed. Thank you for your assistance in resolving this issue.

[DistantThunder]

Hello, with the new patch and Raytracing issue, it's impossible to obtain a Proton Log file reasonably. The game has been starting for 2 hours and log file is 14GB with black screen.

[DistantThunder]

I added WINEDEBUG=trace-unwind and was able to get something. Raytracing breakage PROTON_LOG

• steam-2651280.log

[DistantThunder]

Didn't want to bother VKD3D but I guess this time around randomly not creating an issue there was the wrong move: https://github.com/HansKristian-Work/vkd3d-proton/pull/2395

[warriormaster12]

@Hadrianneue have you found a workaround to cpu under utilization?

[Hadrianneue]

@Hadrianneue have you found a workaround to cpu under utilization?

sadly no, game is just unplayable because of it

[warriormaster12]

sadly no, game is just unplayable because of it

Indeed

[kisak-valve]

Game launcher bugs. Games won't start l, ROG Ally Z1 extreme

Issue transferred from https://github.com/ValveSoftware/SteamOS/issues/2155. @ribenawrath posted on 2025-10-05T07:49:42:

Using steam os.

The entire system feels very fragile like it's going to fall apart. I'm having multiple issues., I've added 5 tickets this week. .. I Often, I'll be playing a game that'll krep crashing on play through (Spiderman 2 ).

I've had games that won't launch at all (titan fall 2.) and I've got a refund.

Some games sometimes run if I hit the play button. I'll keep pressing the play button, it'll keep crashing and sending me back to the game page (quantum break), but run if I start another game it'll start. (NB Tried it this morning and that trick no longer works. I'm 3 hours into this game and can't play it.)

Sometimes games run perfectly without issue (uncharted thieves collection).

The entire game launcher on AMD device needs more stability

Thanks

[kisak-valve]

Hello @ribenawrath, 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 the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[hjpaul7]

It's been a while,

Nvidia DLSS Frame Generation option isn't listed even though using Proton Experimental

Has anyone gotten DLSS Frame Generation to show up in the menu?

[Avalan666]

Adding to this, DLSS FG and RR are unavailable in SM2 for me despite working in all other games. I'm on Bazzite and tried swapping DLLs, using different compatibility tools and nothing worked.