Jump to content

  • Log In with Google      Sign In   
  • Create Account


VB->Optimize question


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
1 reply to this topic

#1 BigCarlito   Members   -  Reputation: 122

Like
Likes
Like

Posted 09 December 1999 - 02:25 PM

Here's one for the D3D gurus: I have several small objects (actually they're bodyparts) whose geometry doesn't change throughout the application. I thought this would be ideal for optimized vertex buffers. Can anyone tell me (since I'm to lazy to actually implement both and see for myself) if the optimize command would work better if I lumped all of these objects (less than 150 tris each) into one big VB or used seperate VB's for each?? Thanks!


Sponsor:

#2 mhkrause   Members   -  Reputation: 122

Like
Likes
Like

Posted 09 December 1999 - 02:25 PM

You should definitely optimize your static geometry, this is a win especially if you're using a AMD processor with 3DNow! or an Intel Pentium III.

VB changes can be expensive, since they are a driver transition. They are even more expensive on Win2K.

I'd recommend lumping them into a single VB, of size up to 1000 vertices, or 64K total vertex buffer size, in bytes. Batch rendering of these objects by VB, and use the new vertex range arguments to avoid retransformation, when possible.





Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS