I've always wanted someone to try this. With a voodoo card, this should give the best results, but I've never managed to try it myself.

Hitting ESC in game is the the only thing that will cause a logical frame buffer read. I expect there is a problem there. It does sound like a bug. I'll take a look, but I can't promise anything.

Glidos wrote:

I've always wanted someone to try this. With a voodoo card, this should give the best results, but I've never managed to try it myself.

Hitting ESC in game is the the only thing that will cause a logical frame buffer read. I expect there is a problem there. It does sound like a bug. I'll take a look, but I can't promise anything.

Paul, you do no testing with actual Voodoo card? Shame on you! Go out and buy a used Voodoo5!
This goes for Fabio too!

(and testing of Glidos/evoodoo would be made simpler if testing on Win98 at first instead of 2000/xp - no need to worry about ACT patches, etc. etc.

Originally posted by Schadenfreude Paul, you do no testing with actual Voodoo card? Shame on you! Go out and buy a used Voodoo5!
This goes for Fabio too!...

Yes! After all, Schadenfreude just volunteered to pay for them all!

*heh**heh**heh*

I have an old voodoo I, but I've lost the knack of making it work.
I think it was the year I started learning javascript; that knowlede overwrote the "how to make a voodoo I card work" part of my memory. 😀

Here's a new Glide2x.ovl to try out. Drop it into your Glidos folder, and be sure to start TR from the Glidos button.

Cool, it works!

Now I can access the TR in-game menus without hanging Glidos. The spinning logo reappears everytime I return to the game, but I suppose this is the normal behaviour.

Thank you very much.

batracio wrote:

Cool, it works!

Now I can access the TR in-game menus without hanging Glidos. The spinning logo reappears everytime I return to the game, but I suppose this is the normal behaviour.

Thank you very much.

Great! That's not quite fully working though. You will notice that the background to the menu is black, rather than a darkened copy of the last game frame. This is because I have disabled logical frame buffer reads. There must have been a bug in that call. I'll look into that.

batracio, are you up for a bit more testing? I think I know what was causing the memory fault.

Hi Paul,

have you discovered the bug? Tell me what to do and I'll have a go.

Great! Thanks! Try going back to the original version of Glide2x.ovl (check you get the crashes back). And then try this new version of Glidos.exe

Hi,

unfortunately, the new version didn't solve the problem. Hitting menu keys crashes again Glidos.exe with the invalid page fault.

But look at what I've discovered: running Voodoo Rush version of Tomb.exe directly, with Voodoo2-specific environment variables setup (SET SST_TMUMEM_SIZE=2, and so on) also crashes the game at the same point, and Tomb.exe exists with the message "ERROR: couldn't lock 3dfx frame buffer". However, Voodoo Graphics version of Tomb.exe runs perfectly, without any crashes (but at 640x480 fixed resolution). Both versions using latest 3dfx's Glide2x.ovl for Voodoo2.

After this testing, I added a new entry in Glidos.ini for Voodoo Graphics patch ("Name: Tomb Raider 3Dfx", "Executable: C:\Tombraid\Tomb3Dfx.exe" and "ExeSizes: 1140735"). Launched Glidos, and guess what? No crashes, as in MS-DOS mode, but the whole screen is rendered in weird colors, the effect is something like a wrong gamma selection, but adjusting gamma controls did nothing. I wish I could have taken some screenshots to show you, I tried several ways but none worked (Hyper Snap DX - useless hotkeys; Winglide - won't run TR in a window).

Anyway, it seems that the issue may affect Voodoo Rush Patch, and not Glidos itself. Has all this stuff any meaning for you?

That's very useful information. I was pretty sure it was a failure to lock the LFB. The first update I gave you, avoided locking the LFB. Then I noticed that I wasn't setting up everything I should whem making the call, hence the second update.

What I should do is detect the call failing. I didn't bother because it seemed unlikely that it would unless I called it wrongly, but you have confirmed it does fail.

This experiment with Tomb3dfx via Glidos sounds strange. It might be that Glidos isn't actually being used in this case. I think that version drives your card directly. But then I don't know why you'd get strange colors. You could try removing the VESASupport line from the Glidos.ini file.

It also sounds like a problem you might see running a Voodoo Rush game on a non-Voodoo Rush card. I'm shocked that it even works. I find it hard to blame GliDOS, more proof is needed.

Besides, isn't it RECOMMENDED to use the Voodoo Graphics version of TR with Glidos anyhow?