Open Susie1818 opened 4 months ago
Supplementary information: right now this game has random crashes A LOT, often when launching or quiting the game or when toggling ray-tracing on/off. Back in early January when I was doing extensive benchmarks (had at least 8 runs because I have 8 sets of statistics in my notes) on this game, it didn't behave like this (I didn't encounter any crash back then). It's not very long ago, only about 1 month ago.
I guess it's because something in Windows system mistakenly makes the Arc driver running on E-cores or the secondary threads of P-cores. Right now if I turn off both E-cores and Hyper-Threading, the game works okay, but if I let either E-core or HT (or both) to be enabled, the game just doesn't work correctly. However, it did work normally back in early January. This is a very weird case. I've been using the Arc GPU since December 2022, and so far this is the first and the only case that manifests this kind of problem.
For your reference: (Ray-Tracing: Very High, object range: 3)
8P+8E / no HT (16C16T, the preferred configuration I have always been using, and it used to work without an issue a month ago)
8P+0E / HT on (8C16T)
8P+8E / HT on (16C24T)
8P+0E / no HT (8C8T) ๐ workaround for now but this is very weird
๐ Ray-Tracing OFF then no problem
For your reference: (on my Windows 11+A750 system, the same Ray-Tracing settings: Very High, object range: 3)
๐This is how it should work correctly.
Hi @Susie1818 this is very helpful. Thanks.
Quick question: your statement "Another important clue is that I just found with another system with Windows 11 and Arc A750 that this problem seems not to exist on Windows 11. The GPU utilization is well above 90% and the framerate is good when running this game on that system." does this mean on win 11 w/ 13700KF it works without any issues but on win 10 with 13700KF you are seeing performance issues?
@mujeeb-intel
I don't think it has anything specific to do with 13700KF.
I understand. Just making sure that the issue does not persist on win 11. This way I can focus on win 10 trying to reproduce this issue. so win 11 doesnt have any issue but with win 10, does.
Hello @Susie1818 we shared this info with our dev teams under ticket number 14022009955. As soon as we have new info we'll be in touch.
Checklist [README]
Game [Required]
Spider-Man Remastered
Game Platform [Required]
Other game platform
No response
Processor / Processor Number [Required]
intel Core i5-13700KF
Graphic Card [Required]
intel Arc A770
GPU Driver Version [Required]
31.0.101.5081
Other GPU Driver version
31.0.101.5186
Rendering API [Required]
Windows Build Number [Required]
Other Windows build number
No response
Intel System Support Utility report
SSU_20240210.txt
Description and steps to reproduce [Required]
I did some benchmarks with this game in early January and it was okay without problems at that time. However, after seeing some people mentioning issues with this game on reddit recently, I retested it and found that some severe problem started to exist.
Back in January when I benchmarked the game, the GPU utilization was above 90% and the framerate was around 90 FPS. Now the GPU utilization drops to 70-ish% and the framerate drops to around 65 FPS. I tried driver version 5081 and 5186 and both have the same behavior (low GPU utilization and low FPS). (It was on driver 5081 when I did the benchmarks in January.)
Currently I find only one workaround which is disabling both Hyper-Threading and E-cores: with only P-cores and Hyper-Threading off, the GPU utilization can jump back to around 90% and the framerate can be restored to roughly 85 FPS, which is still not as good as the result I got in January but apparently helpful as of now, and a key fact is that I didn't have to use this trick (workaround) for it to run properly. Something has gone wrong between now and then.
Since disabling E-core and Hyper-Threading is obviously effective right now, I guess the issue has something to do with process scheduling or Thread Director. Nevertheless, not much have been changed with my PC since then. The only clues I can think of are some Windows Updates during this period of time, so I'll list them below:
Another important clue is that I just found with another system with Windows 11 and Arc A750 that this problem seems not to exist on Windows 11. The GPU utilization is well above 90% and the framerate is good when running this game on that system.
Game graphic quality [Required]
Game resolution [Required]
2560x1440
Game VSync [Required]
Off
Game display mode [Required]
Detailed game settings [Required]
with XeSS "Quality" mode
**Ray-Tracing must be ON. If RT is off then this problem won't occur.
Device / Platform name
No response
Crash dumps [Required, if applicable]
No response
Save game
No response