GOG’s promise is a classic that installs and runs on a modern PC without tinkering — and most of the time it delivers. But GOG’s patches solve compatibility, not display preferences. A GOG release can run perfectly and still lock you into exclusive fullscreen, stretch a 640×480 picture across a 27-inch monitor, or play its music at the wrong speed. That leftover gap is exactly where DxWnd fits: not as a repair for a broken GOG release, but as the window-and-behaviour layer GOG never promised to add.
What GOG Already Fixes — and What It Doesn’t
GOG’s in-house work typically covers the hard part: installers that run on 64-bit Windows, bundled wrappers or tweaks that get the game booting, and fixes for the crash-on-launch problems that plague original CD versions. If a game won’t start at all on your system, the GOG release is usually the version most likely to start.
What GOG generally does not give you is control over how the running game presents itself:
- A window. Many GOG classics still take over the whole screen, with all the alt-tab fragility that implies.
- Window size and position. There is no GOG-side setting for “run this 800×600 game in a window in the corner of my second monitor.”
- Game speed. Titles whose speed is tied to old hardware timing can still run too fast, and a store patch rarely addresses that.
- Per-game display quirks. Palette behaviour and similar era-specific issues are handled case by case, not as a rule.
DxWnd addresses precisely that list: it hooks the game as it launches and forces it into a window you control, with per-game options for speed (time stretching), colours and more. The two layers don’t compete — GOG makes the game run, DxWnd decides how it runs.
Three Covered Games You Can Buy on GOG Today
Three of the game guides on this site are for titles GOG currently sells, and each guide documents settings traced back to the DxWnd project’s own forum:
- Disciples: Sacred Lands — the GOG Gold edition specifically needed a compatibility option (“Skip FreeLibrary recursion”) because of how its launcher hooks the game; the full story and settings are in the guide. The game itself is sold as Disciples: Sacred Lands Gold on GOG.
- Carmageddon 2 — the guide covers the frontend-versus-engine executable problem (launch through the frontend and you lose sound) and the virtual-registry setup the game expects. Sold as Carmageddon 2: Carpocalypse Now on GOG.
- Project IGI 2: Covert Strike — DxWnd gained a dedicated video option for this game (“Video > Min”, in the developer’s own words added because IGI 2 needed it); the guide walks through it. Sold as I.G.I. 2: Covert Strike on GOG.
The full list of covered titles is on the game guides hub.
How GOG Installs Differ (and Why DxWnd Cares)
GOG gives you two install routes, and they put the game files in different places:
- GOG Galaxy installs into its own library folder (by default under the GOG Galaxy program folder), and games are usually started from the Galaxy client or its shortcuts.
- Offline installers — the downloadable setup files from your GOG library page — let you choose any destination folder, and the installed game never needs Galaxy to run. GOG games are DRM-free; the client is optional.
For DxWnd, what matters is that a profile points at the real game executable, as explained in how to use DxWnd. With a GOG install that means browsing into the game’s folder and finding the actual .exe — not a Galaxy shortcut, and ideally not a launcher stub either. Some GOG releases start through a small launcher program first; several forum-documented problems (including the Disciples case above) come down to DxWnd hooking the launcher while the real game process escapes unhooked, or the reverse. If a GOG game ignores DxWnd, the wrong target executable is the first thing to check.
Two practical notes. First, installing GOG games into a folder you control — the offline installer makes this easy — keeps everything in one place and avoids the permission quirks of protected system folders when a hooking tool is involved. Second, launching a GOG game through DxWnd means launching it outside Galaxy: Galaxy-side extras such as its overlay and playtime tracking may simply not engage for that session. The game itself doesn’t care, but if those extras matter to you, that’s the trade-off.
A Version Caveat: GOG Build Is Not the CD Build
One subtlety worth knowing before you borrow settings from anywhere: a GOG release is often a slightly different build of the game than the original CD version — a different executable, sometimes with compatibility work already baked in. Per-game advice, including DxWnd forum threads and shared .dxw profiles, may have been written against either build. When a thread’s settings don’t behave as described on your GOG copy, a build difference is a prime suspect, and it’s also why the guides on this site name the exact edition they cover wherever the forum evidence does. The reverse is true as well: the Disciples guide exists precisely because the GOG edition behaved differently from the disc release and needed its own documented option.
Galaxy-side features deserve the same clear-eyed note as the overlay. Cloud saves and achievements are Galaxy services. A session launched through DxWnd, outside the client, may not sync saves or register achievements the way a Galaxy launch would. For most classic single-player games that’s a footnote — but if you’re mid-campaign in a title whose cloud saves you rely on, test with a copied save folder first rather than discovering the behaviour afterwards.
When You Don’t Need DxWnd at All
Honesty cuts both ways. If a GOG release already offers its own windowed mode, or it runs fullscreen exactly the way you want to play it, adding a hooking tool adds variables without adding value. DxWnd earns its place when there’s a specific behaviour you want to change — a window, a fixed size, a slower game speed, a palette fix. Start from the problem, not from the tool.
If you do have one of those problems, the workflow is the standard one: add the GOG game’s real executable to DxWnd, enable Run in Window, and test — the step-by-step version is in the main DxWnd tutorial, and per-game specifics for the three titles above are in their guides on the games hub.