This section may contain material not related to the topic of the article. Please help improve this section or discuss this issue on the talk page. (January 2024) (Learn how and when to remove this template message)

A display list, also called a command list in Direct3D 12 and a command buffer in Vulkan, is a series of graphics commands so that they may be later run when the list is executed.[1] Systems that make use of display list functionality are called retained mode systems, while systems that do not are as opposed to immediate mode systems. In OpenGL, display lists are useful to redraw the same geometry or apply a set of state changes multiple times.[2][3] This benefit is also used with Direct3D 12's bundle command lists. In Direct3D 12 and Vulkan, display lists are regularly used for per-frame recording and execution.

Appearances in display list functionality

One of the earliest popular systems with a true display list was the Atari 8-bit family. The display list (actually called so in Atari terminology) is a series of instructions for ANTIC, the video co-processor used in these machines. This program, stored in the computer's memory and executed by ANTIC in real-time, can specify blank lines, any of six text modes and eight graphics modes, which sections of the screen can be horizontally or vertically fine-scrolled, and trigger Display List Interrupts (called raster interrupts or HBI on other systems).[4]

The Amstrad PCW family contains a Display List function called the 'Roller RAM'. This is a 512-byte RAM area consisting of 256 16-bit vectors in RAM, one for each line of the 720 × 256 pixel display. Each vector identifies the location of 90 bytes of monochrome pixels that hold the line's 720 pixel states. The 90 bytes of 8 pixel states are spaced at 8-byte intervals, so there are 7 unused bytes between each byte of pixel data. This suits how the text-orientated PCW constructs a typical screen buffer in RAM, where the first character's 8 rows are stored in the first 8 bytes, the second character's rows in the next 8 bytes, and so on. The Roller RAM was implemented to speed up display scrolling as it would have been unacceptably slow for its 3.4 MHz Z80 to move up the 23 KB display buffer 'by hand' i.e. in software. The Roller RAM starting entry used at the beginning of a screen refresh is controlled by a Z80-writable I/O register. Therefore, the screen can be scrolled simply by changing this I/O register.[citation needed]

Another system using a Display List-like feature in hardware is the Amiga, which, not coincidentally, was also designed by some of the same people who made the Atari 8-bits custom hardware. The Amiga display hardware was extremely sophisticated for its time and, once directed to produce a display mode, it would continue to do so automatically for every following scan line. The computer also included a dedicated co-processor, called "Copper", which ran a simple program or 'Copper List' intended for modifying hardware registers in sync with the display. The Copper List instructions could direct the Copper to wait for the display to reach a specific position on the screen, and then change the contents of hardware registers. In effect, it was a processor dedicated to servicing raster interrupts. The Copper was used by Workbench to mix multiple display modes (multiple resolutions and color palettes on the monitor at the same time), and by numerous programs to create rainbow and gradient effects on the screen. The Amiga Copper was also capable of reconfiguring the sprite engine mid-frame, with only one scanline of delay. This allowed the Amiga to draw more than its 8 hardware sprites, so long as the additional sprites did not share scanlines (or the one scanline gap) with more than 7 other sprites. i.e., so long as at least one sprite had finished drawing, another sprite could be added below it on the screen. Additionally, the later 32-bit AGA chipset allowed the drawing of bigger sprites (more pixels per row) while retaining the same multiplexing. The Amiga also had dedicated block-shifter ("blitter") hardware, which could draw larger objects into a framebuffer. This was often used in place of, or in addition to, sprites.[citation needed]

In more primitive systems, the results of a display list can be simulated, though at the cost of CPU-intensive writes to certain display modes, color control, or other visual effect registers in the video device, rather than a series of rendering commands executed by the device. Thus, one must create the displayed image using some other rendering process, either before or while the CPU-driven display generation executes. In many cases, the image is also modified or re-rendered between frames. The image is then displayed in various ways, depending on the exact way in which the CPU-driven display code is implemented.[citation needed]

Examples of the results possible on these older machines requiring CPU-driven video include effects such as Commodore 64/128's FLI mode, or Rainbow Processing on the ZX Spectrum.[citation needed]

Usage in OpenGL

To delimit a display list, the glNewList and glEndList functions are used, and to execute the list, the glCallList function is used. Almost all rendering commands that occur between the function calls are stored in the display list. Commands that affect the client state are not stored in display lists.[5] Display lists are named with an integer value, and creating a display list with the same name as one already created overrides the first.[6]

The glNewList function expects two arguments: an integer representing the name of the list, and an enumeration for the compilation mode. The two modes include GL_COMPILE_AND_EXECUTE, which compiles and immediately executes, and GL_COMPILE, which only compiles the list.[7]

Display lists enable the use of the retained mode rendering pattern, which is a system in which graphics commands are recorded (retained) to execute in succession at a later time. This is contrary to immediate mode, where graphics commands are immediately executed on client calls.[8]

Usage in Direct3D 12

Command lists are created using the ID3D12Device::CreateCommandList or ID3D12Device4::CreateCommandList1 functions.[9] Command lists may be created in several types: direct, bundle, compute, copy, video decode, video process, and video encoding. Direct command lists specify that a command list the GPU can execute, and doesn't inherit any GPU state.[10] Bundles, are best used for storing and executing small sets of commands any number of times. This is used differently than regular command lists, where commands stored in a command list are typically executed only once.[9] Compute command lists are used for general computations, with a common use being calculating mipmaps.[11] A copy command list is strictly for copying and the video decode and video process command lists are for video decoding and processing respectively.[10]

Upon creation, command lists are in the recording state. Command lists may be re-used by calling the ID3D12GraphicsCommandList::Reset function. After recording commands, the command list must be transitioned out of the recording state by calling ID3D12GraphicsCommandList::Close. The command list is then executed by calling ID3D12CommandQueue::ExecuteCommandLists.[9]

Deprecation

Display lists have largely been deprecated in modern graphics architectures, as they represent a set of commands in the fixed function graphics pipeline. Modern architectures use shaders and vertex buffer objects, to avoid tying graphics performance to the CPU. Due to the nature of the display list, it must copy every command and its data, which may be a problem for certain environments where memory is scarce, and can be overall inefficient.[5] However, Vulkan and Direct3D 12 still practice display list-like functionality in the form of command buffers and command lists.

See also

References

  1. ^ "Chapter 7 - OpenGL Programming Guide". www.glprogramming.com. Addison-Wesely. Retrieved 18 November 2018.
  2. ^ OpenGL programming guide: the official guide to learning OpenGL, version 1.1 (2nd ed.). Addison Wesley. 1997. ISBN 978-0201461381.
  3. ^ Mark Segal, Kurt Akeley, The Design of the OpenGL Graphics Interface. http://www.graphics.stanford.edu/courses/cs448a-01-fall/design_opengl.pdf
  4. ^ Small, David; Small, Sandy; Blank, George (1983). The Creative Atari. Creative Computing Press. ISBN 978-0-916688-34-9. Retrieved December 18, 2023.
  5. ^ a b Martz, Paul (2006). OpenGL Distilled (1st ed.). Addison-Wesley Professional PTG. ISBN 9780132701785. Retrieved 28 December 2023.
  6. ^ Wright, Richard S.; Haemel, Nicholas; Sellers, Graham; Lipchak, Benjamin (2010). OpenGL SuperBible: Comprehensive Tutorial and Reference (5th ed.). Addison-Wesley Professional. ISBN 978-0-321-71261-5.
  7. ^ White, Steve (2021-03-09). "glNewList function (Gl.h) - Win32 apps". learn.microsoft.com. Retrieved 2023-12-28.
  8. ^ Quinn Radich (May 30, 2018). "Retained Mode Versus Immediate Mode". Win32 apps. Microsoft. Retrieved 21 December 2019.
  9. ^ a b c White, Steven; Jenks, Alma; badasahog; Coulter, David; Kelly, John; Kinross, Austin; Wenzel, Maira; Jacobs, Mike; Satran, Michael (2021-12-30). "Creating and recording command lists and bundles - Win32 apps". learn.microsoft.com. Retrieved 2024-01-05.
  10. ^ a b White, Steve (2023-02-14). "D3D12_COMMAND_LIST_TYPE (d3d12.h) - Win32 apps". learn.microsoft.com. Retrieved 2024-01-06.
  11. ^ Loggini, Riccardo (2020-10-31). "Compute Shaders in D3D12". Riccardo Loggini. Retrieved 2024-01-06.

Further reading

Category