Jump to content
  • Advertisement
Sign in to follow this  
Raxvan

mesh vs. vertex buffer (render speed)

This topic is 4842 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I recently discovered that milkshape 3d can generate terrain; it is recommended to use in the program a mesh generated by milkshape with the texture or to convert the mesh in a file,open the file,read a vertext buffer and then use normal methods to render the terrain? And i am tacking here about the speed is there a major deference between rendering a mesh or normal rendering a vertex buffer ??

Share this post


Link to post
Share on other sites
Advertisement
Generally speaking a mesh is probaly faster to render then the Vertex Buffer ( though not really that much faster ), it sort of depends on your vertex buffer and stuff like that...

But when we are talking about a terrain you should cull it somehow, that is have a hiearchial tree ( octree or some form of BSP ) and only draw the visible parts of the tree... To do that you would have to split the mesh / VB into alot of smaller parts, and then you should consider using a big VB with lots of small Index Buffers that determins what you should render or not...

the ID3DXMesh interface in DX is really a great tool, but it's not very useful to render terrain with...

Share this post


Link to post
Share on other sites
yes i know that a mesh is almost a vertex buffer but i was tacking about ID3DXMesh and stuff like that to use.


however tnx
I am familiar with the BSP tree but only in dos graphics. hiearchial tree or however you are calling it, i have never heard of it. Can you help me pls with some information or a tutorial.

Share this post


Link to post
Share on other sites
Read the topic: "Rendering Large Enviorments" a bit down on the forum from this topic, it contains information about octrees...

Share this post


Link to post
Share on other sites
Quote:
Original post by JoCCo
Read the topic: "Rendering Large Enviorments" a bit down on the forum from this topic, it contains information about octrees...

Definetly. If you want decent performance, don't use ID3DXMesh for your environment rendering - not because it's slow for rendering normal meshes, but because you need control over which sections of the terrain to render.

As far as "which is faster - rendering right from a VB or from ID3DXMesh?", they are going to be the same. ID3DXMesh is just a light wrapper around a VB and IB.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!