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:

• that I haven't found an existing compatibility report for this game.
• 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