Need for Speed: High Stakes (1999, Electronic Arts — sold as Road Challenge in some regions) closed out the classic NFS era with a career mode, car damage that actually cost you money, and every track from NFS III thrown in. Getting it to run in a window on Windows 10 or 11 has a well-documented trap, worked through in detail in DxWnd’s own forum: the game boots on its software renderer, and the software renderer draws nothing inside a DxWnd window. This guide follows the forum threads — the renderer switch that fixes the black screen, the ready-made profile, and one genuinely strange launch quirk the community found.
The black screen is a renderer problem
High Stakes lets you pick its 3D device, and on a fresh install it defaults to the software device, which renders the picture in a way DxWnd’s window cannot present — menus may appear, but the race itself is black. In the forum thread, the developer’s diagnosis separates two different black screens: a race that starts dark because of the Direct3D path, and a picture that is black from the start because the game is still on the software renderer. The cure for the second, common case is outside DxWnd: open the game’s own 3D Device setup and switch the renderer to Direct3D Device 1. Only then does DxWnd have a Direct3D game it can window properly. Software rendering and DxWnd window mode simply do not combine for this title — that is a documented limitation, not a settings mistake on your side.
A note on the 3D setup utility itself
The renderer switch happens in a small utility that is nearly as old as the game, and it has compatibility problems of its own on modern Windows — players meet installers and setup tools from 1999 that misread today’s system information. Ghotik tested DxWnd against the 3D setup program itself and reported both a path and a warning: he could get the setup running on a Windows 11 laptop with the help of a version-lie compatibility shim, but in that configuration the setup kept resetting the chosen renderer back to Glide. The practical reading of that experiment: if you change the renderer and the game seems not to remember it, you are probably fighting the setup utility, not DxWnd. Make the Direct3D selection, verify it stuck by reopening the setup once, and only then move on to the DxWnd profile below.
Setup
- Install High Stakes, then run its 3D setup once and select Direct3D Device 1 as the renderer.
- Add the game to DxWnd as described in how to use DxWnd, pointing the profile at the game executable.
- Fastest documented route: the community profile named “Need 4 Speed IV High Stakes.dxw”. Ready-made profiles like this one circulated with older DxWnd bundles’ exports folders; current builds no longer ship that folder, but the profile is still shared in the forum thread. Import it with File → Import (see how DxWnd profiles work), fix the install path it contains, and launch. A community member reported that, with slight adjustments to that profile, the game ran on Windows 7 through DxWnd alone — no dgVoodoo or other wrapper needed.
- Use a current DxWnd build. The v2.06.12 release work specifically improved how this game behaves in DxWnd’s colour-emulation fullscreen handling, so an old copy of DxWnd is working against you here; check the latest version if yours is old.
The strange one: it only windows on the second try
A separate thread documents an oddity worth knowing before you declare defeat: on some machines High Stakes ignores the window on a cold first launch, but if you first run another game through DxWnd and then start High Stakes, it windows correctly. Ghotik investigated and replied honestly that he could never reproduce the sequence reliably enough to fix it, so treat this as a community workaround, not a promise: if the game opens fullscreen, quit, launch any other DxWnd profile briefly, and try again. If instead you get a picture but it is dark or broken once the race starts, go back to the renderer — that is the black screen case above, and it is the renderer setting, not DxWnd, that needs changing.
Do you need dgVoodoo as well?
High Stakes is often discussed alongside dgVoodoo, the Glide/DirectX wrapper — and for the Glide renderer path, a wrapper is indeed the usual route. The forum result is worth stating precisely because it cuts the other way: once the game is on its Direct3D device, the community member who documented his working setup in the thread ran High Stakes through DxWnd with no dgVoodoo involved, using the adjusted community profile. So the order of operations this guide recommends is: Direct3D renderer first, community profile second, and only reach for a second wrapper if your machine still misbehaves — every extra layer is another variable when something goes wrong.
Known issues
High Stakes is picky about its hard-coded, 16-bit-era resolution list: DxWnd can stretch the window, but the game itself only offers the modes it shipped with. The 3D setup utility has its own compatibility shims and quirks on modern Windows, which is why the renderer choice sometimes needs to be re-made after reinstalling. And the launch quirk above remains officially unexplained — the thread is the living record if it ever gets solved. Finally, remember that the renderer choice lives in the game, not in DxWnd: reinstalling High Stakes, or moving its folder, can quietly reset the 3D device selection, which is why a setup that worked can appear to “break” after a reinstall until you redo the first step of the setup above.
Where to get High Stakes legally
High Stakes is not currently sold as a digital download — EA has not re-released it on the EA app, Steam or GOG (on GOG it exists only as a community wishlist entry). The legitimate copy is the original CD, still common second-hand. That is also why every guide, this one included, assumes a CD install.
More game-specific setups live on the DxWnd games hub. Sources: the DxWnd forum threads on High Stakes’ in-race black screen and its windowed-mode behaviour, and the v2.06.12 release-candidate notes, all on SourceForge.