16-bit index buffers

#1 I think maybe it is because some older cards don't support 32 bit index buffers. You could support it and just put in checks for card support, but why bother. The only good reason to do this is if you have more than 65536 vertices in a single vertex buffer. I might be wrong about this but I don't think there are many rendering tasks that require so many vertices save maybe a few terrain implimentations. And besides, if somebody needs 32 bit buffers they got the source code they can add it if they need it.

#2 Well, I don't really think it's a support issue, because only really old cards don't support 32-bit index buffers, however TSE (at least in it's current state) won't even run on cards that don't have at least shader model 1.1 on em' (correct me if I'm wrong). And by the way, you said "65536 vertices in a single vertex buffer", which is wrong... :) It has nothing to do with the vertex buffer, but you can't have more than 65536 indices in an index buffer... ;)

#3 Umm, no you can have as many indices as memory allows. The same for vertex buffers. Perhaps i should rephrase myself. By "65536 vertices in a single vertex buffer" It mean that you can't reference more than 65536 different vertices in an a index buffer. Remember 32 & 16 are the size of the indices in the index buffers.

#4 Whoa... sorry... You are totally right!! I feel so embarassed... I guess coding for 12 hours in a row degrades my logic... :)