Project IGI 2: Covert Strike (2003, Innerloop Studios) sent David Jones back into the field for a second round of open-ended stealth missions, on a DirectX 8.1-era engine that modern Windows greets with suspicion — up to and including the classic error that the game “requires DirectX 8.1 or greater”, reported by players on systems with far newer DirectX installed. DxWnd’s forum has followed IGI 2 for years, and the developer even added a video option to current DxWnd releases specifically because of this game. This guide gathers what those threads actually establish — including the part where DxWnd alone was not the whole answer.
What the forum testing shows
The long-running “Project I.G.I. 1 & 2” thread is the core document. A community profile for the games was shared there, and the tester’s conclusion was nuanced: the combination that worked for him was DxWnd together with dgVoodoo2 — DxWnd providing the window and the hooking, dgVoodoo translating the old DirectX calls. With DxWnd alone, he reported the first mission ran, but with very low frame rates when looking across open ground, frame rate snapping back up in enclosed views. That is the honest starting point for IGI 2: you may end up running two tools, and the thread treats that as normal for this title rather than a failure of either one.
The option DxWnd added for this game: Video → Min
During the v2.06.14 development cycle in early 2026, ghotik added a “Video > Min” checkbox whose purpose is to tell a game the minimum resolution it may assume — and his release note names the reason directly: it “seems necessary for IGI 2 depending on the video card capabilities”. Modern GPUs report resolution lists that old engines mishandle; the minimum-resolution floor stops the game from reasoning about modes it cannot use. The option ships in current DxWnd releases (v2.06.16 is the latest version), and the video options around it are covered in DxWnd video settings. If IGI 2 mis-detects resolutions, refuses modes or behaves like your card is older than it is, this checkbox is the first lever the developer himself built for the situation.
The “requires DirectX 8.1” error, in context
The startup error deserves a paragraph of its own, because it sends players down the wrong path. IGI 2 was built when DirectX 8.1 was current, and its startup checks were written for that world: on a modern system the game can conclude that a suitable DirectX is missing even though a far newer one is installed — the check itself is what is obsolete. Players have reported this exact message on Windows 10 machines with DirectX 12 present, in Microsoft’s own support forums, with no modding tools involved. Two consequences follow. First, do not try to “fix” it by installing old DirectX runtimes over a modern system; the version is not the problem. Second, treat the error as the game’s age showing at the gate, separate from anything DxWnd does — the forum route (a known-good profile, the right video options, and dgVoodoo translating the old calls) addresses the underlying mismatch instead of arguing with the checker.
The topic is alive, incidentally: in March 2026 ghotik opened a dedicated IGI 2 thread in the forum, which is where the newest per-build findings for this game are accumulating. If the steps below do not match your machine’s behaviour, that thread is the next stop.
Setup
- Create the profile the standard way (how to use DxWnd), pointing it at the IGI 2 executable, and run DxWnd as administrator.
- Enable Video → Min in the profile’s video settings, per the developer’s note above.
- Launch and judge the frame rate in the first mission’s open areas, where the thread’s low-FPS report was measured — not in the menus.
- If frame rates stay poor, follow the thread’s documented route and add dgVoodoo2 to the chain (its DLLs in the game folder, DxWnd still providing the window). The settings guide explains how DxWnd’s own video options interact with wrapper DLLs like these.
- If a newer DxWnd build ever makes the game misbehave, ghotik’s older advice in the IGI threads is to try the profile’s video mode set to “Native” instead of the default “VGA” — a one-line tip from the developer that has rescued several version-to-version regressions.
What about the first IGI?
The same forum thread treats the original Project IGI (2000) alongside its sequel, and the shared-profile approach documented there was used for both games — the tester who reported the dgVoodoo combination was running the pair of them. So if you own both, this guide’s workflow is your starting point for the first game too. One distinction matters, though: the Video > Min option was added with IGI 2 named in the release note. Do not assume every IGI 2-specific lever maps one-to-one onto the original; the thread is the place where per-game differences are recorded.
Known issues
Performance is the standing caveat: multiple testers’ experience says DxWnd-only can be slow outdoors in this game, and the dgVoodoo pairing exists precisely because of that. One tester also reported a crash after the end cutscene of the “Defend Priboi” mission — which then did not recur when he replayed it; it is recorded here as a single, unreproduced report. Finally, the “requires DirectX 8.1” startup error belongs to the game’s own age checks rather than to DxWnd; players hit it with no tools involved at all, and it is part of why getting this title running at all is a small project.
Where to get IGI 2 legally
The game is sold today as I.G.I. 2: Covert Strike on GOG, DRM-free — the convenient way to own it without hunting down the 2003 discs. (That is an ordinary store link; this site may earn a commission on purchases in future, as explained in our disclaimer.)
More game-specific setups live on the DxWnd games hub. Sources: the DxWnd forum threads “Project I.G.I. 1 & 2” and the IGI 2 problem reports, plus the v2.06.14 release-candidate notes documenting the Video > Min option, on SourceForge.