XPLOITR
Report a bug or exploit
WARDOGSWARDOGS · PC · version Season 2 (Oct 2026)

Crashes while compiling shaders (PC)

UnconfirmedUnpatched

Updated

PC players report that WARDOGS crashes during shader compilation at startup, so they can't get into the game; one sees memory use climb sharply while shaders compile, and another gets a 'Could not decompress shader group with Oodle' crash at launch. No official acknowledgement found.

Lifecycle

Reported · stage 1 of 5

5days open

Since first report

  1. Reported (reached) · now
  2. Confirmed (not yet)next
  3. Acknowledged (not yet)—
  4. Partial (not yet)—
  5. Patched (not yet)—
In current stage 5d
Workaround none yet
Game
WARDOGS
Platform
PC
Affected version
Season 2 (Oct 2026)
Kind
Bug
Confirmation
Unconfirmed
Patch status
Unpatched
First reported
Last updated
Latest fix or workaround
None on the record
How we label issues

Kind

  • Exploit: Repeatable and clearly advantageous to the player using it; essentially cheating.
  • Bug: Everything else: crashes, launch errors, broken features, visual or audio faults.

Confirmation

  • Confirmed: A developer or official account acknowledged it, an official known-issues board lists it, it appears in official patch notes, or 100+ corroborating posts on X were actually counted.
  • Unconfirmed: None of the above yet. Press articles are reports and never confirm an issue on their own.

Patch status

  • Unpatched: Known and open; no fix has been claimed.
  • Reported as unpatched: Players credibly report it persisting, including after a fix claim that never appeared in patch notes.
  • Partially patched: Official patch notes list a fix, but credible later reports say it still happens, or the notes only cover part of it.
  • Reported as patched: A developer, official account or player says it is fixed, but no official patch notes list it.
  • Patched: Official patch notes (a Steam news post or the publisher's patch notes page) list the fix, and nothing credible says it still happens.

Active means still affecting players: Unpatched, Reported as unpatched or Partially patched. Patched and Reported as patched issues are closed.

Estimated impact runs from 0.1 to 9.9 with one decimal. xploitr sets it from the rubric below. Factors: advantage to other players, reach, play blocked or progress lost, frequency, and whether a reliable workaround exists. Patched issues keep their historical impact.

Signed-in community members can report new issues and suggest status changes, such as Fixed or Still unpatched, with their platform, version and a source. Every report and suggestion is reviewed by an editor before anything on the record changes. A new issue is published only when the report has at least three independent sources (distinct accounts, or distinct sites for web pages, after blocked sources are removed), unless the owner approved that issue by hand. Approved input appears as a dated Update from the xploitr community source on the issue's timeline, credited to the member's username (reports can opt out and stay anonymous); nothing is counted or published automatically.

Impact bands

  • 0.1–2.9 Low: Cosmetic, audio, text and UI glitches with no effect on play.
  • 3.0–4.9 Moderate: Narrow gameplay bugs or small exploits, rare or with a workaround.
  • 5.0–6.9 Elevated: Bugs most players in a mode notice: hit registration, desync, balance-breaking damage.
  • 7.0–8.4 High: Widely abused competitive or economy exploits; crashes many players hit.
  • 8.5–9.9 Severe: Launch blockers, widespread progress or item loss, exploits that break the game for everyone.

Each issue has a dated timeline of updates (report, acknowledgement, announcement, fix, workaround). Update summaries are our own words; quotes and excerpts are the source's words, or our English translation when marked.

Estimated impactEstimated impact 7.0 out of 9.9, HighOur estimate from how many players it reaches and what it costs them.

Updates · 5

  1. Report

    Oct 24: a player gets WD-L014 crashes, sometimes during shader compiling.

    Community report · Steam · Forum thread ·
    “Game keeps on crashing. I get error WD-L014. Sometimes it crashes on start sometimes on shader comp. and sometimes on map load.... The game seems fun... when you actually get to play it. I wish the…”
    Community report · Steam · Forum thread · Open source
  2. Report

    Oct 24: a player's game now crashes at launch with 'Could not decompress shader group with Oodle'.

    Community report · Steam · Forum thread ·
    “I played for a 1 hour then crashed. Now i cant even load the game keeps crashing to crash report screen. I get 'Could not decompress shader group with Oodle' I have AMD 7800x3d. 32gb ram tried…”
    Community report · Steam · Forum thread · Open source
  3. Report

    Oct 25: a player can't start the game; it crashes every time while compiling shaders.

    Community report · Steam · Forum reply ·
    “I cant start the game atm, it crash every time when compiling shaders.”
    Community report · Steam · Forum reply · Open source
  4. Report

    Oct 25: the same player saw memory use jump by over 5 GB at 94% of the shader compile before the crash.

    Community report · Steam · Forum reply ·
    “Tried to change shader cache size in driver, came to 94% completed, then it just eat up over 5gb ram and crash”
    Community report · Steam · Forum reply · Open source
  5. Report

    Oct 25: another player still can't get past shader compiling after updating to AMD driver 26.10.1.

    Community report · Steam · Forum reply ·
    “tried upgrading amd to 26.10.1. No longer crashing whole pc but cant get past compiling shaders. game crashes every time”
    Community report · Steam · Forum reply · Open source
Sources · 55 CommunityCommunity reportSteam · Forum thread+ 4 similar community reportsHide
Community reportSteam · Forum thread
“Game keeps on crashing. I get error WD-L014. Sometimes it crashes on start sometimes on shader comp. and sometimes on map load.... The game seems fun... when you actually get to play it. I wish the…”
  • Community reportSteam · Forum threadOpen
    “I played for a 1 hour then crashed. Now i cant even load the game keeps crashing to crash report screen. I get 'Could not decompress shader group with Oodle' I have AMD 7800x3d. 32gb ram tried…”
  • Community reportSteam · Forum replyOpen
    “I cant start the game atm, it crash every time when compiling shaders.”
  • Community reportSteam · Forum replyOpen
    “Tried to change shader cache size in driver, came to 94% completed, then it just eat up over 5gb ram and crash”
  • Community reportSteam · Forum replyOpen
    “tried upgrading amd to 26.10.1. No longer crashing whole pc but cant get past compiling shaders. game crashes every time”
Show fewer