I76 Gold/Nitro's Glide backend is only really made for 2MB tmem'd voodoo cards (Voodoo Graphics) and have texture panics on anything more, including Voodoo2s

leileilol wrote:

I76 Gold/Nitro's Glide backend is only really made for 2MB tmem'd voodoo cards (Voodoo Graphics) and have texture panics on anything more, including Voodoo2s

Okay thanks, I'll try 2mb setting in dgvoodoo.

The only wrapper that gives good results with that buggy mess in my experience is nGlide. I get glitches with dgVoodoo regardless of its settings.

UCyborg wrote on 2019-12-24, 13:07:

The only wrapper that gives good results with that buggy mess in my experience is nGlide. I get glitches with dgVoodoo regardless of its settings.

Oh, can I use nglide to just setup the file? I don't want to emulate glide.

I can't figure out what exactly you're trying to do from what you wrote. nGlide is like dgVoodoo, except that it comes with installer that puts Glide DLLs in system directories so every game sees it right away unless some other Glide DLL is present in the game folder. It can use either D3D9 or Vulkan for rendering and doesn't have all those Voodoo gimmicks exposed in its settings.

On somewhat related note, some time ago I played the game with one of newer test versions of dgVoodoo2 (2.7) for a bit and didn't experience glitches. Voodoo Graphics was selected on Glide tab, 2 MB of onboard RAM and 2048 KB selected for Memory size / TMU.

leileilol wrote on 2019-12-22, 02:55:

I76 Gold/Nitro's Glide backend is only really made for 2MB tmem'd voodoo cards (Voodoo Graphics) and have texture panics on anything more, including Voodoo2s

Run great with QEMU + OpenGlide. If it really fussed about FB and TMU memory, then OpenGlide reports as Voodoo1 8MB framebuffer and 16MB TMU memory. Perhaps wrap-around or overflow would magically make the game work again 😁.