Jump to content
  • Advertisement
Sign in to follow this  
Quat

D3DXMESHOPT_DONOTSPLIT

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

Can someone explain the above ID3DXMesh optimization flag? (I do not follow the SDK docs description.)

Share this post


Link to post
Share on other sites
Advertisement
Splitting = making another vertex with the same values.

That flags stops it from doing that. Which will cause you vertex start and end values to overlap which may be sub-optimal depending on your rendering method. If you use hardware then it won't matter.

Share this post


Link to post
Share on other sites
Quote:
Splitting = making another vertex with the same values.

That flags stops it from doing that. Which will cause you vertex start and end values to overlap which may be sub-optimal depending on your rendering method. If you use hardware then it won't matter.


Oh okay, this answers my other question then that I posted yesterday. Just to verify that I understand:

If this flag is not specified, then the Optimize function will actually duplicate vertices so that the attribute entry vertex ranges do not overlap (i.e., disjoint). If this is specified, then it is possible that the vertex ranges will overlap.

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!