Well I have another question about buffers i was thinking about setting up a global vertex buffer for my terrain grids, the only thing is they are set up in quadtrees so basically there are vertexbuffers setup for each quadtree leaf. So that is alot of vertexbuffers which in my understanding means bad. So i was wondering how many vertices can i put into a single buffer And if setting up a buffer for a whole gird is a good idea.
Yet Another Buffer Question
Hot Topic
- Uninstalling DirectX
- GameOS source code availability
- fable--can't execute application
- Matching view to world - help!
- Where to go?
- DirectInput best practice
- Maximum Range for Mesh.Intersect Function?
- Disable FSAA for some primitives each frame? (disable it temporarily)
- Point Sprite are displayed at the correct place
- HELP "The file system.dll is missing!"
Game Technologies
- Different results between REF and HAL devyce
- DirectPlay Alternative Example?
- If you have the time... please inspect and tell me what you think of my DX Base code, part of this is from microsoft tutorials
- Code behaves differently on 3 different computers. ???
- Setting a custom cursor image [MDX2]
- Render to a Video output #_#
- Preventing window resizing in fullscreen games
- Need UV Atlas help
- Visual C++ Express and DirectX
- Getting rendered graphics (quickly) from the card
Yet Another Buffer Question
Vikram
But whatever the real virtues of small or large VBs, I think you're prematurely optimising. Just write the algorithm using whatever size of VB is most natural. You can always change it later IF you find that is a performance win. But if it's not - don't. There's not point worrying about something that probably won't be a problem.
TomF.