Sorry, but the closest I've come to playing Unreal in Glide is using a Voodoo 2 and a Voodoo 3. Can't remember what drivers I "exactly" used but I never noticed anything like you're describing.
Is your version of Unreal 2.26?
And have you tried changing settings for your V5? Like disabling AA etc to see if it makes any difference?
And, are there any other strange occurrences?

Edit: How about a screenshot? ;D

yeah a screenshot would be nice, I have a v5 setup and unreal runs OK

OK! Please can you tell me what keyboard command I need to enter, to make a screenshot? Thanks. Also, I am using the Unreal Anthology DVD-ROM version. I have tried switching off AA, but that does not fix this problem.

Can you record a video within Unreal? That would be even better than screenshots.

That bug you found is called HOM or "Hall of Mirrors" effect, and it's usually due to an error in the level design, because the map creator forgot to close the inner space with some entity, or a missing texture over a visible surface, or even a transparent texture that allows the player to see beyond the map limits.

If it's not a design error and it can't be seen with other drivers or 3D cards, then it could be the V5 that fails at rendering some texture, allowing the uncleared framebuffer to show the contents of the previous rendered frame. This can be fixed by forcing a frame buffer clear (can't remember if there's an option for this in Unreal, but in Quake engines you have to set r_clear to 1).

It could also be a too aggressive rendering optimization. I think that Z-culling, Guard-Band clipping and Hidden Surface Removal are the usual suspects for this kind of bug. See if disabling them in 3dfx tools fixes the glitch.

I found the screenshot key, it's F9. I took some pics. I also tried various settings, but they all failed to fix the problem. I tried:

AA = on, off
VIA Chipset = Performance, Compatibility, BIOS defaults
Refresh Optimization = Disabled, Enabled
OpenGL/GLide Vertical Sync = Disabled, Enabled

Notes: I am using a VIA KT133A mobo. I also flashed this V5 AGP card's BIOS from version 1.06 to 1.18.

If I move the mouse a tiny bit, the graphics go weird.

If I move the mouse a tiny bit more, the graphics are OK, but then they go weird again, if I move the mouse again.

batracio, thanks a lot for your detailed explanation. We posted at the same time, so initially I didn't see your reply. I tried:

r_clear 1 at the console, but Unreal reports this as being an "unrecognised command". I tried ticking and unticking these 2 options inside V-Control 1.82 Beta: Glide/OpenGL: OpenGL guardband clipping, and also enable OpenGL z-culling. Unfortunately, I can still see the "HOM" effect when I look upwards, towards the monitor in that beginning level area.

I'm not sure where to disable/enabled the Hidden surface removal option. I can't see this option inside V-Control.

Wow, that's weird. Can't offer much assistance but you can see the same bug in Doom and Bulld engine games when using the noclip cheat. I've never seen it in anything newer though.
I'd suggest it is a driver issue, perhaps one of the custom drivers from this page might help: http://www.3dfxzone.it/dir/3dfx/voodoo5/drive … oo45/windows9x/

They are win9x drivers but there are drivers for later OS's on that site if you look around.

I've noticed a similar problem in a game called 'Blockland'. This happens if you have your draw distance set too low, and you're inside an interior. In this case it's maybe a game design flaw.

One thing that stops me from using a custom driver is that I have read on Vogons that many people are using the same driver that I am using, that is the "plain vanilla" 1.04.00 reference driver.

Also, to compound this weirdness, the test rig I am using is a refresh W98SE install. I am using VIA's 4-in-1 driver, version 4.43. I know there are one or two fans of VIA on this website. Hehe, the "sarcasm mode" checkbox was "ticked" just then.

I'm also testing my Voodoo5 these days. Will try to take a look at it.

About the Hidden Surface Removal, I think it appeared later than 1.04 driver.

EDIT: Hidden Surface Removal is called "OpenGL HSR" in V. Control.

Hey GR, did you patch Unreal? It "might" fix the problem. Also, does changing texture detail change anything?
How does it run when not using Glide (No wait!! Don't throw that kettle of hot tar just yet AAHHH!!1 😜).

It's a classic HOM effect due to a mapping error. It can also be seen with the software renderer (run Unreal safe mode). I had already noticed the glitch when I played the game, but completely forgot it over the years.

Ah, thanks a lot for checking!

batracio wrote:

It's a classic HOM effect due to a mapping error. It can also be seen with the software renderer (run Unreal safe mode). I had already noticed the glitch when I played the game, but completely forgot it over the years.

And this was never fixed with any consequent patches for Unreal?

Tetrium wrote:

batracio wrote:

It's a classic HOM effect due to a mapping error. It can also be seen with the software renderer (run Unreal safe mode). I had already noticed the glitch when I played the game, but completely forgot it over the years.

And this was never fixed with any consequent patches for Unreal?

I think Unreal on the Unreal Anthology DVD-ROM version is patched.

Tetrium wrote:

And this was never fixed with any consequent patches for Unreal?

Apparently no. I have just installed 2.26f patch and the glitch is still there. Note that Epic would have needed to include an updated version of vortex2.unr map in every patch, and it's a 3.63 mb file, not a minor download 13 years ago. They may have thought it wasn't worth the bandwidth waste for such a small glitch.

retro games 100 wrote:

Tetrium wrote:

batracio wrote:

It's a classic HOM effect due to a mapping error. It can also be seen with the software renderer (run Unreal safe mode). I had already noticed the glitch when I played the game, but completely forgot it over the years.

And this was never fixed with any consequent patches for Unreal?

I think Unreal on the Unreal Anthology DVD-ROM version is patched.

Ah, I see. I thought you were using the cdrom version, like I do 😜

Still strange as to what is causing this though.

Installed this game over the weekend. Today I see your post so thought I'd give it a shoot.

I get the same deal, the image goes into a repeating loop that will move with the mouse movement for a short time. Also have more missing textures as I go on.

CD-ROM of original Unreal (no Return to Napali edition) patched to unofficial 2.27g.
Voodoo 5 5500 Bios 1.06. Last Evolution driver for windows 98SE.
Render mode (unknown, advanced options keeps crashing all the sudden)
Resolution:1024x768 no/AA
Latest drivers available for system.

Specs:
Intel Pentium III-S 1.4GHz
Soyo TISU mobo (i815ep B-Step)
2x 256MB Crucial CL2 PC133MHz SDRAM
Voodoo 5 5500 AGP Bios 1.06
Western Digital 160GB HDD @ATA-100
Corsair CX430 Watt PSU
Sony FDD
Pioneer 16x DVD-ROM @ATA-66
Diamond Monster MX300 + NEC XR385 Clone
D-Link DFE530TX