Great! That seems to have fixed the game crashing issues. 😀

Using the logging function, I was able to confirm my suspicions that this game doesn't use any depth buffering features of the graphics card whatsoever. Excellent.
Now, to look at how the palette functions.....

Thank you so much for psVoodoo and the help to get it to work with TAW.

Hey, well you did the hard bit, working out what the hell was going on.

Great news. Very pleased to hear it's working.

If you have some anaglyph glasses, then you might be able to see it in proper 3D - although the game's not using depth buffering may mean that wont work.

Is the newest psvoodoo available as standalone download?

@Dominus,
Check out the second post in this thread.

@Paul,
I tried the 3D option out of curiosity, but I don't get the 3D effect.

For me, the real benefit of psVoodoo would be as a base for a game specific wrapper. In the case of TAW, we've known for a while that the palette is split up into functional areas, at least for the textures as they are stored on disk. What I didn't know for sure until today was that this system is maintained for the output to glide as well.
So, we know that the sea, and only the sea, uses the 16 palette positions 112-127. We can intercept these in psVoodoo and temporarily change them to red to prove this theory.

The general idea is that since we can identify which polygons make up the sea, we can replace the repeating sea tiles with some sort of shader. This is probably complete madness though. 😀

bored wrote:

@Paul,
I tried the 3D option out of curiosity, but I don't get the 3D effect.

What, no double image when viewed without glasses, or you just don't see 3D when you use the glasses, and there's still a double image?

For me, the real benefit of psVoodoo would be as a base for a game specific wrapper. In the case of TAW, we've known for a while that the palette is split up into functional areas, at least for the textures as they are stored on disk. What I didn't know for sure until today was that this system is maintained for the output to glide as well.
So, we know that the sea, and only the sea, uses the 16 palette positions 112-127. We can intercept these in psVoodoo and temporarily change them to red to prove this theory.

The general idea is that since we can identify which polygons make up the sea, we can replace the repeating sea tiles with some sort of shader. This is probably complete madness though. 😀

Seems reasonable. Although not in psVoodoo as yet, there's a fair amount of game specific features in Glidos, particularly for TR1.

Regarding 3D, when I selected anaglyph mode, there was no double image in the 3D world although there was some change to the text on the HUD overlay.
..however, that was a few days ago. Now the program crashes with a log entry along the lines of 'unable to draw primitive' in anaglyph mode. Zalman mode (whatever that is) has no effect.
I'll investigate further....

It seems TR1 is still played by a lot of people around here. There are only a few of us that still play TAW....and even fewer that can be bothered to mod it.

...and the 3D behaviour has changed again, probably because I've changed some settings in the config program. Now in zalman mode, I can see two images side by side. Anaglyph mode always gives a hard crash when trying to render this:
DrawPrimitiveUP(D3DPT_TRIANGLELIST, 2, quad, sizeof(AnaglyphVertex))

I've logged some values, but haven't looked into what they all mean...

1psVoodoo v0.12
2Warning: grGlideInit called
3Warning: grSstQueryHardware called
4Warning: grSstSelect called
5Warning: grTexMinAddress called
6Warning: grTexMaxAddress called
7Warning: grSstWinOpen called
8Shader Version: FFFF0300
9Number of texture stages: 8
10Number of simultaneous texture: 8
11Warning: TEXOP_PREMODULATE not supported
12quad[0].x 0.000000
13quad[0].y 0.000000
14quad[0].z 0.500000
15quad[0].rhw 1.000000
16quad[0].u1 0.000312
17quad[0].v1 0.000833
18quad[0].u2 0.500313
19quad[0].v2 0.000833
20quad[1].x 800.000000
21quad[1].y 0.000000
22quad[1].z 0.500000
23quad[1].u1 0.500313
24quad[1].v1 0.000833
25quad[1].u2 1.000313
26quad[1].v2 0.000833
27quad[2].x 800.000000
28quad[2].y 600.000000
29quad[2].z 0.500000
30quad[2].u1 0.500313
31quad[2].v1 1.000833
32quad[2].u2 1.000313
33quad[2].v2 1.000833
34quad[5].x 0.000000
35quad[5].y 600.000000
36quad[5].z 0.500000
37quad[5].u1 0.000312
38quad[5].v1 1.000833
39quad[5].u2 0.500313
40quad[5].v2 1.000833
41i (null)
42sizeof(AnaglyphVertex) 32
43Warning: DrawPrimitive failed