The Battle Between God And Satan

Getting Through The Battle Between God And Satan on Modern Systems

The game is older than most people realize, and running it cleanly on a current Windows installation is less straightforward than it should be. I've gone through this cycle three or four times across different machines, and the core issues always boil down to the same three things: DirectX version mismatch, elevation problems with the registry keys, and the way the installer writes paths that break if you put the game in Program Files. Start by locating a clean copy of the game files. The installer from the original disc or a standard rip works, but skip anything labeled "Repack" unless you trust the source. The repacks tend to strip or corrupt the DLLs that handle the audio fallback, and you'll end up chasing silent crashes later. Once you have the files, create a folder at the root of a drive — D:\BGS or similar. Do not use C:\Program Files. The installer will try to write values into HKLM on the first run, and even as Admin it will chug through elevation prompts every time you launch. Run setup.exe from inside that folder. The default path selection will auto-fill to Program Files, so change it before clicking next. During install, leave the DirectX runtime option checked even if you think you have it. The game bundles a legacy version, and skipping it is what causes the flickering texture bug on NVIDIA cards past driver 530.

After install, close the launcher if it opens automatically. Navigate to the game folder and find BGS.exe. Right-click, Properties, Compatibility tab. Set it to run as administrator and check the box for reducing color depth to 16-bit. This isn't decorative. The game's renderer doesn't handle the HDR negotiation that Windows 10 and 11 push by default, and leaving it on 32-bit color will cause the skybox to render completely black during the outdoor sequences. Save the settings and launch. You should see a brief window resize when the game initializes. That means it picked the correct mode. If you hit a crash on startup, the issue is almost always the audio subsystem. The game uses an old DirectSound layer that conflicts with Windows Audio Service on builds after 21H2. The workaround I use is renaming dsound.dll to dsound_.dll in the root folder. This forces the game into the software mixer fallback. Sound still works, latency is negligible for this type of title, and the crash disappears. I tested this on a Ryzen 5 5600X with 32GB and a RTX 3060, and the rename alone prevented three separate launch failures that I was hitting before I figured out the pattern. The save system is another area where people run into trouble. The game writes saves to AppData\Roaming\BattleGames\bgs_save. If you migrate to a new machine or reinstall Windows, copy that folder over before launching the game the first time on the new install. I lost about six hours of progress once because I assumed the cloud save notice in the menu meant actual cloud sync. It does not. It's a label on the menu screen, not a feature.

Resolution fixes are possible but finicky. The game's native max is 1024x768, and anything beyond that requires a wrapper. dgVoodoo2 is the most stable option I've found. Drop the DLLs into the game folder, point it at BGS.exe, and set the output resolution in the config window. It adds about 2-3 milliseconds of overhead per frame, which is noticeable on a 144Hz monitor but fine at 60. If you don't care about resolution and just want stability, 1024x768 fullscreen with the 16-bit color depth flag is the most reliable configuration for long sessions. One thing the community generally gets wrong is the difficulty scaling. There is no hidden difficulty slider. The enemy damage and health values are hardcoded per zone, and the only variable that shifts between playthroughs is the starting equipment loadout. If you're dying repeatedly in the second act, it's not a skill issue or a settings problem. Equip the shield artifact from the first boss chest before entering the third dungeon. It absorbs roughly 40 percent of incoming melee damage and changes the pacing enough that you stop wasting healing items on fights that should be trivial. Performance tips that actually move the needle are limited. Close browser tabs. The game polls a system resource counter on boot, and having Chrome or Edge open with hardware acceleration enabled will cause stutters during load screens. I cut my average load time from about 18 seconds to 11 seconds just by closing everything except the game. That's not a small difference when you're dying and reloading multiple times in a row.

If you run into the freeze-on-exit bug, where the process stays in Task Manager after you close the game, add a startup flag. Right-click BGS.exe, Properties, Compatibility, then click Change high DPI settings and check Override high DPI scaling behavior. Set it to Application. This stops Windows from applying its own DPI scaling on top of the game's renderer, which is what causes the hang during shutdown on high-DPI displays. The game is free to download from the official site or the developer's page. Install it, rename the DLL if audio is acting up, set the compatibility flags, and skip the cloud save assumption. That covers the majority of the problems I see people running into, and it should get you through without spending hours troubleshooting.