Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualMatias Goldberg

Posted 11 December 2012 - 12:35 PM

What mhagain said. D3DX needs a copy for itself in case your device is lost.

Also if you happen to own an ATI Radeon HD 4000 to 7000, the drivers apparently do some black magic inside regarding storing the index buffers into system memory (rather than GPU memory) and introduce a small hiccup. You may experience this happens with all games that don't pre-render a few frames before showing actual input to give the drivers time to "warm up" (particularly, it's quite obvious in LA. Noire for these cards) as well in some SDK demos with heavy vertex & index count.

Edit: Also, you do realise that you're passing D3DXSHADER_DEBUG to generate your shaders? (which isn't bad, but may explain the initial slowdown)

#1Matias Goldberg

Posted 11 December 2012 - 12:33 PM

What mhagain said. D3DX needs a copy for itself in case your device is lost.

Also if you happen to own an ATI Radeon HD 4000 to 7000, the drivers apparently do some black magic inside regarding storing the index buffers into system memory (rather than GPU memory) and introduce a small hiccup. You may experience this happens with all games that don't pre-render a few frames before showing actual input to give the drivers time to "warm up" (particularly, it's quite obvious in LA. Noire for these cards) as well in some SDK demos with heavy vertex & index count.

PARTNERS