Skip to main content
RespawnDailyExplore

PC Gaming

[VALORANT] Stutter on shader compilation — what actually fixes it

Finally worked this out, so here is the write-up I wish I had found. Everything I read suggests it should just work, and for me it very much does not.

16 replies620 viewsStarted 19 Jun 2026Last activity 24 d ago
  • performance
  • troubleshooting
  1. Aria D.
    Aria D.Original post

    @aria_d19 · 19 Jun 2026, 01:51

    #1

    Finally worked this out, so here is the write-up I wish I had found. Everything I read suggests it should just work, and for me it very much does not.

    I do not want to sink more time or money into it before I understand what I am optimising for. Will update the post if I find a cleaner solution.

  2. Noa E.

    @noa_e · 20 Jun 2026, 11:52

    #2

    Speaking as someone who got it wrong initially, nine times out of ten it is a driver or a background process, not the thing you suspect.

    Report back once you have tried it.

  3. Mika L.

    @mika_l · 22 Jun 2026, 00:37

    #3

    For what it is worth, the difference is real but small enough that you may not notice it while playing.

  4. Pilot KX

    @pilot_kx · 22 Jun 2026, 09:01

    #4

    For what it is worth, it is almost always a setting rather than hardware, so try the free fixes before spending anything.

  5. Cobaltmoth

    @cobaltmoth96 · 23 Jun 2026, 08:00

    #5

    Only partly related, but keep a note of what you changed, otherwise you cannot undo it cleanly later.

    Report back once you have tried it.

  6. Pilot KX

    @pilot_kx · 25 Jun 2026, 05:02

    #6

    Had the exact same issue. give it a clean reinstall before assuming the hardware is at fault.

  7. Driftfox

    @driftfox97 · 25 Jun 2026, 17:35

    #7

    Same boat here. the difference is real but small enough that you may not notice it while playing.

    Worth a shot before anything drastic.

  8. Ravi G.

    @ravi_g23 · 27 Jun 2026, 21:30

    #8

    Worth checking first: measure before and after, otherwise you are just guessing whether it helped.

    Report back once you have tried it.

  9. Theo N.

    @theo_n27 · 28 Jun 2026, 10:15

    #9

    Speaking as someone who got it wrong initially, that behaviour is intentional, even though it is poorly explained in-game.

    Report back once you have tried it.

  10. Riftkin

    @riftkin · 29 Jun 2026, 12:01

    #10

    In my testing, verify the files before anything else; it catches more problems than people expect.

  11. Cinderwave

    @cinderwave · 1 Jul 2026, 00:32

    #11

    Agreed on most of this, except the trick is to change one thing at a time and actually note the result before touching anything else.

    Others may have a cleaner method.

  12. Theo D.

    @theo_d · 1 Jul 2026, 23:26

    #12

    Counterpoint: nine times out of ten it is a driver or a background process, not the thing you suspect.

    Let us know which part worked.

  13. Riftkin

    @riftkin · 2 Jul 2026, 16:57

    #13

    The usual fix here is keep a note of what you changed, otherwise you cannot undo it cleanly later.

    Report back once you have tried it.

  14. Ines H.

    @ines_h · 3 Jul 2026, 03:46

    #14

    This comes up a lot, so: the defaults are conservative on purpose, so there is usually headroom to gain.

  15. Damian Piszczek

    @damianpiszczek · 3 Jul 2026, 17:00

    #15

    For what it is worth, the trick is to change one thing at a time and actually note the result before touching anything else.

    Others may have a cleaner method.

  16. Fluxdrake

    @fluxdrake29 · 5 Jul 2026, 10:08

    #16

    Depends on your setup, but broadly the averages hide the problem; look at the one percent lows instead.

  17. Ines H.

    @ines_h · 6 Jul 2026, 15:45

    #17

    This is the bit people miss — do the cheap diagnostic first — it costs nothing and rules out half the causes.

    Report back once you have tried it.

Be specific and civil. Referral links are removed automatically.