New Turbo GL Problem

[Sitting Bull]

Hi,

I installed the new Turbo GL for my Celeron O/C 464MHz, but when I try to start the Quake 3 demo I get the following information:

Q3 1.11 win-x86 Nov 29 1999
----- FS_Startup -----
Current search path:
D:\Q3Ademo/baseq3

----------------------

Running in restricted demo mode.

----- FS_Startup -----
Current search path:
D:\Q3Ademo\demoq3\pak0.pk3 (1387 files)
D:\Q3Ademo/demoq3

----------------------
execing default.cfg
execing q3config.cfg
couldn't exec autoexec.cfg
...detecting CPU, found x86 (P5/Pentium2, MMX)

------- Input Initialization -------
Initializing DirectInput...
Couldn't set DI coop level
Falling back to Win32 mouse support...
Joystick is not active.
------------------------------------
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
--- Common Initialization Complete ---
Winsock Initialized
Opening IP socket: localhost:27960
Hostname: cs911273-a.cgmo1.ab.wave.home.com
IP: 24.64.231.101
Working directory: D:\Q3Ademo
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\WINDOWS\SYSTEM\opengl32.dll' ): failed
...shutting down QGL
...assuming '3dfxvgl' is a standalone driver
...initializing QGL
...WARNING: missing Glide installation, assuming no 3Dfx available
...shutting down QGL
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
GLW_StartOpenGL() - could not load OpenGL subsystem


So, gurus, have you seen this problem before and how did you fix it?

Thanx,
Sitting Bull

[Larry]

Looks like you have your quake set up to run using the 3Dfx MiniGL. The TurboGL is known to be incompatible with the voodoo family of cards. Although this is supposedly a driver issue, neither of the card manufacturers have actually taken responsibility, so I'm not sure when it will get fixed. If you have an SLI rig, and don't mind the crappy 16-bit color, then use your 3Dfx card for the quakin'. On the other hand, if you have a single v2, or - heaven forbid - a V1 in your system, you might as well rip that mofo out and unintsall the drivers. That'll get your G400 working (you might have to re-install your G400 and TGL drivers).
There are some people who have gotten both cards to work together by doing some swapping of files. If any of you know how to do this, please post it here and help Sitting Bull out!
Personally, the G400 is running great for all my games. The complaint about is Tribes, and I know that Tribes2 is coming, so I'll just wait....

Hope this helps!!!

Larry

[Sitting Bull]

Hi Larry,

Here is the strange thing; I've never even owned a 3Dfx Voodoo card and one has certainly never been in my system! I've had nothing but a G200 and G400!

In any event, I followed a piece of generic advice from another thread and renamed the Quake 3 Opengl32.dll to "old" and after restarting the game, shut it down and re-renamed it back to Opengl32.dll. For some reason that settled it down and it is working, for the time being anyway!

So here is what happened.

Using the new TurboGL driver under Win 98 SE, here is what I have now gotten
for fps on the Quake 3 demo with High settings;

System - ECS P6BX-A+ Motherboard, Celeron 300a O/C 464MHz (4.5x103), 128
Megs PC100 RAM, G400 (Vanilla OEM) 32 Meg Dual Head, IBM Ultrastar 9ES 4.5 Gig
U2W SCSI hard drive.

640x480 at all colour depths: 48 fps

800x600 at all colour depths: 47-48 fps

1024x768 16 bit: 45 fps
32 bit: 40 fps
default: 45 fps

1152x864 16 bit: 39 fps
32 bit: 32 fps
default: 39 fps

1280x1024 16 bit: 30 fps
32 bit: 24 fps
default: 30 fps

1600x1200 16 bit: 21 fps
32 bit: 16 fps
default: 21 fps

I saw no point in going to higher resolutions, as the game is hardly
playable at 1600x1200! Apparently 16 bit and Default colour are identical. This
is clearly a BIG step forward in game performance for the OpenGL crowd, and I
think everyone should give Matrox a big round of applause for coming to the
rescue of a very tiny segment of their customer base with these new drivers.

[Larry]

Nice to see that you got it working! If you never had a voodoo card in your system, I'm not sure how you got those error messages?!?! Nevertheless, even though I'm a proud owner of a PIII, I would have to agree that Matrox have done a great job in supporting those Cel/PII/K6 owners out there!

Larry

[Rob M.]

Q3A always tries to load up 3dfxvgl.dll if it can't find opengl32.dll, no matter what card you have.
(of course it only works if you've got a voodoo card)
no guesses as to why it couldn't find opengl32.dll on your system before though