Preacher

Frogmaster: at last someone who has the exactly same problem with UT OpenGL as I have. Instead of making yourself a cup of coffee while UT starts up, try installing DoomLegacy (you need one of the original Dooms for this) and run it. If you get a segment sharing violation, the new Detonators won´t run with UT OpenGL either

nt

The two letters actually differ a little. Boys, I think I need glasses

Like I said in a previous posting, that´s not an "I", that´s an "L". The correct command is "setup -Lgntforce" (of course without the " ) It´s a little bit unfortunate that there´s no difference between a small L which looks like "l" and a big "I"

Where can I download Direct X 7.0a for W2k? Starfleet Command pops up a message saying it needs this version...

euankirkhope, I already knew that but it won´t stop Starfleet Command from popping up an error message saying it needs DX7a

Nope, W2k comes with DX7 (not DX7a). Why I know this? Because I´ve checked with "dxdiag". So anyone who states something different has an already patched up system or was just misinformed.

FrogMaster, try setting the Buffer Flipping Mode of your graphics-card to Page Flipping, if that won´t work, try Block Transfer

Xiven, did you actually try the new gegistry entry with UT? For me, it still crashes back to the desktop on launching. My opinion is that no registry tweak in the world can fix a messed up nvoglnt.dll. I´ll stick with my modified Det 5.22 Take DoomLegacy for example. Runs perfectly with older versions of the nvoglnt.dll, but with the one from the original Det 5.22 I get a segment violation.

Frogmaster I posted these settings a while ago, here they are again: open the Unrealtournament.ini file, go to the OpenGl section and insert the following lines, deleting whatever is in that section. Don´t forget to make a backup of Unrealtournament.ini before changing it in any way! [OpenGLDrv.OpenGLRenderDevice] Translucency=True VolumetricLighting=True ShinySurfaces=True Coronas=True HighDetailActors=True DetailTextures=True DescFlags=9 Use32BitTextures=True UsePrecache=True UseMipmapping=True UseTrilinear=True UseMultitexture=True UseTripleBuffering=True Use32BitTextures=True UsePageFlipping=True UsePalettes=True UseFullscreen=True UseGammaCorrection=True Use3dfx=False These settings are optimized for my system, maybe you need to change a thing or two. Mathesar, I´m running UT in just 1024x768 32 bpp with everything set to maximum quality. "If it slows down graphics, activate it!"

ledzeppel, it all depends on the viewers POV. Several months ago, 3dfx had planned to make their Glide API available for other graphics hardware manufacturers, so it´s going to become the best API for you, too. What I´m looking for is a Glide emulator I can use to play 3dfx only games with my GeForce.

ledzeppel, what I meant by using the word "Pro´s" was that with a little tweaking the OpenGL settings in the Unrealtournament.inf file can be altered to a way that there´s no more black missile trails in the game. If you get 60 + FPS in UT using D3D, that´s absolutely perfect. Noone (not even I ) can see any difference in going from 60 fps to ´bout 70 or maybe even 80 (assumed OpenGL would still be faster). But there is a SIGNIFICANT difference going from about 15 fps (D3D) to over 40 by using OpenGL, which is the case with my system (OC´d Celeron 300A @ 450, GeForce DDR, 256 MB 100 MHZ SD-RAM). I agree the purpose is to have fun with a game, but 10 minutes into some trial and error to fix some graphics bugs isn´t wasted time. Yeah, Glide is still the best API. From what I´ve read on several news sites OpenGL is too hard to code for and D3D doesn´t come with the functions graphics developer want for their games. That makes Glide superior. And anyone who makes a great API and hardware for it would be stupid to share with others. That´s why 3DFX sued Creative for their glide wrapper called "Unified" Oh, btw, do you know how to install Unified using W2k?

You heard right, there is such an utility. You can get it from your W2k CD. Just look for "Apcompat.exe". If it works, well, that´s another story coming soon here live on NT Compatible!

That´s not an "I", it´s got to be a "L" correct syntax is "setup -Lgntforce" had to experiment with this, too

Switching to D3D to enjoy ... can´t think of anything right now. On my system OpenGL is at least 15 fps faster than D3D. And concerning those black textures where there should normally be a rocket trail or grenade: D3D is for beginners who don´t want to tweak their settings. Better leave OpenGL for he pro´s... Seriously, there are differences in the system specifications of each users machine. On some OpenGL is better, for others D3D works best. But the best API is still Glide, until OpenML is fit for the market

Better wasting time to get OpenGL working than wasting FPSs

Argh, this is just too f*cking great...

Better wasting time to get OpenGL working than wasting FPSs Dammit, got disconnected while transmitting this posting

OK folks, here is what you´ve got to do to get UT running in OpenGL mode using Detonator 5.22: First, download Detonator 5.14 (see www.reactorcritical.com for these drivers) Second, install Detonator 5.22 (ok ok, you already did that ) Third, don´t reboot your machine yet, as this would be a waste of time. Fourth, decompress the Det. 5.14 to somewhere on your harddrive. Fifth, go to the directory containing the 5.14´s and copy these TWO files: "NVOGLNT.DLL" and "NV4_DISP.DLL" Sixth, paste these two files into your "WINNT\SYSTEM32" subdirectory, overwriting any existing files there. Seventh, reboot your machine and enjoy UT with OpenGL again. Oh, btw, I don´t know if there are any problems arising due to merging parts of 5.14 with 5.22. Please post here if you encounter difficulties Geez, found out the hard way that nv4_disp.dll isn´t backwards compatible with nvoglnt.dll. Had some BSOD´s. Using W2k, I thought these were a myth...

I have a theory on the Detonator 5.22 OpenGL issue. If the file responsible for correct OpenGL functions within Det 5.22 is broken, why not replace it with a working one? The name of that file is actually "NVOGLNT.DLL" ... Gotta check this out

Nope, 5.22 don´t work Just went back to good ol´ 5.14...

I have not yet tried the new drivers, but if they are as crappy as 5.16 and 5.17 UT won´t run with OpenGL. I´ll test 5.22 soon

Not the speed of RAM is of importance, the amount is... In fact I had the same problem with UT. Using my Voodoo 2, the game run fine with "just" 128 MB RAM. Then I purchased a GeForce just to encounter some heavy swapping to my harddrive. Someone explained to me that 3DFX products require less RAM than NVidia products. However, after I upgraded to 256 MB RAM all the swapping was gone. Oh, btw, if you manage to get it to work with the latest NVidia betas (5.17) use OpenGL with UT. It is quite faster than D3D. I only can get UT to work with OpenGL by going back to Detonator 5.14.

Since Win9x is a 32 bit OS (well, Microsoft told us it is...) too, you shouldn´t be able to run DOS games with this as well Just kidding For instance, Abuse and Doom both run quite well with W2k

After the last time I tried hibernation, my system was about 50% slower than it should be. Rebooting fixed this, but what can one use the hibernate mode for when the system becomes that slow. Any suggestions? ------------------ Celeron 300A @ 450 256 MB SD-RAM 40 GB HD SB-Live! Value 3Com 905 TX AVM Fritz! Classic GeForce 256 DDR (Annihilator Pro, Det. 5.16) Adaptec 2940 SCSI-2 Pioneer DVD-303 SCSI