TSE -Datablocks?

#1 Uh I think it's the new mapto command that applies a custom shader material. This eliminates the need for older materialsmap file.

Resources will need to be ported / tested by the community. Tank pack is a content pack, for the most part it's already ported. Minus a little bug where you crash when mounting it (well it does that on my build hehe).
Minor stuff.

Edit: Here is a bumped map m1 screen from Tank pack in TSE EA.

The quality is horrible and the body is too dark but I am just experimenting.

#2 The material change has actualy already been made and is in HEAD. Basicly what they did is moved all the shader/material definitions to the client side rather than on the server. So right now, everything shader related is loaded when TSE is loaded(not when a mission is). There are some problems with this(like if you have hundreds of materials using 2+ textures each), but it's much better than the datablock approach(sending all materials over the network when a client joins a mission).

#3 So, they haven't removing datablocks all together?

Edit: English; My English teachers would be ashamed!

#4 Datablocks are designed for networking, and it didn't make sense to network every single bit of information for materials (shaders specifically), so it is the materials system that no longer uses datablocks...for things that should be networked, datablocks are still in use.

#5 Ok, thanks Stephen, makes tons of sense now!

#6 I was a bit worried about the implications of removing he datablocks in TSE, but you have put my mind at rest.

Cheers, Mark.