IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
112 stars 3 forks source link

Crysis (2007) DX10 frametime spikes in driver 5590 #799

Closed jedi95 closed 1 day ago

jedi95 commented 1 week ago

Checklist [README]

Game [Required]

Crysis (2007)

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Core i9 14900KS

Graphic Card [Required]

Arc A770 16GB

GPU Driver Version [Required]

31.0.101.5590

Other GPU Driver version

No response

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

Start the Crysis benchmark via the tool using the following settings:

There should be no significant frametime spikes after the first loop. Using driver 5522 and earlier, there are none. With 5590, the second and third loop will have visible frametime spikes. This can be observed using RTSS or a similar overlay, and by measuring the 1% low FPS from the 2nd and 3rd loop of the benchmark.

I got the following results from my system: 5522: 165 avg / 104 1% low 5590: 185 avg / 18 1% low

This video shows the test with the 5522 and 5590 drivers: https://www.youtube.com/watch?v=nOVUdJtJ16o

Raw version in case youtube compression ruins it: https://jedi95.com/video/crysis_arc_5522_5590.mp4

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

Off

Game display mode [Required]

Detailed game settings [Required]

Device / Platform name

No response

Crash dumps [Required, if applicable]

No response

Save game

No response

Vivek-Intel commented 1 week ago

Hi @jedi95 there have been some improvements in the perf of this game with latest driver 5590 (release note

image

Generally game loads lots of assets and data into memory for first run which can cause perf drop in first loop and it further improves as you play reducing the constant need of loading data and assets, so there could be difference in score between first loop and subsequent run of the benchmark and difference between score here (5522 vs 5590 ) is due to optimization done in latest driver.

Vivek-Intel commented 1 day ago

@IGCIT please help close this