-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spider-Man 2 crashing when switching to Miles #2322
Comments
Is this after the fight against Sandman? |
Yes. |
I've played for a while on a RTX 4080 but haven't been able to get a crash yet. Can you screenshot the exact settings used? |
Ye i have played and gotten past that. Will poke some more |
Well there was a small update patch for the game, and I tried it again and it no longer crashes at this particular spot and I was able to progress and play a mission. Perhaps it's just game related. |
I am able to get the game to freeze after i upped my resolution to the same as yours with gamescope (my monitor is only 1080p) Edit: Actually that might just be gamescope and not the upped resolution. Is acting a bit weird |
Note that this specific game has a lot of performance issues. On Ubuntu 24.04 I have the same issues on windows 11. I don't know how you guys managed to play without crashes but for me on 2 different computers, one with a gtx 1080 and another with a 4090 it crashes in less than 20 minutes (or even less) of playtime. The crashes happen on both operating systems (Ubuntu and windows 11). 4090 pc has 128gb of ram, with a 13900k. I tried playing at 4k.Horrible experience. The gtx 1080 pc gas 64 of ram, with a 6700k. I played at 1080 same experience. So this is just to clarify that maybe it is not proton or vkd3d or dxvk related, but game is badly done and should have a fix soon. |
Description:
When you're able to switch to Miles for the first time and are able to swing it crashes every time. Log shows:
Software information
Spider-Man 2
Maxed out settings
System information
Log files
steam-2651280.log
The text was updated successfully, but these errors were encountered: