← Back to the stories
Games Linux

Horizon Zero Dawn on Linux: The Archived 2022 Downgrade Fix

A game update can leave Linux players waiting for the compatibility stack to catch up. Horizon Zero Dawn had a particularly awkward example after patch 1.11: broken foliage, smearing and other graphics problems appeared in community reports, and rolling back selected game files became a temporary workaround.

I’m keeping this guide as a reference for that workaround. It records what HZDDowngrader changed, when the underlying fixes arrived, and how to stage the historical files separately if there is a reason to investigate them again.

Archive status — checked 24 October 2026: HZDDowngrader is archived. Its author marked it unnecessary on 24 January 2022 after fixes reached Proton Experimental and a contemporary GE build. A working modern installation does not need this downgrade.

What happened · The four historical files · Troubleshooting today · Download into a staging folder · Restore Steam’s current files

Which Horizon Zero Dawn does this apply to?

This archive concerns the original Steam release of Horizon Zero Dawn Complete Edition, AppID 1151640. HZDDowngrader targeted its 1.10 Hotfix files to work around problems introduced with 1.11.

Horizon Zero Dawn Remastered is a separate Steam application, AppID 2561580. These manifests are not a Remastered downgrade. They also do not provide a procedure for the GOG, Epic or console editions.

What happened in December 2021 and January 2022?

The VKD3D-Proton issue for the 1.11 update opened on 8 December 2021. Reports included flickering foliage, smeared imagery and problems when using FSR, with both AMD and NVIDIA systems represented.

On Linux, Proton uses VKD3D-Proton to translate the game’s Direct3D 12 work to Vulkan. The regression was tracked in that compatibility layer, and the linked fix updated its dxil-spirv shader-translation component.

DateWhat changed
8 December 2021The 1.11 graphics regression was reported to VKD3D-Proton.
2 January 2022PercentBoat4164 released the first HZDDowngrader version.
11 January 2022VKD3D-Proton merged the shader-translation update linked as the fix for issue #941.
24 January 2022HZDDowngrader’s final v1.2 release said the tool was no longer necessary, pointing players to the then-current Proton Experimental and Proton-7.0rc6-GE-1.
26 January 2022The game’s separate 1.11.2 patch brought VRAM-management and visual fixes.

The old GE version above belongs to the historical timeline. For troubleshooting now, start with a maintained Proton version available through Steam.

Horizon Zero Dawn benchmark scenery with stone buildings and foliage, captured for the December 2021 Linux graphics bug report.
Historical community capture submitted by phush0 with the December 2021 graphics report. Game imagery © its respective rights holders.

What HZDDowngrader actually replaced

The v1.2 script used DepotDownloader to retrieve four files from two Steam depots. A depot is a group of files delivered by Steam; a manifest identifies a particular snapshot of that group.

Steam depotHistorical manifestFiles selected by the script
11516422110572734960666938HorizonZeroDawn.exe
11516418564283306590138028LocalCacheDX12/HashDB.bin
LocalCacheDX12/ShaderLocationDB.bin
Packed_DX12/Patch.bin

This was a partial rollback of game files, not a complete download of every file from an older game build. It changed no GPU driver. The same four-file combination is not guaranteed to work with every later installation or mod setup.

Keep the application, depot and manifest numbers together. Using the application number alone downloads different content unless the intended depot and historical manifest are also selected.

Why I would not run the archived script unchanged

The final v1.2 release provides a single shell script. Its automation was written for an older Debian-style setup, with assumptions that deserve checking before it touches a current installation:

  • The game directory is hard-coded to ~/.steam/debian-installation/steamapps/common/Horizon Zero Dawn. Other Steam libraries and Flatpak installations can use different paths.
  • It uses APT, Snap, an old .NET runtime and DepotDownloader 2.4.5. Its package-status check and package-install condition are also faulty.
  • The copy commands assume a particular DepotDownloader build-number directory. The script does not stop reliably on download or copy failures, and its final success message is not proof that every operation worked.
  • It overwrites game files without first making a backup. Its cleanup also removes named directories from the working folder.
  • It passes the Steam password as a command-line argument to DepotDownloader, where local process inspection can expose it.

Download tools and copy game files as your normal user. Limit administrator access to installing any required distribution packages; running the whole process as root can leave root-owned files in a Steam library.

If the game has graphics problems today

Start with the current game and compatibility stack. The 2021 regression already received a fix; a new problem needs evidence before applying a historical rollback.

  • Back up saves and any mods you want to retain. Steam Cloud synchronisation is not a substitute for keeping a separate backup.
  • Use a supported graphics driver for your distribution and hardware. Record the GPU and driver version when reporting a problem.
  • In Steam → Properties → Compatibility, compare a current stable Proton version with Proton Experimental. Test one change at a time.
  • Temporarily remove custom launch options, injected overlays and mods while comparing results. Keep a note of the original settings.
  • Use Steam → Properties → Installed Files → Verify integrity of game files to restore modified or missing tracked files. Back up mods first because verification can replace their changes.

For a Proton log, put this in the game’s Steam launch options, reproduce the issue, then remove it when finished:

PROTON_LOG=1 %command%

Proton normally writes steam-1151640.log in your home directory for the original Steam game. Keep the log with the game build, Proton version, driver version, graphics settings and a reproducible description of the fault. Review logs for personal paths before sharing them.

Preserve the historical download method

The following procedure downloads into a new folder and leaves the installed game alone. It is a reference for the original workaround, not a recommendation to downgrade a working game. Access to old Steam manifests can change; a valid game licence does not guarantee that these snapshots remain downloadable.

Use a Steam account that owns the original Complete Edition. These commands target x86-64 Linux and use the official, self-contained Linux x64 build of DepotDownloader 3.4.0, the latest published upstream release checked for this article. That archive includes its .NET runtime; installing an edge-channel .NET SDK is unnecessary for this route.

Run the commands in Bash, keep the same terminal open, and stop if a command fails. You need curl and unzip. On Debian or Ubuntu, install them if missing:

sudo apt update
sudo apt install curl unzip

1. Create an isolated working folder

hzd_work=$(mktemp -d "$HOME/hzd-rollback-archive.XXXXXX") &&
cd "$hzd_work"

Keep this directory for the archive. The remaining download commands run as your normal user.

2. Download the official Linux x64 tool

curl --fail --location \
  --output DepotDownloader-linux-x64.zip \
  https://github.com/SteamRE/DepotDownloader/releases/download/DepotDownloader_3.4.0/DepotDownloader-linux-x64.zip &&
unzip DepotDownloader-linux-x64.zip -d depotdownloader &&
chmod u+x depotdownloader/DepotDownloader

For another CPU architecture, choose the matching official release asset and adapt the filename. A Linux x64 executable is not an ARM build.

3. Write the two file lists

cat > exe-files.txt <<'EOF'
HorizonZeroDawn.exe
EOF

cat > data-files.txt <<'EOF'
LocalCacheDX12/HashDB.bin
LocalCacheDX12/ShaderLocationDB.bin
Packed_DX12/Patch.bin
EOF

4. Request the historical manifests

Read your Steam account name into a shell variable. The commands deliberately omit a password argument: let DepotDownloader prompt for the password and Steam Guard as required. Each invocation may need authentication.

read -r -p "Steam account name: " hzd_steam_user

Download the executable into its own staging directory:

./depotdownloader/DepotDownloader \
  -app 1151640 \
  -depot 1151642 \
  -manifest 2110572734960666938 \
  -username "$hzd_steam_user" \
  -os windows -osarch 64 \
  -filelist "$PWD/exe-files.txt" \
  -dir "$PWD/staged-exe" \
  -validate

After that download succeeds, request the three data files:

./depotdownloader/DepotDownloader \
  -app 1151640 \
  -depot 1151641 \
  -manifest 8564283306590138028 \
  -username "$hzd_steam_user" \
  -os windows -osarch 64 \
  -filelist "$PWD/data-files.txt" \
  -dir "$PWD/staged-data" \
  -validate

The explicit -dir destinations avoid relying on the archived script’s fixed build-number folder. If Steam denies the manifest request, authentication fails or a download is incomplete, stop here. Do not substitute files from an unrelated version.

5. Check and record the downloaded files

ls -lh -- \
  staged-exe/HorizonZeroDawn.exe \
  staged-data/LocalCacheDX12/HashDB.bin \
  staged-data/LocalCacheDX12/ShaderLocationDB.bin \
  staged-data/Packed_DX12/Patch.bin

Confirm that DepotDownloader reported successful downloads and all four files exist and are non-empty. Then record fingerprints for your own archive:

sha256sum \
  staged-exe/HorizonZeroDawn.exe \
  staged-data/LocalCacheDX12/HashDB.bin \
  staged-data/LocalCacheDX12/ShaderLocationDB.bin \
  staged-data/Packed_DX12/Patch.bin > historical-files.sha256

These hashes record the files you received; they are not an independently published checksum set. Retain the two file lists, the manifest numbers and download output alongside them. Avoid sharing account details or authentication material.

Only if a rollback test is justified

Before replacing anything, establish why the old four-file workaround is relevant to the fault being investigated. It does not provide a general method for reverting any future Horizon update.

  1. Use Steam → Properties → Installed Files → Browse to find the actual Complete Edition directory. Confirm AppID 1151640 and the presence of HorizonZeroDawn.exe.
  2. Close the game and Steam. Back up the installation, or at minimum all four files that would be replaced, preserving their relative directories. Back up saves separately; compatibility with an older executable is not guaranteed.
  3. Copy staged-exe/HorizonZeroDawn.exe to the game root. Copy the three files under staged-data into the matching LocalCacheDX12 and Packed_DX12 directories. Replace only those four files, rather than entire directories.
  4. Keep a record of what changed and test the original fault. Steam updates or file verification can replace the historical files, so this is not a permanent version pin.

Return to Steam’s current game files

To undo the modified installation, close the game, open Steam → Properties → Installed Files → Verify integrity of game files, and let Steam reacquire the current tracked files. Remove test launch options and return to the Proton version you normally use.

Verification repairs Steam-managed files, but does not necessarily remove extra files left by mods or other tools. Restore mod changes deliberately from your backup. Keep the historical staging folder separate from the live game directory.

Primary references

Leave a Reply

Your email address will not be published. Required fields are marked *