Jump to content
  • Advertisement
Sign in to follow this  
Chris81

Split static VB's per vertex type or use single vertex type?

This topic is 4850 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

Right now I am planning on using one large static VB for all static geometry. However, what about when you have some static geometry using one vertex type, and one using another? Should I split them up into multiple VB's and incur the penalty of SetStream, or should I just use the greatest common vertex type and incur the penalty of unused and extra memory? The only example I can think of where this matters right now is tangents. Non bump-mapped geometry only need position, normal, and tex coord. Bump mapped needs an additional tangent in the vertex type. If I include tangent in the vertex type, even for non-bump mapped textures, it's unused wasted memory. If I split them up, I then have to manage multiple static vertex buffers, and switch between the streams. Trying to decide which option is better. (Or a third option) Thanks.

Share this post


Link to post
Share on other sites
Advertisement
Guest Anonymous Poster
Check this out:

Here

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Sorry...

http://www.ati.com/developer/gdc/D3DTutorial0_Intro_And_Features.pdf

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!