Swap chain: Difference between revisions

Revision as of 19:13, 29 October 2009

Revision as of 03:10, 30 October 2009

Line 1:

_NOTOC_

In [[computer graphics (computer science)|Computer graphics]], a '''Swap Chain''' is a series of [[framebuffer]]s utilized by the [[graphics card]] or graphics [[API]] in an immediate mode graphics processing environment for [[frame rate]] stabilization and several other functions. The swap chain usually exists in [[Random-access memory| graphics memory]], but it can exist in system memory as well. The first framebuffer, the screenbuffer, is the buffer that is [[Rendering (computer graphics)|rendered]] to the output of the graphics card or a variety of other locations for further processing depending on the environment the client application is running in. Each time new [[Film frame|frame]] is displayed, the next buffer in the swap chain takes the place of the screenbuffer, this is called presentation or '''swapping'''. A variety of other actions may be taken on the previous screenbuffer; it may be erased from memory, or returned to the front of the swap chain for further processing. The action taken is decided by the client application and is API dependent.

In [[Computer graphics (computer science)|computer graphics]], a '''Swap Chain''' is a series of [[framebuffer]]s utilized by the [[graphics card]] or graphics [[API]] in an immediate mode graphics processing environment for [[frame rate]] stabilization and several other functions. The swap chain usually exists in [[Random-access memory| graphics memory]], but it can exist in system memory as well.

==Function==

In [[computer graphics (computer science)|Computer graphics]], a '''Swap Chain''' is a series of [[framebuffer]]s utilized by the [[graphics card]] or graphics [[API]] in an immediate mode graphics processing environment for [[frame rate]] stabilization and several other functions. The swap chain usually exists in [[Random-access memory| graphics memory]], but it can exist in system memory as well. The first framebuffer, the screenbuffer, is the buffer that is [[Rendering (computer graphics)|rendered]] to the output of the graphics card or a variety of other locations for further processing depending on the environment the client application is running in. Each time new [[Film frame|frame]] is displayed, the nextfirst back buffer in the swap chain takes the place of the screenbuffer, this is called presentation or '''swapping'''. A variety of other actions may be taken on the previous screenbuffer; it may be erased from memory, or returned to the front of the swap chain for further processing. The action taken is decided by the client application and is API dependent.

==Direct3D==

[[Microsoft]] [[Direct3D]] implements a 'SwapChain' class. Each host device has at least one swap chain assigned to it, and others may be created by the client application.<ref>http://msdn.microsoft.com/en-us/library/microsoft.windowsmobile.directx.direct3d.swapchain.aspx</ref> The API provides three methods of swapping: 'copy', 'discard', and 'flip'. When the SwapChain is set to 'flip', the screenbuffer is copied onto the last backbuffer, then all the existing backbuffers are copied into the next framebuffer. When 'copy' is set, the screenbuffer is simply copied over, leaving the last backbuffer empty. 'Flip' does not work when there is only one backbuffer, as the screenbuffer is copied over the only backbuffer before it can be presented. In 'discard' mode, the driver selects the best method.<ref>http://nexe.gamedev.net/directKnowledge/default.asp?p=Swap%20Chains</ref>

==Notes==

<references/>

==References==

*{{Cite web

| title = SwapChain Class

| publisher = Microsoft

| url = http://msdn.microsoft.com/en-us/library/microsoft.windowsmobile.directx.direct3d.swapchain.aspx

| accessdate = 30 October 2009}}

*{{Cite web

| title = Swap Chains

| publisher = neXe

| url = http://nexe.gamedev.net/directKnowledge/default.asp?p=Swap%20Chains

| accessdate = 30 October 2009}}