[quote name='AlanWu' timestamp='1354606053' post='5006992']
how to put the texture into one buffer?How to make the textures connect to the vertices?

That depends on what API you're using. Is this DirectX11? XNA? Something else?
In most cases, (assuming the vertices also have texture coordinates associated with them) you pass the texture and the texture coordinates to the pixel shader drawing the mesh.

And what kind of optimizations you think i still can do?

Optimizations could include:
View-frustum culling (don't even bother drawing something the camera can't see)
Storing geometry in a partitioning tree to cull entire branches that aren't visible (makes the culling process more efficient than checking per-mesh)
Instancing (if you have a lot of identical/similar meshes)
Batching by material/effect to reduce changes to the rendering pipeline
...the list goes on. There are a lot of articles and blogs about how different studios grabbed those last extra frames-per-second by some code trickery, but like I said before, pre-optimization is a trap you can fall into, making your task overly-complex without confirming you even NEED to based on your use cases.
[/quote]

ok,thank you!
I will try it.

[quote name='AlanWu' timestamp='1354606053' post='5006992']
how to put the texture into one buffer?How to make the textures connect to the vertices?

That depends on what API you're using. Is this DirectX11? XNA? Something else?
In most cases, (assuming the vertices also have texture coordinates associated with them) you pass the texture and the texture coordinates to the pixel shader drawing the mesh.

And what kind of optimizations you think i still can do?

Optimizations could include:
View-frustum culling (don't even bother drawing something the camera can't see)
Storing geometry in a partitioning tree to cull entire branches that aren't visible (makes the culling process more efficient than checking per-mesh)
Instancing (if you have a lot of identical/similar meshes)
Batching by material/effect to reduce changes to the rendering pipeline
...the list goes on. There are a lot of articles and blogs about how different studios grabbed those last extra frames-per-second by some code trickery, but like I said before, pre-optimization is a trap you can fall into, making your task overly-complex without confirming you even NEED to based on your use cases.
[/quote]

well,i don't know how to do it,do you have some tutorial about using pixel shader to draw the mesh?

could you give me some tutorial or some example?
i just learnt how to use pixel shader yesterday.
thank you!

Loading and sampling a texture is very standard stuff as far as pixel shaders, wherever you learned how to use the shader should also cover texturing. You'll greatly benefit from learning how to search for references on google.

A few minutes of poking around dug up this, which incidentally I found by searching this very site and running across this thread.

thank you!

Loading and sampling a texture is very standard stuff as far as pixel shaders, wherever you learned how to use the shader should also cover texturing. You'll greatly benefit from learning how to search for references on google.

A few minutes of poking around dug up this, which incidentally I found by searching this very site and running across this thread.

i still don't understand.i learnt how to use Pixel Shaders.
But,how to use Pixel Shaders to change the texture?

well,i want to use 100 different textures in one DrawPrimitive() call.
I used PixelShader,but how to pass 100 textures into the PixelShader?
I know use tex2D(sampler,tex coord); to get texture pixel then return it.but,how could i get the texture in PixelShader?
I think i can use SetTexture(xx, Tex) and multiple sampler,but PixelShader 2.0 only support 16 samplers.

And ,do you have a facebook?
I want to add you,facebook chat is easier.