Immediate mode (computer graphics)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Immediate mode" computer graphics – news · newspapers · books · scholar · JSTOR (December 2019) (Learn how and when to remove this message)

Immediate mode is an API design pattern in computer graphics libraries, in which

• the client calls directly cause rendering of graphics objects to the display, or in which
• the data to describe rendering primitives is inserted frame by frame directly from the client into a command list (in the case of immediate mode primitive rendering),

without the use of extensive indirection – thus immediate – to retained resources.^[1] It does not preclude the use of double-buffering.

Retained mode is an alternative approach. Historically, retained mode has been the dominant style in GUI libraries;^[2] however, both can coexist in the same library and are not necessarily exclusive in practice.

In immediate mode, the scene (complete object model of the rendering primitives) is retained in the memory space of the client, instead of the graphics library. This implies that in an immediate mode application, the lists of graphical objects to be rendered are kept by the client and are not saved by the graphics library API. The application must re-issue all drawing commands required to describe the entire scene each time a new frame is required, regardless of actual changes. This method provides on the one hand a maximum of control and flexibility to the application program, but on the other hand it also generates continuous work load on the CPU.

Examples of immediate mode rendering systems include Direct2D,^[1] OpenGL^[3] and Quartz.^[4] There are some immediate mode GUIs that are particularly suitable when used in conjunction with immediate mode rendering systems.

Primitive vertex attribute data may be inserted frame by frame into a command buffer by a rendering API. This involves significant bandwidth and processor time (especially if the graphics processing unit is on a separate bus), but may be advantageous for data generated dynamically by the CPU. It is less common since the advent of increasingly versatile shaders, with which a graphics processing unit may generate increasingly complex effects without the need for CPU intervention.

Although drawing commands have to be re-issued for each new frame, modern systems using this method are generally able to avoid the unnecessary duplication of more memory-intensive display data by referring to that unchanging data (via indirection) (e.g. textures and vertex buffers) in the drawing commands.

Graphical user interfaces traditionally use retained mode-style API design,^[2][5] but immediate mode GUIs instead use an immediate mode-style API design, in which user code directly specifies the GUI elements to draw in the user input loop. For example, rather than having a CreateButton() function that a user would call once to instantiate a button, an immediate-mode GUI API may have a DoButton() function which should be called whenever the button should be on screen.^[6][5] The technique was developed by Casey Muratori in 2002.^[6][5]

• Display list
• Retained mode, usually contrasted with immediate mode
• Scene graph