rec.autos.simulators

by **Jan Hoviu** » Tue, 27 Jul 1999 04:00:00

Hello,

Since I re-installed Glide v2.56 drivers (and got rid of the diamond
control-panel display that shipped with my Monster V2-12MB card) I suddenly
have freezes within GPL on a regular base. In fact I won't even try to host an
online race anymore because I'm almost sure I can expect a 'freeze' within the
first two laps on Spa. BTW: The freezes occur in both on and offline sessions
(FWIW).
What actually happens is that my display freezes but the game actually
continues (I can hear my car crash into the next corner!).

Before the graphics driver cleanup action I had the following situation:
I upgraded the installed Diamond driver with 3dfx's newest one (including
glide v2.56) because diamond itself still doesn't have this one themselves. I
did this via the control panel->system->devices->update driver tab (W98). This
all worked well except for one *** thing: In the display properties of my
system I now found TWO VooDoo setting tabs: One belonging to the Diamond
drivers and one belonging to the new native 3dfx driver!! I tried my glide
based games (MGPRS2 and GPL) without any problem however (one would think some
conflicts would occur but to my surprise it didn't).
Only thing I noticed was that my monitor switched (turned black for a moment)
when selecting the new 3dfx display properties tag.
Because I hate to think that I might have a conflict in my hardware
configuration I finally decided to get really rid of the Diamond version via
Control Panel->Add/Remove Programs. The Diamond Voodoo Driver was still listed
there, probably the part which still showed up in the Display Properties part.
I removed it and next to that also removed the 3dfx (2.56) driver to reinstall
the latter after rebooting. This all worked out well, I only have one Voodoo
properties tag (the native 3dfx one) left in my Display Properties window and
both games still do function but......I do have the freezes described above.
In MGPRS2 all works well.
Before this "cleanup" I now and than experienced this locks but not as regular
as now. In fact I can't really do any racing anymore (either on or offline)
because I'm sure I wont make it to the end of practise.

Anyone any clue out here?

Regards,

Jan.

PS: Sorry for the long post but I want to be as complete as possible.

J.H.Hovius.vcf
< 1K Download

by **Jan Hoviu** » Tue, 27 Jul 1999 04:00:00

> The freezing problem is due to overheating of the card. I still use the
> monster drivers because 1) I like the overclocking slidebar in the advanced
> properties section and 2) the 2.56 drivers had a rendering flaw in
> Podracer. The problem can be eliminated by using the 2.53 version .dll
> file. You can find a copy here "http://216.13.117.36/~schubi/index.htm" in
> the tools section(it's in german, but you'll see it). Just put the .dll
> file in your GPL directory and that should do it. If you overclock the
> monster then get a fan for it, otherwise you will still have lockups if you
> set it over 93MHz or at least I did anyway.

> Vintook

Hello Vintook,

Is the native 3dfx driver put at a higher default clock frequency? I always
was running at 90MHz using the diamond driver! The 3dfx config tab doesn't let
me specify the clock frequency. If the default frequency indeed is set at e.g.
95MHz I can imagine it is an overheating problem. Anybody out here got more
information on what clockfrequency the 3dfx driver puts your V2 by default?

BTW: I don't want to revert to the "old" 2.53 version, simply because GPL
certainly looks (and sometimes I have the feeling it also performs) better
using the 2.56 driver.

Jan.

J.H.Hovius.vcf
< 1K Download

by **Rand** » Tue, 27 Jul 1999 04:00:00

The 3dfx drivers set the voodoo 2's clock speed to 90MHz.

On Mon, 26 Jul 1999 16:14:46 +0200, Jan Hovius

>This is a multi-part message in MIME format.
>--------------63C86FD26D9375BB46450A20
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit

>> The freezing problem is due to overheating of the card. I still use the
>> monster drivers because 1) I like the overclocking slidebar in the advanced
>> properties section and 2) the 2.56 drivers had a rendering flaw in
>> Podracer. The problem can be eliminated by using the 2.53 version .dll
>> file. You can find a copy here "http://216.13.117.36/~schubi/index.htm" in
>> the tools section(it's in german, but you'll see it). Just put the .dll
>> file in your GPL directory and that should do it. If you overclock the
>> monster then get a fan for it, otherwise you will still have lockups if you
>> set it over 93MHz or at least I did anyway.

>> Vintook

>Hello Vintook,

>Is the native 3dfx driver put at a higher default clock frequency? I always
>was running at 90MHz using the diamond driver! The 3dfx config tab doesn't let
>me specify the clock frequency. If the default frequency indeed is set at e.g.
>95MHz I can imagine it is an overheating problem. Anybody out here got more
>information on what clockfrequency the 3dfx driver puts your V2 by default?

>BTW: I don't want to revert to the "old" 2.53 version, simply because GPL
>certainly looks (and sometimes I have the feeling it also performs) better
>using the 2.56 driver.

>Jan.

>--------------63C86FD26D9375BB46450A20
>Content-Type: text/x-vcard; charset=us-ascii;
> name="J.H.Hovius.vcf"
>Content-Transfer-Encoding: 7bit
>Content-Description: Card for Jan Hovius
>Content-Disposition: attachment;
> filename="J.H.Hovius.vcf"

>begin:vcard
>n:Hovius;Jan
>tel;fax:X-31-53-4892799
>tel;work:X-31-53-4892641
>x-mozilla-html:TRUE
>url:http://www.ice.el.utwente.nl/~janh
>org:University of Twente;MESA Research Institute
>adr:;;P.O.Box 217;Enschede;;7500 AE;The Netherlands
>version:2.1

>title:B.Sc.E.E.
>x-mozilla-cpt:;-25376
>fn:Jan Hovius
>end:vcard

>--------------63C86FD26D9375BB46450A20--

To email me remove the "u"s

by **Jan Hoviu** » Wed, 28 Jul 1999 04:00:00

> The 3dfx drivers set the voodoo 2's clock speed to 90MHz.

Where did you obtain this bit of information from?

This morning I decided to reinstall the original Diamond V2 driver on my system so
I got back the Diamond V2 config Tab underneath Display Properties. I immediately
noticed that the clockspeed was set at 95MHz (Advaced submenu - slider at the
bottom of the window) instead of the default 90MHz. It looks like the native 3dfx
driver had put the clockspeed at this speed which could be the explanation that
GPL freezes.

So once again: Are you sure the 3dfx driver operates at 90MHz?

Jan.

by **Alan Layto** » Wed, 28 Jul 1999 04:00:00

>Hello,

Yeah i Was having problems with 2.56 drivers only when i tried to close GPL
My screen would lock up & control alt del wouldn't even save me.
Uninstall 2.56 & go back to the drivers on your Diamond driver CD
It seems some of us just can't run 2.56 while others have no probs.
I have gone back to 2.53 & no more lockups.
Good luck
BIG_AL_OF_OZ

by **Wolfgang Prei** » Wed, 28 Jul 1999 04:00:00

>> The 3dfx drivers set the voodoo 2's clock speed to 90MHz.

>Where did you obtain this bit of information from?

>This morning I decided to reinstall the original Diamond V2 driver on my system so
>I got back the Diamond V2 config Tab underneath Display Properties. I immediately
>noticed that the clockspeed was set at 95MHz (Advaced submenu - slider at the
>bottom of the window) instead of the default 90MHz. It looks like the native 3dfx
>driver had put the clockspeed at this speed which could be the explanation that
>GPL freezes.

>So once again: Are you sure the 3dfx driver operates at 90MHz?

I seem to remember that single Voodoo2s run at 95 MHz, whereas two
SLI'd Voodoo2s are set to 90 MHz by default.

--
Wolfgang Preiss \ E-mail copies of replies to this posting are welcome.

by **Jan Hoviu** » Wed, 28 Jul 1999 04:00:00

I'm pretty sure now the 3dfx driver will operate the card on a higher
frequency. After installing the diamond version (2.54) and the 3dfx (2.56)
on top of that all my freezes have disappeared (operating on 90MHz of
course, setting it via the diamond voodoo properties window).

I think this is important news, could solve a lot of display hangs on other
systems.

Jan.

> >> The 3dfx drivers set the voodoo 2's clock speed to 90MHz.

> >Where did you obtain this bit of information from?

> >This morning I decided to reinstall the original Diamond V2 driver on my
system so
> >I got back the Diamond V2 config Tab underneath Display Properties. I
immediately
> >noticed that the clockspeed was set at 95MHz (Advaced submenu - slider at
the
> >bottom of the window) instead of the default 90MHz. It looks like the
native 3dfx
> >driver had put the clockspeed at this speed which could be the
explanation that
> >GPL freezes.

> >So once again: Are you sure the 3dfx driver operates at 90MHz?

> I seem to remember that single Voodoo2s run at 95 MHz, whereas two
> SLI'd Voodoo2s are set to 90 MHz by default.

> --
> Wolfgang Preiss \ E-mail copies of replies to this posting are welcome.

cancellation

warned.

by **Rand** » Wed, 28 Jul 1999 04:00:00

Sorry for throwing info out there without references, and your post
makes me wonder. I installed the 3dfx drivers after completly
removing all diamond drivers from my C:\ drive and removing all
references in the registry. I then I installed a third party
overclocking utility and it showed both of my voodoo II's at 90MHz.
So now I am thinking that either I had some left over value in the
registry that set them at 90Mhz or you had a left over value that set
the card for 95Mhz or the utility I used set the cards at 90MHz. To
complicate matters more it seems that when ever I had install the
diamond drivers it would set the speed at 92Mhz not 90MHz or 95MHz.
This again could have been left over registry values. The one fact
that makes me still think the 3dfx drivers default to 90MHz is that
prior installing them was the only time I had made an effort to clean
my system of diamond drivers, files, registry entries, etc. and every
video chip OC'ing utility I have tried starts out with the speed I had
last used.

Sorry to cloud the issue more for you.

Randy

On Tue, 27 Jul 1999 13:59:05 +0200, Jan Hovius

>Where did you obtain this bit of information from?

>This morning I decided to reinstall the original Diamond V2 driver on my system so
>I got back the Diamond V2 config Tab underneath Display Properties. I immediately
>noticed that the clockspeed was set at 95MHz (Advaced submenu - slider at the
>bottom of the window) instead of the default 90MHz. It looks like the native 3dfx
>driver had put the clockspeed at this speed which could be the explanation that
>GPL freezes.

>So once again: Are you sure the 3dfx driver operates at 90MHz?

>Jan.

To email me remove the "u"s

rec.autos.simulators

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)

GPL: Sudden display freeze - game continues however (long post)