Method and apparatus for providing logical combination of N alpha operations within a graphics system

Information

  • Patent Grant
  • 7061502
  • Patent Number
    7,061,502
  • Date Filed
    Tuesday, November 28, 2000
    23 years ago
  • Date Issued
    Tuesday, June 13, 2006
    18 years ago
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. Logical combination of N alpha compares can be used to provide a wide range of imaging effects including but not limited to cartoon outlining.
Description
FIELD OF THE INVENTION

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 the use of logical combination of N alpha channel operations to generate interesting visual graphics effects including but not limited to non-photorealistic images such as cartoon outlining.


BACKGROUND AND SUMMARY OF THE INVENTION

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.


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.


Most computer graphics research has tended to focus on producing realistic images. This research has been very successful. Computers can now generate images that are so realistic that you can't tell them apart from photographs. For example, many of us have seen very convincing dinosaurs, aliens and other photorealistic computer-generated special effects in movie and television. New pilots train on computer-based flight simulators so realistic that they nearly duplicate actual flying. Low-cost home video game systems can now provide a remarkable degree of realism, giving the game player an illusion of driving a real race car along a track, skiing down a snow and ice covered ski slope, walking through a medieval castle, or the like. For most games, this illusion of realism significantly enhances the game play experience.


One way to enhance realism is to model the opacity (transparency) of surfaces using a technique called “alpha blending.” Using this conventional technique, each image element is assigned an “alpha value” representing its degree of opacity. The colors of the image element are blended based on the alpha value—allowing one object to appear to be visible through another object. A further conventional technique called “alpha function” or “alpha test” can be used to discard an object fragment based on comparing the fragment's alpha value with a reference function or value. Alpha test may decide to not blend (i.e., to throw away) a potential part of an image because it is transparent and will therefore be invisible.


Alpha blending and alpha test are especially useful for modeling transparent objects such as water and glass. This same functionality can also be used with texture mapping to achieve a variety of effects. For example, the alpha test is frequently used to draw complicated geometry using texture maps on polygons—with the alpha component acting as a matte. By way of illustration, a tree can be drawn as a picture (texture) of a tree on a polygon. The tree parts of the texture image can have an alpha value of 1 (opaque), and the non-tree parts can have an alpha value of 0 (transparent). In this way, the “non-tree” parts of the polygons are mapped to invisible (transparent) portions of the texture map, while the “tree” portions of the polygon are mapped to visible (opaque) portions of the texture map.


The alpha component of a texture can be used in other ways—for example, to cut holes or trim surfaces. As one example, an image of a cutout or a trim region can be stored in a texture map. When mapping the texture to the polygon surface, alpha testing or blending can be used to cut the cutout or trimmed region out of the polygon's surface. Additionally, the alpha channel of a computer graphics system can be also be used to provide non-photorealistic image effects such as cartoon outlining. An arrangement described in U.S. patent application Ser. No. 09/468,109 filed Dec. 21, 1999 uses the alpha channel of a real time rendering system to encode identifications corresponding to different objects or portions of objects. The system renders the objects into a color frame buffer, and writes corresponding object Ids into an alpha frame buffer. An alpha test operation is performed on the alpha frame buffer, and the alpha compare results (i.e., the absolute value of the difference between two alpha values) are used to selectively blend outline coloration around silhouette and other edges defined between image areas encoded with different alpha/Ids.


Typical generally available 3D graphics application programmer interfaces such as DirectX and OpenGL support alpha compares for transparency or other purposes, e.g., to compare an iterated or texture alpha to a constant and “kill” the pixel in the compare fails. As one example, Direct3D provides a command “D3DRENDERSTATE_ALPHATEST-ENABLE that can be used to enable alpha testing. The command D3DCOMFUNC enumerated type allows the programmer to specify the possible tests used in the alpha compare operation (e.g., never, always, <, >, less than or equal to, greater than or equal to, not equal to, etc.) For example, if the alpha comparison function is set to “greater than or equal to”, then if the pixel being rasterized is less opaque than the color already at the pixel, Direct3D will skip it completely—saving the time that would have been required to blend the two colors together and preventing the color and z buffers from being updated. It is also possible to compare the incoming alpha with a programmer-specified reference alpha value (e.g., “if (alpha<128/255) then kill the pixel) by using the D3DRENDERSTATE_ALPHAREF command. See, e.g., Kovach, Inside Direct3D (Microsoft 2000) at 289–291. Similar alpha testing/comparison capabilities are provided in OpenGL by the GL_ALPHA_TEST, GL_ALPHA_TEST_FUNC and GL_ALPHA_TEST_REF commands. See, e.g., Neider et al, OpenGL Programming Guide (Addison-Wesley 1993) at 301–302.


An issue that arises when implementing various complex alpha comparisons including but not limited to the cartoon outlining algorithm mentioned above, is how to efficiently perform more complicated alpha comparisons in hardware using a single rendering pass. For example, while arbitrarily complex alpha tests can typically be straightforwardly be performed by a processor executing software, it may be desirable (e.g., for increased speed performance) to use a hardware-based alpha test. Such an arbitrarily complex alpha test capability has not generally been available in the past within the context of a low cost graphics system such as a home video game or a personal computer graphics card.


The present invention solves this problem by providing a hardware-based pixel shader capable of performing plural alpha comparisons that can be logically combined to achieve a wide range of alpha test functionality. In accordance with one aspect of the invention, the pixel shader can be used to provide a transparency tree analogous to a shade tree. In particular, alpha functionality can be used to provide N logical alpha operations on M alpha inputs, where N and M can be any integers.


One aspect of the invention provides a method of generating a graphics image comprising generating information representing a surface to be imaged, said information including alpha; performing, within the same rendering pass, plural alpha comparisons on said alpha information to provide corresponding plural alpha comparison results; logically combining said plural alpha comparison results; and rendering said graphics image based at least in part on said logical combination. The rendering step may include selecting whether or not to kill a pixel based on said logical combination. The performing step can be performed in hardware and/or using a recirculating shader.


In accordance with a further aspect provided by the invention, a graphics system comprises a texture unit including a texture coordinate matrix multiplier; a shader including an alpha channel; an embedded frame buffer that can store an alpha image; and a copy-out pipeline for copying an alpha image from said frame buffer for use as a texture by said texture unit, wherein said graphics system performs plural alpha comparisons in a single rendering pass.


The combination of alpha compares and alpha logical operations can be used for a wide range of additional alpha-based effects. For example, dual alpha comparisons can be used to provide non-photorealistic effects such as cartoon outlining (e.g., to efficiently determine whether to blend a cartoon outline color based on said logical combination by implementing an absolute value function).





BRIEF DESCRIPTION OF THE DRAWINGS

These and other features and advantages provided by the invention will be better and more completely understood by referring to the following detailed description of presently preferred embodiments in conjunction with the drawings, of which:



FIG. 1 is an overall view of an example interactive computer graphics system;



FIG. 2 is a block diagram of the FIG. 1 example computer graphics system;



FIG. 3 is a block diagram of the example graphics and audio processor shown in FIG. 2;



FIG. 4 is a block diagram of the example 3D graphics processor shown in FIG. 3;



FIG. 5 is an example logical flow diagram of the FIG. 4 graphics and audio processor;



FIG. 6 shows an example reusable recirculating shader;



FIG. 7 shows an example shading pipeline implemented using the recirculating shader;



FIG. 8 shows an example recirculating shader block diagram;



FIG. 9 shows an example recirculating shader input multiplexer;



FIG. 10 shows an example recirculating shader operation block diagram;



FIG. 11 shows an example recirculating shader implementation;



FIGS. 12A and 12B illustrate an example color swap feature;



FIGS. 13–18C show an example cartoon outlining technique using alpha information to encode object ID;



FIG. 19 shows an example cartoon outlining process performed by system 50;



FIG. 20 shows an example cartoon outlining pipeline implemented by system 50; and



FIGS. 21A and 21B show example alternative compatible implementations.





DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS OF THE INVENTION


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.


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.


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.


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.


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.


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



FIG. 2 shows a block diagram of example components of system 50. The primary components include:

    • a main processor (CPU) 110,
    • a main memory 1112, and
    • a graphics and audio processor 114.


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.


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.


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.


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:

    • a programmable read-only memory and/or real time clock 134,
    • 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
    • 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



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:

    • a processor interface 150,
    • a memory interface/controller 152,
    • a 3D graphics processor 154,
    • an audio digital signal processor (DSP) 156,
    • an audio memory interface 158,
    • an audio interface and mixer 160,
    • a peripheral controller 162, and
    • a display controller 164.


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.


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



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 uncached data streams targeted for the graphics and audio processor 114. The write-gathering buffer 111 collects partial cache lines into full cache lines and sends the data out to the graphics and audio processor 114 one cache line at a time for maximum bus usage.


Command processor 200 receives display commands from main processor 110 and parses them—obtaining any additional data necessary to process them from shared memory 112. The command processor 200 provides a stream of vertex commands to graphics pipeline 180 for 2D and/or 3D processing and rendering. Graphics pipeline 180 generates images based on these commands. The resulting image information may be transferred to main memory 112 for access by display controller/video interface unit 164—which displays the frame buffer output of pipeline 180 on display 56.



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:

    • 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,
    • display lists 212 from main memory 112 via an on-chip call FIFO memory buffer 218, and
    • vertex attributes from the command stream and/or from vertex arrays 214 in main memory 112 via a vertex cache 220.


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.



FIG. 4 shows that graphics pipeline 180 may include:

    • a transform unit 1300,
    • a setup/rasterizer 400,
    • a texture unit 500,
    • a texture environment unit 600, and
    • a pixel engine 700.


Transform unit 1300 performs a variety of 2D and 3D transform and other operations 300a (see FIG. 5). Transform unit 1300 may include on or more matrix memories 300b for storing matrices used in transformation processing 300a. Transform unit 1300 transforms incoming geometry per vertex from object space to screen space; and transforms incoming texture coordinates and computes projective texture coordinates (300c). Transform unit 1300 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 1300 can also perform texture coordinate generation (300c) for embossed type bump mapping effects, as well as polygon clipping/culling operations (300d).


Setup/rasterizer 400 includes a setup unit which receives vertex data from transform unit 1300 and sends triangle setup information to one or more rasterizer units (400b) performing edge rasterization, texture coordinate rasterization and color rasterization.


Texture unit 500 (which may include an on-chip texture memory (TMEM) 502) performs various tasks related to texturing including for example:

    • retrieving textures 504 from main memory 112,
    • 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,
    • bump map processing for computing texture coordinate displacements for bump mapping, pseudo texture and texture tiling effects (500b), and
    • indirect texture processing (500c).


Texture unit 500 outputs filtered texture values to the texture environment unit 600 for texture environment processing (600a). Texture unit 500 is recirculating, and is able to perform both direct and indirect texturing and providing a sequence of texture mapping outputs to texture environment unit 600 for blending during a single rendering pass. See U.S. patent application Ser. No. 09/722,382 entitled “Method And Apparatus For Indirect Texture Referencing In A Graphics System”, and its corresponding provisional application Ser. No. 60/226,891, filed Aug. 23, 2000, both of which are incorporated herein by this reference.


Texture environment unit 600 blends polygon and texture color/alpha/depth, and can also perform texture fog processing (600b) to achieve inverse range based fog effects. Texture environment unit 600 can provide multiple stages to perform a variety of other interesting environment-related functions based for example on color/alpha modulation, embossing, detail texturing, texture swapping, clamping, and depth blending. For example, the texture environment unit 600 of system 50 includes a recirculating shader providing a separately controllable alpha channel that processes alpha information independently of color information without slowing down the graphics pipeline. The recirculating shader design of texture environment unit 600 makes it possible to implement alpha transparency “shade trees” providing arbitrarily complex alpha blending and comparison functions. See commonly assigned U.S. patent 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 this reference.


Pixel engine 700 performs depth (z) compare (700a) and pixel blending (700b). In this example, pixel engine 700 stores data into an embedded (on-chip) frame buffer memory 702. Graphics pipeline 180 may include one or more embedded DRAM memories 702 to store frame buffer and/or texture information locally. Z compares 700a′ can also be performed at an earlier stage in the graphics pipeline 180 depending on the rendering mode currently in effect (e.g., z compares can be performed earlier if alpha blending is not required). The pixel engine 700 includes a copy operation 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. A copy-out pipeline that may be part of pixel engine 700 permits, within a single rendering pass, some or all of embedded frame buffer 702 to be copied out into main memory 112 as a texture. Texture unit 500 may then read the copied-out texture into texture memory 502 for use in texture mapping additional visualization into the frame buffer contents. It is possible for system 50 to copy out, for example, alpha information rendered into embedded frame buffer 702 and apply this alpha information as a texture for texture mapping to add to the contents of the embedded frame buffer—all within the same rendering pass. See U.S. patent application Ser. No. 09/722,663 entitled “Graphics System With Copy-Out Conversions Between Embedded Frame Buffer And Main Memory”, and its corresponding provisional application Ser. No. 60/227,030, filed Aug. 23, 2000, both of which are incorporated herein by this reference.


Logical Combination of N Alpha Comparisons


As described in copending application Ser. No. 09/722,367 of Drebin et al entitled “Recirculating Shade Tree Blender For a Graphics System” (the entire disclosure of which including the drawings of which is incorporated herein by reference), the example embodiment recirculating shader 602 (see FIGS. 6–12b) supports different alpha functions including a logical combination of plural alpha test results within a single rendering pass. In the example embodiment, the alpha function compares the source alpha with a reference alpha using any one of the following operations:

    • always,
    • never,
    • not equal,
    • equal,
    • less,
    • greater than or equal,
    • less than or equal,
    • greater than.


The two functions are combined in the example embodiment using:

    • AND,
    • OR,
    • XOR,
    • XNOR.


      If all of the valid pixels in a pixel quad fail the alpha test, the quad is discarded and the frame buffer 702 is thus not updated. Note that in the example embodiment, the alpha compare operation is not part of the recirculation stage, but rather, is performed after recirculation is complete—although the comparator 674 (which is part of the recirculating logic) can be used to perform alpha channel comparisons. The following are some examples of what can be implemented:


Example 1

Asrc>Aref0 AND Asrc<Aref1


Example 2

Asrc>Aref0 OR Asrc<Aref1


Example 3

Asrc>Aref OR Asrc <−Aref


The alpha functionality of recirculating shader 602 (e.g., in combination with the non-recirculating alpha compare) can thus be used to provide a transparency tree analogous to a shade tree. In particular, recirculating shader 602's alpha functionality can be used to provide N logical alpha operations on M alpha inputs, where N and M can be any integers. The combination of alpha compares and alpha logical operations can be used, for example, to provide non-photorealistic effects such as cartoon outlining.


Example Cartoon Outlining Technique



FIGS. 13 and 14 show that it may be desirable to apply border lines or outlines to cartoon characters. The FIG. 13 example cartoon character 1300 has border lines applied to silhouette edge(s) 1302. The outlining applied to silhouette edges 1302 provide a “cartoon outlining” effect that increases the clarity of the image and simulates hand-drawn cartoon or comic book type images.



FIG. 13 shows this cartoon character 1300 as also having a right hand, wrist, and portion of forearm being held in front of the character. A cartoon artist would apply border lines also to edges surrounding the right hand, wrist and forearm portion—even though in the particular character position shown, these are internal edges rather than silhouette edges. FIG. 13 illustrates that portions of the cartoon character 1300 may disappear or become less distinct if cartoon outlining is applied only to silhouette edge(s) 1302 of the character—whereas the viewer would (from experience with coloring books, hand-drawn animated cartoons, and/or comic books) expect a border line to also be applied to demarcate the hand, wrist and forearm.


To make cartoon character 1300 appear as if it were hand-drawn, it would be helpful to apply border lines to silhouette edges as well as to certain internal edges 304—i.e., those internal edges in this example that define the character's hand, wrist and portion of forearm that the character is holding in front of himself. FIG. 14 shows character 1300 with a border line applied to these internal edges 304. These internal edges 304 would be silhouette edges if the character 1300 was holding its arm in an outstretched position, but are internal edges in the arm orientation shown in FIG. 14.


A way to solve this problem is to assign different ID values to different objects or portions of an object, and to keep track of which pixels represent different objects or portions of an object by associating the ID values with the pixels during a rendering process. Such identification values can be assigned, as one example, by allocating bits within frame buffer 702 that are normally used to encode Alpha information. The assigned identification values may be used to determine whether or not to draw a border line at that pixel location. For example, the system may compare the identification value of a pixel to the identification value of a nearby (e.g., adjacent) pixel. If the identification values of two adjacent pixels have a certain predetermined relationship, then no border line is drawn. If the identification values are the same, then the two pixels are on the same surface and no border line is drawn. If the identification values of two adjacent pixels have a certain other predetermined relationship indicating an overlap of different objects or different portions of an object, then a border line is drawn.



FIGS. 15A–15C illustrate an example. FIG. 15A shows a perspective view of an object 1319 comprising three object portions 1320, 1322, 1324. FIG. 15B shows a plan view of the same object 1319. Object portion 1320 is a square, object portion 1322 is a circle, and object portion 1324 is a cone. Suppose the graphics artist wants to draw a border line 330 (see FIG. 15A) where cone 1324 visually meets square 1320, but not where the cone meets circle 1322 or where the circle meets the square.


In this example, pixels within square 1320, circle 1322 and cone 1324 are coded with different respective identification values. By way of example, pixels within square 1320 can be coded with an identification value of “1”; pixels within circle 1322 can be coded with “2”; and pixels within cone 1324 can be coded with “3”. FIG. 15C shows an example Alpha portion of frame buffer 702 storing the coded information, The shaded cells indicate those cells to which a border line color may be applied, based on a difference of 2 (or more) between neighboring alpha/id values.


During a pixel post-processing phase after an alpha and color image has been rendered into the frame buffer 702, the various identification values within the frame buffer can be tested. No border line is drawn for pixels having the same identification value as adjacent pixels (all such pixels are on the same surface). Also, no border line is drawn if a pixel has an identification value that differs by a predetermined criteria or set of criteria from the identification value of adjacent pixels (e.g., if the identification value of pixel k differs by less than 2 from the identification value of pixel k+1, then no border line is drawn). However, a border line is drawn if a pixel has an identification value that differs by a further predetermined criteria or set of criteria from the identification value of adjacent pixels (e.g., if the identification value of pixel k differs by 2 or more from the identification value of pixel k+1, then a border line may be drawn at pixel k).



FIG. 16 is a flowchart of an example pixel post-processing routine 1350 for drawing border lines. Routine 1350 includes a loop (blocks 13521362) that is performed for each pixel[i][j] in an image stored in frame buffer 702. As discussed above, the image generation process may, as part of rendering the image into the frame buffer, set identification values for each distinct part of an object in frame buffer bits normally allocated for storing Alpha values. Routine 1350 tests these Alpha (now ID) values to determine whether or not to draw border lines. In this example, routine 1350 retrieves the Alpha (ID) value of pixel[i][j] as well as the Alpha (ID) values of adjacent pixels (i.e., pixel[i−1][j] and pixel[i][j−1]) (block 1352). Routine 1352 then performs (at block 1354) the following calculation to determine the difference between the Alpha (ID) value of pixel[i][j] and the Alpha (ID) value(s) of adjacent pixels:

diffX=ABS(Alpha[i][j]−Alpha[i−1][j])
diffX=ABS(Alpha[i][j]−Alpha[i][j−1]).

Routine 1350 then tests the resulting calculated difference values diffX and diffY to determine if either exceeds a predetermined difference (e.g., an arbitrary fixed or programmable threshold such as 1) (block 1356). If at least one of the difference values exceeds the predetermined difference, then routine 1350 sets the color of pixel[i][j] to the border line color (block 1358). Thus, when alpha slope is −1 to +1, pixels are considered to be on the same surface in this particular example. Steps 13521358 are repeated for each pixel in the image (blocks 1360, 1362).


In one variation of routine 1350, certain objects can be coded with a special Alpha identification value (e.g., 0x00) to specify that the pixels within the object are to be ignored for the purpose of drawing border lines (see FIG. 16A). This could be useful, for example, to render a non-border-lined object as a bit map (e.g., for explosion animation).



FIG. 17 shows how routine 1350 described above can be applied to efficiently draw border lines on object 1300 shown in FIGS. 13 and 14. In this example, different parts of object 1300 are coded with different Alpha (ID) values. For example, object 1300 may include two arms 1311a, 1311b and a torso 1309. Each arm may comprise a hand 1313, a wrist portion 1315, a lower arm portion 1312, an elbow portion 1308, an upper arm portion 1310, and a shoulder portion 1317. Each of these various portions can be coded with a different Alpha ID as follows:
















Body Part
Alpha ID



















left hand 1313a
1



left wrist 1315a
2



left lower arm 1312a
3



left elbow 1308a
4



left upper arm 1310a
5



left shoulder 1317a
6



torso 1309
7



right shoulder 1317b
8



right upper arm 1310b
9



right elbow 1311b
10



right lower arm 1312b
11



right wrist 1315b
12



right hand 1313b
13










With the example Alpha ID coding above, routine 1350 will draw border lines as shown with dark lines in FIG. 17, but will not draw border lines at the other (dotted line) intersections between objection portions.


The coding above can also be used to apply a border line to intersections between connected portions of the same object 1300. Conventional coloring books, hand-drawn animated cartoons and the like sometimes apply cartoon outlining to such self-intersections in order to give greater definition to the articulated joint, create the illusion of muscle development, and the like. For example, FIGS. 18A–18C show a close-up of the articulated joint 1308 (i.e., elbow) of character 1300 joining the character's upper arm 1310 with forearm 1312. Using the coding described above, when the articulated joint 1308 is bent so that appendages 1310, 1312 are oriented adjacent to (e.g., in contact with) one another as illustrated in FIGS. 18B and 18C, routine 1350 will (based on the difference between Alpha ID of lower arm 1310 and Alpha ID of upper arm 1312 being greater than one) apply a border line segment 1316 to the intersection of body segments 1310, 1312 intersect.


Example Cartoon Outlining Process Implemented On System 50



FIG. 19 shows an example high-level flowchart of how system 50 can be used to provide cartoon outlining, and FIG. 20 shows an example of how system 50 can be configured to implement a cartoon outlining pipeline.


Referring to FIG. 19, to perform cartoon outline imaging or other similar effects, the application sets up frame buffer 702 to include an alpha channel (block 1400). See U.S. patent application Ser. No. 09/722,380 entitled “Embedded DRAM Frame Buffer With Reconfigurable Pixel Format”, and its corresponding provisional application Ser. No. 60/226,910, filed Aug. 23, 2000, both of which are incorporated herein by this reference. System 50 then is controlled to draw a scene into frame buffer 702 (block 1402). During this operation, however, object identifiers that may be provided by main processor 110 as part of per-vertex information, for example, are written into the alpha channel of system 50 for storage into the alpha locations within frame buffer 702.


Some attention to detail should be used when assigning IDs to surfaces. The example embodiment alpha channel is limited to eight bits, so it is possible that IDs may need to be reused if there are more than 256 different objects in a scene. In one example implementation, only seven bits of alpha are available, with the eighth bit being used as a sign bit for the threshold operation. This is acceptable so long as different objects with identical IDs do not overlap. If silhouettes are desired on overlapping sections of concave objects, a more complex ID and threshold system can be used. One way to implement this is to assign IDs that vary by one to different parts of the same object, with a total difference of at least two for possibly overlapping sections. The threshold function then only needs to create silhouettes for differences of at least two. See FIG. 16 above. Of course, different implementations will have different limitations, and these particular arrangements are illustrative only.


Once the desired portion of the image has been rendered into frame buffer 702, pixel engine 700 is controlled to copy the alpha image of the frame buffer to a texture in the external frame buffer or other buffer (block 1404; see FIG. 13). Such copy out can be into IA8 texture format, for example. Appropriate precautions are taken to ensure synchronization and memory coherence. See the synchronization token technique described in U.S. patent application Ser. No. 09/726,227 entitled “Dynamically Reconfiguring of Hidden Surface Processing Based on Rendering Mode”, and its corresponding provisional application, Ser. No. 60/226,890, filed Aug. 23, 2000, both of which are incorporated herein by this reference.


Once the alpha texture has been successfully copied out of the internal frame buffer and then read into texture memory 502 (see FIG. 13), system 50 configures the graphics processor 114 to write outline color to pixels within frame buffer 702 based on differences between neighboring pixel alphas (block 1406). See FIG. 16 above. Such a draw cartoon outline operation may, for example, involve reading out pixel alpha values, modifying those alpha values, and then writing back alpha as a blend parameter. Neighboring alpha values can be looked up from the alpha texture using one set of texture coordinates and two different texture matrices. One matrix can be set to the identity matrix, while the other is set to the identity matrix plus a translation. The blend test/comparison can be implemented using two general alpha compare functions combined with a third logical operation such as OR or AND. This allows us to do inside-outside range testing instead of just greater/less than.


In more detail, to perform the difference computation (e.g., the absolute value of [a0−a1] where a0 is the alpha value for a given pixel and a1 is the alpha value for a neighboring pixel), texture environment unit 600 can be set up to subtract one alpha value from the other and to write the unclamped result to the texture environment unit output register. The alpha compare or other value comparator within texture environment unit 600 can be set up to detect alpha values that exceed the threshold, i.e.:

alpha=texture1−texture 2
acomp1=alpha<−X
acomp2=alpha>X
killpixel=acomp1 OR acomp2.


In one particular implementation, unclamped negative results from texture environment unit 600 may turn into alpha values with the most significant bit set. Thus, for an alpha difference threshold of 2, the application can write the outline color to pixels with an alpha difference greater than 1 and smaller than (max−2) where max might equal 255. Texture environment unit 600 can be set up to blend in a color value from a register based upon the results of the comparison. Main processor 110 can set this color value register to any desired value (e.g., black for a black outlining effect, blue for a blue outlining effect, etc.).


In one particular example, writing outlines can be performed in two recirculation passes of recirculating shader within texture environment unit 600. In the first pass (block 1408), horizontal outlining is drawn into frame buffer 702 based on a texture coordinate transformation matrix multiplication performed by transform unit 300 that is set up to shift the alpha texture image one pixel (texel) vertically. In a second pass (block 1410) used for writing vertical outlines, the texture matrix can be modified to shift the alpha image one pixel (texel) horizontally. Thicker outlines can be achieved by making the shifts larger than one pixel, but visual anomalies may result if the outlines are made too thick.


Once both horizontal and vertical outlines have been written into frame buffer 702, the frame buffer can be copied out for display (block 1412).


EXAMPLE

The following shows an example set of application programming interface calls that can be used to control system 50 to perform cartoon outlining:














Function
Parameters
Description







GXSetTexCopySrc
xOrig, yOrig,
0, 0, SCREEN_WD,



width, height
SCREEN_HT


GXCopyTex
copy buffer
referred by




GXLoadTexObjPreLoaded



texture format
GX_TF_IA8



mipmap filter
GX_DISABLE



clear on copy
GX_DISABLE


GXLoadTexObjPreLoaded
texture map ID
GX_TEXMAP0



texture object
defined by



ptr
GXInitTexObj/TexObjLOD



texture region
defined by



ptr
GXInitTexRegion


GXInitTexObj
texture object
for output



ptr



pointer for
outputted by GXCopyTex



bitmap



width
SCREEN_WD



height
SCREEN_HT



texture format
GX_TF_IA8



clamp_s,
GX_CLAMP,



clamp_t
GX_CLAMP



mipmap enable
GX_DISABLE


GXInitTexObjLOD
texture object
same as GXInitTexObj's



ptr



min_filter
GX_NEAREST



max_filter
GX_NEAREST



min_lod,
0.0f, 0.0f, 0.0f (don't care)



max_lod,



lod_bias



bias_clamp,
GX_DISABLE, GX-



do_edge_lod
DISABLE (don't care)



max_aniso
GX_ANISO_1




(don't care)


GXInitTexPreloadRegion
texture_region
for output



tmem_even
0



size_even
0 (don't care)



tmem_odd
0 (don't care)



size_odd
0 (don't care)





Texture Environment


Blend/Alpha Compare commands


((See “Recirculating Shade Tree Blender For A Graphics System” referenced above.







GXSetTexCopySrc


Description


This function sets the source parameters for the Embedded Frame Buffer (EFB) to texture image copy. This feature is useful when creating textures using the Graphics Processor (GP).


The GP will copy textures into the tiled texture format specified in GXCopyTex. The GP always copies tiles (32B) so image widths and heights that are not a multiple of the tile width will be padded with undefined data in the copied image. Also, the allocated image size in main memory must be a multiple of 32 B, see GXGetTexBufferSize.


Arguments

  • left left most source pixel to copy, multiple of 2 pixels.
  • top top most source line to copy, multiple of 2 lines.
  • wd width to copy, multiple of 2 pixels.
  • ht height to copy, multiple of 2 lines.


    GXCopyTex


Description


This function copies the Embedded Frame Buffer (EFB) to a texture image buffer, dest, in main memory. This is useful when creating textures using the Graphics Processor (GP). If the clear flag is GX_TRUE, the EFB will be cleared to the current clear color (see GXSetCopyClear) during the copy operation. The source image is described by GXSetTexCopySrc. The EFB is converted to the texture format during the copy. The texture format and an optional box filter enable are set using GXSetTexCopyDst.


The allocated buffer is padded to texture tiles (32 B/tile) in X and Y. The function GXGetTexBufferSize is provided to determine the padded size.


The clear flag indicates the frame buffer should be cleared during the copy operation. The frame buffer is cleared to the constant values specified by GXSetCopyClear.


Arguments

  • dest Pointer to texture image buffer in main memory. This pointer should be 32 B aligned.
  • clear If this flag is GX_TRUE the framebuffer should be cleared during the copy.


    GXLoadTexObjPreLoaded


Description


This function loads the state describing a preloaded texture into one of eight hardware register sets. Before this happens, the texture object, obj, should be initialized using GXInitTexObj or GXInitTexObjCI. The id parameter refers to the texture state register set. The texture should be loaded beforehand using GXPreLoadEntireTexture.


Once loaded, the texture can be used in any Texture Environment (Tev) stage using the GXSetTevOrder function. GXInit initially calls GXSetTevOrder to make a simple texture pipeline that associates GX_TEXMAP0 with GX_TEVSTAGE0, GX_TEXMAP1 with GX_TEVSTAGE1, etc.


Note that GXLoadTexObjPreLoaded will not call the functions set by GXSetTexRegionCallBack (and GXSetTlutRegionCallBack if the texture is color index format) because the region is set explicitly. However, these callback functions must be aware of all regions that are preloaded. The default callbacks set by GXInit assume there are no preloaded regions.


Arguments

  • obj Points to a texture object which describes the texture and its properties.
  • region Points to a region object which describes an area of texture memory.
  • id Names the texture for reference in a texture environment (Tev) stage.


    GXInitTexObj


Description


This function is used to initialize or change a texture object for non-color index textures. Texture objects are used to describe all the parameters associated with a texture, including size, format, wrap modes, filter modes, etc. It is the application's responsibility to provide memory for a texture object. Once initialized, a texture object can be associated with one of eight active texture IDs using GXLoadTexObj.


To initialize a texture object for color index format textures, use GXInitTexObjCI.


If the mipmap flag is GX_TRUE, then the texture is a mipmap and the texture will be trilerped. If the mipmap flag is GX_FALSE, the texture is not a mipmap and the texture will be bilerped. To override the filter modes and other mipmap controls, see GXInitTexObjLOD.


Arguments












Arguments
















obj
Pointer to a texture object.


image_ptr
Pointer to the image data for a texture, aligned to 32B.


width
Width of the texture or LOD 0 for mipmaps. Max value



is 1024. Mipmaps must be a power of two.


height
Height of the texture or LOD 0 for mipmaps. Max value



is 1024. Mipmaps must be a power of two.


format
Texel format.


wrap_s
Describes how texture coordinates will be wrapped in



the s direction. Accepted values are: GX_CLAMP,



GX_REPEAT, GX_MIRROR.


wrap_t
Describes how texture coordinates will be wrapped in



the t direction. Accepted values are: GX_CLAMP,



GX_REPEAT, GX_MIRROR.


mipmap
If mipmap = GX_TRUE, the texture is a mipmap and will



have trilinear filtering; otherwise, it is not a mipmap and will



use bilinear filtering.










GXInitTexObjLOD















C Specification









# include <dolphin/gx.h>



void GXInitTexObjLOD(










GXTexObj*
obj,



GXTexFilter
min_filt,



GXTexFilter
mag_filt,



f32
min_lod,



f32
max_lod,



f32
lod_bias,



GXBool
bias_clamp,



GXBool
do_edge_lod,



GXAnisotropy
max_aniso );










Description


This function sets texture Level Of Detail (LOD) controls explicitly for a texture object. It is the application's responsibility to provide memory for a texture object. When initializing a texture object using GXInitTexObj or GXInitTexObjCI, this information is set to default values based on the mipmap flag. This function allows the programmer to override those defaults. Note that this function should be called after GXInitTexObj or GXInitTexObjCI for a particular texture object.


The LOD computed by the graphics hardware can be biased using the lod_bias parameter. The lod_bias is added to the computed lod and the result is clamped between min_lod and max_lod. If bias_clamp is enabled, the effect of lod_bias will diminish as the polygon becomes more perpendicular to the view direction. This prevents over-sharpening the texture in this situation, but allows LOD biasing for oblique polygons.












Arguments
















obj
Pointer to a texture object.


min_filt
Filter mode to use when the texel/pixel ratio is >= 1.0.



Accepted values: GX_NEAR, GX_LINEAR,



GX_NEAR_MIP_NEAR, GX_LIN_MIP_NEAR,



GX_NEAR_MIP_LIN, GX_LIN_MIP_LIN.


mag_filt
Filter mode to use when the texel/pixel ratio is < 1.0.



Accepted values are: GX_NEAR, GX_LINEAR.


min_lod
Minimum LOD value. The hardware will use



MAX(min_lod, lod). Range is 0.0 to 10.0.


max_lod
Maximum LOD value. The hardware will use



MIN(max_lod, lod). Range is 0.0 to 10.0.


lod_bias
Bias to add to computed LOD value.


bias_clamp
If GX_ENABLE, clamp the (LOD + lod_bias) so that



it is never less than the minimum extent of the pixel



projected in texture space. Prevents over-biasing the



LOD when the polygon is perpendicular to the view



direction.


do_edge_lod
Compute LOD using adjacent texels when GX_TRUE,



else use diagonal texels.


max_aniso
The maximum anisotropic filter to use.










GXInitTexPreLoadRegion


Description


This function initializes a Texture Memory (TMEM) region object for preloading. The region is allocated in TMEM by the application and can be used only as a pre-loaded buffer. Cache regions must be allocated by using GXInitTexCacheRegion. For pre-loaded textures, the size of the region must match the size of the texture. An application can create many region objects and some of them can overlap; however, no two overlapping regions can be active at the same time.


The maximum size of a region is 512K.


GXInit creates no region for preloading. So the application should allocate appropriate regions if preloading is necessary. It is also required to create cache regions and its allocator by using GXInitTexCacheRegion and GXSetTexRegionCallBack because new regions may destroy the default texture memory configuration.












Arguments
















region
Pointer to a GXTexRegion structure. The memory for this



structure must be allocated by the application.


tmem_even
Base pointer in Texture Memory for even LODs of a



mipmap. Must be in the opposite bank relative to



tmem_odd and aligned to 32 bytes.


size_even
Size of the the even cache in bytes. The size should be a



multiple of 32B (OSAlloc allocates memory in 32B



chunks).


tmem_odd
Base pointer in Texture Memory for the odd LODs of a



mipmap. Must be in the opposite bank relative to



tmem_even and aligned to 32 bytes.


size_odd
.Size of the the odd cache in bytes. The size should be a



multiple of 32B (OSAlloc allocates memory in 32B



chunks).










Example Software Controlled Process that Implements Cartoon Outlining


The following program fragment can be used to control the graphics pipeline to provide a cartoon outlining effect:














//---------------------------------------------------------------------------


// Cartoon outline settings


//---------------------------------------------------------------------------










#define
ASFT(x)
((x) <<2)
// ID step size ( 6bit alpha )


#ifdef
EPPC








#define
GXInitTexRegionPreLoaded( region, is_32b_mipmap, tmem_even, tmem_odd


)\










GXInitTexRegion(
(region), GX_FALSE, (is_32b_mipmap), \




(tmem_even), 0, 0, (tmem_odd), 0, 0 )







// If exFB can be usable, Use exFB instead of this buffer








u16
alphaBuffer[SCREEN_WD*SCREEN_HT] ATTRIBUTE_ALIGN(32);


GXTexObj
eFBTexObj;


GXTexRegion
eFBTexRegion;







/*---------------------------------------------------------------------------


*









Draw Cartoon outline for HW







*---------------------------------------------------------------------------


*/








void
DrawCartoonOutline( void )


{









static s32 initialized = 0;










//
CopyOut eFB as IA8 texture format









GXSetTexCopySrc( 0, 0, SCREEN_WD, SCREEN_HT );



GXCopyTex( alphaBuffer, GX_TF_IA8, GX_DISABLE, GX_DISABLE );










//
Load the bitmap into TMEM









if ( !initialized )



{










GXInitTexObj(
&eFBTexObj, alphaBuffer, SCREEN_WD, SCREEN_HT,




GX_TF_IA8, GX_CLAMP, GX_CLAMP, GX_DISABLE );










GXInitTexObjLOD(
&eFBTexObj, GX_NEAR, GX_NEAR, 0.0f, 0.0f, 0.0f,




GX_DISABLE, GX_DISABLE, GX_ANISO_1 );










GXInitTexRegionPreLoaded(
&eFBTexRegion, GX_FALSE, 0, 0 );



initialized = 1;









}










GXLoadTexObjPreLoaded(
&eFBTexObj, &eFBTexRegion, GX_TEXMAP0 );



return;







}


#else








u8
alphaBuffer[SCREEN_WD*SCREEN_HT];







/*---------------------------------------------------------------------------


*









Draw Cartoon outline for OpenGL







*---------------------------------------------------------------------------


*/








void
DrawCartoonOutline( void )


{










u32
i;



u8
a00, a01, a10, d01, d10;









// Read out pixel alpha










glReadPixels(
0, 0, SCREEN_WD, SCREEN_HT,




GL_ALPHA, GL_UNSIGNED_BYTE, alphaBuffer );









// Modify alpha



for ( i = 0; i < SCREEN_WD*(SCREEN_HT−1); i ++ )



{









a01 = a00;



a00 = alphaBuffer[i];



a10 = alphaBuffer[i+SCREEN_WD];



d01 = (u8) (a01 − a00 + ASFT(1));



d10 = (u8) (a10 − a00 + ASFT(1));










if ( d01 > ASFT(2) || d10 > ASFT(2) )
alphaBuffer[i] = 0x00;



else
alphaBuffer[i] = 0xff;









}



// Write back alpha as blend parameter











glBlendFunc
(
GL_ZERO, GL_SRC_ALPHA );



glAlphaFunc
(
GL_ALWAYS, 0.0f );



glViewport
(
0, 0, SCREEN_WD, SCREEN_HT );



glScissor
(
0, 0, SCREEN_WD, SCREEN_HT );











glDrawPixels
(
SCREEN_WD, SCREEN_HT,





GL_ALPHA, GL_UNSIGNED_BYTE, alphaBuffer );



return;







}


#endif










Other Example Compatible Implementations


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.


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.


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.



FIG. 21A 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.


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 1305 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).


An emulator 1303 or other platform implementing the FIG. 19 outlining process might not have a recirculating shader, but might instead implement the alpha compare operation using a pipeline of discrete shading/blending stages. Similarly, an alternative implementation might not store alpha and color information in the same frame buffer, but might instead store this information in different frame buffers. For example, the alpha “image” providing object Ids might be stored as a map in main memory. Post processing need not be performed through use of texturing, but could be performed instead by a general purpose processor. Rendering outlines in two passes might not be needed; some implementations might render both horizontal and vertical outlines in the same pass.


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.



FIG. 21B 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.


A number of program modules including emulator 1303 may be stored on the hard disk 211, 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.


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.


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.


The entire contents of all patents, patent applications and other documents referenced above are expressly incorporated herein.


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. For example, although the object of the illustrated embodiment is to provide images with cartoon outlining, the flexible alpha compare operation described herein can be used for a number of different imaging applications. Furthermore, while dual alpha comparisons are described above, the present invention is not limited to just two alpha comparisons. Additionally, while the preferred embodiment uses a recirculating shader, a parallel arrangement having plural alpha comparators could be used. Accordingly, the invention is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims.

Claims
  • 1. A method of generating a graphics image comprising: (a) generating information representing a surface to be imaged, said information including alpha transparency/opacity information;(b) performing, at least in part within a recirculating, hardware-based graphics generator, plural alpha comparisons on said alpha information to provide corresponding plural alpha comparison results;(c) logically combining said plural alpha comparison results; and(d) rendering said graphics image based at least in part on said logical combination,wherein said steps (b) and (c) use said recirculating, hardware-based graphics generator to process a programmable alpha tree by providing N logical alpha operations on M alpha inputs, M and N being any integers, M>1, N>1.
  • 2. The method of claim 1 wherein said rendering step includes selecting whether or not to kill a pixel based on said logical combination.
  • 3. The method of claim 1 wherein said performing step is performed using a recirculating shader.
  • 4. The method of claim 1 wherein both said performing and said logically combining steps are performed at least in part by hardware.
  • 5. The method of claim 1 wherein said rendering step includes selectively determining whether to blend a cartoon outline color based on said logical combination.
  • 6. The method of claim 1 wherein said steps (b) and (c) implement an absolute value function.
  • 7. The method of claim 1 wherein said plural alpha comparisons include any selected ones of the following: always,never,not equal,equal,less than,greater than or equal,less than or equal,greater than.
  • 8. The method of claim 1 wherein said logical combining includes AND, OR, XOR, XNOR.
  • 9. In a home video game system or low cost personal computer graphics card, a hardware-based transparency processor including: an alpha combiner stage that combines at least first and second alpha input values to generate an alpha result;an alpha comparator/tester that compares or tests the alpha result; anda recirculator at least in part responsive to said alpha comparator/tester, said recirculator selectively recirculating said alpha result as at least one of said alpha input values,whereby said transparency processor processes programmable, arbitrarily complex alpha trees; wherein said alpha trees have arbitrary complexity comprising N logical operations on M alpha inputs, M and N being any integers, M>1, N>1.
  • 10. The transparency processor of claim 9 wherein said recirculator selectively recirculates said alpha result conditioned on said alpha comparison or test said alpha comparator/tester performs on said alpha result.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Nos. 60/226,915 and 60/226,888 filed Aug. 23, 2000, the entire contents of which are hereby incorporated by reference. This application is related to concurrently-filed application Ser. No. 09/722,367 of Drebin et al entitled “Recirculating Shade Tree Blender For a Graphics System”.

US Referenced Citations (387)
Number Name Date Kind
4275413 Sakamoto et al. Jun 1981 A
4357624 Greenberg Nov 1982 A
4463380 Hooks, Jr. Jul 1984 A
4491836 Collmeyer et al. Jan 1985 A
4586038 Sims et al. Apr 1986 A
4600919 Stern Jul 1986 A
4615013 Yan et al. Sep 1986 A
4625289 Rockwood Nov 1986 A
4653012 Duffy et al. Mar 1987 A
4692880 Merz et al. Sep 1987 A
4695943 Keeley et al. Sep 1987 A
4710876 Cline et al. Dec 1987 A
4768148 Keeley et al. Aug 1988 A
4785395 Keeley Nov 1988 A
4790025 Inoue et al. Dec 1988 A
4808988 Burke et al. Feb 1989 A
4812988 Duthuit et al. Mar 1989 A
4817175 Tenenbaum et al. Mar 1989 A
4829452 Kang et al. May 1989 A
4833601 Barlow et al. May 1989 A
4855934 Robinson Aug 1989 A
4888712 Barkans et al. Dec 1989 A
4897806 Cook et al. Jan 1990 A
4907174 Priem Mar 1990 A
4918625 Yan Apr 1990 A
4935879 Ueda Jun 1990 A
4965751 Thayer et al. Oct 1990 A
4974176 Buchner et al. Nov 1990 A
4974177 Nishiguchi Nov 1990 A
4975977 Kurosu et al. Dec 1990 A
4989138 Radochonski Jan 1991 A
4996666 Duluk, Jr. Feb 1991 A
5003496 Hunt, Jr. et al. Mar 1991 A
5016183 Shyong May 1991 A
5018076 Johary et al. May 1991 A
5043922 Matsumoto Aug 1991 A
5056044 Frederickson et al. Oct 1991 A
5062057 Blacken et al. Oct 1991 A
5086495 Gray et al. Feb 1992 A
5091967 Ohsawa Feb 1992 A
5097427 Lathrop et al. Mar 1992 A
5144291 Nishizawa Sep 1992 A
5163126 Einkauf et al. Nov 1992 A
5179638 Dawson et al. Jan 1993 A
5204944 Wolberg et al. Apr 1993 A
5224208 Miller, Jr. et al. Jun 1993 A
5239624 Cook et al. Aug 1993 A
5241658 Masterson et al. Aug 1993 A
5255353 Itoh Oct 1993 A
5268995 Diefendorff et al. Dec 1993 A
5268996 Steiner et al. Dec 1993 A
5278948 Luken, Jr. Jan 1994 A
5293235 Guede et al. Mar 1994 A
5307450 Grossman Apr 1994 A
5315692 Hansen et al. May 1994 A
5345541 Kelley et al. Sep 1994 A
5353424 Partovi et al. Oct 1994 A
5357579 Buchner et al. Oct 1994 A
5361386 Watkins et al. Nov 1994 A
5363475 Baker et al. Nov 1994 A
5377313 Scheibl Dec 1994 A
5394516 Winser Feb 1995 A
5402532 Epstein et al. Mar 1995 A
5404445 Matsumoto Apr 1995 A
5408650 Arsenault Apr 1995 A
5412796 Olive May 1995 A
5415549 Logg May 1995 A
5416606 Katayama et al. May 1995 A
5422997 Nagashima Jun 1995 A
5432895 Myers Jul 1995 A
5432900 Rhodes et al. Jul 1995 A
5438663 Matsumoto et al. Aug 1995 A
5448689 Matsuo et al. Sep 1995 A
5461712 Chelstowski et al. Oct 1995 A
5467438 Nishio et al. Nov 1995 A
5467459 Alexander et al. Nov 1995 A
5469535 Jarvis et al. Nov 1995 A
5473736 Young Dec 1995 A
5475803 Stearns et al. Dec 1995 A
5487146 Guttag et al. Jan 1996 A
5490240 Foran et al. Feb 1996 A
5495563 Winser Feb 1996 A
5504499 Horie et al. Apr 1996 A
5506604 Nally et al. Apr 1996 A
5535288 Chen et al. Jul 1996 A
5535374 Olive Jul 1996 A
5543824 Priem et al. Aug 1996 A
5544292 Winser Aug 1996 A
5548709 Hannah et al. Aug 1996 A
5553228 Erb et al. Sep 1996 A
5557712 Guay Sep 1996 A
5559954 Sakoda et al. Sep 1996 A
5561746 Murata et al. Oct 1996 A
5561752 Jevans Oct 1996 A
5563989 Billyard Oct 1996 A
5566285 Okada Oct 1996 A
5572634 Duluk, Jr. Nov 1996 A
5573402 Gray Nov 1996 A
5574835 Duluk, Jr. et al. Nov 1996 A
5579456 Cosman Nov 1996 A
5586234 Sakuraba et al. Dec 1996 A
5593350 Bouton et al. Jan 1997 A
5596686 Duluk, Jr. Jan 1997 A
5600763 Greene et al. Feb 1997 A
5606650 Kelley et al. Feb 1997 A
5607157 Nagashima Mar 1997 A
5608864 Bindlish et al. Mar 1997 A
5616031 Logg Apr 1997 A
5621867 Murata et al. Apr 1997 A
5628686 Svancarek et al. May 1997 A
5638535 Rosenthal et al. Jun 1997 A
5644364 Kurtze et al. Jul 1997 A
5649082 Burns Jul 1997 A
5650955 Puar et al. Jul 1997 A
5651104 Cosman Jul 1997 A
5657045 Katsura et al. Aug 1997 A
5657443 Krech, Jr. Aug 1997 A
5657478 Recker et al. Aug 1997 A
5659671 Tannenbaum et al. Aug 1997 A
5659673 Nonoshita Aug 1997 A
5659715 Wu et al. Aug 1997 A
5664162 Dye Sep 1997 A
5666439 Ishida et al. Sep 1997 A
5669010 Duluk, Jr. Sep 1997 A
5678037 Osugi et al. Oct 1997 A
5682522 Huang et al. Oct 1997 A
5684941 Dye Nov 1997 A
5687304 Kiss Nov 1997 A
5691746 Shyu Nov 1997 A
5694143 Fielder et al. Dec 1997 A
5696892 Redmann et al. Dec 1997 A
5703806 Puar et al. Dec 1997 A
5706481 Hannah et al. Jan 1998 A
5706482 Matsushima et al. Jan 1998 A
5714981 Scott-Jackson et al. Feb 1998 A
5724561 Tarolli et al. Mar 1998 A
5726689 Negishi et al. Mar 1998 A
5726947 Yamazaki et al. Mar 1998 A
5734386 Cosman Mar 1998 A
5739819 Bar-Nahum Apr 1998 A
5740343 Tarolli et al. Apr 1998 A
5740383 Nally et al. Apr 1998 A
5740406 Rosenthal et al. Apr 1998 A
5742749 Foran et al. Apr 1998 A
5742788 Priem et al. Apr 1998 A
5745118 Alcorn et al. Apr 1998 A
5745125 Deering et al. Apr 1998 A
5748199 Palm May 1998 A
5748986 Butterfield et al. May 1998 A
5751291 Olsen et al. May 1998 A
5751292 Emmot May 1998 A
5751295 Becklund et al. May 1998 A
5751930 Katsura et al. May 1998 A
5754191 Mills et al. May 1998 A
5757382 Lee May 1998 A
5760783 Migdal et al. Jun 1998 A
5764228 Baldwin Jun 1998 A
5764237 Kaneko Jun 1998 A
5767856 Peterson et al. Jun 1998 A
5767858 Kawase et al. Jun 1998 A
5768629 Wise et al. Jun 1998 A
5777623 Small Jul 1998 A
5781927 Wu et al. Jul 1998 A
5791994 Hirano et al. Aug 1998 A
5801711 Koss et al. Sep 1998 A
5801720 Norrod et al. Sep 1998 A
5805175 Priem Sep 1998 A
5808619 Choi et al. Sep 1998 A
5808630 Pannell Sep 1998 A
5809219 Pearce et al. Sep 1998 A
5809278 Watanabe et al. Sep 1998 A
5815165 Blixt Sep 1998 A
5818456 Cosman et al. Oct 1998 A
5819017 Akeley et al. Oct 1998 A
5821940 Morgan et al. Oct 1998 A
5822516 Krech, Jr. Oct 1998 A
5828382 Wilde Oct 1998 A
5828383 May et al. Oct 1998 A
5828907 Wise et al. Oct 1998 A
5831624 Tarolli et al. Nov 1998 A
5831625 Rich et al. Nov 1998 A
5831640 Wang et al. Nov 1998 A
5835096 Baldwin Nov 1998 A
5835792 Wise et al. Nov 1998 A
5838334 Dye Nov 1998 A
5844576 Wilde et al. Dec 1998 A
5850229 Edelsbrunner et al. Dec 1998 A
5852451 Cox et al. Dec 1998 A
5856829 Gray, III et al. Jan 1999 A
5859645 Latham Jan 1999 A
5861888 Dempsey Jan 1999 A
5861893 Sturgess Jan 1999 A
5867166 Myhrvold et al. Feb 1999 A
5870097 Snyder et al. Feb 1999 A
5870098 Gardiner Feb 1999 A
5870102 Tarolli et al. Feb 1999 A
5870109 McCormack et al. Feb 1999 A
5870587 Danforth et al. Feb 1999 A
5872902 Kuchkuda et al. Feb 1999 A
5877741 Chee et al. Mar 1999 A
5877770 Hanaoka Mar 1999 A
5877771 Drebin et al. Mar 1999 A
5880736 Peercy et al. Mar 1999 A
5880737 Griffin et al. Mar 1999 A
5883638 Rouet et al. Mar 1999 A
5886701 Chauvin et al. Mar 1999 A
5886705 Lentz Mar 1999 A
5887155 Laidig Mar 1999 A
5890190 Rutman Mar 1999 A
5892517 Rich Apr 1999 A
5892974 Koizumi et al. Apr 1999 A
5894300 Takizawa Apr 1999 A
5900881 Ikedo May 1999 A
5903283 Selwan et al. May 1999 A
5909218 Naka et al. Jun 1999 A
5909225 Schinnerer et al. Jun 1999 A
5912675 Laperriere Jun 1999 A
5912676 Malladi et al. Jun 1999 A
5914721 Lim Jun 1999 A
5914725 MacInnis et al. Jun 1999 A
5914729 Lippincott Jun 1999 A
5920876 Ungar et al. Jul 1999 A
5923332 Izawa Jul 1999 A
5923334 Luken Jul 1999 A
5926182 Menon et al. Jul 1999 A
5926647 Adams et al. Jul 1999 A
5933150 Ngo et al. Aug 1999 A
5933154 Howard et al. Aug 1999 A
5933155 Akeley Aug 1999 A
5933529 Kim Aug 1999 A
5936641 Jain et al. Aug 1999 A
5936683 Lin Aug 1999 A
5940089 Dilliplane Aug 1999 A
5940538 Spiegel et al. Aug 1999 A
5943058 Nagy Aug 1999 A
5943060 Cosman et al. Aug 1999 A
5945997 Zhao et al. Aug 1999 A
5949421 Ogletree et al. Sep 1999 A
5949423 Olsen Sep 1999 A
5949428 Toelle et al. Sep 1999 A
5956042 Tucker et al. Sep 1999 A
5956043 Jensen Sep 1999 A
5958020 Evoy et al. Sep 1999 A
5959640 Rudin et al. Sep 1999 A
5963220 Lee et al. Oct 1999 A
5966134 Arias Oct 1999 A
5977977 Kajiya et al. Nov 1999 A
5977979 Clough et al. Nov 1999 A
5977984 Omori Nov 1999 A
5977987 Duluk, Jr. Nov 1999 A
5982376 Abe et al. Nov 1999 A
5982390 Stoneking et al. Nov 1999 A
5986659 Gallery et al. Nov 1999 A
5986663 Wilde Nov 1999 A
5986677 Jones et al. Nov 1999 A
5987567 Rivard et al. Nov 1999 A
5990903 Donovan Nov 1999 A
5995120 Dye Nov 1999 A
5995121 Alcokrn Nov 1999 A
5999189 Kajiya et al. Dec 1999 A
5999198 Horan et al. Dec 1999 A
6002407 Fadden Dec 1999 A
6002410 Battle Dec 1999 A
6005582 Gabriel et al. Dec 1999 A
6005583 Morrison Dec 1999 A
6005584 Kitamura et al. Dec 1999 A
6007428 Nishiumi et al. Dec 1999 A
6008820 Chauvin et al. Dec 1999 A
6011562 Gagne et al. Jan 2000 A
6011565 Kuo et al. Jan 2000 A
6014144 Nelson et al. Jan 2000 A
6016150 Lengyel et al. Jan 2000 A
6016151 Lin Jan 2000 A
6018350 Lee et al. Jan 2000 A
6020931 Bilbrey et al. Feb 2000 A
6021417 Massarksy Feb 2000 A
6022274 Takeda et al. Feb 2000 A
6023261 Ugajin Feb 2000 A
6026182 Lee et al. Feb 2000 A
6028608 Jenkins Feb 2000 A
6031542 Wittig Feb 2000 A
6035360 Doidge et al. Mar 2000 A
6037948 Liepa Mar 2000 A
6038031 Murphy Mar 2000 A
6038348 Carley Mar 2000 A
6040843 Monroe et al. Mar 2000 A
6040844 Yamaguchi et al. Mar 2000 A
6041010 Puar et al. Mar 2000 A
6043804 Greene Mar 2000 A
6043821 Sprague et al. Mar 2000 A
6046746 Deering Apr 2000 A
6046747 Saunders et al. Apr 2000 A
6046752 Kirkland et al. Apr 2000 A
6049337 Van Overveld Apr 2000 A
6049338 Anderson et al. Apr 2000 A
6052125 Gardiner et al. Apr 2000 A
6052126 Sakuraba et al. Apr 2000 A
6052127 Vaswani et al. Apr 2000 A
6052129 Fowler et al. Apr 2000 A
6052133 Kang Apr 2000 A
6054993 Devic et al. Apr 2000 A
6054999 Strandberg Apr 2000 A
6057847 Jenkins May 2000 A
6057849 Haubner et al. May 2000 A
6057851 Luken et al. May 2000 A
6057859 Handelman et al. May 2000 A
6057861 Lee et al. May 2000 A
6057862 Margulis May 2000 A
6057863 Olarig May 2000 A
6061462 Tostevin et al. May 2000 A
6064392 Rohner May 2000 A
6067098 Dye May 2000 A
6070204 Poisner May 2000 A
6072496 Guenter et al. Jun 2000 A
6075543 Akeley Jun 2000 A
6075546 Hussain et al. Jun 2000 A
6078311 Pelkey Jun 2000 A
6078333 Wittig et al. Jun 2000 A
6078334 Hanaoka et al. Jun 2000 A
6078338 Horan et al. Jun 2000 A
6081274 Shiraishi Jun 2000 A
6088035 Sudarsky et al. Jul 2000 A
6088042 Handelman et al. Jul 2000 A
6088487 Kurashige Jul 2000 A
6088701 Whaley et al. Jul 2000 A
6091431 Saxena et al. Jul 2000 A
6092158 Harriman et al. Jul 2000 A
6094200 Olsen et al. Jul 2000 A
6097435 Stanger et al. Aug 2000 A
6097437 Hwang Aug 2000 A
6104415 Gossett Aug 2000 A
6104417 Nielsen et al. Aug 2000 A
6105094 Lindeman Aug 2000 A
6108743 Debs et al. Aug 2000 A
6111582 Jenkins Aug 2000 A
6111584 Murphy Aug 2000 A
6115047 Deering Sep 2000 A
6115049 Winner et al. Sep 2000 A
6118462 Margulis Sep 2000 A
6128026 Brothers, III Oct 2000 A
6144365 Young et al. Nov 2000 A
6144387 Liu et al. Nov 2000 A
6151602 Hejlsberg et al. Nov 2000 A
6155926 Miyamoto et al. Dec 2000 A
6157387 Kotani Dec 2000 A
6166748 Van Hook et al. Dec 2000 A
6172678 Shiraishi Jan 2001 B1
6177944 Fowler et al. Jan 2001 B1
6191794 Priem et al. Feb 2001 B1
6200253 Nishiumi et al. Mar 2001 B1
6204851 Netschke et al. Mar 2001 B1
6215496 Szeliski et al. Apr 2001 B1
6215497 Leung Apr 2001 B1
6226713 Mehrotra May 2001 B1
6229553 Duluk, Jr. et al. May 2001 B1
6232981 Gossett May 2001 B1
6236413 Gossett et al. May 2001 B1
6239810 Van Hook et al. May 2001 B1
6252608 Snyder et al. Jun 2001 B1
6252610 Hussain Jun 2001 B1
6264558 Nishiumi et al. Jul 2001 B1
6268861 Sanz-Pastor et al. Jul 2001 B1
6268875 Duluk, Jr. et al. Jul 2001 B1
6275235 Morgan, III Aug 2001 B1
6285378 Duluk, Jr. Sep 2001 B1
6285779 Lapidous et al. Sep 2001 B1
6288730 Duluk, Jr. et al. Sep 2001 B1
6292194 Powell, III Sep 2001 B1
6329997 We et al. Dec 2001 B1
6331856 Van Hook et al. Dec 2001 B1
6333744 Kirk et al. Dec 2001 B1
6339428 Fowler et al. Jan 2002 B1
6342892 Van Hook et al. Jan 2002 B1
6353438 Van Hook Mar 2002 B1
6356497 Puar et al. Mar 2002 B1
6408362 Arimilli et al. Jun 2002 B1
6417858 Bosch et al. Jul 2002 B1
6426747 Hoppe et al. Jul 2002 B1
6437781 Tucker et al. Aug 2002 B1
6459429 Deering Oct 2002 B1
6466223 Dorbie et al. Oct 2002 B1
6469707 Voorhies Oct 2002 B1
6476808 Kuo et al. Nov 2002 B1
6476822 Burbank Nov 2002 B1
6496187 Deering et al. Dec 2002 B1
6532013 Papakipos et al. Mar 2003 B1
6597363 Duluk, Jr. et al. Jul 2003 B1
Foreign Referenced Citations (16)
Number Date Country
0 637 813 Feb 1995 EP
9-330230 Dec 1997 JP
WO9304429 Mar 1993 WO
WO 9323816 Nov 1993 WO
WO 9705575 Feb 1997 WO
WO 9705576 Feb 1997 WO
WO 0010372 Mar 2000 WO
WO 0011562 Mar 2000 WO
WO 0011602 Mar 2000 WO
WO 0011603 Mar 2000 WO
WO 0011604 Mar 2000 WO
WO 0011605 Mar 2000 WO
WO 0011607 Mar 2000 WO
WO 0011613 Mar 2000 WO
WO 0011614 Mar 2000 WO
WO0019377 Apr 2000 WO
Provisional Applications (2)
Number Date Country
60226915 Aug 2000 US
60226888 Aug 2000 US