Troubleshooting

DSMapStudio Troubleshooting Guide

Tested on v1.11.1 Updated 2026-06-09

DSMapStudio Troubleshooting Guide

Nearly every DSMapStudio problem is one of a handful of recognizable failures — won't open, no .exe, empty Param Editor, "Unknown DCX format," black Map Editor — and none of them are random. Each has a specific cause and a specific fix, so match your symptom below instead of guessing or reinstalling. Run the five basic checks first; they resolve the majority of "it's broken" reports on their own.

Find your problem

SymptomLikely causeFix
Won't open, no windowMissing Visual C++ x64 / .NET 7 runtimeDSMapStudio won't open
No DSMapStudio.exe after extractingDownloaded source code, not the releaseNo .exe found
"Unknown DCX format" on a fileGame patched past what your version readsUnknown DCX format
Map Editor viewport is blackGPU lacks Vulkan (Intel integrated)Intel GPU / Vulkan
Crashes after launchingAntivirus, stale config, or GPU initDSMapStudio won't open
Crashes on Ctrl+D duplicating an enemyKnown data-specific bugCrash duplicating enemies
Param Editor empty / rows namelessPacked files, wrong Game Type, or a filterParams not showing
"Invalid game executable"Wrong game directory or Game TypeInvalid game executable
On LinuxNeeds Wine 9.0+ with runtimes in the prefixLinux / Wine
Edits don't appear in-gameModEngine2 not configuredQuick fixes

Before anything — the five basic checks

A large share of "DSMapStudio is broken" is one of these. Run them first:

  1. Right release. v1.11.1, downloaded as DSMapStudio.zip from the Releases assets — not the "Source code" zip, which has no .exe.
  2. Runtimes installed. Visual C++ x64 Redistributable and .NET 7 Desktop Runtime. Missing either → it won't open at all.
  3. Game unpacked. DSMapStudio reads UXM-unpacked files (UDSFM for Dark Souls: PTDE), not the packed Steam install. Packed files → empty Param Editor.
  4. Game Type matches the game. A leftover type from a previous project makes every value read as garbage.
  5. Patch is supported. v1.11.1 can't read Elden Ring 1.12+ (post–Shadow of the Erdtree) — that's the "Unknown DCX format" boundary.

All five pass and it's still wrong? Find your symptom above. Setup details: installation guide and first project setup.

Quick fixes for other issues

Smaller problems that don't need a full page:

Edits don't appear in-game

If your changes show under the Modified filter in DSMapStudio but not in the game, the problem is ModEngine2, not your edit. Point its config at your project's mod output folder and launch the game through ModEngine2. For Dark Souls 3, launch offline — modded DS3 online risks a soft ban.

"I saved but the game uses the old file"

DSMapStudio writes to your project's output, not into the packed game. The runtime mod loader (ModEngine2) is what feeds that output to the game — if it's pointed elsewhere, you'll edit forever with no in-game change. Same fix as above.

Still stuck? The DSMapStudio GitHub Issues and the Souls Modding Discord are where to report a specific error with your game, patch, and the exact message. If the blocker is simply that your game is too new for v1.11.1, the answer is usually Smithbox — and once unblocked, the Param Editor hub is where most modding actually happens.