Yes, seems to me like you did the hard part already! Placing the rest of the HUD will be easy. When you'll be integrating peds, don't forget to proceed so that the cockpit "move" when you hit a ped. Good you guessed the tire dust type, it isn't described in C1 track files ("room for extension" instead).

Oh btw, how does your build handle the different texture detail levels? I think there are three: ddraw lomem, himem and 3dfx hires. I guess it only loads the 3dfx ones?
Also, any idea how you'll render those fake env map materials (used in windows)? Or texture-less materials (my Borgnine is all made out of that). For the latter, this entry on my blog talks about it: [url=http://www.toshiba-3.com/dotclear/index.php?post/Untextured-materials-with-custom-lighting]Linky[/url].

Shadetables... scratched my heads often wondering what these were supposed to be. I guess they are related to the global shading processing, not sure if this makes any sense at all... like it'd "control" the beheaviour (contrast vs. fog, specular vs. angles, etc) of the shadows on the buildings, and same with the cars. There's a good lot of these files but most seem to use DRRENDER.TAB, other shadetabs are ACIDFOG, BLEND%%, BLUEGIT, TRACKGIT, DEPTHCUE, IDENTITY, FOG.
The game also generates unnamed ones apparently. C2 beheaves the same. I already tried swapping the most obvious ones with one another but noticed no difference. Should have a serious go at it again.
Most of these TAB files look like gradient of values, which sounds logical IMO. The BLEND ones though are different, their entry at offset 13h is 3Dh while the "normal" TABs have 03h. They probably were used to create that translucid texture effect featured in the Splat Pack?!

I'm not sure the 3dfx patch brings the hires textures. They rather were already there, ready for action. The Splat Pack might have brought some though.

About the untextured materials/gradients: I didn't mean the .mat files themself started with 3Ch or 04h but I use these values as a reference to point the material slots into the .mat file. Each .mat file starts with:
[code]00 00 00 12 00 00 00 08 00 00 00 05 00 00 00 02 00 00 00[/code]
and then the first material slot starts, their type (first byte) being most of the time 3Ch. I guess it means textured material?! If you want original examples of the 04h material type, just look at REG/MATERIALS/SIMPMAT.MAT. These are all made out of 3 (following) colors to make a little gradient (used for the shrapnels or the simple models).
But you are right, I probably made a mistake with the amount of following color IDs. I presented it so that if it's set as 7d then there would be the defined color (in my blog 68h (color ID 104)) PLUS the 7 following IDs. Actually I think that the defined color is included in the 7d value.
For SILVER.MAT, the gradient isn't 3d but 5d and starting with color ID 250 (FAh). It's indeed not used ingame (or doesn't seem so) but we could use it, just like the materials from SIMPMAT.MAT. I guess Stainless thought about using these to spare some texture use/reduce processed texels but finaly gave up on this. I don't remember any use of these kind of materials but the SimpMats for the shrapnels (and I figured the gradient thing etc through them!).
And yes some materials have a huge gradient value, makes the game look like it's on acid when textures don't load correctly.

There's a very common [fake] env map material on every car and it's the window texture. It's moving like a reflection in comparison to the camera and/or source of light. It doesn't work as well as in C2, even if the car has proper smoothing groups. [Oh btw, the gradient material beheaves accordingly to what the smoothing groups say! Smoothing groups support is thus important!]
Env mapped materials aren't used very often either. The texture used for the fake env map in the car windows is set in each track text file. There's a global one I think and then you can change it when the car enters a SFX volume. That's why the windows "reflects" the sky when you are outside of the castle, but reflects the corridor ceiling when you are inside the castle (I mean in Armourgeddon for example). To allow this texture to be changed in tracks, the reflective material must be specified inside the car text file, the material doesn't need to be textured but must have an uvw map (I mean it [b]shouldn't lack[/b] an uvw map, the uvw map itself has no importance has the env map effect totaly ignores it (but seam lines!)).

So if you want to see how the gradient thing beheave in the original C1, just test my Borgnine (I used that type of material on other cars, but only for details). I don't remember using the env map for something else than windows. As for the Night Track, I guess I could zip up what I have so far and send it to you for testing. Would require some time though as really don't remember where I left this project and what the dependenties are. I remember I had a fuckton of noncars to plot (was about to use the noncar tools for that) and setup peds. Had a nasty and unknown crashing issue too.

I guess Jeff won't update this sticky anymore so I'll do.
For those who haven't noticed Jeff kept on updating his project on [url=http://blog.1amstudios.com/]his blog[/url]. Posted a video lately.

IMO globaly it looks great but the physics seem way off sadly, I mean in comparison to the original C1. I understand how hard it must be to get the feeling right, but I was under the impression it was better before?!
Also too much shrapnels, too big, too present. But that's obvious.

Can't wait to see the ped integration.

The point is not liking the physics or not, it's the fact that currently they are wrong. C1 physics aren't realistic but what I see is yet less realistic. It's very obvious.
Check the comments on the last video on YouTube, C2S pointed some examples.

Cut it already with your "you'll be able to change them" bullshit. Nobody will waste his time installing the XNA dev env, trying to understand how things work then try to get stuff done better than the author himself, just for physics. People are waiting for an openC1 that's like the real thing (as it's what Jeff is willing to sell) and works directly on modern systems. If things aren't correct, people won't finish the work themselve. What a stupid thought.
If you don't like or miss something in the final build, will you fix it yourself? haha...

About the community bit, this project isn't part of the community, it's a developer doing his thing. If there was no Carmageddon community anymore, Jeff would do it anyway.
The community is still moving, much slower than five or ten years ago but it's still moving. Who are you to judge? You do nothing at all.

Well I wasn't using existing SimpMats (in the likes of M01.MAT, M24.MAT, etc.) but they worked the same and they were included in the car's MAT file. Their gradient was greater.
So yes I indeed replaced these [i]gradient[/i] materials with env mapped materials (exactly the same output as I created textures depicting the very same gradient) so that glide users can see the effect too.
I still have the gradient versions of these cars though.
[url=http://rr2000.toshiba-3.com/R6/BORGNINE_C1_GRADIENT.RAR]Here's the Borgnine[/url] with the body, chrome and mirrors materials as textureless gradients.

Jeff's currently implementing the peds!
[url=http://www.opencarmageddon.com]Go check that out[/url]!

For those who didn't notice yet (like me), [url=http://www.opencarmageddon.com]demo soon[/url].

Intended to those subscribed to this topic:
[url=http://blog.1amstudios.com]OpenC1 v1.3 released today[/url]!

[url=http://blog.1amstudios.com/]v1.3.1 released[/url].