Stale/corrupt shader cache or loading failure

A damaged LMU shader cache can interrupt car or track loading. A stall near 48% is a clue to investigate, not a diagnosis by itself.

Automatic repair availableActiveEvidence reviewed 2026-09-01Guide updated 2026-09-29

Checks and expected results

Before you repair it

Record the loading stage and check the current trace for shader/cache failures.
Rule out a named unreadable track or vehicle package; that needs content recovery instead.
Close LMU and preserve UserData\Log\Shaders\dynamic.cache before the targeted cache reset.

How to confirm the result

Start LMU and retry the same session. Allow the shader cache to rebuild; the useful result is that loading completes without the previous cache failure.

Repair limits and when to stop

This resets cached shaders, not game packages, graphics drivers, or wheel settings. A vendor-wide graphics cache reset requires separate confirmation and supporting evidence.

How PitMedic recognizes it

Loading failures around track/car initialization without package corruption; repeated shader/cache errors or known 48% load behavior.

Signals PitMedic may recognize

shader
dynamic.cache
48%

Built-in response

Back up then clear UserData\Log\Shaders\dynamic.cache; optionally clear vendor DX shader cache only when the evidence supports it.

Repair safetyAutomatic/reversible for LMU dynamic.cache; vendor cache requires confirmation

Verification sources

PitMedic prioritizes vendor documentation and labels community findings separately.

Common FixesLe Mans Ultimate Support · Official source
Official LMU guidance recommends clearing dynamic.cache for crashes.
Open source
48% loading fixesLe Mans Ultimate Community · Official source
Community moderator guidance also lists dynamic.cache and NVIDIA DX cache cleanup.
Open source