How to Fix the DSMapStudio "Unknown DCX Format" Error

Unknown DCX format almost always lands the day after you update a game. A project that worked yesterday opens, DSMapStudio reaches for regulation.bin (or a map or message file), and instead of loading it throws the error. DCX is the compression wrapper FromSoftware packs its files in, and the message is literal: this build doesn't recognize the wrapper version on that file. The file is newer than the tool — a patch shipped a packing format v1.11.1 was never taught to read.

This is not a corrupt download or a broken install, and the fixes that feel obvious — reinstall the tool, "verify integrity of game files," re-download DSMapStudio — do nothing, because none of them change a format-version mismatch. There are exactly two real fixes: read newer files with Smithbox, or roll the game back to a version v1.11.1 supports. Everything below decides which.

What actually causes it

FromSoftware periodically changes how files are compressed and how param tables are laid out. Every tool that hard-codes the old layout breaks the moment those new files ship. DSMapStudio v1.11.1 (June 2024) was never updated for the changes that arrived with Elden Ring patch 1.12, the post–Shadow of the Erdtree line. Point v1.11.1 at a 1.12+ regulation.bin and you get Unknown DCX format, because the wrapper no longer matches what the tool expects. The same class of error shows up on other games after major patches, or when a file was re-saved by a different, incompatible tool — but the Elden Ring 1.12 boundary is the overwhelming majority of cases.

Step 1 — Check your DSMapStudio version

Confirm you're on v1.11.1. Older builds fail on files v1.11.1 handles, so updating is the cheapest first move, and because the tool is portable "updating" just means extracting the newest DSMapStudio.zip from the Releases page — your projects live elsewhere and are untouched. (Installation guide if you need it.) Already on v1.11.1 and still erroring? The problem is the game patch — Step 2.

Step 2 — Check your game patch

Find the installed patch. Elden Ring shows it in the bottom-right of the title screen (e.g. 1.12.3); on Steam, Properties → Updates shows the build. The one question that decides everything: is Elden Ring on 1.12 or later? If yes, v1.11.1 cannot read it and no setting inside DSMapStudio changes that.

Compatibility by game and patch

The format boundary per game — which patch line introduced files v1.11.1 can't read:

A ✗ row → pick a fix below. A ✓ row but you still see the error → the specific file was likely re-saved by another tool in an incompatible format; re-extract it from a clean copy with UXM.

Fix 1 — Switch to Smithbox (for Elden Ring 1.12+)

For post-SotE Elden Ring the direct fix is Smithbox, the actively maintained fork that continues DSMapStudio's codebase and reads current patches. It's not a rival — it's the successor for newer versions, and the Param Editor workflow is the same one you already know. Bonus: Smithbox doesn't require UXM unpacking before creating a project, a step DSMapStudio needs. Grab it from the Smithbox releases, point it at your game, and the file that threw Unknown DCX format opens. Use this if you want to stay on the current game patch.

Fix 2 — Roll the game back on Steam

If you specifically need v1.11.1 — for example to match a mod built against a pre-1.12 base — downgrade the game instead. Steam has no downgrade button, so it's manual:

1. Find the Depot ID and the Manifest ID of the last pre-1.12 build (SteamDB lists every depot and historical manifest).
2. Open the Steam console (steam://open/console).
3. Run download_depot <AppID> <DepotID> <ManifestID> to pull that exact build.
4. Stop auto-updates (Properties → Updates → "Only update this game when I launch it") or play offline, so it doesn't re-patch.

This pins the game to an older version — fine for offline modding, not ideal if you also want current official content. Manifest IDs change, so verify them on SteamDB before running the command rather than trusting a single forum post.

Dark Souls and the other games

The Souls trilogy, Sekiro, and Bloodborne don't get the frequent format-breaking patches Elden Ring did, so Unknown DCX format is rare there and usually points at a file, not a patch: opening something a different tool already re-compressed, or unpacking the wrong way. Dark Souls: PTDE must be unpacked with UDSFM, not UXM — using the wrong unpacker produces files DSMapStudio can't read. Re-extract the offending file from a clean install with the correct unpacker and it clears.

Still not working?

Tool matched to patch and a specific file still errors? Report it with details — game, patch, exact file — on the DSMapStudio GitHub Issues (someone has usually logged the same boundary), or ask in the SoulsModding Discord.

Once the file opens you're back in business: Param Editor hub to resume editing, or merge regulation.bin for Elden Ring if you were combining mods. If it won't even launch, that's separate — see DSMapStudio won't open.