US 7,002,591 B1Grant
Method and apparatus for interleaved processing of direct and indirect texture coordinates in a graphics system
Issue Date:2006-02-21
•3 Claims
•29 Drawing Sheets
Abstract
A graphics system including a custom graphics and audio processor produces exciting 2D and 3D graphics and surround sound. The system includes a graphics and audio processor including a 3D graphics pipeline and an audio digital signal processor. The graphics pipeline renders and prepares images for display at least in part in response to polygon vertex attribute data and texel color data stored as a texture images in an associated memory. An efficient texturing pipeline arrangement achieves a relatively low chip-footprint by utilizing a single texture coordinate/data processing unit that interleaves the processing of logical direct and indirect texture coordinate data and a texture lookup data feedback path for “recirculating” indirect texture lookup data retrieved from a single texture retrieval unit back to the texture coordinate/data processing unit. Versatile indirect texture referencing is achieved by using the same texture coordinate/data processing unit to transform the recirculated texture lookup data into offsets that may be added to the texture coordinates of a direct texture lookup. A generalized indirect texture API function is provided that supports defining at least four indirect texture referencing operations and allows for selectively associating one of at least eight different texture images with each indirect texture defined. Retrieved indirect texture lookup data is processed as multi-bit binary data triplets of three, four, five, or eight bits. The data triplets are multiplied by a 3×2 texture coordinate offset matrix before being optionally combined with regular non-indirect coordinate data or coordinate data from a previous cycle/stage of processing. Values of the offset matrix elements are variable and may be dynamically defined for each cycle/stage using selected constants. Two additional variable matrix configurations are also defined containing element values obtained from current direct texture coordinates. Circuitry for optionally biasing and scaling retrieved texture data is also provided.
Metadata
Assignee
- Nintendo Co., Ltd.
Inventors
- Mark M. Leather
- Robert A. Drebin
- Timothy J. Van Hook
Application Information
Application Number:US 09/722,382
Filing Date:2000-11-28
Priority Date:2000-08-23
Art Unit:2676
Classifications
IPC:
G09G5/00G06T17/00
Patent Drawings (29 sheets)
Description
Related Applications
[0001] This application claims the benefit of U.S. Provisional Application, Ser. No. 60/226,891, filed Aug. 23, 2000, the entire content of which is hereby incorporated by reference.
Field of the Invention
[0002] The present invention relates to computer graphics, and more particularly to interactive graphics systems such as home video game platforms. Still more particularly this invention relates to direct and indirect texture mapping/processing in a graphics system.
Background and Summary of the Invention
[0003] 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.
[0004] 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.
[0005] A problem graphics system designers confronted in the past was how to create realistic looking surface detail on a rendered object without resorting to explicit modeling of the desired details with polygons or other geometric primitives. Although surface details can be simulated, for example, using myriad small triangles with interpolated shading between vertices, as the desired detail becomes finer and more intricate, explicit modeling with triangles or other primitives places high demands on the graphics system and becomes less practical. An alternative technique pioneered by E. Catmull and refined by J. F. Blinn and M. E. Newell is to “map” an image, either digitized or synthesized, onto a surface. (See “A Subdivision Algorithm for Computer Display of Curved Surfaces” by E. Catmull, Ph.D. Thesis, Report UTEC-CSc-74-133, Computer Science Department, University of Utah, Salt Lake City, Utah, December 1994 and “Texture and Reflection in Computer Generated Images” by J. F. Blinn and M. E. Newell, CACM, 19(10), October 1976, 452–457). This approach is known as texture mapping (or pattern mapping) and the image is called a texture map (or simply referred to as a texture). Alternatively, the texture map may be defined by a procedure rather than an image.
[0006] Typically, the texture map is defined within a 2D rectangular coordinate space and parameterized using a pair of orthogonal texture coordinates such, as for example, (u, v) or (s, t). Individual elements within the texture map are often called texels. At each rendered pixel, selected texels are used either to substitute for or to scale one or more material properties of the rendered object surface. This process is often referred to as texture mapping or “texturing.”
[0007] Most 3-D graphics rendering systems now include a texturing subsystem for retrieving textures from memory and mapping the textures onto a rendered object surface. Sophisticated texturing effects utilizing indirect or multiple textures are also possible such as, for example, multi-texturing, meta-textures or texture tiling, but conventional approaches typically involve complex hardware arrangements such as using multiple separate texture retrieval/mapping circuits (units) where the output of one texturing circuit provides the input to a next texturing circuit. Such duplicated circuitry is essentially idle whenever such effects are not used. In on-chip graphics processing implementations, the additional circuitry requires more chip real-estate, can reduce yield and reliability, and may significantly add to the overall production cost of the system. Consequently, a further problem confronting graphics system designers is how to efficiently implement these more sophisticated texturing effects without associated increases in texture mapping hardware complexity.
[0008] One solution is to use a single texture addressing/mapping circuit and perform multiple texturing passes. Nominally, this may require at least generating a first set of texture addressing coordinates, accessing a first texture, storing the data retrieved in a temporary storage, and then regenerating the same set of texture coordinates again for use in computing new coordinates when accessing a second texture in the next or a subsequent texturing pass. Although this approach may reduce hardware complexity somewhat, it is fairly time consuming, requires generating/providing the same set of texture coordinates multiple times, and results in inefficient processing during mode changes (e.g., switching between direct and indirect texturing operational modes). Moreover, this approach results in a very course granularity in the data processing flow through the graphics rendering system—significantly affecting polygon fill rate.
[0009] To solve this problem and to provide an enhanced repertoire of texturing capabilities for a 3-D graphics system, the present invention provides a versatile texturing pipeline arrangement achieving a relatively low chip-footprint by utilizing a single texture address coordinate/data processing unit that interleaves the processing of logical direct and indirect texture coordinate data and provides a texture lookup data feedback path for “recirculating” retrieved indirect texture lookup data from a single texture retrieval unit back to the texture address coordinate/data processing unit. The interleaved coordinate processing and recirculated/feedback data arrangement of the present invention allow efficient processing of any number of logical direct and/or indirect texture mapping stages from a smaller number of hardware texture processing units while preserving a fine granularity in the overall data processing flow.
[0010] In accordance with one aspect provided by the present invention, the recirculating/data-feedback arrangement of the texturing pipeline portion of the graphics processing enables efficient use and reuse of a single texture lookup (retrieval) unit for both logical direct and indirect texture processing without requiring multiple rendering passes and/or temporary texture storage hardware.
[0011] In accordance with another aspect provided by the invention, the texture address (coordinate) processing hardware is arranged to perform various coordinate computations based on the recirculated/feedback texture data and to process both direct and indirect coordinate data together in a substantially continuous interleaved flow (e.g., to avoid any “course granularity” in the processing flow of graphics data throughout the system). This unique interleaved processing/data-recirculating texture pipeline arrangement enables efficient and flexible texture coordinate processing and texture retrieval/mapping operations while using a minimum amount of hardware for providing an enhanced variety of possible direct and indirect texturing applications.
[0012] In accordance with another aspect provided by this invention, an effectively continuous processing of coordinate data for performing logical direct and indirect texture lookups is achieved by interleaving the processing of both direct and indirect coordinate data per pixel within a single texture coordinate processing hardware unit. For example, a selector can be used to look for “bubbles” (unused cycles) in the indirect texture coordinate stream, and to insert computed texture coordinate data in such “bubbles” for maximum utilization of the texture mapper.
[0013] In accordance with yet another aspect provided by the invention, a hardware implemented texturing pipeline includes a texture lookup data feedback path by which the same texture data retrieval unit can be used and reused to:
-
- [0014] both lookup direct indirect textures, and
- [0015] supply indirect texture lookup data.
The same texture address (coordinate) processing unit can be used and reused for processing both logical direct and indirect texture coordinate data and computing new/modified texture coordinates.
[0016] In accordance with yet another aspect provided by this invention, a set of texture mapping parameters is presented to a texture mapping unit which is controlled to perform a texture mapping operation. The results of this texture mapping operation are recirculated and used to present a further set of texture mapping parameters which are fed back to the input of the same texture mapping unit. The texture mapping unit performs a further texture mapping operation in response to these recirculated parameters to provide a further texture mapping result.
[0017] The first texture mapping operation may comprise an indirect texture mapping operation, and a second texture mapping operation may comprise a direct texture mapping operation. The processing and presentation of texture mapping parameters to a texture mapping unit for performing direct texture mapping operations may be interleaved with the processing and presentation of texture mapping parameters for performing indirect direct texture mapping operations.
[0018] In accordance with a further aspect provided by this invention, a method of indirect texture referencing uses indirect texture coordinates to generate a data triplet which is then used to derive texture coordinates. The derived texture coordinates are then used to map predetermined texture data onto a primitive. In accordance with yet a further aspect provided by the invention, the retrieved data triplet stored in texture memory is used to derive a set of modified texture coordinates which are then used to reference texture data stored in the texture memory corresponding to a predetermined texture.
[0019] In accordance with yet another aspect provided by this invention, a graphics system includes:
-
- [0020] a texture coordinate/data processing unit for interleaved processing of logical direct and indirect coordinate data comprising an arrangement of at least one data multiplier and at least one data accumulator;
- [0021] a texture data retrieval unit connected to the coordinate/data processing unit, the texture data retrieval unit retrieving texture data stored in a texture memory; and
- [0022] a data feedback path from a texture data retrieval unit to the texture coordinate/data processing unit to recycle retrieved texture data through the texture coordinate/data processing unit for further processing;
- [0023] wherein in response to a set of texture coordinates the retrieval unit provides retrieved texture data to the processing unit for deriving modified texture coordinates which are used in mapping a texture to a surface of a rendered image object.
[0024] In accordance with yet another aspect provided by this invention, a texture processing system for selectively mapping texture data corresponding to one or more different textures and/or texture characteristics to surfaces of rendered and displayed images includes a texture coordinate offset matrix arrangement producing a set of offset texture coordinates by multiplying indirect texture data by elements of a matrix, wherein one or more elements of the matrix are a mathematical function of one or more predetermined direct texture coordinates and one or more elements of the matrix can be selectively loaded.
[0025] In accordance with yet another aspect provided by this invention, a set of indirect texture coordinates are used to retrieve data triplets stored in texture memory, and a set of modified texture coordinates are derived based at least in part on the retrieved data triplets. The set of modified texture coordinates is then used for retrieving data stored in texture memory. These steps are reiteratively repeated for a predetermined number of data retrievals, and a set of derived texture coordinates resulting from the repetition is used to map predetermined texture data onto a primitive.
[0026] In accordance with yet another aspect provided by the invention, a set of generalized API (application program interface) indirect texture mapping functions are defined and supported by the texturing pipeline apparatus which permits specifying arguments for performing at least four indirect-texture operations (indirect lookup stages) and for selectively associating one of at least eight pre-defined textures and one of at least eight pre-defined sets of texture coordinates with each indirect texturing operation. The defined API indirect texture mapping functions also permit specifying texture scale, bias and coordinate wrap factors as well as a variety of texture coordinate offset multiplication matrix configurations and functions for computing new/modified texture lookup coordinates within the texturing pipeline.
[0027] In accordance with yet a further aspect provided by the invention, a texture address (coordinate) processing unit transforms retrieved texture color/data from an indirect texture lookup into offsets that are added to the texture coordinates of a regular (non-direct) texture lookup. The feedback path provides texture color/data output from a texture retrieval unit to a texture coordinate processing unit used to generate/provide texture coordinates to the texture retrieval unit.
[0028] In accordance with yet a further aspect provided by the invention, a single texture address processing unit comprising at least a pair of FIFO buffers is utilized for interleaving and synchronizing the processing of both “direct” (regular non-indirect) and “indirect” texture coordinates, and a single texture data retrieval unit is used for retrieving and recirculating indirect-texture lookup data back to the texture address processing unit for computing new/modified texture lookup coordinates. In an example embodiment, the retrieved indirect-texture lookup data is processed as multi-bit binary data triplets of three, four, five, or eight bits. The data triplets are multiplied by a 3×2 element texture coordinate offset matrix before being optionally combined with direct coordinate data, or with computed data from a previous cycle/stage of texture address processing, to compute modified offset texture coordinates for accessing a texture map in main memory. Values of the offset matrix elements are programmable and may be dynamically defined for successive processing cycles/stages using selected predetermined constants or values based on direct coordinates. A variety of offset matrix configurations are selectable including at least three offset matrix configurations containing elements based on programmable constants and two “variable” matrix configurations containing elements based on a values from a set of direct texture coordinates. Circuitry for optionally biasing and scaling retrieved texture data is also provided.
Brief Description of the Drawings
[0029] 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. The file of this patent contains at least one drawing executed in color. Copies of this patent with color drawing(s) will be provided by the Patent and Trademark Office upon request and payment of the necessary fee. The drawings include the following figures:
[0030] FIG. 1 is an overall view of an example interactive computer graphics system;
[0031] FIG. 2 is a block diagram of the FIG. 1 example computer graphics system;
[0032] FIG. 3 is a block diagram of the example graphics and audio processor shown in FIG. 2 ;
[0033] FIG. 4 is a block diagram of the example 3D graphics processor shown in FIG. 3 ;
[0034] FIG. 5 is an example logical flow diagram of the FIG. 4 graphics and audio processor;
[0035] FIG. 6 is block diagram illustrating a logical overview of indirect texture processing in accordance with the present invention;
[0036] FIG. 7A is a functional block diagram illustrating a simple basic example of a regular (non-indirect) texture lookup;
[0037] FIG. 7B is a functional block diagram illustrating a simple basic example of an indirect texture lookup in accordance with the present invention;
[0038] FIG. 8 is a block diagram illustrating an overview of an example physical configuration for implementing indirect texture processing in accordance with the present invention;
[0039] FIG. 9 is a block diagram illustrating a logical overview of the texture address (coordinate/data) processor operation;
[0040] FIGS. 10A–10K are a series of block diagrams illustrating the dynamic progression of direct and indirect data in the example texturing pipeline implementation to provide interleaved direct and indirect texture processing;
[0041] FIG. 11 is a flow chart illustrating example steps for implementing indirect texture processing in accordance with the present invention;
[0042] FIG. 12 is a functional operations diagram illustrating an example of regular (non-indirect) texture processing in accordance with the present invention;
[0043] FIG. 13 is a functional operations diagram illustrating an example of interleaved regular (non-indirect) and indirect texture processing in accordance with the present invention;
[0044] FIG. 14 is a block diagram showing a detailed example of the texture coordinate/bump processing unit shown in FIG. 5 ;
[0045] FIG. 15 is a block diagram showing a detailed example of the indirect texture lookup data/coordinate processing logic (proc) shown in FIG. 14 ;
[0046] FIGS. 16A and 16B show example texture offset matrices used by processing logic circuit (proc) of FIG. 15 ;
[0047] FIG. 17 is a block diagram illustrating example data field formats of control logic registers for controlling the operations within the processing circuitry of FIG. 15 ;
[0048] FIGS. 18 and 19 show example alternative compatible implementations.
Detailed Description of Example Embodiments of the Invention
[0049] 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.
[0050] 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, 52b or 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.
[0051] 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.
[0052] 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.
[0053] The user may use hand controllers 52a, 52b to 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.
[0054] 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. 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.
Example Electronics of Overall System
[0055] FIG. 2 shows a block diagram of example components of system 50. The primary components include:
-
- [0056] a main processor (CPU) 110,
- [0057] a main memory 112, and
- [0058] a graphics and audio processor 114.
[0059] 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.
[0060] 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.
[0061] 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 50 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.
[0062] Graphics and audio processor 114 has the ability to communicate with various additional devices that may be present within system 50. 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:
-
- [0063] a programmable read-only memory and/or real time clock 134,
- [0064] a modem 136 or other networking interface (which may in turn connect system 50 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
- [0065] flash memory 140.
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.
Example Graphics and Audio Processor
[0066] 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:
-
- [0067] a processor interface 150,
- [0068] a memory interface/controller 152,
- [0069] a 3D graphics processor 154,
- [0070] an audio digital signal processor (DSP) 156,
- [0071] an audio memory interface 158,
- [0072] an audio interface and mixer 160,
- [0073] a peripheral controller 162, and
- [0074] a display controller 164.
[0075] 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 56. 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.
[0076] 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.
Example Graphics Pipeline
[0077] 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 115 to minimize memory latency, and also has a write-gathering buffer 111 for non-cached 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.
[0078] Command processor 200 parses display commands received from main processor 110—obtaining any additional data necessary to process the display commands 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 56.
[0079] 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. The command processor 200 fetches:
-
- [0080] 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,
- [0081] display lists 212 from main memory 112 via an on-chip call FIFO memory buffer 218, and
- [0082] vertex attributes from the command stream and/or from vertex arrays 214 in main memory 112 via a vertex cache 220.
[0083] Command processor 200 performs command processing operations 200a that convert attribute types to floating point format, and pass 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.
[0084] FIG. 4 shows that graphics pipeline 180 may include:
-
- [0085] a transform unit 300,
- [0086] a setup/rasterizer 400,
- [0087] a texture unit 500,
- [0088] a texture environment unit 600, and
- [0089] a pixel engine 700.
[0090] 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 300b for 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 300e also performed by transform unit 300b provides 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).
[0091] 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.
[0092] Texture unit 500 (which may include an on-chip texture memory (TMEM) 502) performs various tasks related to texturing including for example:
-
- [0093] retrieving textures 504 from main memory 112,
- [0094] 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,
- [0095] bump map processing for computing texture coordinate displacements for bump mapping, pseudo texture and texture tiling effects (500b), and
- [0096] indirect texture processing (500c).
[0097] Graphics pipeline 180 includes a versatile texturing pipeline architecture that facilitates the implementation of various direct and indirect texturing features. As shown in FIG. 5 , the texturing pipeline basically comprises:
-
- [0098] texture unit 500a for performing texture data lookup retrieval,
- [0099] indirect texture/bump units 500b/500c for texture coordinate/texture data processing,
- [0100] texture lookup data feedback path 500d and
- [0101] texture environment unit 600 for staged color data and alpha (transparency data) blending.
[0102] Reuse of units 500a, 500b, 500c can be used to provide a variety of interesting effects including multitexturing for example. Furthermore, the present invention supports indirect texturing through reuse/recirculation of these components. In an example hardware implementation, texture address coordinate/bump processing block 500b and indirect texture data processing block 500c are portions of a single texture coordinate/data processing unit and the texturing pipeline is configured so as to allow retrieved texture indirect lookup data from texture unit 500a to be provided back via data feedback connection 500d to texture address coordinate/bump processor 500b/500c. The texture coordinate/data processing unit transforms texture data retrieved from an indirect texture lookup into offsets that are then added to texture coordinates for another (regular/non-indirect) texture lookup.
[0103] Using the above described feedback path arrangement, retrieved texture data can effectively be “recirculated” back into the texture processing pipeline for further processing/computation to obtain new/modified texture lookup coordinates. This recirculated/recycled texture lookup data arrangement enables efficient and flexible indirect texture mapping/processing operations providing an enhanced variety of indirect texture applications. A few of the various applications of indirect texture mapping/processing which the texturing pipeline can provide include, for example:
-
- [0104] Texture warping
- [0105] Meta-textures
- [0106] Texture tile maps
- [0107] Pseudo-3D textures
- [0108] Environment-mapped bump mapping
[0109] Texture unit 500 outputs filtered texture values to the texture environment unit 600 for texture environment processing (600a). Texture environment unit (TEV) 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. Texture environment unit 600 can also combine (e.g., subtract) textures in hardware in one pass. For more details concerning the texture environment unit 600, see commonly assigned application Ser. No. 09/722,367, entitled “Recirculating Shade Tree Blender for a Graphics System” and its corresponding provisional application Ser. No. 60/226,888, filed Aug. 23, 2000, both of which are incorporated herein by reference.
[0110] 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. Depth (z) compares can also be performed at an earlier stage 700a′ 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 700c that periodically writes on-chip frame buffer 702 to main memory 112 for access by display/video interface unit 164. This copy operation 700c can 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.
Example Indirect Texturing—logical Overview
[0111] FIG. 6 shows a logical overview of indirect texturing supported by system 50. In accordance with the logical overview as illustrated by FIG. 6 , a rasterizer 6000 may generate N sets of indirect texture addresses (coordinates), ADDR_A0 through ADDR_A(N−1), and M sets of direct texture addresses (coordinates), ADDR_B0 through ADDR_B(M−1). The N sets of indirect texture coordinates, ADDR_A0 through ADDR_A(N−1), are passed to N corresponding logical texture lookup units 6002, 6004, 6006 (A0 through A(N−1)). Each logical texture lookup unit (which, in one example implementation, is provided by reusing the same physical texture lookup units N times) uses the received indirect texture coordinates to look-up (retrieve) a texel value from a corresponding texture map—each of which may be a unique and different texture map. These lookup operations result in N sets of indirect texture lookup values, DATA_A0 through DATA_A(N−1), that are provided to a texture address processor (6008). Texture address processor 6008 also receives M sets of direct texture coordinate inputs. ADDR_A0 to ADDR_A(N−1).
[0112] The Texture Address Processor 6008 computes K sets of new/modified direct texture addresses (coordinates), ADDR_C0 through ADDR_C(K−1), based upon a predetermined function of the indirect texture lookup data values and the direct texture coordinates. Each of the K computed sets of direct texture coordinates (addresses), ADDR_C0 through ADDR_C(K−1), is passed to corresponding logical texture lookup units C0 (6010) and C1 (6012) through C(K−1) (6014). On one example implementation, these logical texture units C0-C(K−1) can be provided by reusing the same physical texture mapper used to provide logical texture units A0-A(N−1). Each texture lookup unit, C0 through C(K−1), uses the received coordinates to look-up a texel value in a corresponding texture map.
[0113] K sets of texture lookup values, DATA_C0 through DATA_C(K−1), resulting from the texture lookups are then provided to a pixel shader (6016). Pixel Shader 6004 receives the K sets of received texture values, along with zero, one, or more sets of rasterized (Gouraud shaded) colors. Pixel Shader 6016 then uses the received texture values, DATA_C0 to DATA_C(K−1), according to a predetermined shading function to produce color output values that may be passed, for example, to a video display frame buffer.
[0114] To aid in understanding, FIGS. 7A and 7B , respectively, illustrate simplified examples of a regular (non-indirect) texture lookup operation and an indirect texture lookup operation. As shown in FIG. 7A , a regular texture mapping lookup operation 950 may require specifying at least a set of regular (non-indirect) texture coordinates and a texture map ID as inputs. For this example, texture color data is retrieved (from the appropriate texture map) by texture unit 500a (FIG. 5 ) and then provided to texture environment unit (TEV) 600a for color blending.
[0115] In an example indirect texture lookup operation, as illustrated in FIG. 7B , a texture mapping occurs in multiple stages/cycles. During a first stage, a set of indirect texture coordinates are provided as inputs 901 along with a texture map ID corresponding to an indirect-texture mapping operation 952. In the next, or a subsequent stage, data retrieved from the indirect texture lookup 952 is used in conjunction with a set of regular (non-indirect) texture coordinates 903 to produce a set of new/modified coordinates 905 for another (regular) texture lookup 950 using input texture map ID 907. During each stage, various programmable operations 909 may be performed on the retrieved data and coordinates to obtain the new/modified lookup coordinates. In one example implementation, blocks 952 and 950 in the FIG. 7B example are performed by the same hardware that is reused or recycled in a staged or recirculating manner.
Example Direct and Indirect Texture Addressing
[0116] FIG. 8 shows an example basic physical configuration for implementing direct and indirect texturing while providing reuse of a physical texture mapping unit(s) in an interleaved fashion. Rasterizer 7000 sequentially generates all the direct and indirect texture address coordinate sets associated with each pixel. In an example implementation, rasterizer 7000 provides coordinate sets in parallel for four pixels in a pixel tile (i.e., a 2×2 or other pixel region), but other implementations are possible. In the example shown, rasterizer 7000 first generates indirect texture coordinate sets per pixel (e.g., ADDR_A0 through ADDR_A(N−1)), followed by all direct texture coordinate sets per pixel (e.g., ADDR-B0 through ADDR_B(M−1)). Each pixel may have differing amounts of direct and indirect coordinate data associated with it depending on the texturing operations being performed. For example, certain pixels may not require indirect texture addressing and will not have associated indirect coordinate data while other pixels may require one or more indirect texture addressing operations and will have one or more corresponding sets of associated direct and indirect coordinates.
[0117] In an example implementation of the texture processing circuitry of the graphics pipeline 180, texture processing is accomplished utilizing the same texture address processor and the same texture retrieval unit. To maximize efficient use of the texture processing hardware and avoid coarse granularity in the overall data processing flow through the pipeline, the processing of logical direct and indirect texture addresses (coordinates) and the lookup (retrieval) of texture data is performed in a substantially continuous and interleaved fashion. Indirect texture coordinate sets generated by rasterizer 7000 per pixel are passed directly to a single texture retrieval unit 7012 via switches S0 (7002) and S1 (7010), while non-indirect (logical direct) coordinate sets are placed in Direct Coordinate FIFO (dFIFO) 7006.
[0118] In an example implementation of the graphics pipeline, texture retrieval unit 7008 operates on at least one texture per clock and is capable of handling multiple texturing contexts simultaneously by maintaining state information and cache storage for more than one texture. Retrieved indirect texture data, DATA_A0 through DATA_A(N−1), is passed via feedback path 7018 to Indirect Data FIFO (iFIFO) 7004 via switch S2, where the retrieved indirect texture data is stored until needed. Direct texture coordinates are passed to Direct Coordinate FIFO (dFIFO) 7006 via switch S0 where they are stored until needed. In the above example discussed with respect to FIG. 6 , Indirect Data FIFO 7004 would receive the N sets of indirect texture data and Direct Coordinate data FIFO 7006 would receive the M sets of direct texture coordinates. Texture Address Processor 7008 would subsequently compute K new sets of texture coordinates based on a predetermined function of the input direct texture coordinates and the retrieved indirect texture data. Since processing of logical direct and indirect coordinates is interleaved, whenever there is more than one direct texture operation intervening between successive indirect texture operations, the processing of direct coordinates may lag behind with respect to the retrieval of corresponding indirect data. Consequently, buffers (e.g., FIFOs) 7004 and 7006 are provided to allow synchronization/realignment of retrieved indirect texture lookup data with the appropriate corresponding set of direct coordinates prior to both being provided simultaneously to texture address processor 7008.
[0119] The computed K sets of texture coordinates, ADDR_C0 through ADDR_C(K−1) are output sequentially over K clocks. Switch S1 (7010) interleaves the computed texture coordinate data (sets) into the incoming indirect texture coordinate stream for providing to texture unit 7012. It does this by looking for unused or idle cycles (“bubbles”) in the incoming indirect texture coordinate stream, and inserting the computed texture coordinate data (sets) during these cycles. Switch S2 (7014) routes the resulting texture lookup data, DATA_C0 to DATA_C(K−1), as well as the rasterized colors to a pixel shader 7016. Pixel shader (TEV) 7016 applies a predetermined shading function and outputs a single set of color values which may then be passed, for example, to a video display frame buffer.
[0120] In an example hardware implementation, the operation of the texture address processor may be simplified by utilizing the following two exemplary operational constraints:
-
- [0121] 1) The number of sets of computed texture coordinates, K, is equal to the number of sets of rasterized direct texture coordinates, M; and
- [0122] 2) The value of a computed texture coordinate set, ADDR_C[i], is a function, f(a, b, c), of a direct texture coordinate set, ADDR_B[i], and one set of indirect texture data, DATA_A[j], together (optionally) with the computed result from the previous processing stage, ADDR_C[i−1]. This operational relationship may be represented by the following equation:
ADDR—C[i]=f(ADDR—B[i],DATA—A[j],ADDR—C[i−1])
[0123] FIG. 9 shows a logical diagram implementation of texture address (coordinate/data) processor 7008 according to the above operational relationship. Buffer 7009 stores and optionally provides a computed texture coordinate result from the previous cycle. Careful FIFO addressing ensures that the correct indirect texture DATA_A value is available at the proper processing cycle/stage.
Example Interleaved Processing in Texture Processing Pipeline
[0124] FIGS. 10A–10K illustrate the dynamic, interleaved operation of the FIG. 8 arrangement. These figures show a series of block diagrams illustrating an example of the relative progression of pixel direct coordinate data and pixel indirect texture data at successive processing stages as a result of interleaved direct and indirect texture processing in the above example recirculating texturing pipeline embodiment of FIG. 8 . In this example illustration, a first pixel, PX0, requires an indirect texturing operation. As shown in FIG. 10A , a set of indirect texture coordinates (PX0 IND), and a corresponding set of direct texture coordinates (PX0 DIR), associated with pixel PX0 are provided by rasterizer (400) and shown as just entering the texturing pipeline at switch S0.
[0125] In FIG. 10B , indirect coordinates PX0 IND for pixel PX0 are provided directly to texture unit 500a via switches S0 and S1. Direct coordinates PX0 DIR for pixel PX0, which follow the direct coordinates for pixel PX0, are provided via switch S0 to Direct FIFO (dFIFO) 7004 for temporary storage while the indirect coordinates are processed. The texture unit 7012 performs an indirect texture lookup based on indirect coordinates PX0 IND for pixel PX0 to provide computed data (see FIG. 10C ) and, as shown next in FIG. 10D , provides (recirculates) the retrieved indirect texture lookup data, PX0 DATA, back to the texturing pipeline input, for example, via switch S2. As shown in FIG. 10D , the recirculated indirect texture lookup data, PX0 DATA, is provided to indirect FIFO (iFIFO) where it is effectively paired (through synchronization between buffers 7004, 7006) with the associated direct texture coordinate set, PX0 DIR. The indirect texture lookup data, PX0 DATA, and the direct texture coordinate set, PX0 DIR, are ready to be processed together by the texture address processor to compute a new/modified texture address coordinate set for pixel PX0. The texturing pipeline consumes this pair of values from buffers 7004, 7006 by computing texture coordinates (see FIG. 10E ) which are used to map a texture and provide color/alpha texel data to the shader (see FIG. 10F ).
[0126] Referring back to FIG. 10D , suppose that the rasterizer continues to provide the texturing pipeline input at switch S0 with sets of texture coordinates for texturing subsequent pixels. In this illustration, a series of subsequent pixels following pixel PX0, for example PX0 through PX49, are to be textured using only direct texturing operations. The rasterizer provides the appropriate direct texture coordinate sets PX1 DIR through PX49 DIR per pixel, which are directed via switch S0 to the direct coordinate FIFO (dFIFO) as shown in FIG. 10E . Once the texture address processor has computed a new/modified texture address coordinate set for pixel PX0, it accepts direct texture coordinate set PX1 DIR (see FIG. 10F ).
[0127] As also shown by FIG. 10F , suppose the rasterizer next provides a pixel. PX50, which follows pixel PX49, is to be textured using an indirect texturing operation. As illustrated by FIG. 10G , switch S0 provides the incoming indirect texture coordinate set, PX50 IND, for pixel PX50 directly to the texture retrieval unit 7012. Giving the indirect texture coordinates priority generally assures that the resulting indirect data from an indirect texture mapping will be present in buffer 7004 by the time it is needed (thus preventing pipeline stalling and wasted cycles). Note, however, that in this example, the indirect texture coordinates for a much later pixel in the rendering sequence (e.g. PX50) are being processed by texture retrieval unit 7012 before the retrieved unit processes an earlier pixel in the sequence (e.g., PX2). Such dynamic interleaving exhibited by the example texture processing pipeline has advantages in terms of efficiency.
[0128] As shown in FIG. 10G , the incoming direct texture coordinate set, PX50 DIR, for pixel PX50 is provided via S0 to direct coordinate FIFO (dFIFO) for buffering (as also shown in FIG. 10G , a texture color, PX1 TEX Color, for pixel PX1 corresponding to direct coordinate set PX1 DIR is output at this point by the texture retrieval unit from the texture lookup and is directed via switch S2 to the pixel shader).
[0129] Next as shown in FIG. 10H , after the texture retrieval unit performs the texture lookup based on indirect coordinate set PX50 IND, the indirect texture lookup data, PX50, retrieved by the texture retrieval unit is recirculated via switch S2 to indirect texture data FIFO (iFIFO). FIG. 10H also shows that the next direct coordinate set, PX2 DIR, in the stream from dFIFO is processed by the texture address processor and provided via switch S1 to the texture retrieval unit.
[0130] FIG. 101 shows a texture color, PX2 TEX Color, for pixel PX2 corresponding to direct coordinate set PX2 DIR being outputted from the texture retrieval unit and directed to the pixel shader via switch S2. In the same processing stage, the next direct texture coordinate set, PX3 DIR, from dFIFO is processed by the texture address processor and provided via switch S1 to the texture retrieval unit and indirect texture lookup data, PX50, is saved in iFIFO awaiting the propagation of the corresponding PX50 direct coordinate through buffer 7006.
[0131] As illustrated by the example in FIG. 10J , the direct coordinate stream, PX5 DIR through PX49 DIR, in the dFIFO are processed in turn by the texture address unit and provided via switch S1 to the texture retrieval unit 7012. Each of the retrieved texture colors corresponding to direct coordinate sets PX5 DIR through PX49 DIR in the stream are then provided in turn to the pixel shader via switch S2. Indirect texture lookup data, PX50 (which is being held in iFIFO 7004 until it can be matched up with the corresponding direct coordinates, PX50 DIR, for pixel PX50 in the dFIFO) is finally ready to be released (as shown in FIG. 10K ), once all the intervening direct coordinate sets, PX5 DIR through PX49 DIR, have been processed. The indirect texture data PX50 stored in the iFIFO can then be paired with its corresponding direct coordinate set PX50 DIR and provided to the texture address processor for computing a new/modified texture coordinate set for pixel 50.
Example More Detailed Implementation
[0132] FIG. 11 is a flow chart showing an example set of basic processing steps used to perform indirect texture mapping for an example implementation. Most of the steps of FIG. 11 are set up by a general indirect texturing API (application program interface) function 801 that sets parameters for processing an indirect texture by texture unit 500 and texture environment unit 600.
[0133] System 50 first stores a texture image/data in texture memory 502 for use as an indirect texture (block 800). Based on one or more API command functions (blocks 802–810), commander processor 200 then provides a specified set of indirect texture coordinates to texture retrieval unit 500a (see FIG. 5 ) which accesses texture memory 504 and retrieves indirect texture lookup data (FIG. 7B block 952). In the example embodiment, one or more API indirect texture function(s) 801 allow a graphics application to set up associations between texture maps and texture coordinates and to specify which sets of texture maps and coordinates are to be used when performing indirect and direct texture referencing operations. For example, in a basic indirect texturing operation, one or more sets of indirect-texture coordinates are specified (block 802), one or more texture maps are identified (block 804), parameters for computing new/modified texture coordinates and the processing order and number of indirect-texture references are specified (block 806), one or more texture maps are identified as indirect textures (block 808) and a set of indirect-texture coordinates is associated with an indirect-texture map (block 810).
[0134] The data retrieved from the indirect-texture lookup operation is “recirculated” back to the same texture address (coordinate) bump/processing circuitry 500b/500c via feedback connection 500d for further processing. Texture bump/processing circuitry 500b/500c then use the retrieved indirect-texture lookup data as coordinates offset factors in computing new texture coordinates based upon a current regular (non-indirect) texture coordinate and/or pre-defined texture scaling, bias and rotation data (block 812). The new/modified coordinates are then used as regular direct (non-indirect) coordinates for mapping a texture to a polygon (block 814; FIG. 7B block 950). Alternatively, these new/modified coordinates can be re-used again for additional/subsequent coordinate operations via a further recirculation of the texture mapping hardware in a yet further texture mapping operation. In this manner, multiple levels of indirection can be staged and processed using a single texture coordinate bump/processing circuit 500b/500c and a single texture retrieval unit 500a. Ultimately, retrieved texture lookup data is provided to texture environment unit 600 for staged color blending, for example, with other textures.
Example Coordination of Texture Operations With Shader Operations
[0135] In an example implementation of system 50, the indirect and direct texturing operations described above are coordinated with corresponding stages of a recirculating shader within texture environment unit 600. See commonly assigned copending application Ser. No. 09/722,367, entitled “Recirculating Shade Tree Blender For A Graphics System”.
[0136] FIG. 12 is a functional diagram illustrating an example of how to set up regular texture mapping to coordinate with shader stages. Texture lookup parameters specified, for example, by an API function(s), identify stored texture maps associated with sets of regular (non-indirect) texture coordinates. Texture lookups are performed using sets of texture coordinates to access the identified texture map(s) stored in memory. The retrieved texture lookup data is then passed to TEV unit 600 for color blending.
[0137] In an example embodiment of the present invention, TEV unit 600 allows programmable color data blending operations for accomplishing polygon texturing and shading during discrete processing stages. These stages are pre-defined by an appropriate API command function. In the example embodiment, up to sixteen TEV processing stages can be pre-defined. Each stage is assigned a processing order ID (number) and processed in sequence. In this example, selected TEV processing stages 910 are associated with a set of texture lookup parameters 912 specifying a regular texture lookup operation using a texture coordinate ID 914 and an associated texture map ID 916. The appropriate texture is looked up using the associated coordinates and the retrieved texture data is provided for the corresponding TEV stage blending. While FIG. 8 reflects that the example embodiment provides up to eight textures and up to sixteen TEV stages, any number can be used in alternate implementations.
[0138] The list of texture coordinate/texture map pairs are processed by recirculating texture unit 500 and texture environment unit 600 in an order specified by a GXSetTevOrder command using a number of recirculating stages as set by the GXSetNumTev stages command. In the particular example shown in FIG. 8 , a set of texture coordinates designated by an API command, GX_TEXCOORD IDs no.7 are used to perform a direct texture mapping using a texture map no.3 designated by a GX_TEXMAP IDs API command. The results of that particular texture lookup in this example are passed to the texture environment unit 600 for processing in a TEV stage zero, as designated by a GEXSetTevOrder API command. In this example, another set of texture coordinates designated no. 2 are used in a further texture mapping process using a texture map no. 4 in a further texture mapping stage (e.g., stage no. 3), and the results of this texture lookup are further processed by the texture environment unit 600 in a TEV processing stage no. 3. FIG. 12 shows a further example texture lookup stage no. 5 using a set of texture coordinates identified by identification no. 3 and a texture map identified by identification no. 4 in a fifth texture lookup stage, and the results of this texture lookup are processed by TEV stage no. 5. Similarly, a texture coordinate set no. 5 is used to lookup a further texture map no. 6 and a seventh texture lookup and associated TEV processing stage; and a set of texture coordinates no. 6 are used to lookup a texture map no. 7 in a ninth texture lookup stage and the results of this texture lookup are processed using a ninth TEV processing stage. The GXSetTevOrder API command specifies the order in which the various texture coordinate/texture map identification pairs are processed by the texture unit 500 and the texture environment unit 600. The particular order and the particular IDs shown in FIG. 12 are by way of example only.
[0139] FIG. 13 is a functional diagram illustrating examples of how to set up a sequence of regular and indirect texture processing to coordinate with recirculating shader stages. In this example, selected TEV processing stages are associated with a set of texture lookup parameters 911 specifying both regular and indirect texture lookup operations. For indirect mapping a set of indirect lookup parameters 913 associate an indirect-texture coordinate ID 904 with a corresponding texture map ID 916. In this case, the texture coordinate is specified as an “indirect” coordinate. An indirect-texture lookup is performed and the indirect texture lookup results are combined with a regular texture coordinate to obtain a new/modified texture coordinate. The new/modified texture coordinate is then used to access an associated texture map 916 and the resulting texture lookup data is provided for the corresponding TEV stage.
[0140] In the FIG. 13 example, additional API commands GXSetIndTexOrder, GXSetNuIndStages and GXSetTevIndirect are used to invoke the indirect texture lookup operations. In the particular example shown, texture coordinate/texture map pair no. 0 are used to perform an indirect texture lookup and the result of that indirect texture lookup is combined by operator 909 (see FIG. 7B ) with the set of texture coordinates designated no. 7 to perform a direct texture lookup using texture map designated no. 3 in a recirculating processing stage 0. In a similar manner, a texture coordinate/texture map pair no. 1 are used to perform an indirect texture lookup to yield retrieved data that operator 909 combines with a texture coordinate set no. 2 to perform texture mapping on a corresponding direct texture map no. 4. In the particular FIG. 13 example shown, a further indirect texture lookup using a texture map no. 2 and a set of texture coordinates no. 4 provide indirect texture lookup results that operator 909 uses for two successive direct texture lookups using a texture coordinate no. 3/texture map no. 5 pair (in TEV processing stage no. 5) and a set of texture coordinates no. 5/texture map no. 6 pair in a seventh TEV processing stage. The particular texture coordinate ID numbers, texture map ID numbers and TEV processing stage numbers shown in FIG. 13 are by way of example only.
Example Api Indirect Texture Function Commands
[0141] As shown in FIGS. 12–13 , one or more graphics API functions are used to set up and initiate direct and indirect texturing operations. Example API functions for setting up indirect texture operations and parameters may be defined as follows:
[0142] GXSetIndTexOrder
[0143] This function is used to specify the texture coordinate and texture map to be used with a given indirect lookup.
[0144] Arguments:
[0145]
| ind_stage | The indirect stage that is being affected. |
| tex_coord | The texcoord to be used for this stage. A given texcoord can |
| be shared by an indirect and regular stage at the same time. | |
| tex_map | The texture map to be used for this stage. A given texture map |
| can only be indirect or regular, not both. | |
[0146] In more detail, example arguments are:
[0147]
| u8 | NumIndtex; | // Number of indirect textures. |
| GXIndTexStageID | IndexTesId[ ]; | // Indirect texture stages being |
| affected. | ||
| GXTexMapID | Tex_map[ ]; | // Indirect texture map (ID) to be |
| used for this stage. | ||
| GXTexCoordID | Tex_coord[ ] | // Associated texture coordinate for |
| each indirect texture map. | ||
[0148] The above function associates a specified texture map and a texture coordinate with an indirect texture map ID name. It is used to specify a texture coordinate and a texture map to use with a given indirect lookup. In one example embodiment, a specified texture map is used as either an indirect or a direct texture, but not both, although alternative arrangements are possible.
[0149] Example Usage:
[0150]
| void GXSetIndTexOrder(GXIndTexStageID ind_stage, | |
| GXTexCoordID tex_coord, | |
| GXTexMapID tex_map); | |
[0151] GXSetTevIndirect (GXSetIndirectTexture)
[0152] This is the general-purpose function used to control how the results from an indirect lookup will be used to modify a given regular TEV stage lookup.
[0153] Arguments:
[0154]
| tev_stage | The TEV stage that is being affected. |
| ind_stage | The indirect stage results to use with this TEV stage. |
| format | Indicates how many bits to extract from the indirect result |
| color to use in indirect offsets and the indirect “bump” | |
| alpha. | |
| bias_sel | Indicates whether or not a bias should be applied to each |
| component of the indirect offset. | |
| matrix_sel | Indicates which indirect matrix and scale value to multiply |
| the offsets with. | |
| wrap_s | Indicates the wrapping factor to use with the S component |
| of the regular texture coordinate. | |
| wrap_t | Indicates the wrapping factor to use with the T component |
| of the regular texture coordinate. | |
| add_prev | Indicates whether the texture coordinate results from the |
| previous TEV stage should be added in. | |
| utc_lod | Indicates whether to use the unmodified (GX_TRUE) or |
| modified (GX_FALSE) texture coordinates for mipmap | |
| LOD computation. | |
| alpha_sel | Indicates which offset component will supply the indirect |
| “bump” alpha, if any. | |
[0155] In more detail, example arguments are:
[0156]
| GXTevStageID | TevStageId; | // TEV color combining stage ID |
| name. | ||
| GXIndTexStageID | indStage; | // indirect tex stage used with this |
| TEV stage. | ||
| GXIndTexFormat | Fmt; | // format of indirect texture offsets. |
| GXIndTexBiasSel | Bias; | // Selects which offsets (S, T) receive |
| a bias. | ||
| GXIndTexAlphaSel | AlphaSel; | // Selects indirect texture alpha |
| output. | ||
| GXIndMtxID | MatrixSel; | // Selects which texture offset matrix |
| and scale. | ||
| GXIndTexWrap | WrapS; | // Wrap value of direct S coordinate. |
| GXIndTexWrap | WrapT; | // Wrap value of direct T coordinate |
| GXBool | IndLOD; | // Use modified texture coordinates |
| for level of detail (LOD). | ||
| GXBool | AddPrev; | // Add output from previous stage to |
| texture coordinates. | ||
[0157] The above function allows setting all of the various parameters for processing a given indirect texture associated with a particular TEV stage. The function associates an indirect texture map with a TEV color combining stage, specifies how the retrieved indirect-texture lookup data (color values) will be converted to texture coordinate offsets (i.e. 3, 4, 5 or 8 bit format), selects texture offset matrix and texture scaling values, specifies texture-coordinate wrap parameters and whether the computed new/modified coordinates should be used for level of detail (LOD) with mip-mapped textures. The function also allows selecting whether the computed output from the texture processing logic 512 (see below) during a previous stage is added to text coordinate in a current stage.
[0158] Example Usage:
[0159]
| void GXSetTevIndirect | (GXTevStageID tev_stage, | |
| GXIndTexStageID ind_stage, | ||
| GXIndTexFormat format, | ||
| GXIndTexBiasSel bias_sel, | ||
| GXIndTexMtxID matrix_sel, | ||
| GXIndTexWrap wrap_s, | ||
| GXIndTexWrap wrap_t, | ||
| GXBool add_prev, | ||
| GXBool utc_lod, | ||
| GXIndTexAlphaSel alpha_sel); | ||
[0160] GXSetIndTexMtx
[0161] This function lets one set one of the three static indirect matrices and the associated scale factor. The indirect matrix and scale is used to process the results of an indirect lookup in order to produce offsets to use during a regular lookup. The matrix is multiplied by the [S T U] offsets that have been extracted (and optionally biased) from the indirect lookup color. In this matrix-vector multiply, the matrix is on the left and the [S T U] column vector is on the right.
[0162] The matrix values are stored in the hardware as a sign and 10 fractional bits (two's complement). Thus the smallest number that can be stored is −1 and the largest is (1−1/1024) or approximately 0.999. Since +1 cannot be stored, you may consider dividing all the matrix values by 2 (thus +1 becomes +0.5) and adding one to the scale value in order to compensate.
[0163] In more detail, example arguments are:
[0164]
| GXIndTexMtsID | MtxId; | // Texture offset matrix name. |
| F32 | Offset Matrix [3][2]; | // Matrix elements for the texture |
| offset matrix. | ||
| GXIndTexFormat | Fmt; | // Exponent value for scaling |
| (scale = 2ScaleExp). | ||
[0165] The above example API function sets matrix M and scale values in lookup data processing logic (proc) 512. The retrieved indirect texture lookup data (e.g. texture coordinate offsets s, t, u) is multiplied by Offset Matrix 525 (M) and the scaling factor 526. The OffsetMatrix is an API function parameter specifying the 3×2 element matrix elements used within indirect processing logic 512 (see below). In a preferred embodiment, the matrix elements are within the range (−1,1). ScaleExp is a parameter specifying power-of-two exponent used for setting the scale factor. The preferred range of ScaleExp is (−32, 32).
[0166] Example Usage:
[0167]
| void GXSetIndTexMtx( | GXIndTexMtxID mtx_sel, | |
| f32 offset_mtx[2][3], | ||
| s8 scale_exp) | ||
[0168] GXSetIndTevOrder
[0169] The above function associates a regular non-indirect texture map and a texture coordinate with an indirect texture map ID name.
[0170]
| GXSetTevStageID | stage | |
| GXSetTexCoordID | coord | |
| GXChannelID | color | |
[0171] Example Usage:
[0172]
| void GXSetIndTexOrder | (GXIndTevStageID | tev_stage, | |
| GXTexCoordID | cood. | ||
| GXChannelID | color); | ||
[0173] GXSetNumIndStages
[0174] This function is used to set how many indirect lookups will take place. The results from these indirect lookups may then be used to alter the lookups for any number of regular TEV stages.
GXSetNumIndStages u8 Stages
[0175] The above function sets the number of indirect texture lookup stages.
[0176] Example Usage:
-
- [0177] void GXSetNumIndStages(u8 nstages);
[0178] GXSetNumTevStages
[0179] This function enables a consecutive number of Texture Environment (TEV) stages. The output pixel color (before fogging and blending) is the result from the last stage. The last TEV stage must write to register GX_TEVPREV, see GXSetTevColorOp and GXSetTevAlphaOp. At least one TEV stage must be enabled. If a Z-texture is enabled, the Z texture must be looked up on the last stage, see GXSetZTexture.
[0180] The association of lighting colors, texture coordinates, and texture maps with a TEV stage is set using GXSetTevOrder. The number of texture coordinates available is set using GXSetNumTexGens. The number of color channels available is set using GXSetNumChans.
[0181] GXInit will set nStages to 1.
[0182] Arguments:
- [0183] nStages Number of active TEV stages. Minimum value is 1, maximum value is 16. In more detail:
GXSetNumTevStages u8 Stages
[0184] The above function sets the number of TEV color blending stages. This function sets parameters associated with the amount of recirculation being performed by texture unit 500 and texture environment unit 600, as well as the sequence the recirculating stages are performed in.
[0185] Example Usage:
-
- [0186] void GXSetNumTevStages(u8 nStages);
[0187] GXSetIndCoordTexScale
[0188] This function is used when one wishes to share a texcoord between an indirect stage and a regular TEV stage. It allows one to scale down the texture coordinates for use with an indirect map that is smaller than the corresponding regular map.
[0189] Arguments:
[0190]
| ind_stage | The indirect stage that is being affected. | |
| scale_s | The scale factor for the S coordinate. | |
| scale_t | The scale factor for the T coordinate. | |
[0191] In more detail, example arguments are:
[0192]
| GXIndTexMapID | IndTexId; | // Indirect texture name. |
| GXIndTexScale | Scale S; | // Scale value for S coordinate. |
| GXIndTexScale | Scale T; | // Scale value for T coordinate. |
[0193] The above function sets a value for scaling the indirect texture coordinates. The texture coordinates are scaled after a perspective divide and before addition to the regular non-direct texture coordinates.
[0194] Example Usage:
[0195]
| void GXSetIndTexCoordScale | (GXIndTexStageID ind_stage, | |
| GXIndTexScale scale_s, | ||
| GXIndTexScale scale_t); | ||
[0196] This function is used when one wishes to use the same texture coordinates for one TEV stage as were computed in the previous stage. This is only useful when the previous stage texture coordinates took more than one stage to compute, as is the same for GXSetTevIndBumpST.
[0197] Example Arguments:
-
- [0198] tev_stage The TEV stage that is being changed.
[0199] Example Usage:
-
- [0200] void GXSetTevIndRepeat(GXTevStageID tev_stage);
GXSetTevIndBumpST
- [0200] void GXSetTevIndRepeat(GXTevStageID tev_stage);
[0201] This function sets up an environment-mapped bump-mapped indirect lookup. The indirect map specifies offsets in (S, T) space. This kind of lookup requires 3 TEV stages to compute. The first two TEV stages should disable texture lookup. The third stage is where the lookup is actually performed. One may use GXSetTevIndRepeat in subsequent TEV stages to reuse the computed texture coordinates for additional lookups. The surface geometry must provide normal/binormal/tangents at each vertex.
[0202] Example Arguments:
[0203]
| tev_stage | The TEV stage that is being affected. |
| ind_stage | The indirect stage results to use with this TEV stage. |
| matrix_sel | Indicates which indirect scale value to multiply the |
| offsets with. | |
[0204] Example Usage:
[0205]
| void GXSetTevIndBumpST | (GXTevStageID tev_stage, | |
| GXIndTexStageID ind_stage, | ||
| GXIndTexMtxID matrix_sel); | ||
[0206] GXSetTevIndBumpXYZ
[0207] This function sets up an environment-mapped bump-mapped indirect lookup. The indirect map specifies offsets in object (X, Y, Z) space. This kind of lookup requires only one TEV stages to compute. The indirect matrix must be loaded with a transformation for normals from object space to eye space. The surface geometry need only provide regular normals at each vertex.
[0208] Example Arguments:
[0209]
| tev_stage | The TEV stage that is being affected. |
| ind_stage | The indirect stage results to use with this TEV stage. |
| matrix_sel | Indicates which indirect matrix and scale value to multiply |
| the offsets with. | |
[0210] Example Usage:
[0211]
GXSetTevDirect
| void GXSetTevIndBumpXYZ | (GXTevStageID tev_stage, | |
| GXIndTexStageID ind_stage, | ||
| GXIndTexMtxID matrix_sel); | ||
GXSetTevDirect
[0212] This function is used to turn off all indirect offsetting for the specified regular TEV stage.
[0213] Example Arguments:
- [0214] tev_stage The TEV stage that is being changed.
[0215] Example Usage:
-
- [0216] void GXSetTevDirect(GXTevStageID tev_stage);
GXSetTevIndWarp
- [0216] void GXSetTevDirect(GXTevStageID tev_stage);
[0217] This function allows an indirect map to warp or distort the texture coordinates used with a regular TEV stage lookup. The indirect map should have 8-bit offsets, which may be signed or unsigned. “Signed” actually means “biased,” and thus if signed_offsets is GX_TRUE, 128 is subtracted from the values looked up from the indirect map. The indirect results can either modify or completely replace the regular texture coordinates. One may use the indirect matrix and scale to modify the indirect offsets.
[0218] Arguments:
[0219]
| tev_stage | The TEV stage that is being affected. |
| ind_stage | The indirect stage results to use with this TEV stage. |
| signed_offsets | Indicates whether the 8-bit offsets should be |
| signed/biased (GX_TRUE) or unsigned (GX_FALSE). | |
| replace_mode | Indicates whether the offsets should replace |
| (GX_TRUE) or be added to (GX_FALSE) | |
| the regular texture coordinates. | |
| matrix_sel | Indicates which indirect matrix and scale value to |
| multiply the offsets with. | |
[0220] Example Usage:
[0221]
GXSetTevIndTile
| void GXSetTevIndWarp | (GXTevStageID tev_stage, | |
| GXIndTexStageID ind_stage, | ||
| GXBool signed_offsets, | ||
| GXBool replace_mode, | ||
| GXIndTexMtxID matrix_sel); | ||
GXSetTevIndTile
[0222] This function may be used to implemented tiled texturing using indirect textures. Note that the regular texture map only specifies tile definitions. The actual number of texels to be applied to the polygon is a function of the base tile size and the size of the indirect map. In order to set the proper texture coordinate scale, one must call GXSetTexCoordScaleManually. One can also use GXSetIndTexScale in order to use the same texcoord for the indirect stage as the regular TEV stage.
[0223] Example Arguments:
[0224]
| tev_stage | The TEV stage that is being affected. |
| ind_stage | The indirect stage results to use with this TEV stage. |
| tilesize_s | Indicates the size of the tile in the S dimension. |
| tilesize_t | Indicates the size of the tile in the T dimension. |
| Tilespacing_s | Indicates the spacing of the tiles in the S dimension. |
| Tilespacing_t | Indicates the spacing of the tiles in the T dimension. |
| Format | Indicates which indirect texture format to use. |
| matrix_sel | Indicates which indirect matrix and scale value to |
| multiply the offsets with. | |
| bias_sel | Indicates the tile stacking direction for pseudo-3D |
| textures. | |
| alpha_sel | Indicates which offset component will supply the indirect |
| “bump” alpha, if any (for pseudo-3D textures). | |
[0225] Example Usage:
[0226]
| void GXSetTevIndTile | (GXTevStageID tev_stage, | |
| GXIndTexStageID ind_stage, | ||
| u16 tilesize_s, | ||
| u16 tilesize_t, | ||
| u16 tilespacing_s, | ||
| u16 tilespacing_t, | ||
| GXIndTexFormat format, | ||
| GXIndTexMtxID matrix_sel | ||
| GXIndTexBiasSel bias_sel | ||
| GXIndTexAlphaSel alpha_sel); | ||
[0227] GXSetTevIndRepeat
[0228] This function is used when one wishes to use the same texture coordinates for one TEV stage as were computed in the previous stage. This is useful when texture coordinates require more than one processing cycle/stage to compute.
Example Arguments:
-
- [0229] Tev_stage The TEV stage that is being changed.
[0230] Example Usage:
-
- [0231] void GXSetTevIndRepeat (GXTevStageID tev_stage);
GXSetAlphaCompare
- [0231] void GXSetTevIndRepeat (GXTevStageID tev_stage);
[0232] This functino sets the parameters for the alpha compare function which uses the alpha output from the last active Texture Environment (TEVk) stage. The number of active TEV stages are specified using GXSetTevStages.
[0233] The output alpha can be used in the blending equation (see GXSetBlendMode) to control how source and destination (frame buffer) pixels are combined.
[0234] The alpha compare operation is:
alpha—pass=(alpha—src(comp0)(ref0)(op)(alpha—src(comp)ref1)
alpha—pass=(alpha—src(comp0)(ref0)(op)(alpha—src(comp)ref1)
-
- [0235] where alpha_src is the alpha from the last active Tev stage. As an example, you can implement these equations:
alpha—pass=(alpha—src>ref0) AND (alpha—src<ref1)
or
alpha—pass=(alpha—src>ref0) OR (alpha—src<ref1)
- [0235] where alpha_src is the alpha from the last active Tev stage. As an example, you can implement these equations:
[0236] The Z compare may occur either before or after texturing. In the case where Z compare is performed before texturing, the Z is written based only the Z test. The color is written if both the Z test and alpha test pass.
[0237] When Z compare is done after texturing, the color and Z are written if both the Z test and alpha test pass. When using texture to make cutout shapes (like billboard trees) that need to be correctly Z buffered, one should perform Z buffering after texturing.
[0238] Example Arguments:
[0239]
| comp0 | Comparison subfunction 0. |
| ref0 | Reference value for subfunction 0, 8-bit. |
| op | Operation for combining subfunction 0 and subfunction 1. |
| Accepted values are: GX_AOP_AND, GX_AOP_OR, | |
| GX_AOP_XOR, GX_AOP_XNOR. | |
| comp1 | Comparison subfunction 1. |
| ref1 | Reference value for subfunction 1, 8-bit. |
[0240] Example Usage:
[0241]
| void GXSetAlphaCompare ( | ||
| GXCompare | comp0, | |
| u8 | ref0, | |
| GXAlphaOp | op, | |
| GXCompare | comp 1, | |
| u8 | ref1); | |
Example Hardware Implementation
[0242] In one preferred example embodiment, texture unit 500 and texture environment unit 600 have been implemented in hardware on a graphics chip, and have been designed to provide efficient recirculation of texture mapping operations as described above. In more detail, the texture address coordinate/bump processing block 500b/500c is implemented in hardware to provide a set of appropriate inputs to texture mapping block 500a and texture environment block 600a. Blocks 500b, 500c in conjunction with sequencing logic use to recirculate blocks 500a, 600a present a sequence of appropriate inputs at appropriate times with respect to various recirculating stages to efficiently reuse blocks 500a, 600a—in some cases creating a feedback loop via path 500d wherein the output of block 500a is modified and reapplied to its input in a later sequential recirculating processing stage. This results in a logical sequence of distinct texture processing stages that, in the preferred embodiment, are implemented through reuse/recirculation of the same hardware circuits over and over again. The resulting functionality provides any desired number of logical texture mapping processing stages without requiring additional hardware. Providing additional hardware for each of the various texture processing stages would increase speed performance but at the penalty of additional chip real estate and associated complexity. Using the techniques disclosed herein, any number of logical texture mapping stages can be provided using a single set of texture mapping hardware. Of course, in other implementations to improve speed performance, it would be possible to replicate the texture mapping hardware so that multiple texture mapping stages could be performed in parallel rather than in seriatim as shown in FIGS. 12 and 13 . Even in such alternative implementations providing multiple sets of the same or different texture mapping hardware, providing the recirculating and indirect texture mapping techniques disclosed herein would be quite valuable in expanding functionality and flexibility of more generic hardware to provide a particular sequence of possibly involved and complicated texture mapping operations or stages specified by an application programmer to achieve particular advanced texture mapping effects.
[0243] FIGS. 14 and 15 show one example implementation of particular hardware used to collect and present various parameters to texture unit 500 for logical direct and/or indirect texture mapping lookup. FIG. 14 shows a block diagram of an example hardware implementation of texture coordinate/bump processing hardware 500b/500c, and FIG. 15 shows an example processing and computation logic within the FIG. 14 example implementation. In the preferred implementation, the particular functions performed by the FIG. 14/FIG. 15 hardware are controlled by control data passes down the graphics pipeline to the hardware control logic registers 503 within coordinate/bump processing unit 500b/500c. Logical functions and computational operations occurring within each unit in graphics pipeline 180 are determined by control codes (bits) provided by command processor 200 in register data packets that are distributed throughout the graphics pipeline. The appropriate control codes/values are placed in control logic registers within each unit for controlling that input during one or more pipeline clocking cycles.
[0244] Referring to the FIG. 14 high level block diagram of an example hardware implementation of texture coordinate processing/bump block 500b/500c. Logical direct and indirect texture coordinates and hardware control register data are passed to texture coordinate processing/bump unit 500b/500c from rasterizer 400 (see FIG. 5 ) over graphics pipeline 180 data bus lines 501 (xym). Graphics pipeline global command data on pipeline command bus 505 (cmd) specifies whether incoming texture coordinates are “direct” or “indirect”. Direct texture coordinates (i.e., regular non-indirect texture coordinates) and indirect texture coordinates are provided from a rasterizer via pipeline data bus lines 507 (st) and are processed together in a substantially continuous interleaved fashion so as to maintain a fine granularity of processing throughout the graphics pipeline. Indirect texture lookup data is retrieved from texture unit 500a and “recirculated” back to coordinate processing/bump unit 500b/500c via texture color/data bus 518 (col) corresponding to data feedback path 500d (FIG. 5 ).
[0245] Control register data received from command processor 200 is stored in registers 503 for controlling indirect texturing operations. Some of the stored control register data is utilized, for example, for selecting and controlling various computational operations that take place within coordinate/lookup data processing logic 512 (proc) (as indicated, for example, by register data lines 520 in FIG. 15 ). A command decoder and synchronizing circuit, sync0 (502), determines whether incoming data on lines 501 (xym) are a set of direct texture coordinates, indirect-texture coordinates, or control logic register packets. Incoming direct coordinates are routed to a FIFO unit 506 (dfifo) for further processing by data synchronizing circuit 510 (sync2) and processing logic unit (proc) 512. Incoming indirect coordinates are routed directly to an output data synchronizing circuit 504 (sync1) for passing on to texture unit 500a (FIG. 5 ). Synchronizing circuits sync0 (502), sync1 (504) and sync2 (510) perform data routing and synchronization to control the timing and handling of indirect and direct texture coordinate data from the rasterizer (400) and retrieved indirect texture lookup data from the texture unit. Effectively, synchronizing circuits sync0 (502), sync1 (504) and sync2 (510) perform the respective functions of switches S0, S1 and S2 in FIG. 8 .
[0246] Incoming “recycled” indirect texture lookup data received via texture color/data feedback bus 518 (col) from texture unit 500a is placed in FIFO unit 508 (ififo). Direct texture coordinates are aligned at the st output of FIFO unit 506 (dfifo) with the incoming indirect texture lookup data at the col output 519 of FIFO unit 506 (dfifo). Synchronizing circuit 510 (sync2) performs further coordinate data alignment and assembles a complete set of operands to provide to processing unit 512 (proc) for indirect texture processing operations based on the control logic codes stored in registers 503. These operands include, for example, multiplication coefficients/constants for the texture offset matrix elements and lookup data formatting parameters for performing texture coordinate computations within processing unit 512 (proc). After coordinate data and retrieved indirect-texture lookup data is processed by proc unit 512, the resulting data (e.g., new/modified texture coordinates) is passed to synchronizing circuit 504 (sync1), where the data is interleaved with a stream of indirect texture coordinates from synchronization unit 502 circuit (sync0) and provided to texture retrieval unit 500a.
[0247] Referring now to the FIG. 15 example of the processing and computational logic within indirect-texture lookup data/coordinate processing unit 512 (proc), retrieved indirect-texture lookup data is in the form of data triplets having three data components (also referred to as s, t and u texture offsets). The number of data bits per component will be dependent in part upon the manner and purpose for which the particular indirect-texture map is used in an indirect texturing operation. Indirect-texture lookup data may also consist of “bump alpha data” used elsewhere in the graphics pipeline for transparency shading/blending. Retrieved indirect-texture lookup data (e.g., s, t and u offset data) on col bus 519 is first passed through Format selection block 521 which selects whether retrieved indirect texture lookup data is “bump alpha” data or is to be processed as multi-bit binary data triplets of three, four, five, or eight bits. The Format selection block provides offset data triplets to bias unit 523 and “bump alpha” data is routed to bump alpha select multiplexer 532 for use in transparency blending elsewhere in the graphics pipeline.
[0248] In a preferred example embodiment of the present invention, the Format unit logic extracts three texture offset data components of 8, 5, 4, or 3-bits from a 24-bit data triplet on the col input bus 519 and extracts 5-bit bump-alpha select values (bs, bt, and bu)for possible output on the xym bus. Bypass multiplexer 532 is provided to allow selection of one bump-alpha value, bs, bt, or bu, to be output on the pipeline xym bus. An optional bias value may be applied to the data triplets by bias unit 523. For example, if eight-bit data triplet components were selected, then a bias of −128 could be applied by bias unit 523 to allow for signed offsets. (If data triplet components of less than eight bits are used, then a bias of +1, for example, is applied).
[0249] A matrix select multiplexer 524 allows loading selected direct coordinates or constants for performing a matrix multiplication operation 525. In addition, a modulo wrap unit 527 is provided to optionally perform coordinate wrap operations on an associated regular direct texture coordinate. For example, using an API function, one may specify a wrap value of 0, 16, 32, 64, 128, or 256.
[0250] A matrix multiplication operation 525 is performed on a data triplet using matrix elements M. For example, the data triplet is loaded into a three-element vector data register V associated with matrix multiplication operation 525 and then multiplied by matrix elements M (FIG. 12A ). Matrix multiplication operation 525 may be used, for example, for rotation, scaling, and re-mapping of s, t and u texture offset triplets retrieved from an indirect-texture via col bus 519. Values of matrix elements M are variable and may be dynamically defined for each texture processing cycle/stage using selected matrix configurations. In a preferred embodiment, the multiplication matrix is a 3 by 2 element matrix having a programmable configuration selected either from one of three constant matrices comprising elements defined from selected logic control register data 520 or, alternatively, selected from one of two “variable” matrices having elements derived from the current direct texture coordinates obtained via the pipeline st coordinate data bus 522. Using an appropriate API function, one may predefine up to three different static matrices or two different variable matrices and select which matrix is to be used for a given indirect texture operation.
[0251] FIG. 16A illustrates an example texture offset matrix multiplication operation using matrix programmable static constant elements ma, mb, mc, md, me and mf. Retrieved indirect-texture lookup data comprising data triplet components s, t and u provide texture offset values are used as a multiplicand column vector matrix for the operation. The resultant product values are a pair of new/modified texture coordinates s′ and t′. In a preferred arrangement, elements of the matrix are represented by multi-bit binary floating point values within a range of −1 to +1. FIG. 16B illustrates two example “variable” matrices, Matrix A and Matrix B, having elements derived from current direct texture coordinates (s, t) obtained via the pipeline st coordinate data bus 522.
[0252] Referring once again to FIG. 15 , a scaling logic 526 is provided for performing optional scaling operations. Scale unit 526 scales the results of the matrix multiplication. The amount of scale is a power of 2 specified by the user. For example, using an API function, one may choose a scale value by specifying an exponent of 2 in the range of −32 to +31. This scale value can be used, for example, to stretch texture offsets over the size of a regular texture map that is associated with the indirect-texturing operation.
[0253] Wrap logic 527 optionally applies a (modulo) wrap to the direct texture coordinates before the final add. The wrap size is a programmable power of 2 specified, for example, by an API function through the control logic registers.
[0254] Once the above processing operations have taken place, the computed offsets are added to the current direct texture coordinates using adder 528. The result becomes the new/modified texture coordinate that is used for further direct or indirect texture lookup. Stage output re-circulation buffer 530 is provided to allow optionally adding the computation results from a previous processing stage may be optionally added. The resulting computed new/modified coordinates are passed to the texture retrieval unit 500a.
Example Hardware Control Register Formats
[0255] FIG. 17 shows example logic control register data field formats which may be used to define and control parameters and operations within processing unit 512. For example, certain data fields may be used to pass programmable constants ffor use as static matrix elements. Other fields may define data triplet format, control bias and scaling factors, indicate the number of indirect operation stages or provide other parameters for operations within proc logic unit 512.
[0256] The following table shows non-limiting example control register descriptions and formats for controlling operations within indirect-texture/bump unit 500b/500c and processing logic 512:
[0257]
| name: | format: | description: |
|---|---|---|
| mai, mbi, | S0.10 | Specifies parameters for one of the three texture |
| mci, mdi, | offset matrices. All recycled texture values are | |
| mei, mfi | passed through the matrix | |
| si | S5 | This field specifies post-scale for the matrix. |
| The scale is done by performing a shift on the | ||
| matrix outputs by an amount equal to (1 << n) for | ||
| positive values, and (1 << (−n)) for negative values. | ||
| bti | 2 | This field one of up to four indirect textures to use |
| during direct texture cycle, i. | ||
| fmti | 2 | This field specifies how the s, t, and u offsets, along |
| with the 5-bit bump alpha select values bs, bt, and | ||
| bu, are selected from the 24-bit recycled texture | ||
| data (col). | ||
| biasi | 3 | This field specifies whether or not to apply bias to |
| the s, t, and u coordinates after formatting and | ||
| before matrix multiplication. The amount of the bias | ||
| is −128 for the FMT_8 format, and +1 for the other | ||
| three formats (see “fmt” field description above). | ||
| mi | 4 | This field selects a matrix and scale to use during |
| the current direct texture cycle. In addition to the | ||
| three constant matrices defined using mai..mfi | ||
| (see above), two variable matrices are also defined | ||
| whose values are obtained from the current direct | ||
| texture coordinates | ||
| Matrix A _ ( s / 256 t / 256 0 0 0 0 ) | ||
| Matrix B _ ( 0 0 s / 256 t / 256 0 0 ) | ||
| swi, twi | 3 | This field implements a wrap on the s and t direct |
| texture coordinates prior to adding the texture offset | ||
| (this is done by using a bit-mask). | ||
| fbi | 1 | This field specifies whether to include computation |
| results from a previous computation stage (retained | ||
| in buffer 530) in the add performed by adder 518. | ||
| imask | 8 | This field specifies, for each of eight sets of texture |
| state, whether the textures associated with this state | ||
| are indirect (1) or direct (0). | ||
[0258] In the proc logic unit, for the control registers shown in FIG. 13 , registers MTXi define matrix element data for three matrices (i.e., i=0,1,2). Registers CMDi define the bump command for each of 16 TEV stages (i=0–15); registers IMASK defines the direct or indirect usage of each of up to eight textures.
Mode Changes
[0259] In an example implementation, operational mode changes within the pipeline are handled by interleaving a control register address-data pair (which contains, for example, the address of a particular hardware logic control register associated with some circuitry within the pipeline and the appropriate control data/instruction for controlling that circuitry) with rasterization data output by the rasterizer. This control register address-data pair information trickles down the graphics pipeline with the data and remains interleaved in the correct order with the data that it affects. Consequently, most operational mode changes may be effected without “flushing” (purging) the pipeline. Although mode changes may be complicated somewhat by the fact that there could be multiple paths data within the pipeline for control register data to reach its ultimate destination, more efficient operation may be obtained, for example, by adherence to the following exemplary operational constraints:
-
- [0260] 1) Hardware control register data affecting the texture address processor 500b/500c is passed through direct texture coordinate FIFO (dFIFO), (e.g., via switch SO);
- [0261] 2) Hardware control register data affecting direct contexts in the texture unit 500a is passed through the direct texture coordinate FIFO (dFIFO) in the texture address processor to texture unit 500a;
- [0262] 3) Hardware control register data affecting indirect texturing contexts in texture unit 500a are passed directly from the rasterizer 400 to texture unit 500a (e.g., via switches SO and S1); and
- [0263] 4) Hardware control register data affecting the pixel shader (TEV) or frame buffer 702 are passed through the direct texture coordinate FIFO (dFIFO), the texture address processor 500b/500c, and the texture unit 500a.
[0264] In an example implementation of the present invention, the possible texturing contexts are defined as either a direct context or an indirect context. Direct contexts may handle only direct texture data, and indirect contexts may handle only indirect texture data. A change in the definition of one or more contexts between, for example, indirect to direct or direct to indirect operation, may require a partial flush of the graphics pipeline.
Example Indirect Texture Processing Results
[0265] As will now be appreciated, the recirculating direct and indirect texture processing architecture described above provides an extremely flexible and virtually unlimited functionality. An application programmer can invoke any number of logical texture mapping stages to provide any desired sequence of any number of direct or indirect texture mapping operations. This powerful capability allows the application programmer to create dynamically a number of complex and interesting texture mapping visual effects.
[0266] As one example, indirect textures can be used for texture warping effects. In this example case, the indirect texture is used to stretch or otherwise distort the surface texture. A dynamic distortion effect can be achieved by swapping indirect maps (or by modifying the indirect map or coordinates). One may apply this effect to a given surface within a scene, or one can take this one step further and apply the effect to the entire scene. In the latter case, the scene is first rendered normally and then copied to a texture map. One then draws a big rectangle that is then mapped to the screen using an indirect texture. Texture warping can be used to produce shimmering effects, special lens effects, and various psychedelic effects.
[0267] As another example, the indirect feature also allows the drawing texture tile maps. In this scenario, one texture map holds the base definition for a variety of tiles. An indirect texture map is then used to place specific tiles in specific locations over a 2D surface. With indirect textures, only one polygon needs to be drawn.
Other Example Compatible Implementations
[0268] 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.
[0269] 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.
[0270] Some general purpose digital computers (e.g., IBM or MacIntosh personal 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 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.
[0271] FIG. 15 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.
[0272] 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 1303 fetches one or a sequence of binary-image program instructions from storage medium 62 and converts these program instructions to one or more equivalent Intel binary-image program instructions. The emulator 1303 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).
[0273] 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.
[0274] In the case where particular graphics support hardware within an emulator does not include the example indirect texture referencing features and functions illustrated by FIGS. 8 through 12 , the emulator designer has a choice of either:
-
- [0275] translating the indirect-texture referencing commands into other graphics API commands the graphics support hardware understands, or
- [0276] implementing indirect-texture referencing in software with a potential corresponding decrease in performance depending upon the speed of the processor, or
- [0277] “stubbing” (i.e., ignoring) the indirect-texture referencing commands to provide a rendered image that does not include effects utilizing indirect-texture referencing.
[0278] While the FIG. 6 flowchart can be implemented entirely in software, entirely in hardware or by a combination of hardware and software, the preferred embodiment performs most of these calculations in hardware to obtain increased speed performance and other advantages. Nevertheless, in other implementations (e.g., where a very fast processor is available), some or all of the processing described herein may be implemented in software to provide similar or identical imaging results.
[0279] FIG. 16 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.
[0280] 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.
[0281] 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.
[0282] 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 62.
[0283] All documents referenced above are hereby incorporated by reference.
[0284] 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. In a graphics system including a graphics processing pipeline that renders and displays images at least in part in response to primitive vertex data and texture data, a texture processing system for mapping a texture to a surface of a rendered image object, said texture processing system comprising:
a texture coordinate/data processing unit that interleaves processing of logical direct and indirect coordinate data;
a texture data retrieval unit connected to the coordinate/data processing unit, the texture data retrieval unit retrieving texture data; and
a data feedback path from the texture data retrieval unit to the texture coordinate/data processing unit to allow reuse of the texture coordinate/data processing unit in the same rendering pass;
wherein in response to a set of indirect texture coordinates the retrieval unit recirculates retrieved texture data back to the processing unit for deriving modified texture coordinates which are used in mapping a texture to a surface of a rendered image object.
2. The graphics system as set forth on claim 1 wherein the texture coordinate/data processing unit further comprises a set of hardware control logic registers coupled to data lines in the pipeline for receiving data and processing command information used to initiate indirect texture referencing and to control multiplication and addition operations for deriving said modified texture coordinates.
3. In a graphics system including a graphics processing pipeline that renders and displays images at least in part in response to polygon vertex data and texture data stored in a memory, the graphics processing pipeline having a texture subsystem for accessing and retrieving texture, the texture subsystem comprising a texture coordinate/data processing unit having: a) at least one binary data multiplier, at least one binary data accumulator and at least one control register for receiving instruction codes and/or data to control texture coordinate/data processing operations, b) a texture data retrieval unit connected to the coordinate/data processing unit, the texture data retrieval unit retrieving data stored in a texture memory, and c) a data feedback path from the texture data retrieval unit to the texture coordinate/data processing unit to retrieve texture data to the texture coordinate/data processing unit for further processing, wherein processing of direct texture coordinates is interleaved with processing of indirect texture coordinates to retrieve texture lookup data for use in deriving modified texture coordinates, a method for controlling the texture subsystem to perform one or more indirect texture referencing operations comprising the step of utilizing a generalized indirect-texture referencing API command function to place appropriate instruction codes and/or data in said control register(s), wherein said indirect-texture referencing function may be used to at least:
(i) define up to eight textures stored in a texture memory;
(ii) specify up to eight sets of texture coordinates;
(iii) define up to four indirect texture maps;
(iv) specify up to four indirect texture referencing operations to be performed;
(v) associate one of said eight textures with each indirect texture map; and
(vi) associate one of said eight sets of texture coordinates with each indirect texture maps.
Patent Citations (456)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4275413(A) | 1981-06-01 | Sakamoto et al. | Applicant |
| US4357624(A) | 1982-11-01 | Greenberg | Applicant |
| US4388620(A) | 1983-06-01 | Sherman | Applicant |
| US4425559(A) | 1984-01-01 | Sherman | Applicant |
| US4463380(A) | 1984-07-01 | Hooks, Jr. | Applicant |
| US4491836(A) | 1985-01-01 | Collmeyer et al. | Applicant |
| US4570233(A) | 1986-02-01 | Yan et al. | Applicant |
| US4586038(A) | 1986-04-01 | Sims et al. | Applicant |
| US4600919(A) | 1986-07-01 | Stern | Applicant |
| US4615013(A) | 1986-09-01 | Yan et al. | Applicant |
| US4625289(A) | 1986-11-01 | Rockwood | Applicant |
| US4653012(A) | 1987-03-01 | Duffy et al. | Applicant |
| US4658247(A) | 1987-04-01 | Gharachorloo | Applicant |
| US4692880(A) | 1987-09-01 | Merz et al. | Applicant |
| US4695943(A) | 1987-09-01 | Keeley et al. | Applicant |
| US4710876(A) | 1987-12-01 | Cline et al. | Applicant |
| US4725831(A) | 1988-02-01 | Coleman | Applicant |
| US4768148(A) | 1988-08-01 | Keeley et al. | Applicant |
| US4785395(A) | 1988-11-01 | Keeley | Applicant |
| US4790025(A) | 1988-12-01 | Inoue et al. | Applicant |
| US4808988(A) | 1989-02-01 | Burke et al. | Applicant |
| US4812988(A) | 1989-03-01 | Duthuit et al. | Applicant |
| US4817175(A) | 1989-03-01 | Tenenbaum et al. | Applicant |
| US4829295(A) | 1989-05-01 | Hiroyuki | Applicant |
| US4829452(A) | 1989-05-01 | Kang et al. | Applicant |
| US4833601(A) | 1989-05-01 | Barlow et al. | Applicant |
| US4855934(A) | 1989-08-01 | Robinson | Applicant |
| US4862392(A) | 1989-08-01 | Steiner | Applicant |
| US4866637(A) | 1989-09-01 | Gonzalez-Lopez et al. | Applicant |
| US4888712(A) | 1989-12-01 | Barkans et al. | Applicant |
| US4897806(A) | 1990-01-01 | Cook et al. | Applicant |
| US4901064(A) | 1990-02-01 | Deering | Applicant |
| US4907174(A) | 1990-03-01 | Priem | Applicant |
| US4914729(A) | 1990-04-01 | Omori et al. | Applicant |
| US4918625(A) | 1990-04-01 | Yan | Applicant |
| US4935879(A) | 1990-06-01 | Ueda | Applicant |
| US4945500(A) | 1990-07-01 | Deering | Applicant |
| US4965751(A) | 1990-10-01 | Thayer et al. | Applicant |
| US4974176(A) | 1990-11-01 | Buchner et al. | Applicant |
| US4974177(A) | 1990-11-01 | Nishiguchi | Applicant |
| US4975977(A) | 1990-12-01 | Kurosu et al. | Applicant |
| US4989138(A) | 1991-01-01 | Radochonski | Applicant |
| US5003496(A) | 1991-03-01 | Hunt, Jr. et al. | Applicant |
| US5016183(A) | 1991-05-01 | Shyong | Applicant |
| US5018076(A) | 1991-05-01 | Johary et al. | Applicant |
| US5043922(A) | 1991-08-01 | Matsumoto | Applicant |
| US5056044(A) | 1991-10-01 | Frederickson et al. | Applicant |
| US5062057(A) | 1991-10-01 | Blacken et al. | Applicant |
| US5086495(A) | 1992-02-01 | Gray et al. | Applicant |
| US5091967(A) | 1992-02-01 | Ohsawa | Applicant |
| US5097427(A) | 1992-03-01 | Lathrop et al. | Applicant |
| US5136664(A) | 1992-08-01 | Bersack et al. | Applicant |
| US5144291(A) | 1992-09-01 | Nishizawa | Applicant |
| US5163126(A) | 1992-11-01 | Einkauf et al. | Applicant |
| US5170468(A) | 1992-12-01 | Shah et al. | Applicant |
| US5179638(A) | 1993-01-01 | Dawson et al. | Applicant |
| US5204944(A) | 1993-04-01 | Wolberg et al. | Applicant |
| US5224208(A) | 1993-06-01 | Miller, Jr. et al. | Applicant |
| US5239624(A) | 1993-08-01 | Cook et al. | Applicant |
| US5241658(A) | 1993-08-01 | Masterson et al. | Applicant |
| US5255353(A) | 1993-10-01 | Itoh | Applicant |
| US5268995(A) | 1993-12-01 | Diefendorff et al. | Applicant |
| US5268996(A) | 1993-12-01 | Steiner et al. | Applicant |
| US5278948(A) | 1994-01-01 | Luken, Jr. | Applicant |
| US5307450(A) | 1994-04-01 | Grosssman | Applicant |
| US5315692(A) | 1994-05-01 | Hansen et al. | Applicant |
| US5345541(A) | 1994-09-01 | Kelley et al. | Applicant |
| US5353424(A) | 1994-10-01 | Partovi et al. | Applicant |
| US5357579(A) | 1994-10-01 | Buchner et al. | Applicant |
| US5361386(A) | 1994-11-01 | Watkins et al. | Applicant |
| US5363475(A) | 1994-11-01 | Baker et al. | Applicant |
| US5377313(A) | 1994-12-01 | Scheibl | Applicant |
| US5392385(A) | 1995-02-01 | Evangelisti et al. | Applicant |
| US5392393(A) | 1995-02-01 | Deering | Applicant |
| US5394516(A) | 1995-02-01 | Winser | Applicant |
| US5402532(A) | 1995-03-01 | Epstein et al. | Applicant |
| US5404445(A) | 1995-04-01 | Matsumoto | Applicant |
| US5408650(A) | 1995-04-01 | Arsenault | Applicant |
| US5412796(A) | 1995-05-01 | Olive | Applicant |
| US5415549(A) | 1995-05-01 | Logg | Applicant |
| US5416606(A) | 1995-05-01 | Katayama et al. | Applicant |
| US5421028(A) | 1995-05-01 | Swanson | Applicant |
| US5422997(A) | 1995-06-01 | Nagashima | Applicant |
| US5432895(A) | 1995-07-01 | Myers | Applicant |
| US5432900(A) | 1995-07-01 | Rhodes et al. | Applicant |
| US5438663(A) | 1995-08-01 | Matsumoto et al. | Applicant |
| US5448689(A) | 1995-09-01 | Matsuo et al. | Applicant |
| US5457775(A) | 1995-10-01 | Johnson, Jr. et al. | Applicant |
| US5461712(A) | 1995-10-01 | Chelstowski et al. | Applicant |
| US5467438(A) | 1995-11-01 | Nishio et al. | Applicant |
| US5467459(A) | 1995-11-01 | Alexander et al. | Applicant |
| US5469535(A) | 1995-11-01 | Jarvis et al. | Applicant |
| US5473736(A) | 1995-12-01 | Young | Applicant |
| US5475803(A) | 1995-12-01 | Stearns et al. | Applicant |
| US5487146(A) | 1996-01-01 | Guttag et al. | Applicant |
| US5490240(A) | 1996-02-01 | Foran et al. | Applicant |
| US5495563(A) | 1996-02-01 | Winser | Applicant |
| US5504499(A) | 1996-04-01 | Horie et al. | Applicant |
| US5504917(A) | 1996-04-01 | Austin | Applicant |
| US5506604(A) | 1996-04-01 | Nally et al. | Applicant |
| US5535374(A) | 1996-07-01 | Olive | Applicant |
| US5543824(A) | 1996-08-01 | Priem et al. | Applicant |
| US5544292(A) | 1996-08-01 | Winser | Applicant |
| US5548709(A) | 1996-08-01 | Hannah et al. | Applicant |
| US5553228(A) | 1996-09-01 | Erb et al. | Applicant |
| US5557712(A) | 1996-09-01 | Guay | Applicant |
| US5559954(A) | 1996-09-01 | Sakoda et al. | Applicant |
| US5561746(A) | 1996-10-01 | Murata et al. | Applicant |
| US5561752(A) | 1996-10-01 | Jevans | Applicant |
| US5563989(A) | 1996-10-01 | Billyard | Applicant |
| US5566285(A) | 1996-10-01 | Okada | Applicant |
| US5573402(A) | 1996-11-01 | Gray | Applicant |
| US5579456(A) | 1996-11-01 | Cosman | Applicant |
| US5582451(A) | 1996-12-01 | Cox et al. | Applicant |
| US5586234(A) | 1996-12-01 | Sakuraba et al. | Applicant |
| US5593350(A) | 1997-01-01 | Bouton et al. | Applicant |
| US5594854(A) | 1997-01-01 | Baldwin et al. | Applicant |
| US5600763(A) | 1997-02-01 | Greene et al. | Applicant |
| US5606650(A) | 1997-02-01 | Kelley et al. | Applicant |
| US5607157(A) | 1997-03-01 | Nagashima | Applicant |
| US5608424(A) | 1997-03-01 | Takahashi et al. | Applicant |
| US5608864(A) | 1997-03-01 | Bindlish et al. | Applicant |
| US5616031(A) | 1997-04-01 | Logg | Applicant |
| US5621867(A) | 1997-04-01 | Murata et al. | Applicant |
| US5628686(A) | 1997-05-01 | Svancarek et al. | Applicant |
| US5638535(A) | 1997-06-01 | Rosenthal et al. | Applicant |
| US5644364(A) | 1997-07-01 | Kurtze et al. | Applicant |
| US5649082(A) | 1997-07-01 | Burns | Applicant |
| US5650955(A) | 1997-07-01 | Puar et al. | Applicant |
| US5651104(A) | 1997-07-01 | Cosman | Applicant |
| US5657045(A) | 1997-08-01 | Katsura et al. | Applicant |
| US5657443(A) | 1997-08-01 | Krech, Jr. | Applicant |
| US5657478(A) | 1997-08-01 | Recker et al. | Applicant |
| US5659671(A) | 1997-08-01 | Tannenbaum et al. | Applicant |
| US5659673(A) | 1997-08-01 | Nonoshita | Applicant |
| US5659715(A) | 1997-08-01 | Wu et al. | Applicant |
| US5664162(A) | 1997-09-01 | Dye | Applicant |
| US5666439(A) | 1997-09-01 | Ishida et al. | Applicant |
| US5678037(A) | 1997-10-01 | Osugi et al. | Applicant |
| US5682522(A) | 1997-10-01 | Huang et al. | Applicant |
| US5684941(A) | 1997-11-01 | Dye | Applicant |
| US5687304(A) | 1997-11-01 | Kiss | Applicant |
| US5687357(A) | 1997-11-01 | Priem | Applicant |
| US5691746(A) | 1997-11-01 | Shyu | Applicant |
| US5694143(A) | 1997-12-01 | Fielder et al. | Applicant |
| US5696892(A) | 1997-12-01 | Redmann et al. | Applicant |
| US5701444(A) | 1997-12-01 | Baldwin | Applicant |
| US5703806(A) | 1997-12-01 | Puar et al. | Applicant |
| US5706481(A) | 1998-01-01 | Hannah et al. | Applicant |
| US5706482(A) | 1998-01-01 | Matsushima et al. | Applicant |
| US5714981(A) | 1998-02-01 | Scott-Jackson et al. | Applicant |
| US5721947(A) | 1998-02-01 | Priem et al. | Applicant |
| US5724561(A) | 1998-03-01 | Tarolli et al. | Applicant |
| US5726689(A) | 1998-03-01 | Negishi et al. | Applicant |
| US5726947(A) | 1998-03-01 | Yamazaki et al. | Applicant |
| US5727192(A) | 1998-03-01 | Baldwin | Applicant |
| US5734386(A) | 1998-03-01 | Cosman | Applicant |
| US5739819(A) | 1998-04-01 | Bar-Nahum | Applicant |
| US5740343(A) | 1998-04-01 | Tarolli et al. | Applicant |
| US5740383(A) | 1998-04-01 | Nally et al. | Applicant |
| US5740406(A) | 1998-04-01 | Rosenthal et al. | Applicant |
| US5742749(A) | 1998-04-01 | Foran et al. | Applicant |
| US5742788(A) | 1998-04-01 | Priem et al. | Applicant |
| US5745118(A) | 1998-04-01 | Alcorn et al. | Applicant |
| US5745125(A) | 1998-04-01 | Deering et al. | Applicant |
| US5748199(A) | 1998-05-01 | Palm | Applicant |
| US5748986(A) | 1998-05-01 | Butterfield et al. | Applicant |
| US5751291(A) | 1998-05-01 | Olsen et al. | Applicant |
| US5751292(A) | 1998-05-01 | Emmot | Applicant |
| US5751295(A) | 1998-05-01 | Becklund et al. | Applicant |
| US5751930(A) | 1998-05-01 | Katsura et al. | Applicant |
| US5754191(A) | 1998-05-01 | Mills et al. | Applicant |
| US5757382(A) | 1998-05-01 | Lee | Applicant |
| US5758182(A) | 1998-05-01 | Rosenthal et al. | Applicant |
| US5760783(A) | 1998-06-01 | Migdal et al. | Applicant |
| US5764228(A) | 1998-06-01 | Baldwin | Applicant |
| US5764237(A) | 1998-06-01 | Kaneko | Applicant |
| US5764243(A) | 1998-06-01 | Baldwin | Applicant |
| US5767856(A) | 1998-06-01 | Peterson et al. | Applicant |
| US5767858(A) | 1998-06-01 | Kawase 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 |
| US5777623(A) | 1998-07-01 | Small | Applicant |
| US5777629(A) | 1998-07-01 | Baldwin | Applicant |
| US5781927(A) | 1998-07-01 | Wu et al. | Applicant |
| US5791994(A) | 1998-08-01 | Hirano et al. | Applicant |
| US5798770(A) | 1998-08-01 | Baldwin | Applicant |
| US5801706(A) | 1998-09-01 | Fujita et al. | Applicant |
| US5801711(A) | 1998-09-01 | Koss et al. | Applicant |
| US5801716(A) | 1998-09-01 | Silverbrook | Applicant |
| US5801720(A) | 1998-09-01 | Norrod et al. | Applicant |
| US5805175(A) | 1998-09-01 | Priem | Applicant |
| US5805868(A) | 1998-09-01 | Murphy | Applicant |
| US5808619(A) | 1998-09-01 | Choi et al. | Applicant |
| US5808630(A) | 1998-09-01 | Pannell | Applicant |
| US5809219(A) | 1998-09-01 | Pearce et al. | Applicant |
| US5809278(A) | 1998-09-01 | Watanabe et al. | Applicant |
| US5815165(A) | 1998-09-01 | Blixt | Applicant |
| US5815166(A) | 1998-09-01 | Baldwin | Applicant |
| US5818456(A) | 1998-10-01 | Cosman et al. | Applicant |
| US5819017(A) | 1998-10-01 | Akeley et al. | Applicant |
| US5821940(A) | 1998-10-01 | Morgan et al. | Applicant |
| US5821949(A) | 1998-10-01 | Deering | Applicant |
| US5822516(A) | 1998-10-01 | Krech, Jr. | Applicant |
| US5828382(A) | 1998-10-01 | Wilde | Applicant |
| US5828383(A) | 1998-10-01 | May et al. | Applicant |
| US5828907(A) | 1998-10-01 | Wise et al. | Applicant |
| US5831624(A) | 1998-11-01 | Tarolli et al. | Applicant |
| US5831625(A) | 1998-11-01 | Rich et al. | Applicant |
| US5831640(A) | 1998-11-01 | Wang et al. | Applicant |
| US5835096(A) | 1998-11-01 | Baldwin | Applicant |
| US5835792(A) | 1998-11-01 | Wise et al. | Applicant |
| US5838334(A) | 1998-11-01 | Dye | Applicant |
| US5844576(A) | 1998-12-01 | Wilde et al. | Applicant |
| US5850229(A) | 1998-12-01 | Edelsbrunner et al. | Applicant |
| US5856829(A) | 1999-01-01 | Gray, III et al. | Applicant |
| US5859645(A) | 1999-01-01 | Latham | Applicant |
| US5861888(A) | 1999-01-01 | Dempsey | Applicant |
| US5861893(A) | 1999-01-01 | Sturgess | Applicant |
| US5867166(A) | 1999-02-01 | Myhrvold et al. | Applicant |
| US5870097(A) | 1999-02-01 | Snyder et al. | Applicant |
| US5870098(A) | 1999-02-01 | Gardiner | Applicant |
| US5870102(A) | 1999-02-01 | Tarolli et al. | Applicant |
| US5870109(A) | 1999-02-01 | McCormack et al. | Applicant |
| US5870587(A) | 1999-02-01 | Danforth et al. | Applicant |
| US5872902(A) | 1999-02-01 | Kuchkuda et al. | Applicant |
| US5874969(A) | 1999-02-01 | Storm et al. | Applicant |
| US5877741(A) | 1999-03-01 | Chee et al. | Applicant |
| US5877770(A) | 1999-03-01 | Hanaoka | Applicant |
| US5877771(A) | 1999-03-01 | Drebin et al. | Applicant |
| US5880736(A) | 1999-03-01 | Peercy et al. | Applicant |
| US5880737(A) | 1999-03-01 | Griffin et al. | Applicant |
| US5883638(A) | 1999-03-01 | Rouet et al. | Applicant |
| US5886701(A) | 1999-03-01 | Chauvin et al. | Applicant |
| US5886705(A) | 1999-03-01 | Lentz | Applicant |
| US5887155(A) | 1999-03-01 | Laidig | Applicant |
| US5890190(A) | 1999-03-01 | Rutman | Applicant |
| US5892517(A) | 1999-04-01 | Rich | Applicant |
| US5892974(A) | 1999-04-01 | Koizumi et al. | Applicant |
| US5894300(A) | 1999-04-01 | Takizawa | Applicant |
| US5900881(A) | 1999-05-01 | Ikedo | Applicant |
| US5903283(A) | 1999-05-01 | Selwan et al. | Applicant |
| US5909218(A) | 1999-06-01 | Naka et al. | Applicant |
| US5909225(A) | 1999-06-01 | Schinnerer et al. | Applicant |
| US5912675(A) | 1999-06-01 | Laperriere | Applicant |
| US5912676(A) | 1999-06-01 | Malladi et al. | Applicant |
| US5914721(A) | 1999-06-01 | Lim | Applicant |
| US5914725(A) | 1999-06-01 | McInnnis et al. | Applicant |
| US5914729(A) | 1999-06-01 | Lippincott | 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 |
| US5923332(A) | 1999-07-01 | Izawa | Applicant |
| US5923334(A) | 1999-07-01 | Luken | Applicant |
| US5926182(A) | 1999-07-01 | Menon et al. | Applicant |
| US5926647(A) | 1999-07-01 | Adams et al. | Applicant |
| US5933150(A) | 1999-08-01 | Ngo et al. | Applicant |
| US5933154(A) | 1999-08-01 | Howard et al. | Applicant |
| US5933155(A) | 1999-08-01 | Akeley | Applicant |
| US5933529(A) | 1999-08-01 | Kim | Applicant |
| US5936641(A) | 1999-08-01 | Jain et al. | Applicant |
| US5936683(A) | 1999-08-01 | Lin | Applicant |
| US5940086(A) | 1999-08-01 | Rentschler et al. | Applicant |
| US5940089(A) | 1999-08-01 | Dilliplane | Applicant |
| US5940538(A) | 1999-08-01 | Spiegel et al. | Applicant |
| US5943058(A) | 1999-08-01 | Nagy | Applicant |
| US5943060(A) | 1999-08-01 | Cosman et al. | Applicant |
| US5945997(A) | 1999-08-01 | Zhao et al. | Applicant |
| US5949421(A) | 1999-09-01 | Ogletree et al. | Applicant |
| US5949423(A) | 1999-09-01 | Olsen | Applicant |
| US5949424(A) | 1999-09-01 | Cabral et al. | Applicant |
| US5949428(A) | 1999-09-01 | Toelle et al. | Applicant |
| US5949440(A) | 1999-09-01 | Krech, Jr. et al. | Applicant |
| US5956042(A) | 1999-09-01 | Tucker et al. | Applicant |
| US5956043(A) | 1999-09-01 | Jensen | Applicant |
| US5958020(A) | 1999-09-01 | Evoy et al. | Applicant |
| US5959640(A) | 1999-09-01 | Rudin et al. | Applicant |
| US5963220(A) | 1999-10-01 | Lee et al. | Applicant |
| US5966134(A) | 1999-10-01 | Arias | Applicant |
| US5969726(A) | 1999-10-01 | Rentschler et al. | Applicant |
| US5977979(A) | 1999-11-01 | Clough et al. | Applicant |
| US5977984(A) | 1999-11-01 | Omori | Applicant |
| US5982376(A) | 1999-11-01 | Abe et al. | Applicant |
| US5982390(A) | 1999-11-01 | Stoneking et al. | Applicant |
| US5986659(A) | 1999-11-01 | Gallery et al. | Applicant |
| US5986663(A) | 1999-11-01 | Wilde | Applicant |
| US5986677(A) | 1999-11-01 | Jones et al. | Applicant |
| US5987567(A) | 1999-11-01 | Rivard et al. | Applicant |
| US5990903(A) | 1999-11-01 | Donovan | Applicant |
| US5995120(A) | 1999-11-01 | Dye | Applicant |
| US5995121(A) | 1999-11-01 | Alcokrn et al. | Applicant |
| US5999189(A) | 1999-12-01 | Kajiya et al. | Applicant |
| US5999196(A) | 1999-12-01 | Storm et al. | Applicant |
| US5999198(A) | 1999-12-01 | Horan et al. | Applicant |
| US6002407(A) | 1999-12-01 | Fadden | Applicant |
| US6002409(A) | 1999-12-01 | Harkin | Applicant |
| US6002410(A) | 1999-12-01 | Battle | Applicant |
| US6005582(A) | 1999-12-01 | Gabriel et al. | Applicant |
| US6005583(A) | 1999-12-01 | Morrison | Applicant |
| US6005584(A) | 1999-12-01 | Kitamura et al. | Applicant |
| US6007428(A) | 1999-12-01 | Nishiumi et al. | Applicant |
| US6008820(A) | 1999-12-01 | Chauvin et al. | Applicant |
| US6011562(A) | 2000-01-01 | Gagne et al. | Applicant |
| US6011565(A) | 2000-01-01 | Kuo et al. | Applicant |
| US6014144(A) | 2000-01-01 | Nelson et al. | Applicant |
| US6016150(A) | 2000-01-01 | Lengyel et al. | Applicant |
| US6016151(A) | 2000-01-01 | Lin | Applicant |
| US6018350(A) | 2000-01-01 | Lee et al. | Applicant |
| US6020931(A) | 2000-02-01 | Bilbrey et al. | Applicant |
| US6021417(A) | 2000-02-01 | Massarksy | Applicant |
| US6022274(A) | 2000-02-01 | Takeda et al. | Applicant |
| US6023261(A) | 2000-02-01 | Ugajin | Applicant |
| US6023738(A) | 2000-02-01 | Priem et al. | Applicant |
| US6025853(A) | 2000-02-01 | Baldwin | Applicant |
| US6026182(A) | 2000-02-01 | Lee et al. | Applicant |
| US6028608(A) | 2000-02-01 | Jenkins | Applicant |
| US6028611(A) | 2000-02-01 | Anderson et al. | Applicant |
| US6031542(A) | 2000-02-01 | Wittig | Applicant |
| US6035360(A) | 2000-03-01 | Doidge et al. | Applicant |
| US6037948(A) | 2000-03-01 | Liepa | Applicant |
| US6037949(A) | 2000-03-01 | DeRose et al. | Applicant |
| US6038031(A) | 2000-03-01 | Murphy | Applicant |
| US6038348(A) | 2000-03-01 | Carley | Applicant |
| US6040843(A) | 2000-03-01 | Monroe et al. | Applicant |
| US6040844(A) | 2000-03-01 | Yamaguchi et al. | Applicant |
| US6041010(A) | 2000-03-01 | Puar et al. | Applicant |
| US6043804(A) | 2000-03-01 | Greene | Applicant |
| US6043821(A) | 2000-03-01 | Sprague et al. | Applicant |
| US6046746(A) | 2000-04-01 | Deering | Applicant |
| US6046747(A) | 2000-04-01 | Saunders et al. | Applicant |
| US6046752(A) | 2000-04-01 | Kirkland et al. | Applicant |
| US6049337(A) | 2000-04-01 | Van Overveld | Applicant |
| US6049338(A) | 2000-04-01 | Anderson et al. | Applicant |
| US6052125(A) | 2000-04-01 | Gardiner et al. | Applicant |
| US6052126(A) | 2000-04-01 | Sakuraba et al. | Applicant |
| US6052127(A) | 2000-04-01 | Vaswani et al. | Applicant |
| US6052129(A) | 2000-04-01 | Fowler et al. | Applicant |
| US6052133(A) | 2000-04-01 | Kang | Applicant |
| US6054993(A) | 2000-04-01 | Devic et al. | Applicant |
| US6054999(A) | 2000-04-01 | Strandberg | Applicant |
| US6057847(A) | 2000-05-01 | Jenkins | Applicant |
| US6057849(A) | 2000-05-01 | Haubner et al. | Applicant |
| US6057851(A) | 2000-05-01 | Luken et al. | Applicant |
| US6057852(A) | 2000-05-01 | Krech, Jr. | Applicant |
| US6057859(A) | 2000-05-01 | Handelman et al. | Applicant |
| US6057861(A) | 2000-05-01 | Lee et al. | Applicant |
| US6057862(A) | 2000-05-01 | Margulis | Applicant |
| US6057863(A) | 2000-05-01 | Olarig | Applicant |
| US6061462(A) | 2000-05-01 | Tostevin et al. | Applicant |
| US6064392(A) | 2000-05-01 | Rohner | Applicant |
| US6067098(A) | 2000-05-01 | Dye | Applicant |
| US6070204(A) | 2000-05-01 | Poisner | Applicant |
| US6072496(A) | 2000-06-01 | Guenter et al. | Applicant |
| US6075543(A) | 2000-06-01 | Akeley | Applicant |
| US6075546(A) | 2000-06-01 | Hussain et al. | Applicant |
| US6078311(A) | 2000-06-01 | Pelkey | Applicant |
| US6078333(A) | 2000-06-01 | Wittig et al. | Applicant |
| US6078334(A) | 2000-06-01 | Hanaoka et al. | Applicant |
| US6078338(A) | 2000-06-01 | Horan et al. | Applicant |
| US6081274(A) | 2000-06-01 | Shiraishi | Applicant |
| US6088035(A) | 2000-07-01 | Sudarsky et al. | Applicant |
| US6088042(A) | 2000-07-01 | Handelman et al. | Applicant |
| US6088487(A) | 2000-07-01 | Kurashige | Applicant |
| US6088701(A) | 2000-07-01 | Whaley et al. | Applicant |
| US6091431(A) | 2000-07-01 | Saxena et al. | Applicant |
| US6092124(A) | 2000-07-01 | Priem et al. | Applicant |
| US6092158(A) | 2000-07-01 | Harriman et al. | Applicant |
| US6094200(A) | 2000-07-01 | Olsen et al. | Applicant |
| US6097435(A) | 2000-08-01 | Stanger et al. | Applicant |
| US6097437(A) | 2000-08-01 | Hwang | Applicant |
| US6104415(A) | 2000-08-01 | Gossett | Applicant |
| US6104417(A) | 2000-08-01 | Nielsen et al. | Applicant |
| US6105094(A) | 2000-08-01 | Lindeman | Applicant |
| US6108743(A) | 2000-08-01 | Debs et al. | Applicant |
| US6111582(A) | 2000-08-01 | Jenkins | Applicant |
| US6111584(A) | 2000-08-01 | Murphy | Applicant |
| US6115047(A) | 2000-09-01 | Deering | Applicant |
| US6115049(A) | 2000-09-01 | Winner et al. | Applicant |
| US6118462(A) | 2000-09-01 | Margulis | Applicant |
| US6128026(A) | 2000-10-01 | Brothers, III | Applicant |
| US6144365(A) | 2000-11-01 | Young et al. | Applicant |
| US6144387(A) | 2000-11-01 | Liu et al. | Applicant |
| US6151602(A) | 2000-11-01 | Hejlsberg et al. | Applicant |
| US6155926(A) | 2000-12-01 | Miyamoto et al. | Applicant |
| US6157387(A) | 2000-12-01 | Kotani | Applicant |
| US6166748(A) | 2000-12-01 | Van Hook et al. | Applicant |
| US6172678(B1) | 2001-01-01 | Shiraishi | 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 |
| US6191794(B1) | 2001-02-01 | Priem et al. | Applicant |
| US6198488(B1) | 2001-03-01 | Lindholm et al. | Applicant |
| US6200253(B1) | 2001-03-01 | Nishiumi et al. | Applicant |
| US6204851(B1) | 2001-03-01 | Netschke et al. | Applicant |
| US6215496(B1) | 2001-04-01 | Szeliski et al. | Applicant |
| US6215497(B1) | 2001-04-01 | Leung | Applicant |
| US6226012(B1) | 2001-05-01 | Priem et al. | Applicant |
| US6226713(B1) | 2001-05-01 | Mehrotra | Applicant |
| US6229553(B1) | 2001-05-01 | Duluk et al. | Examiner |
| US6232981(B1) | 2001-05-01 | Gossett | Applicant |
| US6236413(B1) | 2001-05-01 | Gossett et al. | Applicant |
| US6239810(B1) | 2001-05-01 | Van Hook et al. | Applicant |
| US6252608(B1) | 2001-06-01 | Snyder et al. | Applicant |
| US6252610(B1) | 2001-06-01 | Hussain | Applicant |
| US6259460(B1) | 2001-07-01 | Gossett et al. | Applicant |
| US6264558(B1) | 2001-07-01 | Nishiumi et al. | Applicant |
| US6268861(B1) | 2001-07-01 | Sanz-Pastor et al. | Applicant |
| US6275235(B1) | 2001-08-01 | Morgan, III | Applicant |
| US6285779(B1) | 2001-09-01 | Lapidous et al. | Applicant |
| US6292194(B1) | 2001-09-01 | Powll, III | Applicant |
| US6329997(B1) | 2001-12-01 | Wu et al. | Applicant |
| US6331856(B1) | 2001-12-01 | Van Hook et al. | Applicant |
| US6337689(B1) | 2002-01-01 | Hochmuth et al. | Examiner |
| US6339428(B1) | 2002-01-01 | Fowler et al. | Applicant |
| US6342892(B1) | 2002-01-01 | Van Hook et al. | Applicant |
| US6353438(B1) | 2002-03-01 | Van Hook | Applicant |
| US6356497(B1) | 2002-03-01 | Puar et al. | Applicant |
| US6408362(B1) | 2002-06-01 | Arimilli et al. | Applicant |
| US6417858(B1) | 2002-07-01 | Bosch et al. | Applicant |
| US6426747(B1) | 2002-07-01 | Hoppe et al. | Applicant |
| US6437781(B1) | 2002-08-01 | Tucker et al. | Applicant |
| US6459429(B1) | 2002-10-01 | Deering | Applicant |
| US6466223(B1) | 2002-10-01 | Dorbie et al. | Examiner |
| US6469707(B1) | 2002-10-01 | Voorhies | Applicant |
| US6476808(B1) | 2002-11-01 | Kuo et al. | Applicant |
| US6476822(B1) | 2002-11-01 | Burbank | Applicant |
| US6496187(B1) | 2002-12-01 | Deering et al. | Applicant |
| US6501479(B1) | 2002-12-01 | Root et al. | Applicant |
| US6593923(B1) | 2003-07-01 | Donovan et al. | Examiner |
| US6597363(B1) | 2003-07-01 | Duluk et al. | Examiner |
| CA2070934 | 1993-12-01 | Applicant | |
| EP637813(A2) | 1995-02-01 | Applicant | |
| EP1074945 | 2001-02-01 | Applicant | |
| EP1075146 | 2001-02-01 | Applicant | |
| EP1081649 | 2001-03-01 | Applicant | |
| EP1189172(A9) | 2002-03-01 | Applicant | |
| JP9-330230 | 1997-12-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 | |
| WO/93/04429 | 1993-03-01 | Applicant | |
| WO94/10641 | 1994-05-01 | Applicant |
Non-Patent Literature (187)
- Photograph of Sony PlayStation II System.Applicant
- Photograph of Sega Dreamcast System.Applicant
- Photograph of Nintendo 64 SystemApplicant
- 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.comApplicant
- 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 DirectX6”, Game Developer, Sep. 1998, www.gdmag.com.Applicant
- VisionTek, “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 or 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.netApplicant
- 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, Feb. 1999, 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 Programmers'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
- “Computer 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
- GDC 2000: Advanced OpenGL Game Development, “A Practical and Robust Bump-mapping Technique for Today's GPUs,” by Mark Kilgard, Jul. 5, 2000, www.nvidia.com.Applicant
- Technical Presentations: “Texture Space Bump Mapping,” Sim Dietrich, Nov. 10, 2000, www.nvidia.com.Applicant
- White paper, Huddy, Richard, “The Efficient Use of Vertex Buffers,” (Nov. 1, 2000).Applicant
- White paper, Spitzer, John, et al., “Using GL—NV—array—range and GL—NV—Fence on GEForce Products and Beyond” (Aug. 1, 2000).Applicant
- White paper, Rogers, Douglas H., “Optimizing Direct3D for the GeForce 256” (Jan. 3, 2000).Applicant
- Hook, Brian, “An Incomplete Guide to Programming DirectDraw and Direct3D Immediate Mode (Release 0.46),” printed from web site: www.wksoftware.com, 42 pages.Applicant
- Thompson, Tom, “Must-See 3-D Engines,” BYTE Magazine, printed from web site www.byte.com, 10 pages (Jun. 1996).Applicant
- Thompson, Nigel, “Rendering with Immediate Mode,” Microsoft Interactive Developer Column: Fun and Games, printed from web site msdn.microsoft.com, 8 pages (Mar. 1997).Applicant
- “HOWTO: Animate Textures in Direct3D Immediate Mode,” printed from web site support.microsoft.com, 3 pages (last reviewed Dec. 15, 2000).Applicant
- “INFO: Rendering a Triangle Using an Execute Buffer,” printed from web site support.microsoft.com, 6 pages (last reviewed Oct. 20, 2000).Applicant
- U.S. Appl. No. 09/337,293, filed Jun. 21, 1999, Multi-Format Vertex Data Processing Apparatus and Method [issued as U.S. Appl. No. 6,501,479,B1 on Dec. 31, 2002].Applicant
- Datasheet, SGS-Thomson Microelectronics, nVIDIA™, RIVA 128™ 128-Bit 3D Multimedia Accelerator (Oct. 1997).Applicant
- Product Presentation, “RIVA 128™ Leadership 3 D Acceleration,” 2 pages.Applicant
- ZDNet Reviews, from PC Magazine, “Other Enhancements,” Jan. 15, 1999, wysiwyg://16//http://www4.zdnet.com . . . ies/reviews/0,4161,2188266,00.htmlApplicant
- ZDNet Reviews, from PC Magazine, “Screen Shot of Alpha-channel Transparency,” Jan 15, 1999, wysiwyg://16/http://www4.zdnet.com . . . ies/reviews/0,4161,2188286,00.html.Applicant
- Alpha (transparency) Effects, Future Technology Research Index, http://www.futuretech.vuurwerk.n1/alpha.html.Applicant
- Blythe, David, 5.6 Transparency Mapping and Trimming with Alpha, http://toolbox.sgi.com/TasteOfDT/d . . . penGL/advanced98/notes/node41.html, Jun. 11, 1998.Applicant
- 10.2 Alpha Blending, http://www.sgi.com/software/opengl/advanced98/notes/node146.html.Applicant
- 10.3 Sorting, http://www.sgi.com/software/opengl/advanced98/notes/node147.html.Applicant
- 10.4 Using the Alpha Function, http://www.sgi.com/software/opengl/advanced98/notes/node148.html.Applicant
- Winner, Stephanie, et al., “Hardware Accelerated Rendering Of Antialiasing Using A Modified A-buffer Algorithm,” Computer Graphics Proceedings, Annual Conference Series, 1997, pp 307-316.Applicant
- Debevec, Paul, et al., “Efficient View-Dependent Image-Based Rendering with Projective Texture-Mapping,” University of California at Berkeley.Applicant
- Gibson, Simon, et al., “Interactive Rendering with Real-World Illumination,” Rendering Techniques 2000; 11th Eurographics Workshop on Rendering, pp. 365-376 (Jun. 2000).Applicant
- Segal, Mark, et al., “Fast Shadows and Lighting Effects Using Texture Mapping,” Computer Graphics, 26, 2, pp.. 249-252 (Jul. 1992).Applicant
- White paper, Kilgard, Mark J., “Improving Shadows and Reflections via the Stencil Buffer” (Nov. 3, 1999).Applicant
- “OpenGL Projected Textures,” from web site:HTTP://reality.sgi.com, 5 pages.Applicant
- “5.13.1 How to Project a Texture,” from web site: www.sgi.com, 2 pages.Applicant
- Arkin, Alan, email, subject: “Texture distortion problem,” from web site:HTTP://reality.sgi.com (Jul. 1997).Applicant
- Moller, Tomas et al., “Real-Time Rendering,” pp. 179-183 (AK Peters Ltd., 1999).Applicant
- Williams, Lance, “Casting Curved Shadows on Curved Surfaces,” Computer Graphics (SIGGRAPH '78 Proceedings), vol. 12, No. 3, pp. 270-274 (Aug. 1978).Applicant
- Woo et al., “A Survey of Shadow Algorithms,” IEEE Computer Graphics and Applications, vol. 10, No. 6, pp. 13-32 (Nov. 1990).Applicant
- Heidrich et al., “Applications of Pixel Textures in Visualization and Realistic Image Synthesis,” Proceedings 1999 Symposium On Interactive 3D Graphics, pp. 127-134 (Apr. 1999).Applicant
- Hourcade et al., “Algorithms for Antialiased Cast Shadows”, Computers and Graphics, vol. 9, No. 3, pp. 260-265 (1985).Applicant
- Michael McCool, “Shadow Volume Reconstruction from Depth Maps”, ACM Transactions on Graphics, vol. 19, No. 1, Jan. 2000, pp. 1-26.Applicant
- RenderMan Artist Tools, PhotoRealistic RenderMan 3.8 User's Manual, Pixar (Aug. 1998).Applicant
- RenderMan Interface Version 3.2 (Jul. 2000).Applicant
- White paper, Dietrich, Sim, “Cartoon Rendering and Advanced Texture Features of the GeForce 256 Texture Matrix, Projective Textures, Cube Maps, Texture Coordinate Generation and DOTPRODUCT3 Texture Blending” (Dec. 16, 1999).Applicant
- Peter J. Kovach, Inside Direct 3D, “Alpha Testing,” ppp 289-291 (1999).Applicant
- Web site information, CartoonReyes, REM Infografica, http://www.digimotion.co.uk/cartoonreyes.htm.Applicant
- Raskar, Ramesh et al., “Image Precision Silhouette Edges,” Symposium on Interactive 3D Graphics 1999, Atlanta, 7 pages (Apr. 26-29, 1999).Applicant
- Schlechtweg, Stefan et al., Rendering Line-Drawings with Limited Resources, Proceedings of GRAPHICON '96, 6th International Conference and Exhibition on Computer Graphics and Visualization in Russia, (St. Petersburg, Jul. 1-5, 1996) vol. 2, pp 131-137.Applicant
- Haeberli, Paul et al., “Texture Mapping as a Fundamental Drawing Primitive,” Proceedings of the Fourth Eurographics Workshop on Rendering, 11pages, Paris, France (Jun. 1993).Applicant
- Schlechtweg, Stefan et al., “Emphasising in Line-drawings,” Norsk samarbeid innen grafisk databehandling: NORSIGD Info, medlemsblad for NORSIGD, Nr Jan. 1995, pp. 9-10.Applicant
- Markosian, Lee et al., “Real-Time Nonphotorealistic Rendering,” Brown University site of the NSF Science and Technology Center for Computer Graphics and Scientific Visualization, Providence, RI, 5 pages (undated).Applicant
- Feth, Bill, “Non-Photorealistic Rendering,” [email protected], CS490—Bruce Land, 5 pages (Spring 1998).Applicant
- Elber, Gershon, “Line Art Illustrations of Parametric and Implicit Forms,” IEEE Transactions on Visualization and Computer Graphics, vol. 4, No. 1, Jan.-Mar. 1998.Applicant
- Zeleznik, Robert et al.“SKETCH: An Interface for Sketching 3D Scenes,” Computers Graphics Proceedings, Annual Conference Series 1996, pp. 163-170.Applicant
- Computer Graphics World, Dec. 1997.Applicant
- Reynolds, Craig, “Stylized Depiction in Computer Graphics, Non-Photorealistic, Painterly and 'Toon Rendering,” an annotated survey of online resources, 13 pages, last update May 30, 2000, http://www.red.com/cwr/painterly.html.Applicant
- Render Man Artist Tools, Using Arbitrary Output Variables in Photorealistic Renderman (With Applications), PhotoRealistic Renderman Application Note #24, 8 pages, Jun. 1998, http://www.pixar.com/products/renderman/toolkit/Toolkit /AppNotes/appnote.24.html.Applicant
- Decaudin, Philippe, “Cartoon-Looking Rendering of 3D Scenes,” Syntim Project Inria, 6 pages, http://www-syntim.inria.fr/syntim/recherche/decaudin/cartoon-eng.html.Applicant
- Hachigian, Jennifer, “Super Cel Shader 1.00 Tips and Tricks,” 2 pages, wysiwyg://thePage.13/http://members.xoom.com/—XMCM.jarvia/3D/celshade.html.Applicant
- Digimation Inc., “The Incredible Comicshop,” info sheet, 2 pages, http://www.digimation.com/asp/product/asp?product—id=33.Applicant
- Softimage/3D Full Support, “Toon Assistant,” 1998 Avid Technology, Inc., 1 page, http://www.softimage.com/3dsupport/techn . . . uments/3.8/features3.8/rel—notes.56.html.Applicant
- Cambridge Animo—Scene III, info sheet, Cambridge Animation Systems, 2 pages, http://www.camani.co.uk/casweb/products/software/Scenelll.htm.Applicant
- Mulligan, Vikram, “Toon, ” info sheet, 2 pages, http://digitalcarversguild.com/products/toon/toon.thml.Applicant
- Toony Shaders, “Dang I'm tired of photorealism,” 4 pages, http://www.visi.com/˜mcdonald/toony.html.Applicant
- “Cartoon Shading, Using Shading Mapping,” 1 page, http://www.goat.com/alias/shaders.html#toonshad.Applicant
- Web site information, CartoonReyes, http://www.zentertainment.com/zentropy/review/cartoonreyes.html.Applicant
- VIDI Presenter 3D Repository, “Shaders.” 2 pages, http://www.webnation.com/vidirep/panels/renderman/shaders/toon.phtml.Applicant
- The RenderMan Interface Version 3.1, (Sep. 1989).Applicant
- “Renderman Artist Tools, PhotoRealistic RenderMan Tutorial,” Pixar (Jan. 1996).Applicant
- Web site materials, “Renderman Artist Tools, PhotoRealistic RenderMan 3.8 User's Manual,” Pixar.Applicant
- NVIDIA.com, technical presentation, “AGDC Per-Pixel Shading” (Nov. 15, 2000).Applicant
- NVIDIA.com, technical presentation, Introduction to DX8 Pixel Shaders (Nov. 10, 2000).Applicant
- NVIDIA.com, technical presentation, “Advanced Pixel Shader Details” (Nov. 10, 2000).Applicant
- “Developer's Lair, Multitexturing with the ATI Rage Pro,” (7 pages) from ati.com web site (2000).Applicant
- Slide Presentation, Sébastien Dominé, “nVIDIA Mesh Skinning, OpenGl”.Applicant
- Singh, Karan et al., “Skinning Characters using Surface-Oriented Free-Form Deformations,” Toronto Canada.Applicant
- “Hardware Technology,” from ATI.com web site, 8 pages (2000).Applicant
- “Skeletal Animation and Skinning,” from ATI.com web site, 2 pages (Summer 2000).Applicant
- “Developer Relations, ATI Summer 2000 Developer Newsletter,” from ATI.com web site, 5 pages (Summer 2000).Applicant
- Press Releases, “ATI's RADEON family of products delivers the most comprehensive support for the advance graphics features of DirectX 8.0,” Canada, from ATI.com web site, 2 pages (Nov. 9, 2000).Applicant
- “ATI RADEON Skinning and Tweening,” from ATI.com web site, 1 page (2000).Applicant
- Hart, Evan et al., “Vertex Shading with Direct3D and OpenGL,” Game Developers Conference 2001, from ATI.com web site (2001).Applicant
- Search Results for: skinning, from ATI.com web site, 5 pages (May 24, 2001).Applicant
- Hart, Evan et al., “Graphics by rage,” Game Developers Conference 2000, from ATI.com web site (2000).Applicant
- Efficient Command/Data Interface Protocol For Graphics, IBM TDB, vol. 36, issue 9A, Sep. 1, 1993, pp. 307-312.Applicant
- Shade, Jonathan et al., “Layered Depth Images,” Computer Graphics Proceedings, Annnual Conference Series, pp. 231-242 (1998).Applicant
- Videum Conference Pro (PCI) Specification, product of Winnov (Winnov), published Jul. 21, 1999.Applicant
- Hoppe, Hugues, “Optimization of Mesh Locality for Transparent Vertex Caching,” Proceedings of SIGGRAPH, pp. 269-276 (Aug. 8-13, 1999).Applicant
- Whitepaper: Implementing Fog in Direct3D, Jan. 3, 2000, www.nvidia.com.Applicant
- Akeley, Kurt, “Reality Engine Graphics”, 1993, Silicon Graphics Computer Systems, pp. 109-116.Applicant
- Peter J. Kovach, Inside Direct3D pp. 249-262, Microsoft Press 2000.Applicant
- McCool, M.D. et al., “Texture Shaders,” Proceedings 1999 Eurographics/SIGGRAPH Workshop on Graphics Hardware, Los Angeles, CA, Aug. 8-9, 1999, SIGGRAPH/Eurographics Workshop on Graphics Hardware, New York, NY: ACM, US, pp. 122-125, Figure 4 (Aug. 8, 1999).Applicant
- Heidrich W. et al., “Illuminating micro geometry based on precomputed visibility,” Computer Graphics Proceedings, SIGGRAPH 2000, Conference Proceedings, New Orleans, LA, USA, Jul. 27-28, 2000, pp. 455-464, New York, NY, USA, ACM.Applicant
- Heidrich et al., “Illuminating Micro Geometry Based on Precomputed Visibility,” Computer Graphics Proceedings, Annual Conference Series, 2000, pp. 455-464.Applicant
- McCool et al., “Texture Shaders,” Proceedings 1999 Eurographics Workshop, Los Angeles, CA, Aug. 8-9, 1999, pp. 117-126; 144.Applicant