Shader Complilation on PC: About to become a bigger bottleneck?

II have a ryzen 7 and a 2070
when in the 90's was Doom Eternal, Control, Shadow of the Tomb Raider, Mechwarrior 5, Rage 2, Borderlands 3 ,Just Cause 4, Far Cry 5, ect ect ect released

 

I figured you'd still be running Windows ME or Windows 7 or some only DX11 OS.

 

Why you replied to my post about having increased storage space in windows 10
https://forum.beyond3d.com/threads/latest-windows-update-improves-storage-utilisation.61909/

 

That doesn't mean you use that on your gaming systems.

 

What other use is there for a p.c other than gaming

 

Paperweight.

 

Back to my question I know horizon zero dawn suffers from this (dont own it) and I do remember there was a few seconds delay in battlefield 2 where it said something like "optimising shaders"
but apart from that I dont remember experiencing this massive delay what games does it happen in ?

 

Metro Exodus doesn't have a shader compiling process.

 

Dishonored 2 does usually have a lengthy startup but I thought that might be their Denuvo copy protection. Sometimes the game loads quickly, but usually it takes something like 45 seconds? I didn't think the level loads were especially lengthy.

Actually when I think of shader compilation issues the only game that really comes to mind is the Dolphin emulator. They have been trying to solve emulation stuttering and have a few different approaches for pre-compiling shaders now, and of course Vulkan and D3D12 options.

 

It does whenever you change most settings.

 

Compared to the ridiculously long, mind numbing monologues, the loading screens were nothing.

 

So I tested Metro Exodus and i'd say it took about 100 seconds thats a big difference from the 10-15 minutes some people are claiming for shader compilation

 

Now imagine it on an older CPU and maybe on HDD.

 

If it's something that occurs at install time, not even load time, how is it a bottleneck?

 

It was already explained how it happens at points other than install time.

 

The game is doing it wrong if it happens at any other time than install time (and maybe game boot time after a driver update).

Games should ship with DXIL, then create and cache the pipeline state objects on first boot, the mechanism is already there: https://docs.microsoft.com/en-us/windows/win32/api/d3d12/ns-d3d12-d3d12_cached_pipeline_state .

 

While I do own a nvme drive the game itself is installed on a mechanical hard drive.
I did play it on a i5-2400 I dont remember how long it took but I dont remember it being any kind of problem.
I'm just not buying these scare stories that p.c gamers will be waiting 10-15 minutes for shader compilation