search

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

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

Bad performance in Halo: The Master Chief Collection #350

Open BelleNottelling opened 1 year ago

BelleNottelling commented 1 year ago

Checklist [README]

Game / Application [Required]

Halo: The Master Chief Collection

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

i7 13700K

Graphic Card [Required]

Arc A770 LE 16GB

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu.zip

Description and steps to reproduce [Required]

Looks like Halo: MCC is yet another DX11 title that needs a fair bit of driver TLC. So far I have only played Halo: Reach specifically, however all of the games in the MCC use DX11 and I believe they share the same game engine so the issue should apply across the board.

The FPS is frequently quite bad. To get the game to be even remotely playable, I need to use the "performance" quality preset. Sometimes it will be running at 144fps and is smooth, but it also very often suffers frame-rate drops down to ~20 FPS, they seem to hit mostly when facing a large, open space, but I've even seen it while inside of buildings.

Despite the FPS drops, neither the CPU or GPU are under any kind of heavy utilization so it appears to just be a bottleneck in the drivers slowing things down.

I haven't tried DXVK in this game as it uses anti-cheat. You can launch the game without anti-cheat, but it then completely disables achievements (according to the PC gaming wiki), so I also wouldn't consider that to be an unacceptable workaround for the FPS problems.

Game graphic quality [Required]

Game resolution [Required]

2560x1440

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

The "performance" preset with no other settings changed.

Device / Platform name

No response

Crash dumps [Required, if applicable]

No response

Save game

No response

Arturo-Intel commented 1 year ago

@BelleNottelling Yes, another one to the list. DX11 are not performing well on the actual state of the drivers, but rest assure this problem is well know and is work in progress by our dev drivers teams. I cant give you an exactly ETA of when the fix will arrive, it depends on a lot of things that are outside my control. What I can do is share you news of this mater thought this thread.

Thank you for sharing this and your patience. -- r2

BelleNottelling commented 1 year ago

@BelleNottelling Yes, another one to the list. DX11 are not performing well on the actual state of the drivers, but rest assure this problem is well know and is work in progress by our dev drivers teams. I cant give you an exactly ETA of when the fix will arrive, it depends on a lot of things that are outside my control. What I can do is share you news of this mater thought this thread.

Thank you for sharing this and your patience. -- r2

Thank you

chopstix2594 commented 11 months ago

Performance is still poor on driver 4826, but I decided to give DXVK (2.3) a try and it runs flawlessly. (And indeed, launching the game with EAC enabled won't work with DXVK installed)

Karen-Intel commented 10 months ago

Hi all, just leaving here our internal number for tracking purposes: 16021489943 Issue is still a WIP in our end, we will provide updates as soon as we get them

Karen

Pleune commented 9 months ago

Just to link here, #575 mentions that driver 4952 fixes performance for the steam version. I can personally confirm that this is true of driver 4953 and the steam version of MCC.

I do notice some corrupted geometry for single frames while things load in, which I think is new, but its not very obtrusive and I have no idea if this is halo's problem or the driver's.