Neato. Collision seems to be solid. That's pretty cool.
LegoPepper found a way to reduce the datablock count on maps like these:
As far as I can tell, this method puts the .dts collision shapes into the environment section of the file manifest(the one used for skyboxes and such). Then the TSStatic objects you use for collision don't need a datablock anymore. They just need the client to have downloaded their .dts shape.
That should reduce the datablock count of this map by ~1000.
Also, because you're using transparency, you should split any nontransparent objects such as the pipes off as a separate object. I think that would help with the pipes clipping through the track.
:) Thank you, Tendon! And proxy thanks to LegoPepper. If that script works, I'm gonna go on a map-making marathon... I ported Slopes but it had 3k datablocks.
I realize my mistake with the object separation. The track, though transparent, isn't a TSStatic object - just a transparent material. It's contained in the same object as the opaque pipes. I don't want to make the track TSStatic because I like how the transparency looks as it is, and I had a feeling it wouldn't look how I want it to if it were TSS. Anyway, I'll separate the track, and hopefully things will appear properly. If not, I'll just have to make the track TSS too. Thanks again!
Oh, also, regarding the collision - I find that once I've mapped all the collision, scaling the collision pieces (in Blender) to 0.99 so that there are little gaps between the pieces seems to help avoid vehicles getting stuck, bumped, launched, etc.
Show Posts
