Re: bad performance when running SimpleSample in fullscreen
- From: legalize+jeeves@xxxxxxxxxxxxxxxxx (Richard [Microsoft Direct3D MVP])
- Date: Tue, 23 Jan 2007 14:52:01 -0800
[Please do not mail me a copy of your followup]
"Shogun" <shogun@xxxxxxxxxxxxxxxxxxxxxxxxx> spake the secret code
<2DA3E222-1422-49AB-BBFD-800A724F7CD9@xxxxxxxxxxxxx> thusly:
So if I understand this right, it is a driver issue? Or is it something in
the DX9 API?
It could be the driver or the runtime, but its not something you can
control. The only thing the API says is that you will not get too far
ahead of the rendering in that calling IDirect3DDevice9::Present may block.
You can get the swap chain for the device and call Present on the swap
chain with a flag that will immediately return with
D3DERR_WASSTILLDRAWING if a Present operation would force the
application to block.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
.
- Follow-Ups:
- References:
- Re: bad performance when running SimpleSample in fullscreen
- From: tl
- Re: bad performance when running SimpleSample in fullscreen
- From: Richard [Microsoft Direct3D MVP]
- Re: bad performance when running SimpleSample in fullscreen
- From: Shogun
- Re: bad performance when running SimpleSample in fullscreen
- Prev by Date: Direct3D bug or limitation?
- Next by Date: Re: Direct3D bug or limitation?
- Previous by thread: Re: bad performance when running SimpleSample in fullscreen
- Next by thread: Re: bad performance when running SimpleSample in fullscreen
- Index(es):