> >>Having become frustrated with very short, graphic "hiccups" in GPL, I decided
> >>to re-install Win98 from scratch. Here's my questions:
> >>Win98 starts out with Direct X 5 installed. My Diamond VooDoo II's always ask
> >>for Direct X 5 drivers. Shoud I install the Direct X 5 drivers first & then
> >>upgrade to Direct X 6 drivers?
> >>Also, Diamond's read.me states that one should install Direct X 6 itself AFTER
> >>installing the Diamond drivers. Is this considered to be the proper sequence?
> >>PII 450 128 MB RAM
> >>SB Live ( Liveware 1.0 )
> >>Win98 ( ugh )
> >What is ur problem exactly?
> With the above setup & VooDoo II's in SLI, running at 800 X 600, I get
> very nice graphics. About 20 fps on the grid at Monza. As soon as I
> hit Curva Grande, I get 36 fps which continue throughout a race.
> However...
> At random times, I experience what I can best describe as a "hiccup".
> This glitch lasts less than a second but is *very* distracting. It's a
> though the CPU is being interrupted. It happens in all tracks as soon
> as I race with 17 - 19 AI. I have yet to experience it turning hot
> laps.
> I've just re-formatted my drive & re-installed Win98. I was just
> wondering if the sequence of installing VooDoo drivers & Direct X
> might make a difference.
> >Have u put the glide2x.dll (ver 2.53) in the gpl root dir?
> Yes. I also tried 3dfx reference drivers. Same deal. Swapped
> VooDoo II's with a friend who has V2 1000's ( old STB's ). Same
> deal. If I can't get this fixed, might drop back to Win95.
First of all: If you use Glide than the Direct X stuff has nothing to do with it
(anymore). since you experience this hickup in both scenarios (in Glide and DirectX
mode) I think the problem is not related to the graphics card (and/or drivers at
all).
Since I experience these hickups as well (in both MGPRS2 and in GPL (the latter at
a lower rate but nevertheless) and found out that it has probably to do with the
controller (i.c.w. your gameport) I think you're dealin' with the same problem.
This has nothing to do with your CPU-power (in fact the effect becomes more
noticeable with a more powerfull cpu) but more the way your gameport handles
request from your steering wheel. If it't the good old Analog Gameport your CPU
will be very busy "counting" pulses from your wheel (when you're cornering this
becomes noticeable - the number of pulses send to the gameport is directly related
with the angle of your wheel). While iot is counting these pulses it can't do any
calcultations for your sim (a.w. sending 30-36 fps to your display adapter): Voila
the hickup!
A possible solution might be to add an digital gameport (PDPI L4).
Regards,
Jan.