Article View: alt.games.x-com
Article #259Re: XCOM Interceptor 3DFX Question
From: agame...
Date: Mon, 07 Sep 1998 00:00
Date: Mon, 07 Sep 1998 00:00
34 lines
1811 bytes
1811 bytes
John, I received a reply from Jef Reynders ( jef.re...@unicall.be ) to an earlier post I'd made on the same subject. Here's his reply: |> Hi, a few weeks ago, I had the same problem (same card too). You have to |> download the latest Monster 3D drivers from the Diamond-website and install |> them. After doing so, your card will show up. If you encounter any more |> problems, just post them here and I'll help you. Now, prior to his reply, I believe I'd been using the 3DFX drivers for the Voodoo chipset. In the Interceptor Setup Screen only options 1 and 2 were offered, and, as I mentioned in my original post, Interceptor wouldn't let me select option 2. I installed the Diamond drivers and, poof!, option 3 showed up, and it worked fine. However, no change on option 2. I suggest trying the different drivers. Juggle 3DFX's and Diamonds to see which works best. Usually, I prefer the Chipset makers drivers (for my STB Lightspeed 128 as well as the Monster3D) they seem to be a bit more stable than the card maker's. However, in this case, it looks like I'll have to go with the cardmaker's if I want to play Interceptor with 3D Acceleration. By the way, I'm using DirectX 6 as well. Good luck, Frank P.S. Please let me know if you ever get option 2 to work.
Technical Details
Message-ID:
<35f65737.62513127@news>Path:
mbox-mo1.pugleaf.net!unknown!not-for-mailReferences:
<35f51adf.47062642@news> <6t1g20$hb2$1@the-fly.zip.com.au>Show Full Headers
Complete Article Headers
From: agame...@home.com Subject: Re: XCOM Interceptor 3DFX Question Date: 1998/09/07 Message-ID: <35f65737.62513127@news> X-Deja-AN: 388834234 References: <35f51adf.47062642@news> <6t1g20$hb2$1@the-fly.zip.com.au> Organization: CORE MIME-Version: 1.0 Reply-To: agame...@home.com NNTP-Posting-Date: Mon, 07 Sep 1998 15:11:31 PDT Newsgroups: comp.sys.ibm.pc.games.strategic,alt.games.x-com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit