Im starting this thread because im so frustrated and that because After a while since I started DX , reading many articles And books about DX , ppl are directing me to ABC answers Or most the time to ABC how to spell and English grammar :-) Ok I respect all kind of opinions and all kind point of views I almost have my own engine done which has many features But I still need to know many things actually I end up in a huge mess I know I might ask the same Question that was there somewhere and was answered already But I don’t think that’s enough I need to see more opinions more answers more point of views you cant say this can be done In this way and that’s it we are programmers and we all know things can be done in many many ways. Who he will share his piece of information will be for sure appreciated And get all the gratitude So now let me start my second reason of starting this thread Well Im not asking from repliers to answer all what im going to mention here Pick any point you want and discuss it, or just don’t :-) The subject is about best DX rendering performance 1- Textures: what’s the best way to deal with textures> loading, managing, rendering 2- Vertex, index buffers: as reducing the amount of drawprimitive calls And as how to deal with view frustum when you build many primitives in single Vertex buffer (landscape, trees, plants ... etc) and also billboarding these primitive 3- Meshes: calling drawsubset lots of time(many meshes in the scene) will knock The performance down so what’s the best way to solve that? 4- Collision detection: ive done something crazy checking if two objects intersect I first started with bounding box intersect checking then if its true I take both Transformed Vertex buffer chunks and compare them in separate thread well my PC died but im sure This can work somehow!! Do u have any better ideas?? more points to come , laters for now Have fun thinking, sharing and participating :-)

Don't mix your CD/physics stuff too much with the rendering stuff. Collision detection can be done with low resolution models or even mathematical primitives such as spheres, boxes (AABB/OOBB), cylinders.

- If you need to read from VB you might consider rethinking your algorithm so that you don't need to read from VB.

- Use a spatial partitioning tree such as octree/quadtree/portas for visibility culling.

- Pack stuff in one large texture :) to reduce texture changes. One large texture is better than 4 small ones if it is needed often.

- My artists don't complain about 1 material per mesh. A material can contain several textures though.

- Minimize vertex size. I use several vertex sizes depending on the need. For example, a terrain vertex can be fit in 8 bytes. On the other hand, too many vertex formats is inefficient too.

- Batching is good, nowadays you can also use geometry instancing for an object which appears in the scene many times.

4- I`m not an expert but... For outdoor you could use BSP or Octree to hold all your objects there and check collisions only in nodes as separate spaces. Also your objects should have bounding volumes (your boxes are ok i think) and after you chceck that this volumes intersects you should go to next level - each object should be also a tree (bsp is best i think) of bounding volumes containing some parts of this object (hand, leg etc.). You should test this trees nodes intersection. You can get some thing like O(nlogn) if you do this right. On gamasutra there are some exaples of this approach I think. Hope this helps a bit.

Quote:]Original post by Arex

- Batch meshes


Theoretically, how do you do that?
lets say i have 10 Sam missiles,10 enemy jets which each launches a guided missile toward you , that what you are facing at certain stage at the current level you are at so after passing those you will face another kind(amount) of enemies
so in sum there are lots of objects waiting to be used against you.
What do you do to deal with such case?
Is there a better way than calling drawprimitives or drawsubsets for each object?

Quote:Original post by kovacsp
-use texture atlases (this is connected to reducing the number of drawsubset calls)

sorry,i didnt get that :-o
can you explain that please :-)

Quote:Original post by Demus79
a- Minimize vertex size. I use several vertex sizes depending on the need. For example, a terrain vertex can be fit in 8 bytes. On the other hand, too many vertex formats is inefficient too.

b- Batching is good, nowadays you can also use geometry instancing for an object which appears in the scene many times.

a- how to control vertex size?
is it at design mode or with code??
i remember i got a model from the net and it was 16bit of size
when i rendered it, it came out so ugly so i fixed that by reducing the vertex
count amount in the mesh loading class...it worked for me but i don’t think its the right way to do it

b-again can you please explain what is the best way of batching in more some details please??