Do you have any launch options enabled?

I can play just fine, and even enable RT. something feels off about the performance however, regardless if im on low, or ultra, the game caps out at around 30-40fps. There's no reason it should run the same at Low and Ultra.

@Bitwolfies How did you enable RT? And for the performance side of things it's the same for me, even if I change the graphics, the performance does not seems to change at all. Even DLSS isn't doing much.

@Bitwolfies How did you enable RT? And for the performance side of things it's the same for me, even if I change the graphics, the performance does not seems to change at all. Even DLSS isn't doing much.

I added VKD3D_CONFIG=dxr11 %command% to the launch options.

I have the same symptoms but it does load after the third dialog. 7.0.3 works but Experimental gives me the crash message.

I was able to get it running with proton experimental but performance is awful. I'm running a 5800x3D, RTX 3080, and 32 gig of ram and the game dips to 25fps when swinging through the city. I can confirm the graphics settings pretty much do nothing for me too. Idk why this runs so poorly, it's steam deck verified so shouldn't it run fine on PC?

I'm starting to think it may be an NVIDIA card issue. Everyone with AMD card seems to run the games fine from what I saw.

Yes I suppose that it could be an Nvidia issue. The deck is AMD.

I will try on my Steam Deck, I'm installing it right now.

I was able to get it running with proton experimental but performance is awful. I'm running a 5800x3D, RTX 3080, and 32 gig of ram and the game dips to 25fps when swinging through the city. I can confirm the graphics settings pretty much do nothing for me too. Idk why this runs so poorly, it's steam deck verified so shouldn't it run fine on PC?

Yeah, for the most part it seems to be the swinging, on top of buildings is pretty smooth all things considered, but swinging tanks it, along with the loading times being a bit worse than on Windows seemingly. Im at least happy its not just me who felt like changing settings was pointless.

Im not sure if we really benefit from the game ready drivers like Windows does, but NV has not released a driver on Linux since the one that added the spider man optimizations, which from what ive heard seem critical to making it run alright.

Yah the swinging definitely tanks it, but also the initial fight scene
caused my fps to hover in the 40s. I should be getting way better
performance considering my system. Even their upscaling setting didn’t help.

On Fri, Aug 12, 2022 at 2:15 PM Bitwolf @.***> wrote:

I was able to get it running with proton experimental but performance is
awful. I'm running a 5800x3D, RTX 3080, and 32 gig of ram and the game dips
to 25fps when swinging through the city. I can confirm the graphics
settings pretty much do nothing for me too. Idk why this runs so poorly,
it's steam deck verified so shouldn't it run fine on PC?

Yeah, for the most part it seems to be the swinging, on top of buildings
is pretty smooth all things considered, but swinging tanks it, along with
the loading times being a bit worse than on Windows seemingly.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1213436525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJN47SFM3KEFXLGZYUOEG2DVY2PDVANCNFSM56MINDRA
.
You are receiving this because you commented.Message ID:
@.***>

The upscaling doesn't seems to do anything for me performance wise.

The game for sure is VERY CPU bound, but I only see a difference of 5-10% usage when swinging compared to standing on a roof. I truly think its an NV issue, but if its just a driver update we dont have yet, or a VKD3D issue, im unsure of.

Comments on reddit reporting the same thing. https://www.reddit.com/r/linux_gaming/comments/wmof5i/anyone_got_spiderman_remastered_working_on_linux/

Yeah that's my thread ahah @Bitwolfies

It may be CPU bound, but surely I should get higher than 30fps with a 5800x3D.

I got a somewhat stable 40fps on the Steam Deck tho on very low settings

HQ textures have a really hard time loading, also, this.

Game also by default uses Steam Deck icons for xbox controllers. when not using steam input, if you use steam input, you get the right icons, but rumble does not work due to another bug I reported. https://github.com/ValveSoftware/steam-for-linux/issues/8590#issuecomment-1192813338

Along with this, the adaptive triggers dont work in steam input mode, despite this update, either its a bug or the devs have to implement it per game. https://i.redd.it/y552c86t4pe91.png

Do you have any launch options enabled?

@Vysp3r no launch options enabled/used (besides for the purpose of generating the Proton log).

I was able to get it running with proton experimental but performance is awful. I'm running a 5800x3D, RTX 3080, and 32 gig of ram and the game dips to 25fps when swinging through the city. I can confirm the graphics settings pretty much do nothing for me too. Idk why this runs so poorly, it's steam deck verified so shouldn't it run fine on PC?

Aside from the Nvidia GPU which I haven't experienced the game with just yet, the game seems to require a SSD (at least SATA3 and not too slow). I initially installed the game on a HDD and faced terrible framedrops while navigating around the city. I moved it to a Samsung 850 EVO SSD and it's been pretty much a locked 72fps @ 144Hz (half vsync) at 1440p high/ultra mix on a RX 5700XT and a 5800X (the game is bound to half the cores of my 5950X). If you're already running the game from a SSD then there might be some specific issue on Nvidia.

Yeah I think it's an Nvidia issue because I'm already running it on a 1TB Samsung 870 evo.

Can attest I also have an NVME HP drive, so its not that.

Might be related, but the game only uses around 40% of my 3080 according to mangohud. Very low settings use about 30, everything else, even max, only uses 40%, I think this might be the issue. Is there a way to overrride this?

I tried proton-ge and there was about a 20fps improvement for me.

Sadly GE yielded no uplift for me.

Can confirm, happens the same on my system with a GTX 1650 laptop.
Game either straight up crashes or runs at extremely low fps, am getting the same 'no gpu installed' error on startup.
Probably an Nvidia issue as AMD cards seem to run it fine.

I just thought I would share some information about my experience with the Spiderman game.

I can personally get the game to run with Proton Experiemental (no launch commands). And the game works fine if I use the launch commands required for DLSS and Ray tracing (I say works fine, there's some performance issues and a minor graphical glitch).

Here are my launch commands for DLSS and Ray Tracing: PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_FEATURE_LEVEL=12_1 VKD3D_CONFIG=dxr11 %command%

Some notes about my setup and my experience:

Specs:
CPU: Ryzen 9 5950X
GPU: RTX 3060 with driver 515.65.01 (downloaded directly from Nvidia's website)
Kernel version: 5.18.0-4-amd64
Distrobution: Debian Testing
Controller: Xbox Elite Wireless Controller Series 2 (connected to my PC via a USB cable)

IMPORTANT NOTE:

The game will crash exactly as reported by others users, unless my controller is unplugged when I open the game and during the first few seconds of the intro video. After the first few seconds of the intro video, I can plug the controller in and it works just fine.

i5 9400f, gtx 1660s does not start :(

@Treemcgee324 I can confirm, that having my controller (Xbox 360 Wireless) connected, before the game reaches at least the main menu, seems to be the culprit.

The game starts reliable, if I don't have the controller connected!

When connecting the controller in the main menu, it still sometimes crashes, as soon as the controllers connection is established.
Connecting the controller while already in-game hasn't crashed the game (yet).

No audio in game when using my 32 channel audio interface.

Edit: Got audio working with "protontricks 1817070 sound=alsa"

I tried GE-Proton7-29, GE-Proton7-27, Proton Experimental, winecfg to configure audio, and various launch options that have helped in the past for other games and various sample rate settings (44.1k and 48k).

With my audio interface I need to have it set to 32 channels or else the audio can be very distorted, the wrong speed, etc, but as a test I did put it into a two channel mode and was able to hear garbled audio and the logs no longer contained the thousands of pulse errors I had noticed before.

1859 1259.981:0130:0264:err:pulse:pulse_spec_from_waveformat Invalid channel mask: 8/32 and 63f(63f)
1860 1259.981:0130:0264:err:pulse:pulse_spec_from_waveformat Invalid format! Channel spec valid: 0, format: 5

Steam System Information and full log here....
https://gist.github.com/johnny2k/ade66bee44ef13f79c63bf0e384decff#file-steam-1817070-log
https://gist.github.com/johnny2k/ade66bee44ef13f79c63bf0e384decff#file-steam-system-information

Running it on non deck, I only had a graphic glitch, on the bag in the lab at the start.

I'm dual booting with windows 11 so I tried running it on that. I got a massive performance uplift on my system (5800X3D, 32GB RAM, RTX3080). I went from hitting ~25fps when swinging through the city to a rock solid 100fps (my monitor refresh rate). I've only seen very rare drops to the 80s in particularly intense scenes. Definitely seems like proton performance is rough and I'll be sticking to windows until this is updated.

Whenever I enable DLSS ingame, all graphics (except menus) are black.
Game runs at 120FPS in Ultra otherwise with FSR or IGTI. Same thing with GE-Proton7-29.

Ryzen 5 5600H + RTX 3060 (Laptop)

@Treemcgee324 I can confirm, that having my controller (Xbox 360 Wireless) connected, before the game reaches at least the main menu, seems to be the culprit.

The game starts reliable, if I don't have the controller connected!

When connecting the controller in the main menu, it still sometimes crashes, as soon as the controllers connection is established. Connecting the controller while already in-game hasn't crashed the game (yet).

I also had this issue with an Xbox One controller. Game finally launched after my sixth attempt and it hasn't crashed on me since.

I have a Ryzen 5 5600X + RX 6600 XT PC running PopOS 22.04. Whenever I launch the game, I get a brief driver warning that I can safely ignore.

But my main complaint is how even after closing the game launcher, it still runs until I kill it.

I have a Ryzen 5 5600X + RX 6600 XT PC running PopOS 22.04. Whenever I launch the game, I get a brief driver warning that I can safely ignore.

But my main complaint is how even after closing the game launcher, it still runs until I kill it.

try gamemoderun %command% -nolauncher as a launch option

Whenever I launch the game, I get a brief driver warning that I can safely ignore. But my main complaint is how even after closing the game launcher, it still runs until I kill it.

I also have this issue.

try gamemoderun %command% -nolauncher as a launch option

Didn't work. :(

Has anyone noticed that their game suddenly crashes/freezes a lot more often recently? I bought the game on launch and I had barely any issues.

I have a Ryzen 7 2700X + GTX 1080 Ti running both Arch and Gentoo Linux. Before today, I've run Spider-Man on Proton Experimental and GE Proton and it was running fine on both distros and Proton versions. Then, suddenly my game crashes like every 5 minutes.

I've tested it on my Gentoo and Arch. I uninstalled and reinstalled to different hard drives. I switched back and forth between Fullscreen, Exclusive, and Windowed, and changed multiple settings. I tampered with the launch options as some comments suggested. No fix for me. Still crashes.

I'm seeing comments that suggest it's an Nvidia driver issue, which that may be the case, but it's strange since I was running the game pretty well before today.

I usually do all the side content I can do before advancing to the main story. I'm in the part where you just got access to Harry's Research Labs to earn Research Tokens. And it's like suddenly after that, my game freezes every so often.

Anyone who is also getting this issue with a similar setup?

My only solution is to either wait for a new Nvidia GPU driver or to play Spider-Man on Windows :(

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1217318377

Yep, I get consistent crashes at the research stations also and I have a 1080ti running on Manjaro. No settings I tried as far as I can tell changes the crashing. I'm leaning toward it being a Nvidia driver issue as well.

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1217334996

Okay. That makes sense. I figured I wasn't the only one having these problems. It's strange how it was running perfectly fine before I progressed to the stations. Anyway, it sounds like either we're going to have to wait for a new driver update or simply play Spider-Man on Windows.

Has anyone noticed that their game suddenly crashes/freezes a lot more often recently?

Mine has always frozen after some amount of time. I don't think it's every crashed out. It just gets stuck on a frame and the audio continues to play. I can kill -15 and restart and then have it play just fine in the same part.

I've been trying various tweaks, graphics settings but nothing seems to make it more or less reliable.

Nvidia 970 for me.

Tried the game both in Linux and Windows. On Linux the game was unplayable, the warnings describe here don't happen on Windows. I noticed a great performance hit between these 2 OSs. On Linux I barley hit 30 fps with high settings + fsr, on Windows I get 30+ fps with the same settings.

The crashes however are totally related to proton, tried with lutris' version of wine and the game booted correctly and had no random crashes

The crashes however are totally related to proton, tried with lutris' version of wine and the game booted correctly and had no random crashes

Can you share any details on your configuration for running Spider-Man with Lutris? I'd like to test this as well.

Compatibility Report

• Name of the game with compatibility issues: Marvel’s Spider-Man Remastered
• Steam AppID of the game: 1817070

System Information

• GPU: Radeon 6900 XT
• Driver/LLVM version: Mesa 22.1.6
• Kernel version: 5.19.3-arch1-1
• Link to full system information report as Gist: System Info
• Proton version: 7.0-4, Exprerimental, and a few GE-7 up to the GE-7.29

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.

Symptoms

Crash a few seconds after steam launchs the game. Doesn't even open a window.

Reproduction

Always happen

I tried :

• To upgrade and reboot my system
• With and without gamemoderun
• With and without the -nolauncher parameter
• With and without a controller attached

Logs

steam-1817070.log

Snippet of the log before the dump :

1058.334:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\winedbg.exe" at 0000000140000000: builtin
1058.335:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernelbase.dll" at 000000007B000000: builtin
1058.335:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernel32.dll" at 000000007B600000: builtin
1058.337:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msvcrt.dll" at 00000001C8DB0000: builtin
1058.338:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ucrtbase.dll" at 00000003AF670000: builtin
1058.338:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\sechost.dll" at 000000032A700000: builtin
1058.338:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\advapi32.dll" at 0000000330260000: builtin
1058.338:0174:0178:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\dbghelp.dll" at 00000003BE590000: builtin
1058.413:0130:0164:trace:seh:call_handler handler at 000000017005FC40 returned 1
Unhandled exception: page fault on read access to 0x00000007fffffff8 in 64-bit code (0x0000000141cfb4fd).
Register dump:

* GPU: Radeon 6900 XT

* Driver/LLVM version: Mesa 22.1.6

You will need a newer mesa version than that. Install mesa 22.3 or git builds. If you're using flatpak, you either need to install the mesa-git platform packages (and setup an env var) or install the steam beta from the flathub beta repo

Just tried with the AUR mesa-git package, and stable llvm Mesa 22.3.0-devel (git-1a250eeae3) / LLVM 14.0.6

Still the exact same crash, down to the address of the segfault.

You will need a newer mesa version than that. Install mesa 22.3 or git builds.

I'm not sure about that, the game is perfectly playable for me tested over 10 hours on mesa 22.1.4. Only issue I've observed is water surrounding the city looking a bit iffy.

Today's spider-man update broke the game, the game crashes all the time, I had to rollback to get it some what stable again on steam deck.

there's some trouble detecting triggers. They get released sometimes while im holding them or they get registered too late

Are you guys still getting crashes still? I mean, this isn't all that important to me since I beat the game already on my Windows laptop, but I'm still curious if you guys are experiencing the same problems. @Javillin @johnny2k

@Dishoungh, the update seems to have helped my situation. It's still freezing but not as frequently. Maybe every 30 minutes instead of 5.

@Dishoungh not as far as I can tell. It still crashes the same way in about the same time frame. I'm pretty sure it's a Nvidia driver issue for me and will have to wait on a fix unfortunately.

ISSUE: Spiderman will crash after 5-ish minutes creating a mdmp file in pfx's Documents folder.

HW/OS

• OS: Garuda
• CPU: i7-7700K
• RAM: 32GB DDR4
• DRIVER: Nvidia Current
• Kernel: Zen

The game will start fine, play perfectly fine for a while. If i die or a major cutscene happens, the game will completely lock up resulting in me having to terminate the process. After the initial crash, whenever the game is loaded it will crash within seconds until a reboot happens. Game files have been validated multiple times as well.

PROTON: Crashes on these versions.

• Experimental
• GE 7-29/30/31

Game runs well enough over here, haven't managed to encounter any crashes yet. However ryzen 9 3900x + 2070 super is failing to reach consistent framerates when swinging around the city. On windows this game runs great.

This is how I got it to work on:

• Ubuntu 22.04 amd64
• 32 Gb Ram
• i7 11700
• NVIDIA GTX 1650

no way to get it working with steam/proton, standard wine in the distribution or lutris, all last version.
With wine-devel (7.16) it runs.

Here the instructions https://wiki.winehq.org/Ubuntu, install wine-devel.

Well, first of all I used Lutris to install the game, configuring the path of the game folder and the executable, then I configured the Lutris game using the custom wine executable path, that's /opt/wine-devel/bin/wine64

I was having the same Nvidia freeze/crash issues on experimental and GE, but I've switched back to Proton 7.0-4, and so far it's not frozen again. No launch command options set. It's not great performance with the graphics card I've got, but it's playable.

Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
16GB RAM
Kernel Version: 5.19.1-3-MANJARO
Steam Runtime Version:
NVIDIA Corporation NVIDIA GeForce GTX 1050 Ti

7.0-4 seems to have fixed my freezing! Thank you!

OS: Garuda Linux x86_64
CPU: Intel Core i7-7700K (8) @ 4.5GHz
GPU: Nvidia GeForce GTX 1080
Kernel: 5.19.7-zen2-1-zen

Since switching to Proton 7.0-4, I haven't had a crash yet.Thanks @gajama, I would have never thought to try it out if it wasn't for your post! So far so good.

Started to play this game yesterday and it looks really good.
But everytime I have to change between maps (indoors/outdoors) the game freezes.

System:
CPU: 3700X
GPU: RX 6700XT with AMDGPU and Mesa 22.1.7
Kernel: 5.19.8-arch1-1
Software: Proton Experimental, Raytracing disabled

Edit: played now several hours after the first two sequences and suddenly the game does not crash anymore
if I change between indoor and outdoor.
Weird stuff, but okay, taking it.

7.04 Also work's great for me but everything else I tried even get builds I keep getting a soft freeze or hard crash.

World love to be able to use newer proton.

I'm starting to think it may be an NVIDIA card issue. Everyone with AMD card seems to run the games fine from what I saw.

I think your right about Nvidia being a factor

7.04 %command% -nolauncher seems pretty good everything. But none of the he features us young kids crave.

For some reason the launcher kills the fps though. Definitely do -nolauncher

I'm consistently getting freezes (not out of memory) since the last experimental update 5 days ago. Wine log is full of this message:

0204:warn:d3d12_command_list_IASetIndexBuffer: Invalid index format 0. This will map to R16_UINT to match observed driver behavior.

This is probably nvidia related (GTX 1650, 515.76, Fedora), downgrading the driver didn't help at all so the problem's on proton side.

Edit: The freezes only happen when swinging or zipping, both things that turn on motion blur. Normal movement and perch takedowns don't trigger it. Looks like dxvk has problems with that specific shader.

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1268813926

I'm also seeing this behavior, started with latest patch.
I'm on manjaro, with gtx 1660 ti:
Linux stacjonarny 5.19.13-1-MANJARO #1 SMP PREEMPT_DYNAMIC Tue Oct 4 14:48:49 UTC 2022 x86_64 GNU/Linux
| NVIDIA-SMI 515.76 Driver Version: 515.76 CUDA Version: 11.7 |

Do you see anything in dmesg? On my machine I see this:

[  428.212087] NVRM: GPU at PCI:0000:01:00: GPU-f41b3810-9762-f160-1637-9c2540ef2dfd
[  428.212090] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 1: SAVE_RESTORE_ADDR_OOB
[  428.212100] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x508900=0x80000001
[  428.212111] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 2: SAVE_RESTORE_ADDR_OOB
[  428.212121] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x510900=0x80000001
[  428.212250] NVRM: Xid (PCI:0000:01:00): 13, pid=30161, name=Spider-Man.exe, Graphics Exception: ChID 0046, Class 0000c597, Offset 00000000, Data 00000000

Edit: Reverting the game version, didn't help. I don't know where the problem is then :(
Edit2: Reverting the nvidia driver to 515.65.01 fixed the issue for me

@pooroligarch @Mikaka27 There was a recent change made in experimental that enabled dxvknvapi for a number of games including this one. It is relatively easy to see if this change is what broke the game for you - you can edit the proton script (located by default at ~/.steam/steam/steamapps/common/Proton - Experimental/proton) and comment out line 1106 (which is "1817070", #marvel's spider-man remastered) by adding a # at the very beginning of the line.

For context - the change was here: https://github.com/ValveSoftware/Proton/pull/6120

Edit: I missed @Mikaka27 's last comment saying that reverting the driver fixed the issue. In this case, the problem should be reported to the NVIDIA driver team. Proving that dxvknvapi was not also at fault is still interesting though - if you have time to test commenting out the line, I would be interested in the results :)

Unfortunately it's not fixed with 520.56.06, it's just more rare, I get this error in dmesg:

[ 5124.589407] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 1: SAVE_RESTORE_ADDR_OOB
[ 5124.589421] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x508900=0x80000001
[ 5124.589435] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 2: SAVE_RESTORE_ADDR_OOB
[ 5124.589447] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x510900=0x80000001
[ 5124.589586] NVRM: Xid (PCI:0000:01:00): 13, pid=225953, name=Spider-Man.exe, Graphics Exception: ChID 0016, Class 0000c597, Offset 00000000, Data 00000000

Probably needs this to be merged: https://github.com/HansKristian-Work/vkd3d-proton/pull/1254

Finally got the 520xx driver (fedora 🙁) and no crashes so far.

Edit: got a crash at the end of a cutscene

[ 1703.547430] NVRM: GPU at PCI:0000:01:00: GPU-e5606bf4-196a-3829-a527-e8558185b922
[ 1703.547439] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 1: SAVE_RESTORE_ADDR_OOB
[ 1703.547452] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x508900=0x80000001
[ 1703.547599] NVRM: Xid (PCI:0000:01:00): 13, pid=7018, name=Spider-Man.exe, Graphics Exception: ChID 0013, Class 0000c597, Offset 00000000, Data 00000000

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1287817853

I no longer experience these crashes on vkd3d-proton 2.7

Hi,

I'm trying to run this game on Fedora 36. After the launcher menu, I've got a black screen, then the message telling me that the game crashed and that I can report it to the dev. I've got a RTX 3070ti with drivers 525.60.11-1 drivers but it was the same with 520 drivers. When NVAPI is on, I've also got a message telling me that my drivers are outdated, even with DXVK_NVAPI_DRIVER_VERSION=52756.

I've tried Proton 7.0-5, Experimental and GE 7-42. And everytime, there is the same crash.

Here is the log file:
https://gist.github.com/Skiski/7c59d34f6c3886e6410de043492e4ddc

@Skiski try without vkbasalt.

@mbriar Awesome, that was it. I didn't even know I had it activated. I must have installed it some time ago and forgot about it. I may as well uninstall it or at least disable it.

Thanks a lot.

I'm having the drivers outdated warning box on every launch running on a prime setup, using a 1660Ti with the latest drivers (525.85.05) on Arch Linux. I've tried setting nvapi version to the latest windows driver version, but to no avail. I also do not have VKBASALT installed, and disabling mangohud entirely also does not help

Ever since I got a 7900XTX, this game has been crashing either loading the main game or even before the menu.
However, I can't see any grapĥics-related error message.

• Proton: 7.0.5/Experimental/GE-38
• Mesa-git : 23.1.0_devel.165238.4fb2463a37f-1 / 22.3.3
• LLVM: 16
• Linux firmware: 20230117.7e4f0ed-1
• Linux 6.1.8-zen1-1-zen

steam-1817070.log.gz

@Bitwolfies How did you enable RT? And for the performance side of things it's the same for me, even if I change the graphics, the performance does not seems to change at all. Even DLSS isn't doing much.

I added VKD3D_CONFIG=dxr11 %command% to the launch options.

Hello, could you please make a mini guide on what exactly you did to the game to enable ray tracing, not keen on Vulkan and the whole topic, just want to enable ray tracing settings in a game, thank you!

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1408894965

Right click game In steam, add what I said to the properties section, turn it on ingame, cross fingers and hope it works.

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1409323894

Thanks, unfortunately before asking I knew nothing about proton/wine, after checking I understood it's all about the linux, so it wouldn't help me after all, I'm thinking how to make spider man think I have dx12.1 tier when I have only 12.0 so I could enable ray tracing, don't even know if it's possible on non rtx card

Thanks, unfortunately before asking I knew nothing about proton/wine, after checking I understood it's all about the linux, so it wouldn't help me after all, I'm thinking how to make spider man think I have dx12.1 tier when I have only 12.0 so I could enable ray tracing, don't even know if it's possible on non rtx card

If it's not an rtx card turning on ray tracing would give you single digit frame rates, it's not worth it. It's also not on topic unfortunately so I hope you find the help you need!

Thanks, unfortunately before asking I knew nothing about proton/wine, after checking I understood it's all about the linux, so it wouldn't help me after all, I'm thinking how to make spider man think I have dx12.1 tier when I have only 12.0 so I could enable ray tracing, don't even know if it's possible on non rtx card

If it's not an rtx card turning on ray tracing would give you single digit frame rates, it's not worth it.

Yeah, think same but still want to try as it was good on gtx 1080 in Guardins of Galaxy and Watch Dogs 3 with dlss, like 30+ fps all the time on medium ray tracing lvl

I am also experiencing this with a fresh 7900 XTX installed.

Also experiencing low texture quality and extremely poor performance on what should be a reasonable playing experience. Ryzen 5 5600x, RTX 3070, 970 Evo Plus, 32gb 3600c18, etc.

Always get this annoying message when I launch the game. my laptop has a GTX 1660 TI 6gb

Getting model issues, texture issues and wierd color banding but Hmm might be a Nvidia driver issue

Okay well that's a new one. Into the spider verse dlc launched early I see.
😁

On Tue, Apr 11, 2023, 7:49 AM Corey Bruce @.***> wrote:

Always get this annoying message when I launch the game

[image: Screenshot from 2023-04-08 23-07-11]
https://user-images.githubusercontent.com/8393780/231153429-461619a4-e11a-4ff9-91e8-5c61eae1fb63.png

Getting model issues, texture issues and wierd color banding on the latest
experimental proton

[image: Screenshot from 2023-04-11 21-31-25]
https://user-images.githubusercontent.com/8393780/231153472-318aca6f-b284-40b0-9950-f13d56c7e32c.png

[image: Screenshot from 2023-04-11 21-48-28]
https://user-images.githubusercontent.com/8393780/231153883-26fcb75b-25f6-4a09-9614-006d4b2c9fb5.png

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1503181308,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5F5KE5UCQCTNEJPX6TORLXAVAMBANCNFSM56MINDRA
.
You are receiving this because you commented.Message ID:
@.***>

My gamepad (wired xbox one controller) stopped working in the game since the last update of proton experimental. Before, I was using the "7.0" experimental version and it worked great. Since the update to the "8.0" branch, it stopped working only for this game. I've tried Horizon Zero Dawn that I also play with the experimental branch and the gamepad is still working.
I've tried other games, not necessarily with proton experimental, and my gamepad works great.
I've also tried with the new proton 8.0 and still no gamepad. If I try with proton 7.0.6, the game crashes at launch.
If someone can confirm that or explain to me what I can do, it would be nice.
Thanks

I've enabled Steam Input in the controller settings and it works. It wasn't enabled before for this game and it was working.
Thanks for the quick answer. Do you still need the log file?

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1503181308

Eventually figured out the colour and graphic issue was a weird bug on proton, deleting the compatdata folder for the game resolved the issue.

With the last Experimental update, I can disable steam input and my xbox controller is working "natively".

With the last Experimental update, I can disable steam input and my xbox controller is working "natively".

Wow that's awesome and can confirm it works. Cant wait for this to go the next stable release of Proton. :smile:

I'm having a issue with lutris

The GPU Power usage in very low (35W) instead of the full 85W
That costs the game to run at 21 FPS which is unplayable while on Windows i get 40-60 FPS

I'm on a nvidia geforece rtx 3050 with the 530 drivers on Arch and using VKD3d 2.9

I'm having a issue with lutris

The GPU Power usage in very low (35W) instead of the full 85W That costs the game to run at 21 FPS which is unplayable while on Windows i get 40-60 FPS

I'm on a nvidia geforece rtx 3050 with the 530 drivers on Arch and using VKD3d 2.9

Why are you using Lutris for the game and it Steam itself?

I have the same issue on Steam , i thought it would run better on lutris but nope

As you can see the GPU power is sitting at 35W while it should be at 85W
The FPS is bad (this is the Steam proton version) Lutris has about the same performance

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1576787604

That is indeed odd, is this a desktop or laptop?

Looks like a laptop to me considering it's a 3050 Mobile

Yeah it's a laptop

Ah yeah right, I didn't zoom in on my phone to read it 😋

Is your laptop plugged in? And also is your laptop set to performance mode and not balanced or especially battery saving which would cause performance issues? It not being plugged in could cause it not hit higher wattage for example

Game is completely borked on RX 590/Ryzen 5 3600. Lights are very glitchy and the PC freezes sooner or later (sound will still be playing, but the image just stays frozen).

Kernel 6.3.9, Mesa 23.1.3. Proton Experimental/Proton 8.0-2/GE 8.4. It won't even launch with 7.0.

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-1614555329

Hey try deleting the proton prefix for the game and run the game again so it creates a new one

Hey try deleting the proton prefix for the game and run the game again so it creates a new one

First thing I tried, it changes nothing. It appears to be an issue with just this game, and possibly the Miles one, but I don't have that one to test, since I tried The Witcher 3 on DX12 and it works and looks fine.

Hey try deleting the proton prefix for the game and run the game again so it creates a new one

First thing I tried, it changes nothing. It appears to be an issue with just this game, and possibly the Miles one, but I don't have that one to test, since I tried The Witcher 3 on DX12 and it works and looks fine.

If you're using dynamic resolution scaling, try disabling it (the framerate target setting, set that to off). This game crashes outright for me if dynamic res is on but works fine with it off.

If you're using dynamic resolution scaling, try disabling it (the framerate target setting, set that to off). This game crashes outright for me if dynamic res is on but works fine with it off.

I've already tried setting everything to off/lowest, tried changing scaling/no scaling or to higher settings with more things on, mostly the same results, only difference is the amount of time it takes for it to freeze, lighting still glitches.

Is there support for Nvidia card on this game now? I only see the playstation crash window of always. My pc has an i9 13th gen, RTX 4090 and the game is on nVME ssd.

Is there support for Nvidia card on this game now? I only see the playstation crash window of always. My pc has an i9 13th gen, RTX 4090 and the game is on nVME ssd.

What version of proton and nvidia driver are you using?

I tried proton experimental, proton 8, 7 and GE. My current driver is below:

NVIDIA-SMI 535.129.03 Driver Version: 535.129.03 CUDA Version: 12.2

Here is the log from running with PROTON_LOG=1 %command%

steam-1817070.log

Hope it helps :)

@kisak-valve thank you for the help. The game launches now with a warning that couldn't find the GPU, but it works perfectly in the end. Also, some textures show up in very low resolution, but it is playable.

Here is the gist with the diagnostics: https://gist.github.com/Pedrexus/ea7972f6ed0de5c030bf1719ec940db8

Hey try deleting the proton prefix for the game and run the game again so it creates a new one

First thing I tried, it changes nothing. It appears to be an issue with just this game, and possibly the Miles one, but I don't have that one to test, since I tried The Witcher 3 on DX12 and it works and looks fine.

Did you ever solve this? I am seeing this issue testing the gpu on a framework amd laptop, with the steam flatpak, which uses mesa 23.3.0

Hearing reports that the latest steam deck client update broke controller icons on the oled

@ClearlyClaire Sorry to ping you here, but any chance I could ask for some pointers on how you went about figuring out what games were doing to test for the advanced DualSense features? I'm willing to do the leg work on figuring this out for this game, but I'm sadly stuck and not sure what to try next (other than disassembling game binaries, which I suspect would be very difficult to get useful information from, and also, I don't really know how to do it..).

@ClearlyClaire Sorry to ping you here, but any chance I could ask for some pointers on how you went about figuring out what games were doing to test for the advanced DualSense features? I'm willing to do the leg work on figuring this out for this game, but I'm sadly stuck and not sure what to try next (other than disassembling game binaries, which I suspect would be very difficult to get useful information from, and also, I don't really know how to do it..).

Sorry, I missed that message. Basically, I increased wine's log levels on particular subsystems and tried to figure out how the API calls were used by reading the logs and a lot of documentation.

PROTON_DUMP_DEBUG_COMMANDS=1 PROTON_LOG=1 WINEDEBUG=+timestamps,+xaudio2,+mmdevapi,+setupapi,+hid,+pulse

This can be really noisy, since obviously each of these subsystems are used for more than just the Dualsense audio. hid is probably way too noisy to be useful here, but iirc I had confirmed some stuff from those logs. Also, there may be other relevant subsystems I am not aware of.

DualSense haptics still don't work in Spider-Man Remastered even though the latest Proton Experimental changelog says otherwise:

https://github.com/ValveSoftware/Proton/wiki/Changelog#available-in-proton-experimental-as-of-2025-10-24

Available in Proton Experimental (as of 2025-10-24):
Fixed haptics support for DualSense controllers which should now work in most games that support it.

@nokia8801 Thank you for the report - this is exactly why we said "most games" ... we actually did know about this one already and we are separately working on it, but if you find any other games where the DualSense haptics support is still failing, please report on the issue and feel free to tag me :)

@nokia8801 Thank you for the report - this is exactly why we said "most games" ... we actually did know about this one already and we are separately working on it, but if you find any other games where the DualSense haptics support is still failing, please report on the issue and feel free to tag me :)

Hey there. I wasn't trying to be mean or anything. I just really love these Spider-Man games and have used haptics on PS5 for years. Unfortunately, I have a feeling that most users are confusing haptics with normal rumble/classic vibrations and think haptics are working when it actually isn't. Haptics are little audio based thumps all over the controller, like very tiny vibrations.

This unfortunately doesn't work with Spider-Man Remastered at the moment.

Also, there is no mention of this anywhere but are we supposed to be using tools like Helvum? Or is it supposed to be plug-and-play? Because I've even tried that but it still doesn't work. Spider-Man Remastered launched three stereo audio instances and DualSense has two instances, one for the input microphone which isn't related, and one for the speaker/haptics with 4 channels.

But I've tried connecting all three Spider-Man instances to the controller through Helvum yet there was still no haptic feedback.

Also, I've forgot to mention this but the controller speaker in this game doesn't work either. I don't know if that's related to haptics or not. Web zips and other specific sounds should be coming from the controller speaker (when the feature is turned on) but it doesn't work either.

No confusion for me I understand the difference . Last time I played both haptics (ie haptic triggers)
and rumble worked for me duel since 5. Nvidia 3060 kde neon 6. x11 plasma desktop.

No confusion for me I understand the difference . Last time I played both haptics (ie haptic triggers)
and rumble worked for me duel since 5. Nvidia 3060 kde neon 6. x11 plasma desktop.

You're already calling Adaptive Triggers as haptic triggers so I find it hard to believe you aren't confused.

Adaptive Triggers are just that, adaptive triggers, has nothing to do with haptics we are discussing. It's just resistance when you push R2 and L2. Adaptive Triggers work without any issues.

And haptics aren't the same as vibration/rumble that most people are familiar with. Rumble/Vibration still works. Haptics don't. Which is why I said:

Haptics are little audio based thumps all over the controller, like very tiny vibrations.

Unless most people played on a PS5 or on Windows and experienced this themselves, I have a strong feeling they are mistaking normal rumble/classic vibration with haptic feedback.

At least in Spider-Man Remastered's case. Haptic feedback doesn't work right now. I hope it does in the future.

Replying to https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-3501009256

You argument of sematics wont change anything. I understood perfectly and it works fine.
Your talking to someone to reapairs these controllers. I know the location of every servo, and gear and what it does. Every function works as intended the controller is 100% utilized PS5 duel shock 5.

Replying to [#6088 (comment)](https://github.com/ValveSoftware/Proton/issues/6088#issuecomment-3501009256)

You argument of sematics wont change anything. I understood perfectly and it works fine. Your talking to someone to reapairs these controllers. I know the location of every servo, and gear and what it does. Every function works as intended the controller is 100% utilized PS5 duel shock 5.

I'm just talking about this specific game. Marvel's Spider-Man Remastered (and also Miles Morales Remastered). Haptic feedback doesn't work in these two games. It might work in others, I can't comment on them. That's why I'm on this specific issue report for this specific game, as it doesn't work here.

Check for yourself: https://docs.google.com/spreadsheets/d/1YvnaCKplTCEyWBWw-ypcDK1N_saDmuygA3RWhpcO8Ak/

It works fine in both games. At least for me

It works fine in both games. At least for me

Yeah sorry but now I know for a fact you're confusing normal rumble with haptic feedback. Literally everyone, Valve dev, that list and many more people say it's not working (with or without Helvum) but somehow it's working for you. Ok mate.

Game still has major issues with HQ textures loading in late.

Game still has major issues with HQ textures loading in late.

Yep. Experiencing this myself. Thought it was just me.

RT on or off, lowest or highest settings, it doesn't matter. Every few 100 meters Spider-Man swings the game either pauses or mud textures are loaded instead. It looks disgusting even with the highest settings and RT on. Most visible when standing stationary and looking at stuff not even that far away. They're all low textures.

Compatibility Report

• Name of the game with compatibility issues: Marvel’s Spider-Man Remastered
• Steam AppID of the game: 1817070

System Information

• GPU: RX 9070 XT
• Video driver version: Mesa 25.3.3
• Kernel version: 6.17.7-ba25.fc43.x86_64
• Link to full system information report as Gist:
• Proton version: 10.0-3

I confirm:

• [X ] that I have checked whether there are updates for my system available.

Symptoms

If RT reflections are enabled, the game immediately crashes with an error that the game is attempting to use more video memory than your system can support. This occurs regardless of the input and output resolution, and testing on Windows reveals actual VRAM usage is maxing out at 11-12 GiB at identical settings at 4K, which shouldn't be an issue as the 9070 XT has 16 GiB VRAM. Lowering the output resolution to 1440p doesn't resolve the issue.

I tested in Steam Game Mode (bazzite-deck) and from my KDE desktop, and included logs for both. I see the same behavior in both cases. I also validated files in Steam, but no errors were found.

Another user reported the same error on Nvidia hardware using the proprietary Nvidia driver on Proton-GE 10-26, and in that case, the error appeared to be caused by a zero-sized pipeline object passed to vkd3d-Proton. See https://github.com/HansKristian-Work/vkd3d-proton/issues/2763

steam-1817070-gamemode.log
steam-1817070.log

Reproduction

1. Enable RT reflections. The game will immediately crash with the above error.
2. To establish this is the cause, edit home/USERNAME/.steam/steam/steamapps/compatdata/1817070/pfx/user.reg and change "RTReflections"=dword:00000001" to "RTReflections"=dword:00000000"
3. Restart game and the game will run without crashing.

EDIT:

It turns out that I can prevent the crashes by using SteamDeck=0. When doing so, RT works normally without the crash/error message and VRAM usage is well below 16 GiB. SteamDeck=1 is set automatically by the Bazzite-deck image (boots directly into Steam Gaming Mode), and apparently it still applies when booting the game from the KDE desktop. Unlike other games, all the graphical options are available, but internally, it must be setting a low VRAM cap based on the limitations of the Steam Deck hardware.