to sum up the step required to get GPL and my new V3 300 to cooperate I
would be grateful. I am abel to run the game just fine except most objects
are all colorful and pixely. thanks
edk
edk
If you download and use the patch that rrevved so kindly pointed you to, you
DO NOT need to start GPL with that bat file. Just start it normally after
patching it.
Kyle
> >I feel like a dolt having to ask again, but if someone would be so kind
as
> >to sum up the step required to get GPL and my new V3 300 to cooperate I
> >would be grateful. I am abel to run the game just fine except most
objects
> >are all colorful and pixely. thanks
> >edk
> Get this:
> http://www.grandprix2.com/gpl/patches/glide2x.zip
> Unzip the stuff into your gpl folder and execute GPL with
> this .bat file:
> rem --------------------
> SET FX_GLIDE_TMU_MEMSIZE=8
> GPL.EXE
> rem --------------------
In fact, when testing the approach of limiting texture memory, I found that
neither the control panel-imposed 2MB limit, nor the batch file-implemented
8MB limit, fixed all the texture problems.
Even with texture memory limited to 8MB, I found quirks in replay files if
the wrapper was not used. For example, if you have a Voodoo3 record a bit of
a full-AI field race at Zandy, without using the wrapper. Make sure all the
graphics options are selected and then take a look at the replay using
TV1/2. Do you see what appears to be clear visors over the drivers' faces?
With the wrapper I've seen no such abnormalities, and the memory limit
appears unnecessary. Also, the wrapper solves the problem of starting GPL
from Spy Boy or GPaL (shameless plug: www.RaceLive.com/GPaL :0 )
Jack Rambo
- I updated the patch to work with the Voodoo3 cards
(version 1.0.0.4) the *DAY* I got my Voodoo3 card
which was the *WEEK* of it's release which was nearly
a *MONTH* ago (4/9/99)
- Prior to that the only thing that keep it from
working was a conflict with the 3Dfx splash screen
DLL, running GPL from a batch file that limits
the texture memory range in *NO* way fixes that
conflict. The real workaround at the time was to
delete the splash screen DLL (aren't we all tired
of downloading 2Mb+ of splash screen DLLs everytime
a new driver set come out anyways?).
- The most recent update (version 1.0.0.5) I posted three
days ago just fixes the mouse trails, nothing more,
nothing less.
- The patch is completely free, I don't see a dollar from
it, I don't want to see a dollar from it. However I also
don't expect to be disparaged by people who don't seem to
know what they are talking about in public newsgroups
for something I devote what little free time have to. If
you want to make snide comments towards someone I suggest
either Papyrus or 3Dfx, both of which seem to forever
blame the other for this particular problem.
George M. Smiley (author of the patch)
See you at the track,
"ZZ"
--
Official member IGPS (Internet Grand Prix Series)
And Sim Racing Mag Ferrari Challenge
----------------
Busch Motorsports
"Remember racecar is racecar spelled backward"
-----------------
Busch Carpentry
"Plans?"
Kyle
> > Thanks Kyle. Apparently the author of the .DLL finally got
> > around to fixing it within the last 48 hours. Prior to that, it
> > wouldn't work at all, without the .BAT..
> Finally?!? I think a few points are in order:
> - I updated the patch to work with the Voodoo3 cards
> (version 1.0.0.4) the *DAY* I got my Voodoo3 card
> which was the *WEEK* of it's release which was nearly
> a *MONTH* ago (4/9/99)
> - Prior to that the only thing that keep it from
> working was a conflict with the 3Dfx splash screen
> DLL, running GPL from a batch file that limits
> the texture memory range in *NO* way fixes that
> conflict. The real workaround at the time was to
> delete the splash screen DLL (aren't we all tired
> of downloading 2Mb+ of splash screen DLLs everytime
> a new driver set come out anyways?).
> - The most recent update (version 1.0.0.5) I posted three
> days ago just fixes the mouse trails, nothing more,
> nothing less.
> - The patch is completely free, I don't see a dollar from
> it, I don't want to see a dollar from it. However I also
> don't expect to be disparaged by people who don't seem to
> know what they are talking about in public newsgroups
> for something I devote what little free time have to. If
> you want to make snide comments towards someone I suggest
> either Papyrus or 3Dfx, both of which seem to forever
> blame the other for this particular problem.
> George M. Smiley (author of the patch)
> Well just to add to the confusion, I've been using the GPL Voodoo Graphics
> Glide2x Wrapper (version 1.0.0.4 dated 4/12/99) for about a week now with a
> Voodoo3 3000, without a limit on texture memory, and have had no problems.
> In fact, when testing the approach of limiting texture memory, I found that
> neither the control panel-imposed 2MB limit, nor the batch file-implemented
> 8MB limit, fixed all the texture problems.
> Even with texture memory limited to 8MB, I found quirks in replay files if
> the wrapper was not used. For example, if you have a Voodoo3 record a bit of
> a full-AI field race at Zandy, without using the wrapper. Make sure all the
> graphics options are selected and then take a look at the replay using
> TV1/2. Do you see what appears to be clear visors over the drivers' faces?
> With the wrapper I've seen no such abnormalities, and the memory limit
> appears unnecessary. Also, the wrapper solves the problem of starting GPL
> from Spy Boy or GPaL (shameless plug: www.RaceLive.com/GPaL :0 )
> Jack Rambo
Mike
Any help would be appreciated.
Win98
AMD-k6-2 350mz