Jump to content
  • Advertisement
Sign in to follow this  

Some resourcesuggestions/help

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

Hi! I like to hear some suggestions. I have a nice litte graphicsengine with huge use of directx. For my gameworld, I'm using vertex and indexbuffers to store all of the geometry data. That gives nice performance. But when it comes to things like collision detection and other things, I can't really use them (the buffers). How are you guys solving this? Keeping the geometrydata in two separate places, one for cd and one for gfx?

Share this post


Link to post
Share on other sites
Advertisement
Usually you will be using different geometry for collision detection -- so there is no copy; there is just different data. For example, one could use axis-aligned bounding boxes or object-oriented bounding boxes. Once computed, they can be used separate from the vertex/face geomtry of the mesh. When using complex per-face collision detection, the cd data comes closest to the actual mesh data. But even then, you can usually gain a lot since you don't need to have duplicate vertices (otherwise required for multi-texturing or materials) and you don't need to have extra triangles in flat surfaces. In such a case it is still best to store it separately.

Greetz,

Illco

Share this post


Link to post
Share on other sites
Ohh.. I see! Thanks!

My world geometry was pretty simple (mostly blocks/"houses" and some flat road), so I didn't even think of optimizing it. But of course you are right!

Thanks again

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.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!