Spring RTS Engine

SM3 conceptually is a superior map format, in practice it is a superior map format, in spring its as useful as a brick simulation, its like dynamic water only it isnt fancy looking on a GF7900.

It needs to meet the reality of it's normal practice format. This format would greatly reduce map sizes and if properly implemented it should run more effeciently then SMT.

With shaders turned on I got a framerate of 4 fps on my geforce 5200. The same map gives sub optimal performance on a geforce 8800GTS (640MB version).

..

It was too much fun implementing bumpmapping, even though it didnt really have a good function in a strategy game where you never view the map up close.
I expected people would use around 3 layers for the average map, but in practice this was usually something like 7. It's probably best if I disable the bumpmapping completely, it speeds things up a lot.

Also there are still a few bugs with the SM3 mapformat which i added to the bugtracker :)

damn u

jc, there's also this bug with refractive water, dunno if you've seen it...

jc, when a con unit levels the ground for a building it causes terrain tears. The terrain clips at a distance and a few other things. please look a the pictures I posted of that test map.

The bumpmapping is nice but I would prefer a more functional sm3 first.

Would it be possible to disable the bump mapping in the .sm3 instead of removing it completely, maps with artificial surfaces like metal or even rock in the flat areas would benefit from bump mapping visually, like in these two shots.. Maps like this would in all likelyhood never need more than three layers, as is the case here.

Also allow the user to turn off bump mapping incase it makes SM3 unplayable for them, for example the above map and a user with an FX 5200...

OY!

Chopper says bump this thread or he'll fucking stab ya!

Now I've gotten sad