The right opengl32? There should only be one and it should be in your system32 directory. You shouldn't be worried about tho since it's the OGL ICD that comes with your vid card drivers that you'll need to be using. Hopefully your not playing Blood in software OGL.

Games that use palette tricks are hopeless on ATI cards because they don't implement glColorTableEXT. You can try setting IgnorePaletteChanges to 1 in OpenGLid.INI, but that will lose the lighting effects. Its a real pain. Not sure what to do. I think I could implement it with pixel shaders, but from what I can see, if you use pixel shaders for anything, you have to use them for everything, so its a big big change.

Hi! I want to play Blood with 3DFX patch, Glidos 1.32, VDMsound 2.1.0, Geforce 6800GT, ForceWare 77.76 (NGO), AthlonXP 2800+ (OC 2,4GHz). I can start and play Blood but its real slow. When i look at a wall or the ground its smooth. Without Glidos it runs normal.

Hmmm! Should be fine on nVidia cards. Maybe I've screwed something up recently. I'll test it out on an old GF3ti500 when I get a chance.

Support for paletted textures has been removed in GeForce 6xxx series too. 😠

Damn! It is something I want to sort out at some stage, but its complicated.

What I think I need as a starting point is a pixel shader program that has exactly the same effect as not using a shader program. So it must perform all the functions of the stage it replaces.

At least, that's what I think I need. Only briefly looked at shaders.

I don't think that pixel shaders help there (but maybe I'm wrong).
I know, there are instruction(s) for texture lookup operations, but, what if bilinear interpolation is applied to the texture?
So that, there is a 256x1 texture containig the palette itself, and there is a texture in some kind of textureformat containing the palette index values in one of its components. And then, using the pixels of the "paletted" texture as direct positions in the "palette" texture would work, I think. But, if bilinear filtering is on, then the interpolation would be applied on the palette indices themself, not on the lookup values from the "palette" texture. There are problems with the order of operations.
(Or, you should read all of the 4 pixels "rounding" a given position, then make a lookup for all of them, and then do the interpolation "by hand". Could it be done in a pixel shader at an acceptable speed? It seems very complitated to me.)

Just keep spamming Monolith's e-mail inbox, forcing them to release the source code for Blood already, then they probably might listen... 😏

P.S: So far, I've only tried chaning priorities, and tried other programs like "dgVoodoo" or whatever it's called and others, looks like they won't run properly as well.

dgVoodoo works fine for me, I find Blood to be playable with it. But this topic isn't about that...

dgVoodoo works fine for me, I find Blood to be playable with it. But this topic isn't about that...

Yeah dgVoodoo uses DirectX. I assume that provides some palette support.

You still get all the textures in strips with dgVoodoo though, don't you? In Glidos, I collect all the timy strips that the buid engine produces and coalesce them into much bigger polygons so that I can obtain proper bilinear interpolation. Probably the most complicated part of Glidos, put in only for Blood.

Anonymous wrote:

I don't think that pixel shaders help there (but maybe I'm wrong).

You may well be right. It was a while ago I looked into this, and I think I can remember being worried about the interpolation thing. I remember thinking it was solvable, but might have been overoptimistic.

I noticed the cpu usage goes up to 99% when i look in the room. Directly befor a wall it is about 50-60% and ntdvm.exe uses the rest.

The CPU usage is because Glidos raises the thread priority of the game. Its all part of getting the game to at least try to run at correct speed, which is quite difficult to achieve under XP.

The business about being fine if you are looking at a wall or the floor all makes sense. The palette tricks are used to darken things in the distance, so if those aren't in view, there's no problem.

This is something I want to sort out, especially as all modern cards have dropped the palettised texture extension. What I might have a go at is recognising that a palette is being set to const + factor * old_palette. That way I could leave the palette unchanged, and have glide apply the factor and constant. That is what the game should be doing really. Some games don't simply because they were first written for software rendering.

So, is it faster without the palette tricks? If so, is it possible to disable these tricks in the glidos.ini, or are they used for something else, too?

Its faster and looks awful without the palette tricks. You can disable palette tricks by setting IgnorePaletteChanges to 1 in OpenGLid.ini, but I don't think you will like the results.

Thanks! Tried it, framerate is perfect but looks awful (black sprites and some textures), as you said before. I hope you can find a way to fix that problem.

Sorry, it'll take ages.... uh no, I've done it! 😁

For a card with no palette support, OpenGLide builds an OpenGL texture for each palette. That works hopelessly for Red Baron 3D (the game for which I introduced all this stuff) because it generates loads of different palettes, but Blood looks to build only a few, so I was a bit confused as to why it wasn't working. When I ran it through the debugger, I found that Blood uses Alpha/Palette textures; for those OpenGLide had the "texture per palette" thing disabled. I've enabled it and it all seems to run at an acceptable speed - here at least.

Here's a new version of Glide2x.dll to pop into your Glidos folder.

Wow, that did it! Now its fully playable, thanks!

Is it possible to change the refreshrate? 60Hz is too low for me, i can still see it flicker.