Open sysms opened 2 years ago
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
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.
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:
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:
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 :)
I found errors just like @Mikaka27 but with different class and chid:
[ 901.123552] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 0: SAVE_RESTORE_ADDR_OOB
[ 901.123576] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x500900=0x80000001
[ 901.123594] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 1: SAVE_RESTORE_ADDR_OOB
[ 901.123613] NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception: ESR 0x508900=0x80000001
[ 901.123748] NVRM: Xid (PCI:0000:01:00): 13, pid=5828, name=Spider-Man.exe, Graphics Exception: ChID 0013, Class 0000c597, Offset 00000000, Data 00000000
Commenting out the appid and manually setting PROTON_ENABLE_NVAPI=0 PROTON_HIDE_NVIDIA_GPU=1
didn't help.
Hello, per "Fixed a bug where Marvel's Spider-Man Remastered would sometimes crash with Xid 13 errors on Turing and later." in the NVIDIA 520.56.06 video driver release, please retest that video driver release (or newer) once it comes available through your normal distro update channel(s).
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.
@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
Hello @Skiski, 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.)
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?
Compatibility Report
System Information
I confirm:
Symptoms
After starting the game, a first window appears, telling me, I've no GPU installed. Clicking on OK starts the launcher, which works well. Tried different graphical presets (low, medium). After this, another window tells me, I've not the latest version of graphics driver. Clicking on OK, a black screen appears, and after some seconds, the game crashes. Sometimes the crash reporter appears, sometimes it doesn't.
Game works well on my Steam Deck. :)
Reproduction
Always.
steam-1817070.log