05.08.2013 Views

Intel HD Graphics DirectX Developer's Guide (Sandy Bridge)

Intel HD Graphics DirectX Developer's Guide (Sandy Bridge)

Intel HD Graphics DirectX Developer's Guide (Sandy Bridge)

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Intel</strong>® <strong>HD</strong> <strong>Graphics</strong> <strong>DirectX</strong>* <strong>Developer's</strong> <strong>Guide</strong><br />

3.10.6 Avoid writing to unlocked buffers<br />

We have found multiple cases of corruption which were caused by the writes to<br />

unlocked buffers. Typically the title first locked the buffer, then unlocked the buffer<br />

and then attempted to writing to the buffer that is already unlocked. This sometimes<br />

works because the system might have not moved the buffer and has not dispatched<br />

the rendering commands to the graphics hardware. This is inconsistent with Microsoft<br />

<strong>DirectX</strong>* specifications and is not safe for applications to expect it to work<br />

consistently.<br />

Avoid writing to buffers that have not been locked. Some drivers on other hardware<br />

platforms are more forgiving of this approach, and may handle it gracefully. The <strong>Intel</strong><br />

driver makes optimizations based on the specified behavior of the API, so the behavior<br />

of this platform will be undefined in this case.<br />

3.10.7 Avoid tight polling on queries<br />

Tight polling on event/occlusion queries degrade performance by interfering with the<br />

GPU‟s turbo mode operation.<br />

Allow for queries to work asynchronously and avoid waiting on the query response<br />

immediately after sending the query.<br />

34 Document Number: 321371-002US

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!