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

Horizon Forbidden West temporary full black screen during shader compilation #788

Closed akarnokd closed 1 week ago

akarnokd commented 1 month ago

Checklist [README]

Game [Required]

Horizon Forbidden West

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

i7 13700K

Graphic Card [Required]

Arc A770 LE

GPU Driver Version [Required]

31.0.101.5518

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]

With driver 5518, I launched Horizon Forbidden West v1.4.59.0, which of course started recompiling shaders.

When I fast travelled to the Burning Shores, my monitor went black twice. As I fast travelled around the entire map, whenever more shader compilation happened, my monitor went black occasionally.

I could repeatedly trigger this temporary black screen by

As seen in the video below, I have the Arc Control overlay open, so it's not just the game that stops displaying image, but the entire desktop.

https://www.youtube.com/watch?v=P48fordjrqA

As far as I can tell from the recording, neither the GPU nor the CPU is loaded when this black screen happened.

My PSU is a Corsair RM750x (2021), In service since February 2023. The monitor is attached via a recent, 8k60 HDMI cable to the A770. The card has separate 8 and 6 pin PCIe power coming from the PSU.

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

image

image

image

Device / Platform name

No response

Crash dumps [Required, if applicable]

No response

Save game

quicksave0.zip

Zack-Intel commented 1 month ago

Hi @akarnokd,

Thank you for the detailed description. I'll begin replication to see what can be done.

In the meantime, I have a couple quick clarifying questions:

  1. Has this happened with any older graphics drivers, or is this a regression?
  2. Do any other fast travels show this issue as well?
akarnokd commented 1 month ago

Never happened with this game before between 5382 and 5445.

It can happen when travelling between biomes that have many shaders to compile. The home - burning shores is the most consistent.

akarnokd commented 1 month ago

5522 after DDU. The same black screen when traveling from the save location to the burning shores, at the same phase. With 5522, I got the black screen when traveling back right after arriving at the burning shores.

Zack-Intel commented 3 weeks ago

Hi @akarnokd

I have been working to test on multiple systems with the same graphics settings, but I'm still not able to see the issue described. I'll try some other settings and see if that changes anything.

In the meantime, can you also let me know the CPU/GPU usage as it loads the game for you? I want to see if there's potential issues with usage of the GPU

akarnokd commented 3 weeks ago

Sure, will do it in about 10 hours from now.

akarnokd commented 3 weeks ago

I was unable to trigger the issue, even after two shader cache clears. Still on 5522.

This was my load profile, but no black screens. It loaded in about that 10 second Window:

image

The GPU power remains < 70W during all the initial shader compilations. Only the CPU goes to 80-95% on the initial compilation load. The first fast travel is <60% where the black screen used to happen.

I'm on a B760 board with 13700K not OC'd but haven't applied any PL2 power limit as I had no strange crash issues in the past 15 months. Will however monitor the CPU power usage again to see if it spikes too high.

akarnokd commented 3 weeks ago

No power spike above spec, no black screen either:

image

Cooler is a Be Quiet Dark Rock 4, rated at 200W.

akarnokd commented 1 week ago

I couldn't trigger the issue after DDU clean installing 5590 either.

Since you couldn't trigger the problem either since the inital report, feel free to close this issue for now.

Zack-Intel commented 1 week ago

Hi @akarnokd

Thank you for verifying, and I'm glad the clean install of the new driver seems to resolve it on your end.

If the issue pops up again, feel free to open a new case linking this one and we can pick up where it was left off.