Skip to content

Troubleshooting

codingncaffeine edited this page Oct 15, 2026 · 5 revisions

Troubleshooting

No game engine is found

If Play says "No game engine was found to play in", install UZDoom (or GZDoom), then press Play again. Editing works meanwhile. Remixing a game's own map needs one too, because WadSmith reads the engine's own rules for what each line does.

  • On Linux: from Flathub as org.zdoom.UZDoom, the AppImage from UZDoom's releases, or on Arch uzdoom-bin from the AUR. On Windows: the zip from UZDoom's releases, or winget install UZDoom.UZDoom.
  • Installed somewhere WadSmith does not look? Choose it in Preferences, under Engine: the uzdoom or gzdoom program (uzdoom.exe on Windows), an AppImage, or a Flatpak's command.

See Installing.

No games found

The start screen says "No games found yet" when WadSmith finds no game data.

  • Press Pick a game file... and choose the WAD itself (DOOM2.WAD, HERETIC.WAD, or a ZIP holding one), or Add a folder... (both also in Preferences, under GAME FOLDERS). WadSmith looks inside ZIPs and in the folders beside and above the one you choose; when it still finds no base game it says what the folder held, which usually shows what went wrong.
  • Or press Get Freedoom. WadSmith downloads it, checks it and keeps it in its own games folder, ~/.local/share/wadsmith/games/freedoom. If the download fails, put freedoom1.wad and freedoom2.wad in a folder yourself and add that folder.

Adding a folder makes WadSmith look again.

The game shows a checkerboard

A checkerboard in the game means a wall, floor or ceiling uses a texture name the game does not have. WadSmith warns about it before you play ("a picture the game does not have"), and after a Play it names the missing texture and where it is used. Open Problems, press Show, and drop a texture from the Textures shelf there. Textures from your other games are copied into the project when you drop them. See Things, Textures and Shelves.

Play from here will not start

It starts where the 3D view stands, so turn on 3D first. If the spot is outside the map, or the player does not fit there, WadSmith says so; walk or fly the view into a room.

The Game's view stays plain or black

The Game's view asks GZDoom for a picture on a private screen. If the picture comes back black, WadSmith switches to the software renderer from then on and writes a line in the log.

"Your changes could not be kept"

The status bar shows this, or the reason WadSmith gives, when a change could not be written to the project. The log has more. If it keeps happening, report it (below).

A project will not open

  • "Is not a WadSmith project": the folder has no wadsmith.json; WadSmith makes that file in every project. Pick the project folder itself. To edit a WAD someone gave you, use Open a map file... (or put it in a folder and open that: its maps are offered).
  • "No longer in …": the map's file was moved or deleted after WadSmith found it. WadSmith looks again by itself; a file moved into one of your game folders is listed again where it is now.
  • "Saved by a newer WadSmith": update WadSmith.

Where the log is

  • WadSmith: ~/.local/state/wadsmith/logs/wadsmith.log. Earlier runs are kept beside it, numbered. With --portable DIR it is DIR/state/logs/wadsmith.log.
  • The last game run: in ~/.local/share/wadsmith/engine/ (under DIR/data in portable mode), log-last-play.txt from UZDoom, last-play from GZDoom.

Run wadsmith --version to see which version you have. See Projects and Files.

Reporting a problem

WadSmith is early, so please report what you find in GitHub Issues. Say:

  1. What you did, and what you expected to happen.
  2. The version from wadsmith --version, and your distribution and whether you use X11 or Wayland.
  3. The end of wadsmith.log.
  4. If it is about one map, whether it happens in a new map too.

Clone this wiki locally