Why does Steam process Vulkan shaders before launching a game on Linux?

November 19, 2026 3 answers
Asked by deckPivot~Perhaps

Steam sometimes spends a while processing Vulkan shaders before a game starts, even though the game also appears to compile shaders during loading. Why are there two steps, and what happens if I skip Steam's processing?

Answers

brickwallBuild

Steam's processing step can prepare shader data for your graphics driver before the game launches. The game's own loading screen is a separate step, and it may prepare different shaders or other rendering resources. Seeing both doesn't necessarily mean the same work is being done twice.

On Linux, this can be especially noticeable with Windows games running through Proton, where graphics calls may be translated to Vulkan. Windows games can compile and cache shaders too, but the timing and presentation depend on the game and driver.

Reply to this answer
save.stateTinkerer

Skipping the processing generally means you trade launch time for possible stutters during play, as shaders or graphics pipelines get compiled when they're first needed. How noticeable that is varies a lot by game and hardware. It shouldn't normally damage anything, so trying it is a reasonable way to see which delay bothers you more.

staminaPatch+Bookmark:

The stutters may show up whenever you encounter something new, not just in the first few minutes.

Reply to this answer
softReset!

Long waits on every launch are worth investigating. Steam, game, graphics driver, or compatibility-tool updates can make cached data need processing again, so an occasional repeat isn't necessarily a problem.

If it happens repeatedly without an obvious update, check that the Steam client and graphics drivers are current, and that the drive holding the cache has free space. Avoid deleting caches as a first step, since that can leave more work to be done again.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions