Okay, Glidos, here's the bad news. TR1 doesn't use floating point coordinates. Remember, the Glide capability was a bolt on to an internal 3D software renderer. The 3D plot calls basically take the form: do_op(TrVertex *vertices) { if (glide_enabled) do_op_with_glide(vertices); else { original code …

Looked around a bit more, and I haven't found all the places it's doing it. The first lot I found was in the geometry clipping - rounding the newly-calculated screen edge intersection vertices to whole pixels. But I haven't found where it is in the main calculations yet. I'll keep looking at it.

Ah, gotcha. By clamping I assumed you to mean range-limiting, and I didn't really understand what that had to do with anything. But the Glide APIs accept fractional coordinates, I see, and the game is rounding the coordinates to whole pixels. (Can't see anywhere in my Glide 2.2 docs that requires …

Hi slube. Hopefully when I complete my patch, you'll be able to finish off the triggers very quickly. Each trigger condition will be no more complex than: level=2 x>=25 x<=30 y=52 z=10 I'm making good progress on my investigation of the TR1 binary. Although for the last few days I've gotten …

Okay, so maybe nearly 40% is done, but that's taken a long, long time. It appears to be tedious, boring intricate work, and error prone, looking at this thread. I wouldn't bet on it taking less than another couple of years. Whereas I reckon the tomb.exe binary can be hacked fairly rapidly, and that …

Hmm, so it's ground to a halt. 3 years and less than half done? When all that's left is giving the trigger points? It strikes me that you need to give up and start again. The method of setting up triggers (looking out for certain textures being drawn in certain positions) is far too difficult. I can …