Posted May 28, 2010
Edit (18/7/2010): Before starting, many people have reported instabilities when using dgVoodoo with I-War. The GOG version uses Zeckensack's Glide Wrapper by default, and mhe has provided detailed information on configuring it. (<-- that's a link. Why do we have underlining instead of italics, GOG??) If you are having issues with the defaults, be sure to look there as well as here.
I've just tested that dgVoodoo still seems to work fine as an alternative Glide wrapper for the 3Dfx graphics with GOG's version of the game, as detailed in the FAQ on the Atari forum (but I'll reproduce what I said there, here :)
Disclaimer: YMMV -- this has worked for myself and others, but undoubtedly there are combinations of video card and drivers which will not cooperate with dgVoodoo. If the settings below do not work for you, and you manage to find alternative settings which are successful, PLEASE detail your changes and your video card in this thread so that others with similar systems can benefit from your knowledge.
If you try this, make sure you back up your original glide2x.dll file from the GOG install before clobbering it with dgVoodoo's version. Also back up the version in the Defiance directory while you are at it -- you will need a separate copy of dgVoodoo in there if you wish to use this wrapper for the expansion as well.
Note also that this was written for the original CD release. I may edit it later.
I did notice I mentioned the 800x600 shortcut. You would need to create your own using the -b -16 -800x600 command-line arguments to IWar.exe (see command-line arguments), if GOG's version is running at 640x480 (which I'm pretty sure it is).
If running IWar.exe directly is a problem (it may well be), and I'm right about iwar_start.exe using 640x480, then you can still increase the resolution by configuring dgVoodoo to run at 1280x960 (that being the equivalent increase from 640x480 that 1600x1200 is for 800x600).
dgVoodoo Glide wrapper.
Both I-War and Defiance appear to work perfectly (pre-rendered in-game movies included) with v1.50 of the dgVoodoo wrapper (n.b. v1.4 had a subtle bug which causes problems with I-War in some missions).
To use this wrapper with I-War, extract/copy the following files from the dgVoodoo archive into the root game directory (whereever you installed the game to; e.g. C:\games\I-War )
* glide2x.dll
* glide2x.ovl
* dgVoodoo.vxd
* dgVoodooSetup.exe
Only these four files are needed.
Edit (10/6/2010): (To use dgVoodoo with the Defiance expansion pack, you will need to copy these files into the Defiance sub-directory, but you should wait until you have the wrapper configured and working before doing this, because configuring dgVoodoo modifies its DLL file, and you want to be copying the newly-modified and working version from your I-War directory.)
To configure the wrapper, run dgVoodooSetup.exe (the new copy in the I-War directory!), select the "Glide" tab, and under "LFB Access" select the "Closer to real hardware" checkbox. This will prevent some confusing 'ghosting' problems that can occur with the HUD in the game's full-screen (TAB) mode.
Edit (30/5/2010): Stormwatcher reports that on a Radeon HD4850-based system, enabling "Closer to real hardware" had the inverse effect, and that leaving that option disabled was necessary. I would still suggest that you try enabling the option to begin with, but do then try disabling it if you find that you encounter visual problems.
Edit (29/5/2010): With my current Radeon video card, I also needed to set the Renderer API to "Direct3D9" (under the "Global" tab) due to various visual glitches. If the default Direct3D7 doesn't work well for you, try changing this setting.
You may in addition wish to enable dgVoodoo's "windowed mode" option. This enables the entire game to run in a window, which can be invaluable if you have CTD (crash to desktop) issues with the game, as your desktop resolution and colour depth will not be affected by a CTD. To enable windowed mode, go to the "Global" tab in dgVoodooSetup, and select the "Windowed mode" checkbox.
Edit (30/5/2010): When configuring the "Full screen" screen mode in the dgVoodoo "Global" settings tab, you may also need to select "32-bit" under "Screen bit depth". Try it both ways if you have problems. If using Windowed mode, I believe dgVoodoo uses the bit-depth of your desktop (which is almost certainly 32-bit on any modern PC).
Now run the game! You can choose both the 640x480 and 800x600 Glide/3Dfx video modes, or for the best possible display quality, try setting the Resolution (under the Glide tab in dgVoodooSetup) to 1600x1200 and then using the 800x600 shortcut to run the game (if doing this in Windowed mode, you will of course also need to set a desktop resolution of at least 1600x1200!). Some aspects of the game such as the menus and the in-game HUD will still render at an effective 800x600, but as the consequent scaling is by a factor of exactly two, there are no resulting artifacts. On-screen 3D objects will benefit from the higher resolution, however! Having said that, the scaling can cause the pre-rendered video performance to suffer quite noticeably, so you may still prefer to stick to 800x600.
The game appears to run perfectly with the above settings, so I do not recommend further modifications to the default configuration. In particular, do NOT force triple buffering (under Glide - Miscellaneous) or you will likely suffer problems with the in-game movies.
The information given here is based on testing performed under Win98SE with a GeForce4 Ti4200 and nVidia's 56.64 drivers.
I've just tested that dgVoodoo still seems to work fine as an alternative Glide wrapper for the 3Dfx graphics with GOG's version of the game, as detailed in the FAQ on the Atari forum (but I'll reproduce what I said there, here :)
Disclaimer: YMMV -- this has worked for myself and others, but undoubtedly there are combinations of video card and drivers which will not cooperate with dgVoodoo. If the settings below do not work for you, and you manage to find alternative settings which are successful, PLEASE detail your changes and your video card in this thread so that others with similar systems can benefit from your knowledge.
If you try this, make sure you back up your original glide2x.dll file from the GOG install before clobbering it with dgVoodoo's version. Also back up the version in the Defiance directory while you are at it -- you will need a separate copy of dgVoodoo in there if you wish to use this wrapper for the expansion as well.
Note also that this was written for the original CD release. I may edit it later.
I did notice I mentioned the 800x600 shortcut. You would need to create your own using the -b -16 -800x600 command-line arguments to IWar.exe (see command-line arguments), if GOG's version is running at 640x480 (which I'm pretty sure it is).
If running IWar.exe directly is a problem (it may well be), and I'm right about iwar_start.exe using 640x480, then you can still increase the resolution by configuring dgVoodoo to run at 1280x960 (that being the equivalent increase from 640x480 that 1600x1200 is for 800x600).
dgVoodoo Glide wrapper.
Both I-War and Defiance appear to work perfectly (pre-rendered in-game movies included) with v1.50 of the dgVoodoo wrapper (n.b. v1.4 had a subtle bug which causes problems with I-War in some missions).
To use this wrapper with I-War, extract/copy the following files from the dgVoodoo archive into the root game directory (whereever you installed the game to; e.g. C:\games\I-War )
* glide2x.dll
* glide2x.ovl
* dgVoodoo.vxd
* dgVoodooSetup.exe
Only these four files are needed.
Edit (10/6/2010): (To use dgVoodoo with the Defiance expansion pack, you will need to copy these files into the Defiance sub-directory, but you should wait until you have the wrapper configured and working before doing this, because configuring dgVoodoo modifies its DLL file, and you want to be copying the newly-modified and working version from your I-War directory.)
To configure the wrapper, run dgVoodooSetup.exe (the new copy in the I-War directory!), select the "Glide" tab, and under "LFB Access" select the "Closer to real hardware" checkbox. This will prevent some confusing 'ghosting' problems that can occur with the HUD in the game's full-screen (TAB) mode.
Edit (30/5/2010): Stormwatcher reports that on a Radeon HD4850-based system, enabling "Closer to real hardware" had the inverse effect, and that leaving that option disabled was necessary. I would still suggest that you try enabling the option to begin with, but do then try disabling it if you find that you encounter visual problems.
Edit (29/5/2010): With my current Radeon video card, I also needed to set the Renderer API to "Direct3D9" (under the "Global" tab) due to various visual glitches. If the default Direct3D7 doesn't work well for you, try changing this setting.
You may in addition wish to enable dgVoodoo's "windowed mode" option. This enables the entire game to run in a window, which can be invaluable if you have CTD (crash to desktop) issues with the game, as your desktop resolution and colour depth will not be affected by a CTD. To enable windowed mode, go to the "Global" tab in dgVoodooSetup, and select the "Windowed mode" checkbox.
Edit (30/5/2010): When configuring the "Full screen" screen mode in the dgVoodoo "Global" settings tab, you may also need to select "32-bit" under "Screen bit depth". Try it both ways if you have problems. If using Windowed mode, I believe dgVoodoo uses the bit-depth of your desktop (which is almost certainly 32-bit on any modern PC).
Now run the game! You can choose both the 640x480 and 800x600 Glide/3Dfx video modes, or for the best possible display quality, try setting the Resolution (under the Glide tab in dgVoodooSetup) to 1600x1200 and then using the 800x600 shortcut to run the game (if doing this in Windowed mode, you will of course also need to set a desktop resolution of at least 1600x1200!). Some aspects of the game such as the menus and the in-game HUD will still render at an effective 800x600, but as the consequent scaling is by a factor of exactly two, there are no resulting artifacts. On-screen 3D objects will benefit from the higher resolution, however! Having said that, the scaling can cause the pre-rendered video performance to suffer quite noticeably, so you may still prefer to stick to 800x600.
The game appears to run perfectly with the above settings, so I do not recommend further modifications to the default configuration. In particular, do NOT force triple buffering (under Glide - Miscellaneous) or you will likely suffer problems with the in-game movies.
The information given here is based on testing performed under Win98SE with a GeForce4 Ti4200 and nVidia's 56.64 drivers.
Post edited March 08, 2013 by Shadowcat