It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
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.
Post edited March 08, 2013 by Shadowcat
For those still having troubles with the graphics, another alternative might be nGlide: http://www.zeus-software.com/downloads/nglide
I noticed that the installer (for v0.92) wants to do some kind of global installation rather than requiring any file(s) to be copied to the game directory, and I didn't really want to do that. However I also noticed that I could open the installation .exe file with 7-zip, extract the glide2x.dll file, and drop it into my I-War directory, so I gave that a whirl.
The results were only partially successful on my machine -- the game runs, but the graphics have lots of errors -- so I won't be spending any more time on this one, but all Glide wrappers are different, and some may work better than others on different systems or video cards, so I'll leave this here in case it works better for other people (or Zeus improve it in the meantime such that it works better than it does for me now).
Another tip. I noticed that the colours when using the dgVoodoo wrapper were very blocky, especially the nebulas.
To fix this set the colour depth to 32bit in the global section of the dgVoodoo setup program.
Performance doesn't seem to be affected much and it makes the game look much much better. Running the 3D in high-res 32bit colour makes the ships look pretty good considering the age of the game.
I have used dgVoodoo with IWar Deluxe before, and that Atari guide has a huge mistake:
Quote:"Next 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. "
Turning "Closer to real hardware" on COMPLETELY broke the graphics for me, actually creating the whole ghosting issue. At least on my Radeon HD4850, you have to turn that option OFF for the game to run correctly.
EDIT:
Whoa, I tested the GOG version with dgVoodoo, holy cow, it's AWESOME. Best possible way to play it. I'm still trying to nail the best resolution, but the game is technically perfect.
Thanks for the hint, I never thought the GOG version could be used with dgVoodoo.
Post edited May 29, 2010 by Stormwatcher
Thanks for that info, Stormwatcher. I'll take issue with it being "a huge mistake", as it was absolutely what was required on the system I tested it on at the time (GeForce 4), and it's working for my current machine as well (Radeon 3600). Clearly it's something which can vary between systems, though, so I'll update the description above!
Post edited May 29, 2010 by Shadowcat
avatar
Shadowcat: Thanks for that info, Stormwatcher. I'll take issue with it being "a huge mistake", as it was absolutely what was required on the system I tested it on at the time (GeForce 4), and it's working for my current machine as well (Radeon 3600). Clearly it's something which can vary between systems, though, so I'll update the description above!

Oh, I didn't mean to offend, it's just when I tested it, the game practically blew up on my face, and then, as I had read that the particular option was important, it took me some time to nail it down as being the culprit.
I'd guess that the newer Radeons (4XXX onwards) are the ones that won't work with that option, because many things changed when they came, overall.
Sorry for anything :P And Thanks again :D
I get worse performance and gameplay problems (events happen too fast) with this, so it's not for everyone.
Also tried Zeckensack's Glide wrapper, but the one used by GOG is still the best.
dgVoodoo much improves the graphics and also removes the fullscreen cutscene ghosting problems for me :)
on the flip side it create some window (upper bar with close buttons) appearances during fullscreen videos and is not as stable on some missions (like Venturi) unlike the gog wraper
:(
I'm a tad slow. I tweaked around with settings for an hour without ever noticing a difference. Then I finally realized that Defiance has it's own subdirectory which will need a 2nd copy of dgVoodoo. Doh!
avatar
Letsparty: dgVoodoo much improves the graphics and also removes the fullscreen cutscene ghosting problems for me :)
on the flip side it create some window (upper bar with close buttons) appearances during fullscreen videos and is not as stable on some missions (like Venturi) unlike the gog wraper
:(

The window bar thing went away after I messes around with some settings. I'll post a screenshot later.
It globally works really well.
Beside the reported stability problems, there's still a little something that annoys me (a bit). When I turn on the small 3d close-up window in the pilot seat (you know, in the little sceen on the bottom right), all my other instruments disappear. Not the actual cockpit but the contact list, the autopilot icons, etc... Is anybody else having this? Any idea on how to fix it?
I tried to get dgVoodoo to work on my system, no luck so far.
I have a radeon HD4890, and I had to untick "closer to real hardware" to prevent ghosting.
Now, the game runs pretty normally (and is better looking that with GOG glidewrapper), but all "wireframe" HUD elements do not appear : I have no reticle, no Lagrange points, no ship trails...
I tried all of the tips mentionned here, without success. I also tried to activate/deactivate almost all settings in dgVoodoo, no success either. Am I the only one with this problem ?
I've stopped using dgVoodoo for now. It's works better than the original glide wrapper, in that it scales properly and the movies all work but it's just too unstable and I've had to repeat missions a few times because it crashes.
OK, back to the default wrapper then. Too bad, the game was looking great with dgVoodoo.
I have an ATI Radeon 4200 and it seems to run dgVoodoo just fine with the Render API as Direct3D9 with the screen depth on 32-bit under the Global settingstab and just leaving the stuff under the Glide tab as is. Just a word of advise is to not enable the starfield blur under the game's option screen cause it will slow your mission to a halt (again, default settings are fine).
I'm so happy to finally play this game without the error messages.
Edit: The resolution trick doesn't seem to work on Defiance.
Post edited June 10, 2010 by sfried