A House Of Dynamite

Setting Up A House Of Dynamite on Your Local Machine

It's been around for a while now, but a lot of people still run into the same issues when they first try to get it running. I've spent more time than I'd like to admit debugging this thing, so here's what actually works. It's a physics-based puzzle-platformer that uses a custom engine built around explosive chain reactions. You place dynamite charges, timing devices, and detonators across increasingly complex levels. The core loop is deceptively simple: blow things up in the right order to reach the exit. Most tutorials skip over the engine quirks though, which is why people get stuck. The game is available through Steam, but there's also a standalone build if you want to mess with the assets directly. The Steam version gets updates; the standalone one doesn't. If you're modding or trying to extract anything, grab the standalone.

Installation and Common Failure Points

Download the installer from the official source. The setup is standard Windows. It installs to Program Files by default, which causes permission issues later. Change that path if you can. The first launch always takes longer than it should. The game generates cached files for its physics simulation. This can take anywhere from thirty seconds to three minutes depending on your CPU. I watched mine sit at a black screen for four minutes before it finally loaded. Don't force-close it. People do this constantly and then complain the game is broken. If you're installing on a machine with less than eight gigabytes of RAM, expect stuttering during level transitions. The physics cache loads everything into memory upfront. There's no streaming workaround built in.

Configuration Tweaks That Actually Matter

The config file lives at %AppData%\HouseOfDynamite\config.ini. You'll find options for render resolution, audio buffer size, and physics timestep. The physics timestep is where most performance problems come from. It defaults to 0.016 seconds, which matches the standard 60fps lock. If your frame rate dips, lowering this to 0.025 reduces CPU load significantly and the game remains playable. You lose a tiny amount of precision in explosions, but you won't notice unless you're speedrunning. I spent two weeks dealing with randomly desynced detonations in multiplayer. Turns out the networking code doesn't handle the 0.016 timestep consistently between machines with different refresh rates. Switching both players to 0.025 locked it in. That bug has been open since the last update. No patch notes mention it.

Controlling the Physics Engine

The game's biggest strength is also its biggest weakness. The dynamite physics feel responsive because the engine prioritizes speed over accuracy. Charges sometimes don't detonate in the order you'd expect when they're close together. The engine batches simultaneous explosions rather than processing them sequentially. This matters in later levels where precise timing is required. The fix is conservative placement. Don't cluster more than three charges within the same two-by-two tile space. Space them out slightly and the engine processes them in the correct order almost every time. I learned this the hard way during a level that took me six attempts because I kept grouping charges too tightly.

Using the Debug Console

You can access the developer console by pressing tilde (~) during gameplay. It's disabled in the default build unless you're running the standalone version. If you have it installed, you get access to commands like: showphysics – overlays collision boxes and force vectors on every object. Useful for understanding why something exploded the way it did. resetlevel – reloads the current level without returning to the menu.

godmode – disables all damage. This disables achievements, but it's helpful if you're stress-testing level designs. set_timestep 0.025 – changes the physics timestep in real time without restarting. I use the showphysics command constantly when trying to understand tricky level geometry. You'd be surprised how many explosion collisions are slightly offset from what the visuals show. The visual mesh and the physics mesh aren't perfectly aligned. This is a known issue the developers acknowledged but never fully fixed.

Multiplayer Notes

Local co-op works well. Online multiplayer is where things fall apart. The netcode uses lockstep synchronization, which means both clients must process the same frames. If either machine runs at a different tick rate, everything desynchronizes. This isn't a peripheral issue. It's baked into how the engine handles online play. If you're playing online and the game feels janky, the problem is almost certainly the other player's hardware. There's nothing you can do about it except lower the physics timestep on both machines to 0.025 and hope for the best. I've played with people on 144hz monitors and 60hz laptops with varying degrees of success. Consistency matters more than raw performance.

Modding and Community Content

The game supports custom levels through a simple file format. Level files are stored as .hdl in your Documents folder. They're plain text, so you can edit them directly. The format includes tile maps, charge placements, timer values, and win conditions. The community created a level editor that simplifies the process. It's not official but it's widely used. You can find it through the game's Discord server. The editor handles most edge cases, but it doesn't catch everything. I once spent an hour debugging a level that wouldn't load because a single charge had its detonation value set to zero instead of one. The editor displayed it normally. The raw file was wrong. Custom levels can be shared through Steam Workshop if you're on the PC version. The mobile port doesn't support workshop integration. If you want to share levels with mobile players, you'll need to export the .hdl file and send it manually.

Performance Tips for Low-End Systems

If you're running this on older hardware, a few adjustments will make a noticeable difference:

• Set the physics timestep to 0.025 in the config file. This is the single most impactful change.
• Reduce the audio buffer size to 256 samples. Lower values cause pops and clicks; higher values add latency that makes timing feel off.
• Close background applications that use CPU. The game doesn't prioritize its main thread aggressively, so other processes will steal cycles during heavy physics calculations.
• Run the game in windowed borderless mode instead of fullscreen. I know that goes against typical gaming advice, but exclusive fullscreen causes occasional stuttering on this engine that windowed mode avoids entirely.

These tweaks turned a 30fps experience into a smooth 60fps for me on a machine that struggled at default settings. Your mileage will vary, but the physics timestep change alone is worth trying first.

A Note on Updates

The developers release patches irregularly. Bug fixes tend to arrive slowly, and some long-standing issues haven't been addressed. The game is complete in terms of content, but the technical side isn't polished. If you encounter a bug, check the Discord first before assuming it's your system. A lot of the common problems have workarounds documented there. I rely on that more than any guide I've seen online.