dgVoodoo2 and DxWnd are the two names every retro PC player meets first — and they are not really competitors. dgVoodoo2 translates what the game draws: it replaces the obsolete graphics APIs of the Glide and early DirectX era with modern Direct3D. DxWnd manages everything around the drawing: it forces the game into a window and emulates the behaviours of the era’s Windows itself. Because the layers differ, the community routinely stacks the two — our own Project IGI 2 guide documents a forum-tested pairing. This page is part of our DxWnd alternatives comparison series.
What dgVoodoo2 Does
dgVoodoo2, written by dege and distributed free from his site, is a graphics-API wrapper. You copy its DLLs into a game’s folder, and when the game calls the old APIs, dgVoodoo2 answers instead: per its own documentation it wraps Glide (including the later Napalm variant), DirectDraw versions 1–7, and early Direct3D up to version 9, translating everything to Direct3D 11 or 12 underneath. Configuration lives in the dgVoodoo control panel and a per-game dgVoodoo.conf.
This translation layer is the definitive answer to a specific family of failures: games whose rendering itself is broken on modern hardware — Glide titles with no Glide hardware left to run on, DirectDraw games whose surfaces modern drivers handle badly, titles that need resolution forcing or MSAA injected at the API level to look right. dgVoodoo2 can also present its output in a window, which is where the confusion with DxWnd starts. But a window was never its headline act; it is a renderer first, and the emulation of period GPU behaviour — down to emulated hardware profiles — is a depth DxWnd does not attempt.
What DxWnd Does Instead
DxWnd does not translate graphics APIs. It hooks the game process at launch and intercepts the calls by which the game interacts with Windows: claiming the screen, setting display modes, reading the clock, handling the mouse and keyboard, opening files and registry keys, playing CD audio. From those hooks it builds the window — forced, sized, positioned, as our DirectX settings guide explains from the profile side — and applies the era’s behavioural emulation: 256-colour palettes, time stretching, locale, virtual CD and registry tricks. Its home territory overlaps dgVoodoo2’s in years but not in function: the same 1997 game can have a graphics problem, a window problem, both, or neither.
The cleanest mental model is a pipeline. The game speaks two languages: graphics calls, and Windows calls. dgVoodoo2 interprets the first language. DxWnd interprets the second. A game fails to run on a modern PC when either conversation breaks down.
Depth Where the Other Tool Is Shallow
It is worth spelling out how far dgVoodoo2’s specialisation goes, because “wrapper” undersells it. Its documentation describes emulating the behaviour of period graphics hardware — including named GPU profiles of the era — managing texture memory the way the period APIs expected, applying dithering and colour post-processing, and forcing resolutions the game never offered. A wrapped application can start windowed or fullscreen under the control panel’s say-so and switch with Alt+Enter mid-game. For a Glide racing game or a DirectDraw strategy title whose surfaces corrupt on a modern driver, this is not a workaround layered over the problem; it is a reimplementation of the environment the game was compiled against.
DxWnd’s corresponding depths are elsewhere, and dgVoodoo2 simply has no entries in those columns: it will not slow a game whose speed is welded to a period CPU, will not make a Japanese title decode its text under a Western Windows, will not conjure CD music from ripped audio files, and will not virtualise the registry keys a paranoid 1999 installer demands. There is also a workflow asymmetry. dgVoodoo2’s DLLs and dgVoodoo.conf live inside each game’s folder, so a forty-game library means forty installations to version and maintain; DxWnd keeps its whole library as profiles in one portable folder. Neither model is wrong — per-game isolation is exactly what a renderer wants, and central profiles are exactly what a behaviour manager wants.
Where They Overlap — and Collide
There are two honest complications. First, overlap: dgVoodoo2 can window its output, and DxWnd ships its own proxy DLLs (covered in our proxy mode guide), so either tool can appear to “do” the other’s trick for easy titles. Second, collision: both tools may want to supply the same file — two different ddraw.dll wrappers cannot both occupy a game’s folder and both load. Stacking them is a deliberate configuration, not an accident to stumble into: dgVoodoo2’s DLLs render the game, while DxWnd is set up to handle the window and behaviour without fighting over the same surface. Forum threads in the DxWnd project document working pairings for specific titles — follow a per-game recipe where one exists (the games hub collects ours) rather than improvising the combination blind.
| Question | dgVoodoo2 | DxWnd |
|---|---|---|
| Primary layer | Graphics API translation | Process/window behaviour + compatibility |
| APIs covered | Glide, DirectDraw 1–7, Direct3D ≤9 → D3D 11/12 | Hooks the game’s DirectX/DirectDraw usage in place; no translation |
| Install model | DLLs copied into each game’s folder | One portable folder; per-game profiles |
| Forced resolution / MSAA at API level | Yes — a strength | No |
| Palette, timing, locale, CD, registry fixes | No | Yes |
| Price | Free | Free and open-source |
Which Failure Do You Actually Have?
If the game launches and windows but renders garbage, crashes in its graphics code, or is a Glide title, suspect the graphics layer: dgVoodoo2 first. If the game renders fine fullscreen but you cannot get it into a window, or its problems are speed, colours-in-menus, mouse capture, missing CD music or language — suspect the behaviour layer: DxWnd first, starting from how to use DxWnd. If it does both — renders badly and refuses to window — you are in stacking territory, and per-game documentation beats experimentation.
One audience note, because it decides real purchases of time if not money: dgVoodoo2 rewards users comfortable working inside game folders — copying the right DLL variant (32-bit builds for the era’s games, regardless of your 64-bit Windows) and reading a technical readme. DxWnd rewards users comfortable working inside one big settings dialog. Both learning curves are honest work; neither tool is the “easy” one, they are easy about different things.
The Verdict
| Choose… | If… |
|---|---|
| dgVoodoo2 | Your game’s problem is rendering: Glide support, broken DirectDraw/Direct3D on modern drivers, or you want forced resolution and MSAA at the API level. |
| DxWnd | Your game’s problem is the window and the era’s behaviour around it — fullscreen-only launches, palette colours, game speed, locale, CD audio. Get it from the download page, and do not be surprised if the complete fix for a stubborn title is DxWnd with dgVoodoo2 underneath. |