US 6,424,348 B1Grant
Application program interface for a graphics system
Issue Date:2002-07-23
•4 Claims
•21 Drawing Sheets
Abstract
An interface for a graphics system includes simple yet powerful constructs that are easy for an application programmer to use and learn. Features include a unique vertex representation allowing the graphics pipeline to retain vertex state information and to mix indexed and direct vertex values and attributes; a projection matrix value set command; a display list call object command; and an embedded frame buffer clear/set command.
Metadata
Assignee
- Nintendo Co., Ltd.
Inventors
- Vimal Parikh
- Robert Moore
- Howard Cheng
Application Information
Application Number:US 09/886,264
Filing Date:2001-06-22
Priority Date:2000-11-28
Art Unit:7
Classifications
IPC:
G06F 1516G06T 1500
Field of Search:
345501345503345419345551345520345522345559345567709328712208
Patent Drawings (21 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] See the following copending patent applications incorporated herein by reference:
[0003] application Ser. No. 09/465,754, filed Dec. 17, 1999 of Moore et al. entitled “Vertex Cache For 3D Computer Graphics”; claiming benefit from provisional application No. 60/161,915, filed Oct. 28, 1999,
[0004] Application Ser. No. 09/726,215, filed Nov. 28, 2000 (atty. dkt. no. 723-959), of Fouladi et al. entitled “Method and Apparatus for Buffering Graphics Data in a Graphics System” claiming benefit from provisional application No. 60/226,912 filed Aug. 23, 2000;
[0005] application Ser. No. 09/722,367, filed Nov. 28, 2000 (atty. dkt. no. 723-968) of Drebin et al. entitled “Recirculating Shade Tree Blender For A Graphics System” claiming benefit from provisional application No. 60/226,888, filed Aug. 23, 2000;
[0006] application Ser. No. 09/722,663, filed Nov. 28, 2000 (atty. dkt. no. 723-963) of Fouladi et al. entitled “Graphics System With Copy Out Conversions Between Embedded Frame Buffer And Main Memory” claiming benefit from provisional application No. 60/227,030, filed Aug. 23, 2000;
[0007] application Ser. No. 09/722,390, filed Nov. 28, 2000 (atty. dkt. no. 723-966) of Demers et al., entitled “Low Cost Graphics System With Stitching Hardware Support For Skeletal Animation” claiming benefit from provisional application No. 60/226,914, filed Aug. 23, 2000;
[0008] application Ser. No. 09/726,216, filed Nov. 28, 2000 (atty. dkt. no. 723-967) of Drebin et al., entitled “Achromatic Lighting in a Graphics System and Method” claiming benefit from provisional application No. 60/227,007, filed Aug. 23, 2000.
FIELD OF THE INVENTION
[0009] The present invention relates to computer graphics, and more particularly to interactive graphics systems including but not limited to home video game platforms. Still more particularly this invention relates to an advantageous software programming interface including binary command functions for controlling a graphics chip and to methods for generating, storing and decoding same.
BACKGROUND AND SUMMARY OF THE INVENTION
[0010] Many of us have seen films containing remarkably realistic dinosaurs, aliens, animated toys and other fanciful creatures. Such animations are made possible by computer graphics. Using such techniques, a computer graphics artist can specify how each object should look and how it should change in appearance over time, and a computer then models the objects and displays them on a display such as your television or a computer screen. The computer takes care of performing the many tasks required to make sure that each part of the displayed image is colored and shaped just right based on the position and orientation of each object in a scene, the direction in which light seems to strike each object, the surface texture of each object, and other factors.
[0011] Because computer graphics generation is complex, computer-generated three-dimensional graphics just a few years ago were mostly limited to expensive specialized flight simulators, high-end graphics workstations and supercomputers. The public saw some of the images generated by these computer systems in movies and expensive television advertisements, but most of us couldn't actually interact with the computers doing the graphics generation. All this has changed with the availability of relatively inexpensive 3D graphics platforms such as, for example, the Nintendo 64(® and various 3D graphics cards now available for personal computers. It is now possible to interact with exciting 3D animations and simulations on relatively inexpensive computer graphics systems in your home or office.
[0012] A problem graphics system designers confronted in the past was how to provide a control interface for a graphics system that enables fast, efficient and flexible use of the graphics system by applications designed to be executed thereon. Various application programming interfaces (APIs) and application binary interfaces (ABIs) have been developed in the past for the purpose of enabling graphics application programmers to control the operation of a graphics chip provided in a graphics system. Perhaps the most commonly-used 3D graphics application programming interfaces in current use are Microsoft's Direct3D interface and the OpenGL interface developed through cooperation with Silicon Graphics. See, for example, Kovach, Inside Direct3D: The Definitive Guide to Real-Time3D Power and Performance for Microsoft Windows(Microsoft Press 2000); and Neider et al., OpenGL Programming Guide: The Official Guide to Learning OpenGL Release1 (Addison-Wesley Publishing Co. 1993).
[0013] As explained in the Kovach book, Microsoft's DirectX application programming interface (API) provides a set of interfaces offering efficient control of multimedia hardware on a computer running Microsoft Windows. Kovach states that DirectX lets programmers work with commands and data structures that are very close to those that the hardware can natively process, without being so low level that code has to be written differently for each device. By writing device-independent code, programmers can create software that will theoretically always perform at its best (according to Kovach)—even as users enhance their systems with new and improved 3D graphics accelerators, sound cards, input devices and other system capabilities.
[0014] Kovach explains that the device-independence of DirectX is obtained because the DirectX APIs are built on a hardware abstraction layer (HAL) that hides the device-specific dependencies of the hardware. In fact, DirectX defines some hardware acceleration support features that aren't available on much of the hardware built today in order to provide extensibility for the future.
[0015] While the DirectX approach has been widely adopted and is successful in providing compatibility across a wide range of different platform configurations, the use of a thick hardware abstraction layer and associated hardware emulation layer is not particularly suitable for current low cost dedicated video game platforms at the current time. The DirectX API was primarily designed for personal computers costing many hundreds or thousands of dollars and manufactured in a variety of different configurations and permutations. While the DirectX API has been successful in providing compatibility across a wide range of such different platform configurations, this compatibility has come at the expense of efficiency and performance. In the context of a dedicated low-cost video game platform, it is possible to do much better in terms of providing a fully capable programming interface that is very close to the hardware while providing a highly capable and flexible interface for achieving a wide variety of interesting 3-dimensional graphics effects.
[0016] One prior approach is described in U.S. patent application Ser. No. 08/990,133 filed Dec. 12, 1997 by Van Hook et al., entitled “Interface For A High Performance Low Cost Video Game System With Coprocessor Providing High Speed Efficient 3D Graphics And Digital Audio Signal Processing.” However, further improvements are possible and desirable. In particular, some people criticized the interface described in this prior Van Hook et al., patent application because they thought it was difficult to write applications to. In the home video game arena, it is desirable to maximize performance while keeping the interface used to invoke and control such performance and capabilities as simple and easy to use as possible. Requiring application programmers to write to an unduly complicated interface may increase the time it takes to develop such applications. This can have devastatingly negative effects when it comes time to launch a new video game platform—since the success of the platform may often depend on achieving a certain “critical mass” in terms of the number of games or other applications available at launch time. As some developers of prior new home video game platforms found out, no one wants to buy a new video game system if there are no games to play on it. It is therefore desirable to provide a graphics programming interface that is simple and easy to use and yet is very powerful and flexible.
[0017] The present invention solves this problem by providing new and improved interface for graphics systems that is designed to be as thin as possible in order to achieve high performance, while also providing a logical and orthogonal view of the graphics hardware.
[0018] The present invention provides a graphics system programming interface with graphics commands allowing geometry to be rendered with many attributes. The interface provides two main methods for drawing geometry. An immediate mode allows the command stream source to send a stream of graphics commands directly to the graphics processor for consumption. This immediate mode interface is useful when the main processor must synthesize geometry data from a higher-level description (e.g., a height field or Bezier patch). The second method feeds a command stream to the graphics processor using a memory-resident display list format. This interface provides superior performance for static data. The immediate interface and the display list interface both support configurable vertex representations. The configurable vertex representations include, for example, direct or indexed vertex components. Vertex components (e.g., position, normal, color and texture coordinates for a number of textures) can all be indexed independently from arrays, or placed directly in the command stream. Additional flexibility is provided by allowing each vertex component to have a differently-sized representation and precision. The available direct types may include, for example, 8-bit signed and unsigned integer, 16-bit signed and unsigned integer, and 32-bit floating point. A scale is available to position the decimal point for the integer types. The indirect types (e.g., 8-bit index or 16-bit index) can be used to index into an array of any of the direct types. This flexible representation allows the game developer to organize vertex data in a way that is appropriate for the game. The ability to index each component separately eliminates a great deal of data duplication.
BRIEF DESCRIPTION OF THE DRAWINGS
[0019] These and other features and advantages provided by the invention will be better and more completely understood by referring to the following detailed description of presently preferred embodiments in conjunction with the drawings, of which:
[0020] FIG. 1 is an overall view of an example interactive computer graphics system;
[0021] FIG. 2 is a block diagram of the FIG. 1 example computer graphics system;
[0022] FIG. 3 is a block diagram of the example graphics and audio processor shown in FIG. 2;
[0023] FIG. 4 is a block diagram of the example 3D graphics processor shown in FIG. 3;
[0024] FIG. 5 is an example logical flow diagram of the FIG. 4 3D graphics processor;
[0025] FIG. 6 is a general flow chart of functions performed by an example application for the FIG. 1 graphics system;
[0026] FIG. 7 is a flow chart showing the functions of FIG. 6 in more detail;
[0027] FIG. 8 shows example simple graphics command stream;
[0028] FIG. 9 shows an example binary level interface for setting the embedded color and depth buffer of the FIG. 1 system to a particular (e.g., initial) value;
[0029] FIG. 9A shows example pixel engine copy clear register formats;
[0030] FIG. 10 shows an example vertex data structure hierarchy including example description information;
[0031] FIG. 11 shows an example binary level interface defining a vertex attribute array;
[0032] FIG. 12 shows an example binary level interface defining a vertex descriptor;
[0033] FIGS. 13A and 13B together show an example binary level interface defining a vertex attribute table;
[0034] FIG. 14 schematically illustrates an example vertex attribute format table;
[0035] FIG. 15 shows example graphics primitives that may be represented using the vertex data structures herein;
[0036] FIG. 16 shows an example binary level interface defining a projection matrix;
[0037] FIG. 17 shows an example binary level interface defining a display list to be called; and
[0038] FIGS. 18A and 18B show example alternative compatible implementations.
DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION
[0039] FIG. 1 shows an example interactive 3D computer graphics system 50. System 50 can be used to play interactive 3D video games with interesting stereo sound. It can also be used for a variety of other applications.
[0040] In this example, system 50 is capable of processing, interactively in real time, a digital representation or model of a three-dimensional world. System 50 can display some or all of the world from any arbitrary viewpoint. For example, system 50 can interactively change the viewpoint in response to real time inputs from handheld controllers 52a,52bor other input devices. This allows the game player to see the world through the eyes of someone within or outside of the world. System 50 can be used for applications that do not require real time 3D interactive display (e.g., 2D display generation and/or non-interactive display), but the capability of displaying quality 3D images very quickly can be used to create very realistic and exciting game play or other graphical interactions.
[0041] To play a video game or other application using system 50, the user first connects a main unit 54 to his or her color television set 56 or other display device by connecting a cable 58 between the two. Main unit 54 produces both video signals and audio signals for controlling color television set 56. The video signals are what controls the images displayed on the television screen 59, and the audio signals are played back as sound through television stereo loudspeakers 61L, 61R.
[0042] The user also needs to connect main unit 54 to a power source. This power source may be a conventional AC adapter (not shown) that plugs into a standard home electrical wall socket and converts the house current into a lower DC voltage signal suitable for powering the main unit 54. Batteries could be used in other implementations.
[0043] The user may use hand controllers 52a,52bto control main unit 54. Controls 60 can be used, for example, to specify the direction (up or down, left or right, closer or further away) that a character displayed on television 56 should move within a 3D world. Controls 60 also provide input for other applications (e.g., menu selection, pointer/cursor control, etc.). Controllers 52 can take a variety of forms. In this example, controllers 52 shown each include controls 60 such as joysticks, push buttons and/or directional switches. Controllers 52 may be connected to main unit 54 by cables or wirelessly via electromagnetic (e.g., radio or infrared) waves.
[0044] To play an application such as a game, the user selects an appropriate storage medium 62 storing the video game or other application he or she wants to play, and inserts that storage medium into a slot 64 in main unit 54. Storage medium 62 may, for example, be a specially encoded and/or encrypted optical and/or magnetic disk that stores commands for graphics and audio processor 114 and/or instructions controlling main processor 110 to develop such commands. The user may operate a power switch 66 to turn on main unit 54 and cause the main unit to begin running the video game or other application based on the software stored in the storage medium 62. The user may operate controllers 52 to provide inputs to main unit 54. For example, operating a control 60 may cause the game or other application to start. Moving other controls 60 can cause animated characters to move in different directions or change the user's point of view in a 3D world. Depending upon the particular software stored within the storage medium 62, the various controls 60 on the controller 52 can perform different functions at different times.
[0045] Example Electronics of Overall System
[0046] FIG. 2 shows a block diagram of example components of system 50. The primary components include:
[0047] a main processor (CPU) 110,
[0048] a main memory 112, and
[0049] a graphics and audio processor 114.
[0050] In this example, main processor 110 (e.g., an enhanced IBM Power PC 750) receives inputs from handheld controllers 108 (and/or other input devices) via graphics and audio processor 114. Main processor 110 interactively responds to user inputs, and executes a video game or other program supplied, for example, by external storage media 62 via a mass storage access device 106 such as an optical disk drive. As one example, in the context of video game play, main processor 110 can perform collision detection and animation processing in addition to a variety of interactive and control functions.
[0051] In this example, main processor 110 generates 3D graphics and audio commands and sends them to graphics and audio processor 114. The graphics and audio processor 114 processes these commands to generate interesting visual images on display 59 and interesting stereo sound on stereo loudspeakers 61R, 61L or other suitable sound-generating devices.
[0052] Example system 50 includes a video encoder 120 that receives image signals from graphics and audio processor 114 and converts the image signals into analog and/or digital video signals suitable for display on a standard display device such as a computer monitor or home color television set 56. System 100 also includes an audio codec (compressor/decompressor) 122 that compresses and decompresses digitized audio signals and may also convert between digital and analog audio signaling formats as needed. Audio codec 122 can receive audio inputs via a buffer 124 and provide them to graphics and audio processor 114 for processing (e.g., mixing with other audio signals the processor generates and/or receives via a streaming audio output of mass storage access device 106). Graphics and audio processor 114 in this example can store audio related information in an audio memory 126 that is available for audio tasks. Graphics and audio processor 114 provides the resulting audio output signals to audio codec 122 for decompression and conversion to analog signals (e.g., via buffer amplifiers 128L, 128R) so they can be reproduced by loudspeakers 61L, 61R.
[0053] Graphics and audio processor 114 has the ability to communicate with various additional devices that may be present within system 100. For example, a parallel digital bus 130 may be used to communicate with mass storage access device 106 and/or other components. A serial peripheral bus 132 may communicate with a variety of peripheral or other devices including, for example:
[0054] a programmable read-only memory and/or real time clock 134,
[0055] a modem 136 or other networking interface (which may in turn connect system 100 to a telecommunications network 138 such as the Internet or other digital network from/to which program instructions and/or data can be downloaded or uploaded), and
[0056] flash memory 140.
[0057] A further external serial bus 142 may be used to communicate with additional expansion memory 144 (e.g., a memory card) or other devices. Connectors may be used to connect various devices to busses 130, 132, 142.
[0058] Example Graphics and Audio Processor
[0059] FIG. 3 is a block diagram of an example graphics and audio processor 114. Graphics and audio processor 114 in one example may be a single-chip ASIC (application specific integrated circuit). In this example, graphics and audio processor 114 includes:
[0060] a processor interface 150,
[0061] a memory interface/controller 152,
[0062] a 3D graphics processor 154,
[0063] an audio digital signal processor (DSP) 156,
[0064] an audio memory interface 158,
[0065] an audio interface and mixer 160,
[0066] a peripheral controller 162, and
[0067] a display controller 164.
[0068] 3D graphics processor 154 performs graphics processing tasks. Audio digital signal processor 156 performs audio processing tasks. Display controller 164 accesses image information from main memory 112 and provides it to video encoder 120 for display on display device 102. Audio interface and mixer 160 interfaces with audio codec 122, and can also mix audio from different sources (e.g., streaming audio from mass storage access device 106, the output of audio DSP 156, and external audio input received via audio codec 122). Processor interface 150 provides a data and control interface between main processor 110 and graphics and audio processor 114.
[0069] Memory interface 152 provides a data and control interface between graphics and audio processor 114 and memory 112. In this example, main processor 110 accesses main memory 112 via processor interface 150 and memory interface 152 that are part of graphics and audio processor 114. Peripheral controller 162 provides a data and control interface between graphics and audio processor 114 and the various peripherals mentioned above. Audio memory interface 158 provides an interface with audio memory 126.
[0070] Example Graphics Pipeline
[0071] FIG. 4 shows a more detailed view of an example 3D graphics processor 154. 3D graphics processor 154 includes, among other things, a command processor 200 and a 3D graphics pipeline 180. Main processor 110 communicates streams of data (e.g., graphics command streams and display lists) to command processor 200. Main processor 110 has a two-level cache 112 to minimize memory latency, and also has a write-gathering buffer 111 for uncached data streams targeted for the graphics and audio processor 114. The write-gathering buffer 111 collects partial cache lines into full cache lines and sends the data out to the graphics and audio processor 114 one cache line at a time for maximum bus usage.
[0072] Command processor 200 receives display commands in binary format from main processor 110 and parses and decodes them—obtaining any additional data necessary to process them from shared memory 112. The command processor 200 provides a stream of vertex commands to graphics pipeline 180 for 2D and/or 3D processing and rendering. Graphics pipeline 180 generates images based on these commands. The resulting image information may be transferred to main memory 112 for access by display controller/video interface unit 164—which displays the frame buffer output of pipeline 180 on display 102.
[0073] FIG. 5 is a logical flow diagram of graphics processor 154. Main processor 110 may store graphics command streams 210, display lists 212 and vertex arrays 214 in main memory 112, and pass pointers to command processor 200 via bus interface 150. The main processor 110 stores graphics commands in one or more graphics first-in-first-out (FIFO) buffers 210 it allocates in main memory 110 or elsewhere. The command processor 200 fetches:
[0074] command streams from main memory 112 via an on-chip FIFO memory buffer 216 that receives and buffers the graphics commands for synchronization/flow control and load balancing,
[0075] display lists 212 from main memory 112 via an on-chip call FIFO memory buffer 218, and
[0076] vertex attributes from the command stream and/or from vertex arrays 1000 in main memory 112 via a vertex cache 220.
[0077] Command processor 200 performs command processing operations 200athat convert attribute types to floating point format, and passes the resulting complete vertex polygon data to graphics pipeline 180 for rendering/rasterization. A programmable memory arbitration circuitry 130 (see FIG. 4) arbitrates access to shared main memory 112 between graphics pipeline 180, command processor 200 and display controller/video interface unit 164.
[0078] FIG. 4 shows that graphics pipeline 180 may include:
[0079] a transform unit 300,
[0080] a setup/rasterizer 400,
[0081] a texture unit 500,
[0082] a texture environment unit 600, and
[0083] a pixel engine 700.
[0084] Transform unit 300 performs a variety of 2D and 3D transform and other operations 300a(see FIG. 5). Transform unit 300 may include one or more matrix memories 300bfor storing matrices used in transformation processing 300a.Transform unit 300 transforms incoming geometry per vertex from object space to screen space; and transforms incoming texture coordinates and computes projective texture coordinates (300c). Transform unit 300 may also perform polygon clipping/culling 300d.Lighting processing 300ealso performed by transform unit 300bprovides per vertex lighting computations for up to eight independent lights in one example embodiment. Transform unit 300 can also perform texture coordinate generation (300c) for embossed type bump mapping effects, as well as polygon clipping/culling operations (300d).
[0085] Setup/rasterizer 400 includes a setup unit which receives vertex data from transform unit 300 and sends triangle setup information to one or more rasterizer units (400b) performing edge rasterization, texture coordinate rasterization and color rasterization.
[0086] Texture unit 500 (which may include an on-chip texture memory (TMEM) 502) performs various tasks related to texturing including for example:
[0087] retrieving textures 504 from main memory 112,
[0088] texture processing (500a) including, for example, multi-texture handling, post-cache texture decompression, texture filtering, embossing, shadows and lighting through the use of projective textures, and BLIT with alpha transparency and depth,
[0089] bump map processing for computing texture coordinate displacements for bump mapping, pseudo texture and texture tiling effects (500b), and indirect texture processing (500c).
[0090] Texture unit 500 outputs filtered texture values to the texture environment unit 600 for texture environment processing (600a). Texture environment unit 600 blends polygon and texture color/alpha/depth, and can also perform texture fog processing (600b) to achieve inverse range based fog effects. Texture environment unit 600 can provide multiple stages to perform a variety of other interesting environment-related functions based for example on color/alpha modulation, embossing, detail texturing, texture swapping, clamping, and depth blending.
[0091] Pixel engine 700 performs depth (z) compare (700a) and pixel blending (700b). In this example, pixel engine 700 stores data into an embedded (on-chip) frame buffer memory 702. Graphics pipeline 180 may include one or more embedded DRAM memories 702 to store frame buffer and/or texture information locally. Z compares 700a′ can also be performed at an earlier stage in the graphics pipeline 180 depending on the rendering mode currently in effect (e.g., z compares can be performed earlier if alpha blending is not required). The pixel engine 700 includes a copy operation 700cthat periodically writes on-chip frame buffer 702 to main memory 112 for access by display/video interface unit 164. This copy operation 700ccan also be used to copy embedded frame buffer 702 contents to textures in the main memory 112 for dynamic texture synthesis effects. Anti-aliasing and other filtering can be performed during the copy-out operation. The frame buffer output of graphics pipeline 180 (which is ultimately stored in main memory 112) is read each frame by display/video interface unit 164. Display controller/video interface 164 provides digital RGB pixel values for display on display 102.
[0092] Example Graphics System Application Interface
[0093] As described above, main processor 110 sends graphics commands to graphics and audio processor 114. These graphics commands tell the graphics and audio processor 114 what to do. For example, the graphics commands can tell the graphics and audio processor 114 to draw a particular image onto display device 56. Commands might also tell the graphics and audio processor 114 to produce a particular sound for output by loudspeakers 61. Still other commands might tell the graphics and audio processor 114 to perform so-called “housekeeping” commands and/or to set up a particular state in preparation for a subsequent “action” command.
[0094] In the example embodiment, the commands that main processor 110 sends to graphics and audio processor 114 can come from a number of sources. One source of commands is the main processor 110 itself. Under control of program instructions provided, for example, by mass storage access device 106 and/or boot ROM 134, main processor 110 can dynamically create or generate graphics commands under program control to send to graphics and audio processor 114. Main processor 110 can create and send graphics and audio processor 114 any command that the graphics and audio processor understands. Graphics and audio processor 114 will act on the commands and perform the action requested by the command.
[0095] Another source of graphics commands for graphics and audio processor 114 is mass storage access device 106. It takes some time for main processor 110 to dynamically create graphics commands. When system 50 is animating a scene in response to real-time inputs from hand controllers 52 or the like, there may be no alternative other than for main processor 110 to dynamically create the graphics commands telling the graphics and audio processor 114 to draw a particular cartoon or other character in a particular position. That way, as the user operates hand controllers 52 of system 50 responds to other input devices, main processor 110 can dynamically adjust or animate the displayed scene in response to those real-time inputs to provide interactive animation. Such fun and exciting interactive animation is generally provided by main processor 110 dynamically creating graphics commands “on the fly.”
[0096] Sometimes, however, some part of a scene to be displayed is relatively static and does not change in response to real-time inputs. For example, a complicated 3D world background such as a castle, a mountain fortress, a landscape or an undersea world may not change much or at all as animated characters move through the world. In such cases, it is possible to use an offline authoring computer to develop the complex series of graphics commands required to draw the particular scene or portion of the scene and store them in a preconstructed is display list. Similarly, sound effects, music and other sounds can be pre-generated off-line by a sound authoring system. The resulting display list(s) and/or audio list(s) can be stored on an optical disk 62 or other mass storage device. When it comes time to draw the scene and/or play the sound, the associated display list(s) and/or audio list(s) can simply be read from the mass storage device 62 and stored into main memory 112. Main processor 110 may then, under program control, tell the graphics and audio processor 114 where to find the preconstructed display list(s) and/or audio list(s), and instruct the graphics and audio processor to execute the lists. In this way, main processor 110 does not have to devote its processing resources to develop complicated display lists and/or audio lists since that task is off-loaded to an off-line authoring system that pre-compiles the lists in preparation for use by the graphics and audio processor 114. Such display lists can be stored by any storage device within system 50 or accessible to it, including but not limited to memory card 144, flash memory 140, boot ROM 134, audio memory 126, etc. The commands could be embedded in hardware such as gate arrays or the like, and communicated to system 50 via any of the external interfaces such as bus 142, bus 132, handheld controller ports, parallel bus 130, infrared, etc.
[0097] Still another possibility is for commands intended for processing by the graphics and audio processor 114 to arrive via a data communications connection such as network 138. In one example, graphics commands, audio commands and/or other commands intended to be processed by graphics and audio processor 114 may arrive from a data communications network 138 via modem 136. Such commands could be transmitted, for example, from a remote system 50 of the same configuration as that shown in FIG. 2 in order to provide interactive multi-user remote game play. The commands could originate from any other source including a personal computer, a mini-computer or main frame computer, a data transmitter, or any other data source.
[0098] Irrespective of how commands intended for graphics and audio processor 114 arrive and how they are stored before and/or after arrival, the first step in causing such commands to be processed by the graphics and audio processor 114 is to make them available to the graphics and audio processor. In the example embodiment, making the commands available to graphics and audio processor 114 can be accomplished either by having main processor 10 send the commands directly to the graphics and audio processor via a data bus in an immediate mode of command transfer, or by storing the commands in some memory accessible to the graphics and audio processor 114 (e.g., main memory 112, audio memory 126, or any other memory device to which the graphics and audio processor 114 is coupled) and informing the graphics and audio processor where to find the commands and instructing it to begin processing those commands.
[0099] Graphics Command Stream
[0100] In the example embodiment, graphics and audio processor 114 may receive register and other commands from main processor 110 and/or some other source (e.g., main memory 112) in the form of a graphics command stream. Generally, the data that is sent from main processor 110 to the graphics and audio processor 114 can be called the “command stream.” The command stream holds drawing commands along with vertices and their attributes and mechanisms for loading registers and changing modes in the graphics pipeline 180. The stream of graphics commands are sent to the graphics and audio processor 114 for processing in a generally sequential manner. Such stream commands can be provided in a so-called “immediate mode” directly from main processor 110 to the graphics and audio processor 114 through a write gatherer arrangement (see FIG. 4) to provide very efficient transfer of graphics and audio commands from the main processor 110 to the graphics and audio processor 114. The graphics command stream can also be provided to graphics and audio processor 114 via main memory 112 or other memory or other data communications capabilities within system 50. The cache/command processor 200 within the graphics and audio processor 114 performs tasks such as, for example, fetching the command stream from main memory 112; fetching vertex attributes (e.g., either from the command stream or from arrays in main memory); converting attribute types to appropriate formats (e.g., floating point); and transferring complete vertices to the remainder of the graphics pipeline 180 for processing.
[0101] As shown in FIG. 5, the command stream is fetched from the first-in-first-out buffer 210 (see also above-referenced Provisional Application No. 60/226,912, filed Aug. 23, 2000 and its corresponding utility application No. 09/726,215, filed Nov. 28, 2000 (atty. dkt. no. 723-959), both entitled “Method and Apparatus for Buffering Graphics Data in a Graphics System ”, and read into a FIFO buffer 216. The command processor 200 strips and decodes the commands to decide the number of data associated with it. The data is then taken from the stream and/or fetched from an array in main memory 112, based on an index value. The vertex attributes are converted to floating, point data that can be consumed by the transform engine 300.
[0102] The following, are example command stream formats in the example embodiment:
| TABLE I | |||
|---|---|---|---|
| Opcode | Opcode(7:0) | Next | Followed by |
| NOP | 00000000 | none | none |
| Draw_Quads | 10000vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_ Triangles | 10010vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_Triangle_strip | 10011vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_ Triangle_ fan | 10100vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_ Lines | 10101vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_ Line_strip | 10110vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| Draw_ Points | 10111vat(2:0) | VertexCount(15:0) | Vertex attribute stream |
| CP_LoadRegs | 00001xxx | Address[7:0] | 32 bits data |
| (for CP only registers) | |||
| XF_LoadRegs | 00010xxx | none | (N+2)*32 bits |
| (This is used for | First 32 bit: | ||
| loading all XF | 15:00 register address in XF | ||
| registers, including | 19:16 number of 32 bit registers to be | ||
| matrices. It can be | loaded (N+1, 0 means 1, 0xff means 16) | ||
| used to load matrices | 31:20 unused | ||
| with immediate data) | Next N+1 32 bits: | ||
| 31:00 register data | |||
| XF_IndexLoadRegA | 00100xxx | none | 32 bits |
| (registers are in the | 11:0 register address in XF | ||
| first 4K address space | 15:12 number of 32 bit data, (0 means 1, | ||
| of the XF. It can be | 0xff means 16) | ||
| used to block load | 31:16 Index to the register Array A | ||
| matrix and light | |||
| registers) | |||
| XF_IndexLoadRegB | 00101xxx | none | 32 bits |
| (registers are in the | 11:0 register address in XF | ||
| first 4K address space | 15:12 number of 32 bit data, (0 means 1, | ||
| of the XF. It can be | 0xff means 16) | ||
| used to block load | 31:16 Index to the register Array B | ||
| matrix and light | |||
| registers) | |||
| XF_IndexLoadRegC | 00110xxx | none | 32 bits |
| (registers are in the | 11:0 register address in XF | ||
| first 4K address space | 15:12 number of 32 bit data. (0 means 1, | ||
| of the XF. It can be | 0xff means 16) | ||
| used to block load | 31:16 Index to the register Array C | ||
| matrix and light | |||
| registers) | |||
| XF_IndexLoadRegD | 00111xxx | none | 32 bits |
| (registers are in the | 11:0 register address in XF | ||
| first 4K address space | 15:12 number of 32 bit data, (0 means 1, | ||
| of the XF. It can be | 0xff means 16) | ||
| used to block load | 31:16 Index to the register Array D | ||
| matrix and light | |||
| registers) | |||
| Call_Object | 01000xxx | none | 2x32 |
| 25:5 address (need to be 32 byte align) | |||
| 25:5 count (32 byte count) | |||
| V$ Invalidate | 01001xxx | none | none |
| SU_ByPassCmd | 0110,SUattr(3:0) | none | 32 bit data |
| (This includes all the | |||
| register load below XF | |||
| and all setup unit | |||
| commands, which | |||
| bypass XF) | |||
[0103] As shown in Table I above, the graphics command stream can include register load commands. Register commands are, in general, commands that have the effect of writing particular state information to particular registers internal to the graphics and audio processor 114. The graphics and audio processor 114 has a number of internal registers addressable by main processor 110. To change the state of the graphics and audio processor 114 in particular way, main processor can write a particular value to a particular register internal to the graphics and audio processor 114. Register commands have the advantage of allowing the graphics pipeline to retain drawing state information that main processor 110 can selectively change by sending further register load commands.
[0104] For example, the vertices in a draw command can all share the same vertex attribute data structure defining a number of attributes associated with a vertex. Sending all of the vertex attribute information before a draw command could be costly. It therefore may be desirable to store most of the common vertex types in registers within the graphics and audio processor 114, and to simply pass an index to the stored table. These tables may not need to be updated each time a new draw command is sent down, but may only need to be updated every once in a while. In the example embodiment, command processor 200 holds a vertex command descriptor register (VCD) and a eight-entry vertex attribute table (VAT) defining whether the attribute is present and if so whether it is indexed or direct. A “load_VCD” register command is used to update the register whenever updating is necessary.
[0105] In certain situations, main processor 110 may also read the graphics and audio processor 114 internal registers to determine the state of the graphics and audio processor. For example, the main processor 110 can start and stop the graphics and audio processor 114 and/or determine its general status by reading from and/or writing to internal registers within the graphics and audio processor. Main processor 110 can also load a number of graphics values (e.g., transformation matrices, pixel formats, vertex formats, etc.) by writing to registers within the graphics and audio processor 114. As another example, main processor 110 can write to a series of FIFO control registers within the graphics and audio processor 114 that control where the graphics and audio processor 114 obtains further commands for processing.
[0106] The following are example command registers used for defining transformation matrices, vertex control data, vertex attribute tables, vertex arrays, vertex stride, and other state parameters:
| TABLE II | ||
|---|---|---|
| Register name | Register address[7:0] | Bit fields |
| MatrixIndexA | 0011xxxx | 5:0 index for position/ |
| normal matrix | ||
| 11:6 index for tex0 matrix | ||
| 17:12 index for tex1 matrix | ||
| 23:18 index for tex2 matrix | ||
| 29:24 index for tex3 matrix | ||
| MatrixIndexB | 0100xxxx | 5:0 index for tex4 matrix |
| 11:6 index for tex5 matrix | ||
| 17:12 index for tex6 matrix | ||
| 23:18 index for tex7 matrix | ||
| VCD_Lo | 0101xxxx | 16:00 VCD 12 to 0 |
| 0 PosMatIdx | ||
| 1 Tex0MatIdx | ||
| 2 Tex1MatIdx | ||
| 3 Tex2atIdx | ||
| 4 Tex3MatIdx | ||
| 5 Tex4MatIdx | ||
| 6 Tex5MatIdx | ||
| 7 Tex6MatIdx | ||
| 8 Tex7MatIdx | ||
| 10:9 Position | ||
| 12:11 Normal | ||
| 14:13 ColorDiffused | ||
| 16:15 ColorSpecular | ||
| VCD_-Hi | 0110xxxx | 15:00 VCD 20 to 13 |
| 01:00 Tex0Coord | ||
| 03:02 Tex1Coord | ||
| 05:04 Tex2Coord | ||
| 07:06 Tex3Coord | ||
| 09:08 Tex4Coord | ||
| 11:10 Tex5Coord | ||
| 13:12 Tex6Coord | ||
| 15:14 Tex7Coord | ||
| VAT_group0 | 0111x,vat[2:0] | 32 bits |
| 08:00 Position parameters | ||
| 12:09 Normal parameters | ||
| 16:13 ColorDiffused para- | ||
| meters | ||
| 20:17 ColorSpecular para- | ||
| meters | ||
| 29:21 Tex0Coord parameters | ||
| 30:30 ByteDequant | ||
| 31:31 NormalIndex3 | ||
| VAT_group1 | 1000x,vat[2:0] | 32 bits |
| 08:00 Tex1Coord parameters | ||
| 17:09 Tex2Coord parameters | ||
| 26:18 Tex3Coord parameters | ||
| 30:27 Tex4Coord para- | ||
| meters sub-field[3:0] | ||
| 31unused | ||
| VAT_group2 | 1001x,vat[2:0] | 32 bits |
| 04:00 Tex4Coord para- | ||
| meters sub-field[8:4] | ||
| 13:05 Tex5Coord parameters | ||
| 22:14 Tex6Coord parameters | ||
| 31:23 Tex7Coord parameters | ||
| ArrayBase | 1010,array[3.0] | 32 bit data |
| array[3.0]: | 25:00 Base(25:0) |
[0107] In the example embodiment, the command processor 200 converts the command stream to a vertex stream which it sends to transform unit 300 for further processing. The vertex stream sent to the transform unit 300 can change based on the current mode, but the data ordering per vertex is essentially the same and is fixed as shown in the following table:
| TABLE III | ||
|---|---|---|
| Location in stream | ||
| (in words) | Data | Description |
| 0 to 2 | X, Y, Z in 32b SPFP | Geometry information in |
| single precision floating | ||
| point format | ||
| 3 to 5 | Nx, Ny, Nz in | Normal vector |
| 32b SPFP | ||
| 6 | RGBA in 32b integer | Color0 per vertex (RGBA) |
| (8b/comp) | ||
| 7 | RGBA in 32b integer | Color1 per vertex (RGBA) |
| (8b/comp) | ||
| 8 to 10 | Tx, Ty, Tz in | Binormal vector T |
| 32b SPFP | ||
| 11 to 13 | Bx, By, Bz in | Binormal vector B |
| 32b SPFP | ||
| 14 to 15 | S0, T0 in 32b SPFP | Texture 0 data |
| 16 to 29 | Sn, Tn in 32b SPFP | Texture 1 to n data |
[0108] The location of words in the stream is order dependent, but not exact. For example, if the per-vertex color is not supplied, then the first texture will start at word 6 instead of word 8. Texture comes after color.
[0109] Example Graphics Application Processing Loop
[0110] FIG. 6 shows an example summary flow chart of steps that may be performed by system 50 under control of an application such as a video game program to develop graphics for display on the display 56. System 50 is first booted from boot ROM 134 (block 610). During or after system boot, main processor 110 and graphics and audio processor 114 are initialized and the operating system is also initialized (block 612). System 50 is then ready to have its logic set up for a specific application, such as a videogame (block 614). The state of the graphics and audio processor 114 is set by sending an appropriate graphics command stream to the graphics and audio processor (block 616). The system 50 is then ready to process vertex information provided through a further command stream describing a primitive in terms of vertex data structure, and draw commands (block 618). Once the embedded frame buffer 702 has a completed frame of data, further commands sent to the graphics and audio processor 114 cause the processor to copy its embedded frame buffer to an external frame buffer 113 allocated in main memory 112 (block 620). The video interface 164 is then used to display the image data in the external frame buffer on a display device (block 622). Once a completed frame is copied from the embedded frame buffer, the system is ready to begin processing the next frame, as indicated by the frame loop 624 in FIG. 6. FIG. 7 shows is greater detail some of the possible graphics commands that can be performed in connection with each of the various steps shown in FIG. 6.
[0111] Example Simple Graphics Command Stream
[0112] For purposes of illustration FIG. 8 shows an example simple graphics command stream drawing a single graphics primitive (e.g., a single triangle) on display 56. In this example simple graphics command stream, the first set of graphics commands initializes the graphics pipeline 180 (GXInit( )) (block 1002). When the graphics and audio processor 114 comes out of hardware reset, its internal register values are undefined and therefore need to be set by main processor 110 under control of boot ROM 134 and/or the application program. A series of initialization commands such as register load commands may be issued to set the state of graphics and audio processor 114 to a known, pre-defined state that is suitable for the particular application that is to be performed. Of course, the application can reset any of these values to any other desired value on a dynamic basis. However, to save the application work, it may be desirable for boot ROM 134 to provide a series of state-setting graphics initialization commands that set up the graphics and audio processor 114 so that it is operating in a known functioning default graphics mode.
[0113] One example initialization may be to clear (set) the internal embedded frame buffer 702 to an all-black color value with z (distance) of the corresponding embedded depth buffer being set to infinite distance at each location. Such a “set copy clear” instruction effectively sets up a clean canvas onto which graphics and audio processor 114 can draw the next image, and is re-formed during an embedded frame buffer copy operation in the example embodiment. FIG. 9 shows an example binary data stream that may be sent to the graphics and audio processor 114 to control it to clear (set) its internal frame buffer 113 to a black color at each and every pixel location and to set the corresponding internal depth buffer to infinite distance at every pixel. In the particular example shown, such a command stream comprises three pixel engine register load commands:
[0114] pixel engine copy clear (alpha red),
[0115] pixel engine copy clear (green blue),
[0116] pixel engine copy clear (z).
[0117] In this example, the first portion of each register load command includes a “cp_cmd_su_bypass” command string (0x61) (where “0x” indicates hexadecimal). As explained in Table I above, this command string provides access to registers within graphics pipeline 180 below transform unit 300. This string is followed by a pixel engine register designation (0x4F in the case of a pixel engine copy clear alpha/red command), a 1-byte pad; and a 1-byte alpha value and a 1-byte red value (FF for black).
[0118] A similar format is used for the pe_copy_clear_green blue command except that the last two bytes indicate the green and blue values (FF for black), and a different pixel engine register designation (0x50) is used for the green/blue register values. Similarly, the pe_copy_clear_z command is issued by sending a cp_cmd_su_bypass string (0x61) followed by a register designator 0x51 (designating a pixel engine z value register) followed by a 24-bit z (depth) value. The three set copy clear commands shown n FIG. 9 could be issued in any order (e.g., set z copy clear or set green/blue copy clear could be issued first). See FIG. 9A which shows example register formats.
[0119] In response to receipt of the FIG. 9 commands, pixel engine 700 writes the specified alpha, red, green, blue and z values into embedded frame buffer 702.
[0120] Referring once again to FIG. 8, a next step in preparing to display an image onto display 56 may be to define the various data structures associated with the vertices of the primitive to be drawn. The FIG. 10 diagram shows, for purposes of illustration, example vertex and vertex attribute descriptors that can be used to describe vertices. In the example embodiment, all vertices within a given primitive share the same vertex descriptor and vertex attribute format. The vertex descriptor in the example embodiment describes which attributes are present in a particular vertex format and how they are transmitted from the main processor 110 (or other source) to the graphics processor 114 (e.g., either direct or indexed). The vertex attribute format describes the format (e.g., type, size, format, fixed point scale, etc.) of each attribute in a particular vertex format. The vertex attribute format together with the vertex descriptor may be thought of as the overall vertex format.
[0121] The following is an example of a vertex attribute table (VAT) (see also above-referenced application Ser. No. 09/465,754 filed Dec. 17, 1999 entitled “Vertex Cache For 3D Computer Graphics”) indexed by a draw command “vat” field, with each entry in the table specifying characteristics for all of the thirteen attributes:
| TABLE IV |
|---|
| VERTEX ATTRIBUTE TABLE (VAT) |
[0122] As described in application Ser. No. 09/465,754, as well as above, entries in the vertex descriptor information can be either direct or indexed. Indexed vertex attributes include an index to an array instead of a value. The index may be an 8-bit or 16-bit pointer into an array of attributes. In the example embodiment, there is one base address register per attribute in the command processor 200. The index is not simply an offset into the array, but rather depends on a number of factors including, for example, the number of components in the attribute; the size of the component; padding between attributes for alignment purposes; and whether multiple attributes are interleaved in the same array. To provide maximum flexibility, there is also an array stride register for each attribute. The distance between two attributes (computed by software) is loaded into this register. Calculations are used to calculate the offset and to calculate the actual memory address based on an index value. An example address calculation is as follows:
[0123] Memory address=ArrayBase[I]+index*ArrayStride[I],
[0124] where I is the attribute number. In one particular implementation, the ArrayBase value is a 26-bit byte address, and ArrayStride is an 8-bit value.
[0125] A vertex can have direct and indirect attributes intermixed. For short values, it may be more efficient to send the actual value than a pointer to the value.
[0126] Any attribute in the example embodiment can be sent directly or as in index into an array.
[0127] In general, the steps required to draw a primitive include describing which attributes are present in the vertex format (i.e., define the vertex attribute table); describing whether the attributes are indexed or referenced directly (i.e., define the vertex descriptor); for indexed data, delivering a vertex array that can be referenced by array pointers and strides; describing the number of elements in each attribute and their type; describing the primitive type; and then, finally, drawing the primitive by sending the graphics processor 114 draw command with a stream of vertices that match the vertex description in attribute format (see FIG. 8, blocks 1004, 1006, 1008).
[0128] FIG. 11 shows an example “set array” command used to help define a vertex format (see FIG. 8 block 1004, “Define and Align Vertex Arrays”). In the example embodiment, the example “set array” command sets the command processor array base register for a particular vertex array and also sets the array stride register for the array. FIG. 11 shows particular example binary bit patterns that may be used for this command. In this example, to set an array base register, the graphics command stream may include:
[0129] an initial “0x08” value indicating “cp_cmd_load reg” (i.e., load a command processor 200 register) followed by
[0130] a 2-byte value indicating which array base register is to be loaded, followed by
[0131] an additional 4-byte value providing an address to the array in memory.
[0132] In this particular example, the 2-byte value indicating which array base register is to be loaded has the format “0xAx”, where the byte “x” following the “A” value encodes a particular one of the attributes set forth in Table IV above. Note that some of the Table IV attributes (i.e., the matrix indices) are not included in the encoding in the example embodiment. In the example embodiment, the 4-byte address in memory is encoded by providing six initial bits of 0 padding followed by a 26-bit address. Setting the array stride register value is similar except that the third and fourth bytes indicate an array stride register (e.g., “0xBx” and the following value comprises four bytes containing an initial 24-bit 0 padded value and an 8-bit stride value for the array.
[0133] Referring once again to FIG. 8, a further step preliminary to issuing a draw command may be to set up a vertex descriptor and a vertex attribute table (block 1006). FIG. 12 shows an example command stream used to set a vertex descriptor. In the example embodiment, setting a vertex descriptor involves setting two associated register values (“vcd_lo” “vcd_hi”) within command processor 200 in order to specify the particular vertex descriptor attributes associated with the primitive to be displayed. FIG. 12 shows particular binary encodings used to tell the graphics and audio processor 114 to load the vcd_lo and vcd_hi registers (e.g., “0x0850” for an example vcd_lo register and “0x0860” to specify loading a cp_vcd_hi register). Values following each of these 4-byte commands indicates particular vertex attribute values as shown in Table 4 above, and as encoded in the particular binary bit patterns slots shown in FIG. 12.
[0134] In more detail, the vertex descriptor stored in the VCD_lo VCD_hi register includes at least one bit for each of the twenty attributes shown in Table IV, that bit generally indicating whether the attribute is provided directly or via an array. In the example embodiment, the VCD_lo register contains a 17-bit value, providing bit flags indicating direct or indexed for each of the first twelve attributes in Table IV. The particular bit encodings are shown in the last column of Table IV. Note that certain attribute encodings indicate whether or not the attribute is present (since the attribute is always direct if it is present), and certain other encodings span multiple bits and provide information as to the type of index if the attribute is indexed (e.g., the “position” value may span two bits with a value “01” for direct, “10” for 8-bit index, and “11” for 16-bit index). Similarly, the VCD-hi register contains bit fields corresponding to attributes 13-20 (i.e., texture 0 coordinate through texture 7 coordinate) as shown in Table IV above.
[0135] On a more abstract level, the GXSetVtxDesc command is used to indicate whether an attribute is present in the vertex data, and whether it is indexed or direct. There is only one active vertex descriptor, known as the current vertex descriptor. A GXSetVtxDesc command can be used to set a value of GX_NONE for all the attributes in the current vertex descriptor to indicate that no data for this attribute will be present in the vertex. Once the VCD registers are cleared, the application only needs to describe attributes that it intends to provide. As shown in Table IV, possible attributes are:
[0136] Position, GX_VA_POS (this attribute is required for every vertex descriptor).
[0137] Normal, GX_VA_NRM, or normal/binormal/tangent, GX_VA_NBT.
[0138] Color—0, GX_VA_CLR0.
[0139] Color—1, GX_VA_CLR1.
[0140] Up to 8 texture coordinates, GX_VA_TEXO—7.
[0141] A position/normal matrix index, GX_VA_PNMTXIDX.
[0142] A texture matrix index, GX_VA_TEX0MTXIDX-GX_VA_TEX7MTXIDX.
[0143] The last two attributes listed are 8-bit indices which are used for referencing a transformation matrix in the on-chip matrix memory. This supports simple skinning of a character, for example. These indices are different from the other attributes in that they may only be sent as direct data.
[0144] The graphics processor (GP) 114 assumes that the application will send any attribute data you have specified in the ascending order shown in Table IV, that is:
[0145] Order Attribute
[0146] 0 GX_VA_PNMTXIDX
[0147] 1 GX_VA_TEX0MTXIDX
[0148] 2 GX_VA_TEX1MTXIDX
[0149] 3 GX_VA_TEX2MTXIDX
[0150] 4 GX_VA_TEX3MTXIDX
[0151] 5 GX_VA_TEX4MTXIDX
[0152] 6 GX_VA_TEX5MTXIDX
[0153] 7 GX_VA_TEX6MTXIDX
[0154] 8 GX_VA_TEX7MTXIDX
[0155] 9 GX_VA_POS
[0156] 10 GX_VA_NRM or GX_VA_NBT
[0157] 11 GX_VA_CLR0
[0158] 12 GX_VA_CLR1
[0159] 13 GX_VA_TEX0
[0160] 14 GX_VA_TEX1
[0161] 15 GX_VA_TEX2
[0162] 16 GX_VA_TEX3
[0163] 17 GX_VA_TEX4
[0164] 18 GX_VA_TEX5
[0165] 19 GX_VA_TEX6
[0166] 20 GX_VA_TEX7
[0167] Texture coordinates are enabled sequentially, starting at GX_VA_TEX0.
[0168] Describing Attribute Data Formats
[0169] FIGS. 13A and 13B show an example command stream for setting vertex attribute formats. The Vertex Attribute Format Table (VAT) allows the application to specify the format of each attribute for up to eight different vertex formats. The VAT is organized as shown in FIG. 14. The application can store eight predefined vertex formats in the table. For each attribute in a vertex, the applicaiton can specify the following:
[0170] The number of elements for the attribute.
[0171] The format and size information.
[0172] The number of fractional bits for fixed-point formats using the scale parameter (the scale parameter is not relevant to color or floating-point data).
Example Vertex Attribute Format Command (GXSetVtxAttrFmt)
[0173] //format index attribute n elements format n frac bits
[0174] GXSetVtxAttrFmt(GX_VTXFMT0, GX_VA_POS, GX_POS_XYZ, GX_S8, 0);
[0175] GXSetVtxAttrFmt(GX_VTXFMT0, GX_VA_CLR0, GX_CLR_RGBA, GX_RGBA8, 0);
[0176] The high-level code above defines vertex attribute format zero. GX_VTXFMT0 indicates that “position” is a 3-element coordinate (x, y, z) where each element is an 8-bit 2's complement signed number. The scale value indicates the number of fractional bits for a fixed-point number, so zero indicates that the data has no fractional bits. The second command specifies that the GX_VA_CLR0 attribute has four elements (r, g, b, a) where each element is 8 bits. The matrix index format is not specified in the table because it is always an unsigned 8-bit value. The scale value is implied for normals (scale=6 or scale=14) and not needed for colors. Also, normals are assumed to have three elements, Nx, Ny, Nz (for GX_VA_NRM), and nine elements, Nx, Ny, Nz, Bx, By, Bz, Tx, Ty, Tz (for GX_VA_NBT). Normals are generally always signed values. The normal format (GX_VA_NRM) is also used for binormals/tangents (GX_VA_NBT) when they are enabled in the current vertex descriptor. The VAT in the Graphics Processor has room for eight vertex formats. The application can describe most of its attribute quantization formats early in the application, loading this table as required. Then the application provides an index into this table, which specifies the vertex attribute data format, when it starts drawing a group of primitives. If the application requires more than eight vertex formats it must manage the VAT table by reloading new vertex formats as needed.
[0177] FIGS. 13A and 13B show example binary-level commands for controlling the graphics and audio processor 114 to load an example vertex attribute table (VAT). In the example embodiment, the VAT spins three separate register loads (VAT_A, VAT_B, VAT_C) so that setting a vertex attribute format involves writing values to three internal “VAT” registers within the graphics and audio processor 114, i.e.:
[0178] “0x0870” [4-byte value] to write to the cp_VAT_A register,
[0179] “0x880” [4-byte value] to write to the cp_VAT_B register, and
[0180] “0x0890” [4-byte value] to write to the cp_VAT_C register.
[0181] As shown in FIG. 13A, the binary bit field encoding for the VAT_A register write involves providing position, normal, color 1, color 2, texture 0 coordinate, and other information (i.e., byte dequantization and normal index bits) in the binary pattern slots shown. Similarly, the binary bit field encoding for the VAT B register write invovlves providing formatting information for texture coordinate 1, texture coordinate 2, texture coordinate 3 and part of texture coordinate 4; and the information to be stored in the VAT_C register provides attribute format information for the rest of texture coordinate 4, texture coordinate 5, texture coordinate 6 and texture coordinate 7. FIGS. 13A and 13B show the particular bit pattern encodings that may be used. Additional explanation of these particular attributes is set forth in Table V:
| TABLE V | |||||
|---|---|---|---|---|---|
| Bit | Attribute | Attribute | .CompCount | .CompSize | .Shift amount |
| field | number | name | sub-field(0) | sub-field(3:1) | sub-field(8:4) |
| 8:0 | 9 | Position | 0: two (x,y) | 0:ubyte 1:byte 2:ushort | Location of decimal point |
| 1: three | 3:short 4:float 5-7 | from LSB. This shift applies | |||
| (x,y,z) | reserved | to all u/short components and | |||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 12:9 | 10 | Normal | 0: three | 0:reserved 1:byte | NA (Byte: 6, Short:14) |
| normals | 2:reserved | ||||
| 1: nine | 3:short 4:float 5-7 | ||||
| normals | reserved | ||||
| 16:13 | 11 | Color0 | 0: three | 0: 16 bit 565 (three comp) | NA |
| (r,g,b) | 1: 24 bit 888 (three comp) | ||||
| 1: four | 2: 32 bit 888x (three | ||||
| (r,g,b,a) | comp) | ||||
| 3: 16 bit 4444 (four comp) | |||||
| 4: 24 bit 6666 (four comp) | |||||
| 5: 32 bit 8888 (four comp) | |||||
| 20:17 | 12 | Color1 | 0: three | 0: 16 bit 565 (three comp) | NA |
| (r,g,b) | 1: 24 bit 888 (three comp) | ||||
| 1: four | 2: 32 bit 888x (three comp) | ||||
| (r,g,b,a) | 3: 16 bit 4444 (four comp) | ||||
| 4: 24 bit 6666 (four comp) | |||||
| 5: 32 bit 8888 (four comp) | |||||
| 29:21 | 13 | Tex0Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 38:30 | 14 | Tex1Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 47:39 | 15 | Tex2Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 56:48 | 16 | Tex3Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 65:57 | 17 | Tex4Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 74:66 | 18 | Tex5Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 83:75 | 19 | Tex6Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 92:84 | 20 | Tex7Coord | 0: one (s) | 0:ubyte 2:ushort 4:float | Location of decimal point |
| 1: two (s,t) | 1:byte 3:short 5-7 | from LSB. This shift applies | |||
| reserved | to all u/short components and | ||||
| to u/byte components where | |||||
| ByteDequant is asserted | |||||
| (Below). | |||||
| 93:93 | FLAG | ByteDequant | (Rev B Only) | 0: Shift does not apply to | Shift applies for u/byte |
| u/byte | components of position and | ||||
| 1: Shift does apply to | texture attributes. | ||||
| u/byte | |||||
| 94:94 | FLAG | NormalIndex3 | (Rev B Only) | 0: Single index per Normal | When nine normals selected |
| 1: Triple index per nine- | in indirect mode, input will | ||||
| Normal | be treated as three staggered | ||||
| indices (one per triple biased | |||||
| by component size), into | |||||
| normal table. | |||||
| NOTE!! | |||||
| First index internally biased | |||||
| by 0. | |||||
| Second index internally | |||||
| biased by 1. | |||||
| Third index internally | |||||
| biassed by 2. | |||||
[0182] Defining and Drawing Graphics Primitives
[0183] FIG. 15 illustrates some of the different types of primitives supported by the graphics system 50, including:
[0184] GX_POINTS—draws a point at each of the n vertices.
[0185] GX_LINES—draws a series of unconnected line segments. Segments are drawn between v0 and v1, v2 and v3, etc. The number of vertices drawn should be a multiple of 2.
[0186] GX_LINESTRIP—draws a series of connected lines, from v0 to v1, then from v1 to v2, and so on. If n vertices are drawn, n-1 lines are drawn.
[0187] GX_TRIANGLES—draws a series of triangles (three-sided polygons) using vertices v0, v1, v2, then v3, v4, v5, and so on. The number of vertices drawn should be a multiple of 3 and the minimum number is 3.
[0188] GX_TRIANGLSTRIP—draws a series of triangles (three-sided polygons) using vertices v0, v1, v2, then v1, v3, v2 (note the order), then v2, v3, v4, and so on. The number of vertices must be at least 3.
[0189] GX_TRIANGLEFAN—draws a series of triangles (three-sided polygons) using vertices v0, v1, v2, then v0, v2, v3, and so on. The number of vertices must be at least 3.
[0190] GX_QUADS—draws a series of non-planar quadrilaterals (4-sided polygons) beginning with v0, v1, v2, v3, then v4, v5, v6, v7, and so on. The quad is actually drawn using two triangles, so the four vertices are not required to be coplanar. It is noted that the diagonal common edge between the two triangles of a quad is oriented as shown in FIG. 11. The minimum number of vertices is 4.
[0191] The application draws primitives by calling vertex functions (GXPosition, GXColor, etc.) between GXBegin/GXEnd pairs. The application should call a vertex function for each attribute it enables using GXSetVtxDesc( ). Each vertex function has a suffix of the form GXData[n][t], which describes the number (n) and type (t) of elements passed to the vertex function.
[0192] The following case fragment demonstrates how to draw primitives using vertex functions:
[0193] GXBegin(GX_TRIANGLES, GX_VTXFMT0, 3);
[0194] GXPosition1x8(0); //index to position
[0195] GXColor1x16(0); //index to color
[0196] GXPosition1x8(1);
[0197] GXColor1x16(1);
[0198] GXPosition1x8(2);
[0199] GXColor1x16(2);
[0200] GXEnd( );
[0201] GXBegin specifies the type of primitive, an index into the VAT, and the number of vertices between the GXBegin/GXEnd pair. This information, along with the latest call to GXSetVtxDesc( ), fully describes the primitive, vertex, and attribute format. GXEnd( ) is actually a null macro that can be used to make sure that GXBegin and GXEnd are paired properly.
[0202] Loading a Projection Matrix
[0203] FIG. 16 shows an example binary bit stream used to load a projection matrix into transform unit 300 (see FIG. 8, block 1004). As described above in connection with FIG. 8, the application generally defines a projection matrix in order to transform a primitive from one space into another space (e.g., object space to world space). The transform unit 300 automatically transforms the vertices in the primitive using this projection matrix.
[0204] FIG. 16 shows an example binary bit stream that can be used to load a projection matrix into transform unit 300. In the example embodiment, this loading process involves sending a binary bit pattern of “0x10” to the graphics and audio processor 114 indicating “cp_cmd_xf_loadregs” followed by a 4-byte value. In this 4-byte value, the first eleven bits are 0 padding and the succeeding bits indicate a register address within the transform unit 300 (bits 0-15) and the number of 32-bit registers within the transform unit to be loaded (bits 16-19). Following these bit patterns are a sequence of from one to sixteen 32-bit words specifying projection matrix values.
[0205] In the example embodiment, every register in the transform unit 300 is mapped to a unique 32b address. All addresses are available to the xform register load command (command 0x30). The first block is formed by the matrix memory. Its address range is 0 to 1k, but only 256 entries are used. This memory is organized in a 64 entry by four 32b words. Each word has a unique address and is a single precision floating point number. For block writes, the addresses auto increment. The memory is implemented in less than 4-32b rams, then it is possible that the memory writes to this block will require a minimum write size larger than 1 word:
| Register Address | Definition | Configuration | |
|---|---|---|---|
| 0x0000 | Matrix Ram word 0 | 32b matrix data | |
| 0x0001-0x00ff | Matrix Ram word (n) | 32b matrix data | |
| 0x0100-0x03ff | Not used | ||
[0206] The second block of memory is mapped to the 1k˜1.5k range. This memory is the normal matrix memory. It is organized as 32 rows of 3 words. Each word has a unique address and is a single precision floating point number. Also, each word written is 32b, but only the 20 most significant bits are kept. For simplicity, the minimum granularity of writes will be 3 words:
| Register Address | Definition | Configuration |
|---|---|---|
| 0x0400-0x402 | Normal Ram words 0,1,2 | 20b data |
| 0x0403-0x045f | Normal Ram word (n) | 20b data |
| 0x0460-0x05ff | Not used | |
[0207] The third block of memory holds the dual texture transform matrices. The format is identical to the first block of matrix memory. There are also 64 rows of 4 words for these matrices. These matrices can only be used for the dual transform of regular textures:
| Register Address | Definition | Configuration |
|---|---|---|
| 0x0500 | Matrix Ram word 0 | 32b matrix data |
| 0x0501-0x05ff | Matrix Ram word (n) | 32b matrix data |
[0208] The fourth block of memory is the light memory. This holds all the lighting information (light vectors, light parameters, etc.). Both global state and ambient state are stored in this memory. Each word written is 32b, but only the 20 most significant bits are kept. Each row is 3 words wide. Minimum word write size is 3 words.
[0209] Example Call Display List Command
[0210] As described in the above-referenced patent application No. 09/726,215, filed Nov. 28, 2000 (atty. dkt. no. 723-959) entitled “Method and Apparatus for Buffering Graphics Data in a Graphics System,” system 50 includes a capability for calling a display list. FIG. 17 shows an example binary bit stream format used to call a display object such as a display list. In the example shown, the binary bit pattern format includes an initial “0x40” indicating “CP_CMD_CALLOBJECT”, followed by a 4-byte address of the display list in memory as well as a 4-byte count or size of the display list. The 4-byte address field may include an initial seven bits of 0 padding followed by a 25-bit value. The 4-byte count value may include an initial seven bits of padding followed by a 25-bit count value indicating the count or size of the display list in 32-byte chunks.
[0211] Other Example Compatible Implementations
[0212] Certain of the above-described system components 50 could be implemented as other than the home video game console configuration described above. For example, one could run graphics application or other software written for system 50 on a platform with a different configuration that emulates system 50 or is otherwise compatible with it. If the other platform can successfully emulate, simulate and/or provide some or all of the hardware and software resources of system 50, then the other platform will be able to successfully execute the software.
[0213] As one example, an emulator may provide a hardware and/or software configuration (platform) that is different from the hardware and/or software configuration (platform) of system 50. The emulator system might include software and/or hardware components that emulate or simulate some or all of hardware and/or software components of the system for which the application software was written. For example, the emulator system could comprise a general purpose digital computer such as a personal computer, which executes a software emulator program that simulates the hardware and/or firmware of system 50.
[0214] Some general purpose digital computers (e.g., IBM or MacIntosh personal to computers and compatibles) are now equipped with 3D graphics cards that provide 3D graphics pipelines compliant with DirectX or other standard 3D graphics command APIs. They may also be equipped with stereophonic sound cards that provide high quality stereophonic sound based on a standard set of sound commands. Such multimedia-hardware-equipped personal computers running as emulator software may have sufficient performance to approximate the graphics and sound performance of system 50. Emulator software controls the hardware resources on the personal computer platform to simulate the processing, 3D graphics, sound, peripheral and other capabilities of the home video game console platform for which the game programmer wrote the game software.
[0215] FIG. 18A illustrates an example overall emulation process using a host platform 1201, an emulator component 1303, and a game software executable binary image provided on a storage medium 62. Host 1201 may be a general or special purpose digital computing device such as, for example, a personal computer, a video game console, or any other platform with sufficient computing power. Emulator 1303 may be software and/or hardware that runs on host platform 1201, and provides a real-time conversion of commands, data and other information from storage medium 62 into a form that can be processed by host 1201. For example, emulator 1303 fetches “source” binary-image program instructions intended for execution by system 50 from storage medium 62 and converts these program instructions to a target format that can be executed or otherwise processed by host 1201.
[0216] As one example, in the case where the software is written for execution on a platform using an IBM PowerPC or other specific processor and the host 1201 is a personal computer using a different (e.g., Intel) processor, emulator 1203 fetches one or a sequence of binary-image program instructions from storage medium 1305 and converts these program instructions to one or more equivalent Intel binary-image program instructions. The emulator 1203 also fetches and/or generates graphics commands and audio commands intended for processing by the graphics and audio processor 114, and converts these commands into a format or formats that can be processed by hardware and/or software graphics and audio processing resources available on host 1201. As one example, emulator 1303 may convert these commands into commands that can be processed by specific graphics and/or or sound hardware of the host 1201 (e.g., using standard DirectX, OpenGL and/or sound APIs).
[0217] An emulator 1303 used to provide some or all of the features of the video game system described above may also be provided with a graphic user interface (GUI) that simplifies or automates the selection of various options and screen modes for games run using the emulator. In one example, such an emulator 1303 may further include enhanced functionality as compared with the host platform for which the software was originally intended.
[0218] FIG. 18B illustrates an emulation host system 1201 suitable for use with emulator 1303. System 1201 includes a processing unit 1203 and a system memory 1205. A system bus 1207 couples various system components including system memory 1205 to processing unit 1203. System bus 1207 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. System memory 1207 includes read only memory (ROM) 1252 and random access memory (RAM) 1254. A basic input/output system (BIOS) 1256, containing the basic routines that help to transfer information between elements within personal computer system 1201, such as during start-up, is stored in the ROM 1252. System 1201 further includes various drives and associated computer-readable media. A hard disk drive 1209 reads from and writes to a (typically fixed) magnetic hard disk 1211. An additional (possible optional) magnetic disk drive 1213 reads from and writes to a removable “floppy” or other magnetic disk 1215. An optical disk drive 1217 reads from and, in some configurations, writes to a removable optical disk 1219 such as a CD ROM or other optical media. Hard disk drive 1209 and optical disk drive 1217 are connected to system bus 1207 by a hard disk drive interface 1221 and an optical drive interface 1225, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules, game programs and other data for personal computer system 1201. In other configurations, other types of computer-readable media that can store data that is accessible by a computer (e.g., magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs) and the like) may also be used.
[0219] A number of program modules including emulator 1303 may be stored on the hard disk 1211, removable magnetic disk 1215, optical disk 1219 and/or the ROM 1252 and/or the RAM 1254 of system memory 1205. Such program modules may include an operating system providing graphics and sound APIs, one or more application programs, other program modules, program data and game data. A user may enter commands and information into personal computer system 1201 through input devices such as a keyboard 1227, pointing device 1229, microphones, joysticks, game controllers, satellite dishes, scanners, or the like. These and other input devices can be connected to processing unit 1203 through a serial port interface 1231 that is coupled to system bus 1207, but may be connected by other interfaces, such as a parallel port, game port Fire wire bus or a universal serial bus (USB). A monitor 1233 or other type of display device is also connected to system bus 1207 via an interface, such as a video adapter 1235.
[0220] System 1201 may also include a modem 1154 or other network interface means for establishing communications over a network 1152 such as the Internet. Modem 1154, which may be internal or external, is connected to system bus 123 via serial port interface 1231. A network interface 1156 may also be provided for allowing system 1201 to communicate with a remote computing device 1150 (e.g., another system 1201) via a local area network 1158 (or such communication may be via wide area network 1152 or other communications path such as dial-up or other communications means). System 1201 will typically include other peripheral output devices, such as printers and other standard peripheral devices.
[0221] In one example, video adapter 1235 may include a 3D graphics pipeline chip set providing fast 3D graphics rendering in response to 3D graphics commands issued based on a standard 3D graphics application programmer interface such as Microsoft's DirectX 7.0 or other version. A set of stereo loudspeakers 1237 is also connected to system bus 1207 via a sound generating interface such as a conventional “sound card” providing hardware and embedded software support for generating high quality stereophonic sound based on sound commands provided by bus 1207. These hardware capabilities allow system 1201 to provide sufficient graphics and sound speed performance to play software stored in storage medium 1305.
[0222] Example Higher-Level API Cells
[0223] The following show example higher level API cells that a library interprets and/or computes to create the binary level command streams described above:
[0224] GXSetCopyClear
[0225] Argument:
| GXColor | ClearColor; | //Color value to clear the framebuffer to during |
| copy. | ||
| u32 | ClearZ; | //24 bit Z value to clear the framebuffer to |
| during copy. | ||
[0226] This sets the two clear values used for clearing the framebuffer during copy operations.
[0227] GXSetVtxDesc
[0228] Arguments:
| GXAttr | Attr; | //Which attribute (Position, Normal, Color, etc.) |
| GXAttrType | Type; | //Attribute Type (None, Direct, Indexed, etc.) |
[0229] This function is used for setting the type of a single attribute in the current vertex descriptor (i.e., vertex attribute register). The vertex attribute register defines which attributes are present in a vertex and how each attribute is referenced.
[0230] GXSetVtxAttrFmt
[0231] Argument:
| GXVtxFmt | vtxfmt; | //Index into the Vertex Attribute Table |
| (0-7). | ||
| GXAttr | Attr; | //Attribute Type. |
| GXCompCnt | CompCnt; | //Number of components for the attribute. |
| GXCompType | CompType | //Type of each Component. |
| u8 | Shift; | //Locatin of decimal point for fixed point |
| format types. | ||
[0232] This function sets the attribute format for a single attribute in the vertex attribute format table (VAT). There are 8 vertex formats in the VAT vertex attribute array. Each register describes the data type and component types of all attributes that can be used in a vertex packet. The application can pre-program all 8 registers and then select one of them during actual drawing of the geometry.
[0233] GXSetArray
[0234] Arguments:
| GXAttr | Attr; | //Attribute type. |
| u32 | Base; | //Address (25:0) of the attribute data array in main |
| memory. | ||
| u8 | Stride; | //Number of bytes between successive elements in the |
| attribute array. | ||
[0235] This function sets the address and stride of the data array in main memory for each indexed attribute. The system uses these arrays to get actual data when an indexed attribute is sent with a vertex packet.
[0236] GXSetProjection
[0237] Arguments:
| f32 | Matrix[4][4] | //Projection matrix. |
| GXProjMtxType | type; | //Indicates if the projection is |
| orthographic. | ||
[0238] Sets projection matrix parameters. The projection matrix is specified as follows:
[0239] Perspective Projection:
[0240] Orthographic Projection:
[0241] All documents referred to herein are expressly incorporated by reference as if expressly set forth.
[0242] As used herein, the notation “0x” indicates a hexadecimal value. For example, “0x61” indicates a hexadecimal value. For example, “0x61” indicates a two-byte hexadecimal value of “61”—which people of ordinary skill in the art understand has a binary format of “01100001”. See Table VI below for conversion of hexadecimal notation to binary notation:
| TABLE VI | ||
|---|---|---|
| Hex | Binary | |
| 0 | 0000 | |
| 1 | 0001 | |
| 2 | 0010 | |
| 3 | 0011 | |
| 4 | 0100 | |
| 5 | 0101 | |
| 6 | 0110 | |
| 7 | 0111 | |
| 8 | 1000 | |
| 9 | 1001 | |
| A | 1010 | |
| B | 1011 | |
| C | 1100 | |
| D | 1101 | |
| B | 1110 | |
| F | 1111 | |
[0243] While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims.
Claims
We claim:
1. A graphics system command stream for use in a graphics system to set an array, the command stream comprising:
an array base load register command comprising 0x08Ax, where the second-mentioned “x” after “A” encodes an attribute indicator,
a 32-bit including a 26-bit address,
a stream command 0x08Bx, where the second-mentioned “x” after “B” encodes an attribute indicator, and
a succeeding 32-bit value including eight bits indicating a stride for an array,
wherein upon executing of the command stream an array base and an array stride register are set for a vertex array.
2. A computer readable storage medium encoded with executable instructions for setting an array, comprising:
an array base load register comprising 0x08Ax, where the second-mentioned “x” after “A” encodes an attribute indicator, and
a 32-bit value including a 26-bit address,
a stream command 0x08Bx, where the second-mentioned “x” after “B” encodes an attribute indicator, and
a succeeding 32 -bit value including eight bits indicating a stride for an array,
wherein upon execution of the command stream an array base register and an array stride register are set for a vertex array.
3. A graphics command stream decoder comprising:
a first decoding section decoding an array base load register command comprising 0x08Ax, where the second-mentioned x encodes an attribute indicator, and
a second decoding section decoding a 32-bit value including a 26-bit address,
a third decoding section decoding a stream command 0x08Bx, where the second-mentioned x encodes an attribute indicator, and
a fourth decoding section decoding a succeeding 32-bit value including eight bits indicating a stride for an array.
4. A method of setting an array in a graphics system using a graphics command stream comprising:
generating an array base load register comprising 0x08Ax, where the second-mentioned x encodes an attribute indicator, and
generating a 32-bit value including a 26-bit address,
generating a stream command 0x08Bx, where the second-mentioned x encodes an attribute indicator, and
generating a succeeding 32-bit value including eight bits indicating a stride for an array,
wherein upon execution of the command stream an array base register and an array stride register are set for a vertex array.
Patent Citations (93)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4388620(A) | 1983-06-01 | Sherman | Applicant |
| US4425559(A) | 1984-01-01 | Sherman | Applicant |
| US4570233(A) | 1986-02-01 | Yan et al. | Applicant |
| US4658247(A) | 1987-04-01 | Gharachorloo | Applicant |
| US4725831(A) | 1988-02-01 | Coleman | Applicant |
| US4829295(A) | 1989-05-01 | Hiroyuki | Applicant |
| US4862392(A) | 1989-08-01 | Steiner | Applicant |
| US4866637(A) | 1989-09-01 | Gonzalez-Lopez et al. | Applicant |
| US4901064(A) | 1990-02-01 | Deering | Applicant |
| US4914729(A) | 1990-04-01 | Omori et al. | Applicant |
| US4945500(A) | 1990-07-01 | Deering | Applicant |
| US5136664(A) | 1992-08-01 | Bersack et al. | Applicant |
| US5170468(A) | 1992-12-01 | Shah et al. | Applicant |
| US5392385(A) | 1995-02-01 | Evangelisti et al. | Applicant |
| US5392393(A) | 1995-02-01 | Deering | Applicant |
| US5404445(A) | 1995-04-01 | Matsumoto | Applicant |
| US5421028(A) | 1995-05-01 | Swanson | Applicant |
| US5432900(A) | 1995-07-01 | Rhodes et al. | Applicant |
| US5438663(A) | 1995-08-01 | Matsumoto et al. | Applicant |
| US5457775(A) | 1995-10-01 | Johnson, Jr. et al. | Applicant |
| US5504917(A) | 1996-04-01 | Austin | Applicant |
| US5594854(A) | 1997-01-01 | Baldwin et al. | Applicant |
| US5608424(A) | 1997-03-01 | Takahashi et al. | Applicant |
| US5671401(A) | 1997-09-01 | Harrell | Examiner |
| US5687357(A) | 1997-11-01 | Priem | Applicant |
| US5701444(A) | 1997-12-01 | Baldwin | Applicant |
| US5721947(A) | 1998-02-01 | Priem et al. | Applicant |
| US5727192(A) | 1998-03-01 | Baldwin | Applicant |
| US5751295(A) | 1998-05-01 | Becklund et al. | Applicant |
| US5764243(A) | 1998-06-01 | Rosenthal et al. | Applicant |
| US5768626(A) | 1998-06-01 | Munson et al. | Applicant |
| US5768629(A) | 1998-06-01 | Wise et al. | Applicant |
| US5774133(A) | 1998-06-01 | Neave et al. | Applicant |
| US5777629(A) | 1998-07-01 | Baldwin | Applicant |
| US5798770(A) | 1998-08-01 | Baldwin | Applicant |
| US5801706(A) | 1998-09-01 | Fujita et al. | Applicant |
| US5801716(A) | 1998-09-01 | Silverbrook | Applicant |
| US5805868(A) | 1998-09-01 | Murphy | Applicant |
| US5808868(A) | 1998-09-01 | Murphy | Applicant |
| US5815166(A) | 1998-09-01 | Baldwin | Applicant |
| US5821949(A) | 1998-10-01 | Deering | Applicant |
| US5870587(A) | 1999-02-01 | Danforth et al. | Applicant |
| US5874969(A) | 1999-02-01 | Storm et al. | Applicant |
| US5917496(A) | 1999-06-01 | Fujita et al. | Applicant |
| US5920326(A) | 1999-07-01 | Rentschler et al. | Applicant |
| US5920876(A) | 1999-07-01 | Ungar et al. | Applicant |
| US5936641(A) | 1999-08-01 | Jain et al. | Applicant |
| US5940086(A) | 1999-08-01 | Rentschler et al. | Applicant |
| US5949424(A) | 1999-09-01 | Cabral et al. | Applicant |
| US5949440(A) | 1999-09-01 | Krech, Jr. et al. | Applicant |
| US5969726(A) | 1999-10-01 | Rentschler et al. | Applicant |
| US5995121(A) | 1999-11-01 | Alcorn et al. | Applicant |
| US5999196(A) | 1999-12-01 | Storm et al. | Applicant |
| US6002409(A) | 1999-12-01 | Harkin | Applicant |
| US6023738(A) | 2000-02-01 | Preim et al. | Applicant |
| US6025853(A) | 2000-02-01 | Baldwin | Applicant |
| US6028611(A) | 2000-02-01 | Anderson et al. | Applicant |
| US6031548(A) | 2000-02-01 | Gueziec et al. | Examiner |
| US6037949(A) | 2000-03-01 | DeRose et al. | Applicant |
| US6052133(A) | 2000-04-01 | Kang | Applicant |
| US6057852(A) | 2000-05-01 | Krech, Jr. | Applicant |
| US6057863(A) | 2000-05-01 | Olarig | Applicant |
| US6075540(A) | 2000-06-01 | Hoppe | Examiner |
| US6078331(A) | 2000-06-01 | Pulli et al. | Examiner |
| US6092124(A) | 2000-07-01 | Priem et al. | Applicant |
| US6151602(A) | 2000-11-01 | Hejlsberg et al. | Applicant |
| US6173367(B1) | 2001-01-01 | Aleksic et al. | Applicant |
| US6177944(B1) | 2001-01-01 | Fowler et al. | Applicant |
| US6181352(B1) | 2001-01-01 | Kirk et al. | Applicant |
| US6198488(B1) | 2001-03-01 | Lindholm et al. | Applicant |
| US6226012(B1) | 2001-05-01 | Priem et al. | Applicant |
| US6307551(B1) | 2001-10-01 | Gueziec et al. | Examiner |
| CA2070934 | 1993-12-01 | Applicant | |
| EP1074945 | 2001-02-01 | Applicant | |
| EP1075146 | 2001-02-01 | Applicant | |
| EP1081649 | 2001-03-01 | Applicant | |
| JP11053580 | 1999-02-01 | Applicant | |
| JP11076614 | 1999-03-01 | Applicant | |
| JP11161819 | 1999-06-01 | Applicant | |
| JP11203500 | 1999-07-01 | Applicant | |
| JP11226257 | 1999-08-01 | Applicant | |
| JP11259671 | 1999-09-01 | Applicant | |
| JP11259678 | 1999-09-01 | Applicant | |
| JP2000-66985 | 2000-03-01 | Applicant | |
| JP2000-92390 | 2000-03-01 | Applicant | |
| JP2000-132704 | 2000-05-01 | Applicant | |
| JP2000-132706 | 2000-05-01 | Applicant | |
| JP2000-149053 | 2000-05-01 | Applicant | |
| JP2000-156875 | 2000-06-01 | Applicant | |
| JP2000-182077 | 2000-06-01 | Applicant | |
| JP2000-207582 | 2000-07-01 | Applicant | |
| JP2000-215325 | 2000-08-01 | Applicant | |
| WO94/10641 | 1994-05-01 | Applicant |
Non-Patent Literature (99)
- Photograph of Sony PlayStation II System.Applicant
- Photograph of Sega Dreamcast System.Applicant
- Photograph of Nintendo 64 System.Applicant
- Whitepaper: 3D Graphics Demystified, Nov. 11, 1999, www.nvidia.com.Applicant
- Whitepaper: “Z Buffering, Interpolation and More W-Buffering”, Doug Rogers, Jan. 31, 2000, www.nvidia.com.Applicant
- Whitepaper: Using GL_NV_vertex_array and GL_NV_fence, posted Aug. 1, 2000, www.nvidia.com.Applicant
- Whitepaper: Anisotropic Texture Filtering in OpenGL, posted Jul. 17, 2000, www.nvidia.com.Applicant
- Whitepaper: Mapping Texels to Pixels in D3D, posted Apr. 5, 2000, www.nvidia.com.Applicant
- Whitepaper: Guard Band Clipping, posted Jan. 31, 2000, www.nvidia.com.Applicant
- Whitepaper: Cube Environment Mapping, posted Jan. 14, 2000, www.nvidia.com.Applicant
- Whitepaper: Color Key in D3D, posted Jan. 11, 2000, www.nvidia.com.Applicant
- Whitepaper: Vertex Blending Under DX7 for the GeForce 256, Jan. 5, 2000, www.nvidia.com.Applicant
- Whitepaper: Optimizing Direct3D for the GeForce 256, Jan. 3, 2000, www.nvidia.com.Applicant
- Whitepaper: Dot Product Texture Blending, Dec. 3, 1999, www.nvidia.com.Applicant
- Whitepaper: Technical Brief: AGP 4X with Fast Writes, Nov. 10, 1999, www.nvidia.com.Applicant
- Technical Brief: Transform and Lighting, Nov. 10, 1999, www.nvidia.com.Applicant
- Technical Brief: What's New With Microsoft DirectX7, posted Nov. 10, 1999, www.nvidia.com.Applicant
- Mitchell et al., “Multitexturing in Direct X6”, Game Developer, Sep. 1998, www.gdmag.com.Applicant
- Vision Tek, “GeForce2 GS Graphics Processing Unit”, ©2000 www.visiontek.com.Applicant
- Jim Bushnell et al. “Advanced Multitexture Effects With Direct3D and OpenGL”, Pyramid Peak Design & ATI Research, Inc., GameDevelopers Conference, ©1999.Applicant
- Sony PlayStation II Instruction Manual, Sony Computer Entertainment Inc., ©2000.Applicant
- Stand and Be Judged, Next Generation, May 2000.Applicant
- PlayStation II: Hardware Heaven of Hell?, Next Generation, Jan. 2000.Applicant
- Chris Charla, “Play Station II: The Latest News”, Next Generation, Sep. 1999.Applicant
- “First PlayStation II Gameplay Screens Revealed!”, Next Generation, Sep. 1999.Applicant
- Game Enthusiast Online Highlights, Mar. 18, 1999.Applicant
- Game Enthusiast Online Highlights, Mar. 19, 1999.Applicant
- Game Enthusiast Online Highlights, Mar. 17, 1999.Applicant
- Game Enthusiast Online Highlights, Oct. 20, 1999.Applicant
- Joel Easley, “PlayStation II Revealed”, Game Week, Sep. 29, 1999.Applicant
- Inside Sony's Next Generation Playstation, ©1999.Applicant
- Press Releases, Mar. 18, 1999.Applicant
- Chris Johnston, “PlayStation Part Deux”, Press Start, ©1999.Applicant
- Nikkei Shimbun, “Sony Making SME, Chemical and SPT into Wholly-Owned Subsidiaries”, Mar. 9, 1999.Applicant
- AM News: Japanese Developers Not All Sold on PS2, Next Generation, Mar. 16, 1999.Applicant
- Sony To Turn PlayStation Maker Into Wholly Owned Unit-Nikkei, Dow Jones News Service, Mar. 8, 1999.Applicant
- Yumiko Ono, Sony Antes Up Its Chips In Bet On New Game System, Dow Jones News Service, Mar. 4, 1999.Applicant
- MacWeek.Com Gets Inside Story on Connectix VGS for Windows; Controversial Emulator of Sony PlayStation Games Cureently Available for Macs Only, Business Wire, Mar. 12, 1999.Applicant
- “DexDrive Bridges Gap”, The Tampa Tribune, Mar. 12, 1999.Applicant
- A Microprocessor With a 128b CPU, 10 Floating-Point MAC's, 4 Floating-Point Dividers, and an MPEG2 Decoder, 1999 IEEE International Solid-State Circuits Conference, Feb. 16, 1999.Applicant
- Dreamcast Instruction Manual, Sega Enterprises, Ltd., ©1998.Applicant
- “Sega To Launch Video Camera for Dreamcast”, Reuters Business News, Feb. 16, 2000.Applicant
- David Pescovitz, “Dream On”, Wired, Aug. 1999.Applicant
- Randy Nelson, “Dreamcast 101: Everything You Ever Wanted To Know About Sega's Powerful New Console”, Official Sega Dreamcast Magazine, Jun. 1999.Applicant
- 2D/3D Graphics Card User Manual, Guillemot ©1999.Applicant
- Nintendo 64 Instruction Booklet, Nintendo of America, 1998.Applicant
- Steven Levy, “Here Comes PlayStation II”, Newsweek, Mar. 6, 2000.Applicant
- David Sheff, “Sony Smackage: Test Driving The PlayStation II”, Wired, Nov. 1999.Applicant
- Introducing The Next Generation PlayStation, Sony Computer Entertainment Inc., ©1999.Applicant
- Leadtek GTS, Aug. 3, 2000, www.hexus.net.Applicant
- Voodoo 5 5500 Review, Jul. 26, 2000, www.hexus.net.Applicant
- ATI Radeon 64 Meg DDR OEM, Aug., 19, 2000, www.hexus.net.Applicant
- Microsoft Xbox—The Future of Gaming, Microsoft Xbox Performance Sheet, www.xbox.com.Applicant
- Robert L. Cook, “Shade Trees”, Computer Graphics, vol. 18, No. 3, Jul. 1984.Applicant
- Wang et al., “Second-Depth Shadow Mapping”, Department of Computer Science, Univ. N.C, Chapel Hill, N.C. pp. 1-7.Applicant
- Peercy et al., “Efficient Bump Mapping Hardware”, Computer Graphics Proceedings, Annual Conference Series, 1997.Applicant
- Gustavo Oliveira, “Refractive Texture Mappig, Part One”, www.gamasutra.com, Nov., 10, 2000.Applicant
- John Schlag, Fast Embossing Effects on Raster Image Data, Graphics Gems IV, Edited by Paul S. Heckbert, Computer Science Department, Carnegie Mellon University, Academic Press, Inc., 1994,pp. 433-437.Applicant
- James F. Blinn, “Simulationof Wrinkled Surfaces,” Caltech/JPL, pp. 286-292, SIGGRAPH 78 (1978).Applicant
- Tomas Möller and Eric Haines “Real-Time Rendering”, AK Peters, Ltd., ©1999, pp. 127-142.Applicant
- Technical Presentation: Vertex Buffers, posted Jun. 12, 2000, www.nvidia.com.Applicant
- Technical Presentation: Hardware Transform and Lighting, www.nvidia.com, posted Jun. 12, 2000.Applicant
- Technical Presentation: Hardware Bump-mapping Choices and Concepts, Jun. 7, 2000, www.nvidia.com.Applicant
- Technical Presentation: How to Bump Map a Skinned Polygonal Model, Jun. 7, 2000, www.nvidia.com.Applicant
- Technical Presentation: Computations for Hardware Lighting and Shading, Mar. 17, 2000, www.nvidia.com.Applicant
- Technical Presentation: Practical Bump-mapping for Today's GPUs, Mar. 17, 2000 www.nvidia.com.Applicant
- Technical Presentation: Shadows, Transparency, & Fog, Mar. 17, 2000 www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 Register Combiners, Mar. 17, 2000,www.nvidia.com.Applicant
- Technical Presentation: TexGen & The Texture Matrix, Mar. 15, 2000 www.nvidia.com.Applicant
- Technical Presentation: Toon Shading, Mar. 15, 2000, www.nvidia.com.Applicant
- Technical Presentation: D3D 7 Vertex Lighting, Mar. 15, 2000, www.nvidia.com.Applicant
- Technical Presentation: Per-Pixel Lighting (by S. Dietrich) Mar. 14, 2000 www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 and RIVA TNT Combiners, Dec. 8, 1999, www.nvidia.com.Applicant
- Technical Presentation: Vertex Cache Optimization, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Vertex Blending, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Hardware Transform and Lighting, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 Overview, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: DirectX 7 and Texture Management, Nov. 12, 1999 www.nvidia.com.Applicant
- Technical Presentation: Dot Product Lighting, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Texture Coordinate Generation, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Phong Shading and Lightmaps, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: The ARB_multitexture Extension, Nov. 3, 1999 www.nvidia.com.Applicant
- Technical Presentation: Multitexture Combiners, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Emboss Bump Mapping, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Hardware Accelerated Anisotropic Lighting, Nov. 3, 1999 www.nvidia.com.Applicant
- Technical Presentation: Guard Band Clipping, Nov. 3, 1999, www.nvidia.com.Applicant
- The RenderMan Interface, Stephan R. Keith, Version 3.1, Pixar Animation Studios, Sep. 1989.Applicant
- The RenderMan Interface, Version 3.2, Pixar Animation Studios, Jul. 2000, www.pixar.com.Applicant
- NVIDIA Product Overview, “GeForce2Ultra”, NVIDIA Corporation, Aug. 21, 2000, www.nvidia.com.Applicant
- Duke, “Dreamcast Technical Specs”, Sega Dreamcast Review, Sega, 2/99, www.game-revolution.com.Applicant
- Marlin Rowley, “GeForce 1 & 2 GPU Speed Tests”, May 11, 2000, www.g256.com.Applicant
- “Dreamcast: The Full Story”, Next Generation, Sep. 1998.Applicant
- DirectX 7.0 Programmer's Reference, Microsoft Corporation,1995-1999 (as part of the DirectX 7.0 SDK on the Companion CD included with “Inside Direct3D”, Microsoft Programming Series, Peter J. Kovach, Microsoft Press, 1999).Applicant
- “Inside Direct3D”, Microsoft Programming Series, Peter J. Kovach, Microsoft Press, 1999.Applicant
- “OpenGL Programming Guide, The Official Guide to Learning OpenGL, Release 1”, Jackie Nieder, Tom David, Mason Woo, Addision-Wesley Publishing Co., 1993.Applicant
- “Procedural Elements for Computer Graphics,” Second Edition, David F. Rogers, McGraw Hill,1998.Applicant
- “Real-Time Rendering,” Tomas Molleir, Eric Haines, AK Peters, 1999.Applicant
- “Computers Graphics, Principles and Practice,” Second Edition, The Systems Programming Series, Foley, van Dam, Fiener, Hughes, Addison Wesley, 1990.Applicant
- “Principles of Three-Dimensional Computer Animation”, Revised Edition, Michael O'Rourke, W.W. Norton & Company, 1998.Applicant