G400 and GLquake

[foxm]

I have the problem that GLquake runs
very slow on my brand new PIII/600/128MB
under W95. In fact, it doesnt even display the frame rate after finishing "timedemo demo2". But from past experience it is like
10fps.

It also seems that whatever resolutions I enter, I get more or less the same visual picture and speed - even though it correctly displays the the resolution in the video options (I tried 640x480, 800x600 and 1024x768 under both 16 and 32 bit).
I also ran these from desktops with the same
corresponding resolutions.

At _one_ instance, the circumstances of which I cannot reproduce, I got 60fps under 800x600x16 - still far too low, this is what
I am used from my V2 on PII/333.

I use a G400/32/AGP (IRQ 11) and the only other card so far is a network card (IRQ 10).
I installed the original drivers and also
the 5.41 together with DirectX7a. I did also
a complete install from scratch.
I also installed GLquake 1.09 from
scratch, surely no opengl32.dll is in the game dir. Do I need install DirectX Media
as well ?

However, there is an opengl32.dll in w95/system, dated from 1996 - can this be right ? I used a network install, and there
is the remote possibility that this
downloaded something that is conflicting here. How can I find out the correct working
of openGL ?

Help would be highly appreciated, I am
sitting for two days on it to no avail...

[foxm]

PS:
forgot to mention some more data:

The MB is a brand new ATX BX2.

I surely had disabled the dual head output.

The DirectX Diagnostic tool says under
the Display tab:
AGP support: not available.
Can this be a hint of something ?

Thanxx !

[cjolley]

Hi foxm,
1, The first thing to do is use the Matrox Uninstaller from this site (or M's of course!) to uninstall the Matrox drivers.
Make sure you install the latest drivers without installing any earlier drivers. In other words: go straight from plain VGA to 5.41 or 5.50b.
2, The opengl in your system dir is prob. Microsoft's and it needs to stay.
3, Check your AGP aperture size in your bios & set it to 256.
4, put -fullsbar on the command line of glquake.
5, Put the opengl32.dll from the turbogl into your quake dir.
6, It will be dark in the game. I used idgamma to lighten things up. Some people just turn up the gamma in PD befor they start the game.

Thats a start.

chuck
PS Try reseating your G400 in the AGP slot.


[This message has been edited by cjolley (edited 10 February 2000).]

[This message has been edited by cjolley (edited 10 February 2000).]

[foxm]

Allright, thanks,
I did a new install (non-network but with CD), set AGP to 256, and it works
almost OK. Still I don't get more than 60fps with GLquake, rather independent
of resolution or 16/32. I guess 60fps
at 1024x768/32 is sort of OK, while
at lower res. it is not so great.
This perhaps shows that the G400 is, relatively speaking, good at higher resolutions but more or less sucks at lower ones (I mean the drivers here).

You wrote:
5, Put the opengl32.dll from the turbogl into your quake dir.

Hmm - the turbogl seems to contain just
an ICD (G400icd.dll), I didnt see an
opengl32.dll. Also, this supposedly works only for W98 (which I dont have), and for
Q2,3 not GL Q1. Or do I miss something here ?

One other little thing, for people who know what fastvid is (a little dos prog enabling certain framebuffer properties;
it was crucial for the old PII systems).
If I just dos-boot, then the vspeed utility shows me 50MB/s for both VGA and
LF buffers; if I use fastvid, then the
VGA goes up to 100MB/s, and the LFB to
200MB/s - good values !

However, if I boot into w95 with the G400
drivers, adding fastvid in autoexec gives
an error (same for running from prompt).
Running vspeed shows me indeed for the LFB
ca 200MB/s, which tells that the drivers
deal with the LFB right - but the VGA
still remains at 50MB/s.
Is this a flaw to be improved, or does it
matter at all ?

[foxm]

Allright, thanks,
I did a new install (non-network but with CD), set AGP to 256, and it works
almost OK. Still I don't get more than 60fps with GLquake, rather independent
of resolution or 16/32. I guess 60fps
at 1024x768/32 is sort of OK, while
at lower res. it is not so great.
This perhaps shows that the G400 is, relatively speaking, good at higher resolutions but more or less sucks at lower ones (I mean the drivers here).

You wrote:
5, Put the opengl32.dll from the turbogl into your quake dir.

Hmm - the turbogl seems to contain just
an ICD (G400icd.dll), I didnt see an
opengl32.dll. Also, this supposedly works only for W98 (which I dont have), and for
Q2,3 not GL Q1. Or do I miss something here ?

One other little thing, for people who know what fastvid is (a little dos prog enabling certain framebuffer properties;
it was crucial for the old PII systems).
If I just dos-boot, then the vspeed utility shows me 50MB/s for both VGA and
LF buffers; if I use fastvid, then the
VGA goes up to 100MB/s, and the LFB to
200MB/s - good values !

However, if I boot into w95 with the G400
drivers, adding fastvid in autoexec gives
an error (same for running from prompt).
Running vspeed shows me indeed for the LFB
ca 200MB/s, which tells that the drivers
deal with the LFB right - but the VGA
still remains at 50MB/s.
Is this a flaw to be improved, or does it
matter at all ?

[foxm]

Allright, thanks,
I did a new install (non-network but with CD), set AGP to 256, and it works
almost OK. Still I don't get more than 60fps with GLquake, rather independent
of resolution or 16/32. I guess 60fps
at 1024x768/32 is sort of OK, while
at lower res. it is not so great.
This perhaps shows that the G400 is, relatively speaking, good at higher resolutions but more or less sucks at lower ones (I mean the drivers here).

You wrote:
5, Put the opengl32.dll from the turbogl into your quake dir.

Hmm - the turbogl seems to contain just
an ICD (G400icd.dll), I didnt see an
opengl32.dll. Also, this supposedly works only for W98 (which I dont have), and for
Q2,3 not GL Q1. Or do I miss something here ?

One other little thing, for people who know what fastvid is (a little dos prog enabling certain framebuffer properties;
it was crucial for the old PII systems).
If I just dos-boot, then the vspeed utility shows me 50MB/s for both VGA and
LF buffers; if I use fastvid, then the
VGA goes up to 100MB/s, and the LFB to
200MB/s - good values !

However, if I boot into w95 with the G400
drivers, adding fastvid in autoexec gives
an error (same for running from prompt).
Running vspeed shows me indeed for the LFB
ca 200MB/s, which tells that the drivers
deal with the LFB right - but the VGA
still remains at 50MB/s.
Is this a flaw to be improved, or does it
matter at all ?

[foxm]

Allright, thanks,
I did a new install (non-network but with CD), set AGP to 256, and it works
almost OK. Still I don't get more than 60fps with GLquake, rather independent
of resolution or 16/32. I guess 60fps
at 1024x768/32 is sort of OK, while
at lower res. it is not so great.
This perhaps shows that the G400 is, relatively speaking, good at higher resolutions but more or less sucks at lower ones (I mean the drivers here).

You wrote:
5, Put the opengl32.dll from the turbogl into your quake dir.

Hmm - the turbogl seems to contain just
an ICD (G400icd.dll), I didnt see an
opengl32.dll. Also, this supposedly works only for W98 (which I dont have), and for
Q2,3 not GL Q1. Or do I miss something here ?

One other little thing, for people who know what fastvid is (a little dos prog enabling certain framebuffer properties;
it was crucial for the old PII systems).
If I just dos-boot, then the vspeed utility shows me 50MB/s for both VGA and
LF buffers; if I use fastvid, then the
VGA goes up to 100MB/s, and the LFB to
200MB/s - good values !

However, if I boot into w95 with the G400
drivers, adding fastvid in autoexec gives
an error (same for running from prompt).
Running vspeed shows me indeed for the LFB
ca 200MB/s, which tells that the drivers
deal with the LFB right - but the VGA
still remains at 50MB/s.
Is this a flaw to be improved, or does it
matter at all ?

[Shoyu]

Without the TGL Opengl32.dll, 5.50's ICD would give me colourful wall textures. Haven't tried the newly released 5.50 b10 though.

[HollyBerri]

Shoyu, see this thread for instructions on how to prevent the rainbow textures.

-----------------------
Holly

[cjolley]

Nice catch Holly!
I forgot about the textures.
chuck

[cjolley]

Oops, my bad.
I forgot that you had win95.
Find a copy of Win98 upgrade.
My 333 celeron o/c to 500 puts out 120 fps
using the tgl @ 800x600.
You may not even need the tgl with the new beta drivers.
chuck


------------------
ABit BF6, Celery 333@500, 128mb gh@cas2, 10gb IBM@7200, SB Live Value@3.0, noname CDRom@40x, Mitsumi CDRW@2x2x8, Acatel 1000 ADSL@1.5mb/sec, Linksys EtherFast NIC, Princeton EO75, USB mouse,Matrox G400 MAX!!!!

[Wombat]

Ummm, v-sync?

[Shoyu]

Thanks HollyBerri! The colorful textures were so irritating that I was forced to use TGL. But should I be getting higher fps with the ICD? It doesn't look like it - I'll do further benchmarking.

[Shoyu]

Whoops, v-sync.
My G400 Tweak settings are now all off except triple buffering.
My quake settings are as follows:
gl_finish "0"
gl_keeptjunctions "0"
gl_subdivide_size "2028"
gl_triplebuffer "1"
gl_picmip "0.8"
gl_ztrick "1"
gl_flashblend "1"
gl_polyblend "0"
gl_playermip "2"
gl_texturemode GL_LINEAR_MIPMAP_NEAREST
gl_ztrick "1"

r_shadows "0"
r_wateralpha "1"
r_mirroralpha "1"
r_dynamic "0"

Timedemo of rpn_machine:
ICD: 58.6
TGL: 65.4



------------------
Shoyu
Asus P2B, Intel Celeron 466MHz, 128MB PC-100 SDRAM, Matrox G400 MAX.
(DX7, Bios 1.5.22, PD5.50.010 w/TurboGL1.00.002)

[Shoyu]

Hmmm, so TGL still sits on top of the ICD for Quake1? Would be great to see some response :P