US 6,811,489 B1Grant
Controller interface for a graphics system
Issue Date:2004-11-02
•43 Claims
•19 Drawing Sheets
Abstract
A video game system includes a game program executing system executing a game program and one or more controllers supplying user inputs to the game program executing system. An interface between the controllers and the game program executing system is programmable to periodically poll the controller without involvement of the game program executing system.
Metadata
Assignee
- Nintendo Co., Ltd.
Inventors
- Dan Shimizu
- Ko Shiota
- Munehito Oira
- Kazuo Koshima
Application Information
Application Number:US 09/722,664
Filing Date:2000-11-28
Priority Date:2000-08-23
Art Unit:7
Classifications
IPC:
G06F 1900G06F 300
Field of Search:
463 1463 30273148 B700 90700306710 1710 4710 36710 46710220711 1711100711109345422345661345682345716345156345161345501345506345520345530345539345949345667
Patent Drawings (19 sheets)
Description
Related Applications
[0002] This application claims priority from provisional Application No. 60/226,885, filed Aug. 23, 2000, the contents of which are incorporated herein.
Field of the Invention
[0003] 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 a controller interface used to connect a controller to a graphics system.
Background and Summary of the Invention
[0004] 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 a 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.
[0005] 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.
[0006] In an interactive real time system such as a gaming platform, user-manipulable controls are provided for player inputs. The controls may take many forms including buttons, switches, joysticks, trackballs and the like. These player inputs are used during game play, for example, to move characters left, right, up and down; to take character actions such as jumping; etc. Thus, in game systems, some means must be provided to interface with user-manipulable controls such as hand-held controllers or the like. The present invention provides such an interface. More specifically, the present invention provides an interface for interfacing an audio and graphics coprocessor with a variety of different types of accessory devices including but not limited to hand-held game controllers. The serial interface provides a single bit serial interface using a state-based interface protocol. The interface supports four separate serial interfaces to four hand-held controllers or associated devices. Each interface can be accessed in parallel. In a controller mode, the last state of the controller is stored in a double-buffered register to support simple main processor reads for determining state. The example embodiment automatically polls controller state using hardware circuitry with configurable polling periods. A bulk mode supports changeable data size. A pair of light gun signals can be used to control separate horizontal/vertical counters to support flash and shutter light guns. An LCD shutter can be supported through automatic polling and a serial control command. The system interface includes automatic control of presence detect to save effort on the part of the main processor.
[0007] In accordance with one particular aspect of the present invention, a video game system includes a game program executing system executing a game program and one or more controllers supplying user inputs to the game program executing system. An interface between the controllers and the game program executing system is programmable to periodically poll the controller without involvement of the game program executing system.
Brief Description of the Drawings
[0008] 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:
[0009] FIG. 1 is an overall view of an example interactive computer graphics system;
[0010] FIG. 2 is a block diagram of the FIG. 1 example computer graphics system;
[0011] FIG. 3 is a block diagram of the example graphics and audio processor shown in FIG. 2;
[0012] FIG. 4 is a block diagram of the example 3D graphics processor shown in FIG. 3;
[0013] FIG. 5 is an example logical flow diagram of the FIG. 4 graphics and audio processor;
[0014] FIG. 6 shows an example input/output subsystem;
[0015] FIGS. 7A and 7B show an example serial interface;
[0016] FIG. 7C shows example serial interface registers;
[0017] FIG. 8 shows a more detailed view of the serial interface of FIGS. 7A and 7B;
[0018] FIG. 9 shows a more detailed view of a portion of the serial interface shown in FIG. 8;
[0019] FIG. 10 shows an example controller;
[0020] FIG. 11 shows the example system elements involved in data transfers using a communication RAM;
[0021] FIG. 12 is used to illustrate the meaning of the X line interval register and the Y times register;
[0022] FIG. 13 shows an example light gun;
[0023] FIGS. 14A-14C are timing diagrams for explaining the light gun and light pen operations;
[0024] FIGS. 15A-15E depict signals used in data transfer;
[0025] FIG. 16 illustrates the communication protocol between the serial interface and the controllers;
[0026] FIG. 17 depicts the lines for the channels of serial interface 1000; and
[0027] FIGS. 18A and 18B show example alternative compatible implementations.
Detailed Description of Example Embodiments of the Invention
[0028] 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.
[0029] In this example, system 50 is capable of processing, interactively in real time, a digital representation or model of a three-dimensional world. System 50 can display some or all of the world from any arbitrary viewpoint. For example, system 50 can interactively change the viewpoint in response to real time inputs from handheld controllers 52a,52bor other input devices. This allows the game player to see the world through the eyes of someone within or outside of the world. System 50 can be used for applications that do not require real time 3D interactive display (e.g., 2D display generation and/or non-interactive display), but the capability of displaying quality 3D images very quickly can be used to create very realistic and exciting game play or other graphical interactions.
[0030] 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.
[0031] 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.
[0032] The user may use hand controllers 52a,52ato 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.
[0033] 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.
[0034] Example Electronics of Overall System
[0035] FIG. 2 shows a block diagram of example components of system 50. The primary components include:
[0036] a main processor (CPU) 110,
[0037] a main memory 112, and
[0038] a graphics and audio processor 114.
[0039] In this example, main processor 110 (e.g., an enhanced IBM Power PC 750) receives inputs from handheld controllers 52 (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.
[0040] 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.
[0041] 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.
[0042] 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:
[0043] a programmable read-only memory (PROM) and/or real time clock (RTC) 134,
[0044] 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
[0045] a flash memory 140.
[0046] 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.
[0047] Example Graphics and Audio Processor
[0048] 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:
[0049] a processor interface 150,
[0050] a memory interface/controller 152,
[0051] a 3D graphics processor 154,
[0052] an audio digital signal processor (DSP) 156,
[0053] an audio memory interface 158,
[0054] an audio interface and mixer 1300,
[0055] a peripheral controller 162, and
[0056] a display controller 164.
[0057] 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 1300 interfaces with audio codec 122, and can also mix audio from different sources (e.g., streaming audio from mass access storage 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.
[0058] 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.
[0059] Example Graphics Pipeline
[0060] 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.
[0061] 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.
[0062] 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 112. The command processor 200 fetches:
[0063] 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,
[0064] display lists 212 from main memory 112 via an on-chip call FIFO memory buffer 218, and
[0065] vertex attributes from the command stream and/or from vertex arrays 214 in main memory 112 via a vertex cache 220.
[0066] Command processor 200 performs command processing operations 200athat 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 131 (see FIG. 4) arbitrates access to shared main memory 112 between graphics pipeline 180, command processor 200 and display controller/video interface unit 164.
[0067] FIG. 4 shows that graphics pipeline 180 may include:
[0068] a transform unit 300,
[0069] a setup/rasterizer 400,
[0070] a texture unit 500,
[0071] a texture environment unit 600, and
[0072] a pixel engine 700.
[0073] Transform unit 300 performs a variety of 2D and 3D transform and other operations 300a(see FIG. 5). Transform unit 300 may include one or more matrix memories 300bfor storing matrices used in transformation processing 300a.Transform unit 300 transforms incoming geometry per vertex from object space to screen space; and transforms incoming texture coordinates and computes projective texture coordinates (300c). Transform unit 300 may also perform polygon clipping/culling 300d.Lighting processing 300ealso performed by transform unit 300 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).
[0074] 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.
[0075] Texture unit 500 (which may include an on-chip texture memory (TMEM) 502) performs various tasks related to texturing including for example:
[0076] retrieving textures 504 from main memory 112,
[0077] 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,
[0078] bump map processing for computing texture coordinate displacements for bump mapping, pseudo texture and texture tiling effects (500b), and indirect texture processing (500c).
[0079] Texture unit 500 outputs filtered texture values to the texture environment unit 600 for texture environment processing (600a). Texture environment unit 600 blends polygon and texture color/alpha/depth, and can also perform texture fog processing (600b) to achieve inverse range based fog effects. Texture environment unit 600 can provide multiple stages to perform a variety of other interesting environment-related functions based for example on color/alpha modulation, embossing, detail texturing, texture swapping, clamping, and depth blending.
[0080] Pixel engine 700 performs depth (z) compare (700a) and pixel blending (700b). In this example, pixel engine 700 stores data into an embedded (on-chip) frame buffer memory 702. Graphics pipeline 180 may include one or more embedded DRAM memories 702 to store frame buffer and/or texture information locally. Z compares 700a′ can also be performed at an earlier stage in the graphics pipeline 180 depending on the rendering mode currently in effect (e.g., z compares can be performed earlier if alpha blending is not required). The pixel engine 700 includes a copy operation 700cthat periodically writes on-chip frame buffer 702 to memory portion 113 of main memory 112 for access by display/video interface unit 164. This copy operation 700ccan also be used to copy embedded frame buffer 702 contents to textures in the main memory 112 for dynamic texture synthesis effects. Anti-aliasing and other filtering can be performed during the copy-out operation. The frame buffer output of graphics pipeline 180 (which is ultimately stored in main memory 112) is read each frame by display/video interface unit 164. Display controller/video interface 164 provides digital RGB pixel values for display on display 56.
[0081] Example Input/Output Subsystem
[0082] FIG. 6 shows an example input/output subsystem. In this example, the input/output subsystem includes a serial interface 1000, an external interface 1100, a disk interface 1200 and an audio interface 1300. Serial interface 1000 is used to communicate with controllers 52 or other devices that can be coupled to one of four serial ports of system 50. External interface 1100 is used to communicate with a variety of devices such as PROM RTC 134, modem 136, flash memory 140, memory card 144, etc. via various buses 132, 142. Disk interface 1200 is used to communicate with mass storage access device 106 via a parallel bus 130. Audio interface 1300 is used to stream the audio output data from an audio buffer in main memory 112 to audio codec 122.
[0083] In the example embodiment, the external interface 1100 and disk interface 1200 have direct access to memory controller 152 via a bus 900. Details of the operation of memory controller 152 may be found in provisional Application No. 60/226,894, filed Aug. 23, 2000 and its corresponding utility application Ser. No. 09/726,220, filed Nov. 28, 2000, both entitled “Graphics Processing System with Enhanced Memory Controller” and provisional Application No. 60/226,886, filed Aug. 23, 2000 and its corresponding utility application Ser. No. 09/722,665, filed Nov. 28, 2000, both entitled “Method and Apparatus for Accessing Shared Resources.” The contents of each of these applications are incorporated herein by reference. In addition, each one of interfaces 1000, 1100, 1200 and 1300 as well as audio digital signal processor 156 share a common bus 902 used to communicate between these components and a bus interface 904. The bus interface 904, in turn, can be used to arbitrate access to graphics unit 180. In the example embodiment, there is also a connection 906 between DSP 156 and audio interface 1300.
[0084] Briefly, disk interface 1200 provides an interface to mass storage access device 106 providing a direct memory access (DMA) capability with interrupt. Serial interface 1000 provides a serial interface to hand controllers 52 or other serial devices using automatic controller polling and bulk data mode. The serial interface also includes a light gun interface. The external interface 1100 provides multiple SBI buses as well as a memory-mapped area for boot PROM 134. Audio interface 1300 provides an output to audio codec 122 as well as an input for streaming audio from mass storage access device 106.
[0085] Example Serial Interface
[0086] FIGS. 7A and 7B show an example serial interface 1000. In this particular example, serial interface 1000 is a single bit serial interface that runs at 250 kHz. This single bit serial interface is similar to the controller interface used in the prior art Nintendo 64® product manufactured by Nintendo, but there are some differences. Example serial interface 1000 provides the following features in the example embodiment:
[0087] four separate 250 kHz serial interfaces for four controllers 52,
[0088] each interface can be accessed in parallel,
[0089] in controller mode, the last state of the controller 52 is in a double-buffered processor input/output register so that main processor 110 can simply read the register to determine the controller state,
[0090] the controller state is automatically polled by hardware with configurable polling periods,
[0091] bulk mode (changeable data size),
[0092] two light gun signals are used to control two separate horizontal/vertical counters to support both flash and shutter light guns,
[0093] an LCD shutter is supported through automatic polling and serial control commands, and
[0094] the serial interface 1000 can automatically detect the presence of hand controllers 52.
[0095] FIG. 7A shows the external interface of serial interface 1000. In this example, there are four separate controller ports 1002 on system 50. Each port 1002 has a pair of input and output pins (shown by the “x” mark blocks in FIG. 7A). The input pin connects directly to an external game controller 52 in the example embodiment. The output pin in the example embodiment connects to an external open-drain driver (see FIG. 9) which in turn connects directly to the external game controller 52. In the example embodiment, two of the ports 1002 have horizontal/vertical latch signals that can be used to latch horizontal/vertical counters within the video interface 164. These signals combined with the functionality of serial interface 1000 provide support for flash and shutter type light guns. The vertical latch and control registers used for this functionality are located in the video interface 164 in the example embodiment. FIG. 7A shows each of the four serial ports 1002 including an SIDI (bi-directional) line and an SIDO (uni-directional) controller output-to-serial interface line. The following shows example descriptions of these two signals:
| Name | Dir | Type | Description |
|---|---|---|---|
| SIDI[3:0] | I | LVCMOS | Serial Interface Data Input: SIDI[3:0] are input signals, each |
| bit is a separate half-duplex, 250kbit/s input serial channel. | |||
| The serial protocol is an asynchronous interface and is self | |||
| timed, using a pulse width modulated signaling scheme. | |||
| SID0[3:0] | O | LVCMOS | Serial Interface Data Output: SIDO[3:0] are output signals, |
| each bit is a separate half-duplex, 250kbit/s output serial | |||
| channel. The serial protocol is an asynchronous interface and, | |||
| is self timed, using a pulse width modulated signaling scheme. | |||
[0096] FIG. 7B is a more detailed block diagram of serial interface 1000. As shown in this Figure, serial interface 1000 includes a main processor interface 1010, serial interface communication circuitry and registers 1012, a small (128 byte) communication RAM 1014, and an input/output buffer arrangement 1016 for each of the four serial ports 1002.
[0097] FIG. 7C shows an example set of registers (register map) used to control serial interface 1000 in the example embodiment. The base address for these serial interface registers in the example embodiment is 0x0C006400. The following describes each of these various example registers in the example embodiment:
| SIC0OUTBUF SI Channel 0 Output Buffer |
[0098] This register is double buffered, so main processor writes to the SIC0OUTBUF will not interfere with the serial interface output transfer. Internally, a second buffer is used to hold the output data to be transferred across the serial interface. To check if SIC0OUTBUF has been transferred to the second buffer, main processor 110 polls the SISR[WRST0] register. When SIC0OUTBUF is transferred, SISR[WRST0] is cleared.
| SIC0INBUF SI Channel 0 Input Buffer High |
[0099] SIC0INBUFH and SIC0INBUFL are double buffered to prevent inconsistent data reads due to the main processor 110 conflicting with incoming serial interface data. To insure data read from SIC0INBUFH and SIC0INFUBL are consistent, a locking mechanism prevents the double buffer from copying new data to these registers. Once SIC0INBUFH is read, both SIC0INBUFH and SIC0INBUFL are ‘locked’ until SIC0INBUFL is read. While the buffers are ‘locked’, new data is not copied into the buffers. When SIC0INBUFL is read, the buffers become unlocked again.
| SIC0INBUF SI Channel 0 Input Buffer Low |
[0100] When programming the SICOMCSR after a SICOM transfer has already started (e.g., SICOMCSR[TSTART] is set), the example software reads the current value first, then and/or in the proper data and then writes the new data back. The software should not modify any of the transfer parameters (OUTLNGTH, INLNGTH, CHANNEL) until the current transfer is complete. This is done to prevent a SICOM transfer already in progress from being disturbed. When writing the data back, the software should not set the TSTART bit again unless the current transfer is complete and another transfer is required.
| SISI SI Status Register |
[0101] FIG. 8 is an even more detailed overall view of serial interface 1000. Controllers 52aand 52b(and 52cand 52d,if present) are connected to game console 54 via connector ports 1002. Modem 1404 modulates and demodulates data transferred between the controllers and the console. In the example system, communication between the console and the controllers uses duty-cycle (pulse-width) modulation and the data is communicated over one line. The communication is half-duplex. The byte transfer order is “big-endian” in which within a given multi-byte numeric representation, the most significant byte has the lowest address (i.e., the data is transferred “big-end” first). Controller input/output buffer 1016 is used for normal data transfers involving controllers 52a-52d.As shown in FIG. 8 and as will be explained in greater detail below, input/output buffer 1016 is arranged as a double buffer. Communication RAM 1014 is provided for use in variable-size data transfers to and from controllers 52a-52d.In the example system, the maximum data size of these variable-size data transfers is 32 words. Of course, the present invention is not limited in this respect. Channel selector circuit 1408 controls selectors 1412a-1412dto selectively connect modem 1404 to either communication RAM 1014 or input/output buffer 1016. An HV counter latch circuit 1406 latches the screen position of a flash signal when a trigger input is received from a light gun unit. In the example system shown in FIG. 8, triggers inputs to the HV counter latch circuit 1406 are provided for connectors 1 and 2 only. It will be apparent that trigger inputs may be provided for the other connectors if desired. HV counter latch circuit 1406 may also be used with light pens connected to connectors 1 and/or 2.
[0102] FIG. 9 shows additional details of the connections between controllers 52a-52dand serial interface 1000. The outputs of modem 1404 are supplied to controllers 52a-52dthrough open-drain driver buffers 1430 and the inputs from controllers 52a-52dare supplied to modem 1404 through Schmitt buffers 1432. Similarly, the outputs of controllers 52a-52dare supplied to serial interface 1000 through driver buffers 1434. The outputs to controllers 52a-52dfrom serial interface 1000 are supplied to controller integrated circuits (ICs) 1436.
[0103] FIG. 10 shows details of one of controllers 52. Controller 52 is connected to serial interface 1000 via a cable (not shown) about 2 meters in length in the example system. In other implementations, the communication between the controllers and the console may be over a wireless communication path such as infrared or radio frequency. Controller 52 contains an interface circuit 1504 arranged between the controller components and serial interface 1000. A button data input circuit 1502 accepts inputs from buttons disposed on an external surface of controller 52. “Buttons” as used herein refers to any device that is manipulable by a user to cause a game or other application to start, characters to move, etc. and includes, for example, buttons, switches, joysticks, and the like. The length of the controller button and status data that is provided to serial interface 1000 is 64 bits. Vibration circuit 1506 is responsive to signals from main unit 54 via serial interface 1000 for selectively vibrating the housing of controller 52 to provide sensations to the a game player. Controller 52 also includes a 64 kbit EEPROM 1510 with a unique identifier number that is usable, for example, to store game back-up data, high game scores, etc. Controller 52 also includes a motor control system 1508 for controlling an external motor and two output ports (not shown) connectable to external components such as a motor.
[0104] Polling Via Serial Interface 1000
[0105] The input/output data size is fixed in the standard command/response packet in the example implementation. This packet is used primarily for reading data of the controllers. This data includes data indicative of which buttons are being pressed, is there a controller plugged in, the value of the analog joysticks, etc. This data is used as player input for a game (e.g., move character left/right, look up/down, fire gun, etc.). Because the polling of the controllers is performed by serial interface 1000, the workload of main processor 110 is reduced. Thus, for example, the last state of the controller 52 is in the double-buffered processor input/output register 1016 so that main processor 110 can simply read the register to determine the controller state.
[0106] An output command packet includes a 1-byte command and 2 bytes of data. With reference to the serial interface register map set forth above, SIC0OUTBUF for sending a command packet to a controller connected to connector port 1002(0), for example, includes a command byte register CMD that is an opcode for the command sent to the controller during each command/response packet. OUTPUT0 and OUTPUT1 registers are for first and second data bytes of the command packet. An input response packet includes 8 bytes of data, of which 62 bits are button data and 2 bits are controller status bits. Again with reference to the serial interface register map, SIC0INBUF (SI Channel 0 Input Buffer High) for receiving the response packet from the controller includes ERRSTAT, ERRLATCH, INPUT0, INPUT1, INPUT2 and INPUT3 registers. The ERRSTATUS bit represents the current error status for the last polling transfer on channel 0. This register is updated after each polling transfer on this channel. The ERRLATCH bit is an error status summary of the error bits for channel 0. If an error has occurred on a past transfer on channel 0 (polling or a transfer from communication RAM 1014), this bit will be set. To determine the exact error, the SISR register (see register map) may be read. The ERRLATCH bit is actually an “or” of the latched error status bits for channel 0 in the SISR. The bit is cleared by clearing the appropriate error status bits latched in the SISR. The no response error indicates that a controller is not present on the channel. INPUT0, INPUT1, INPUT2 and INPUT3 are first through fourth data bytes of the response packet sent from controller 52 to serial interface 1000 for channel 0. In the example, implementation, the most significant two bits of INPUT0 are assumed to be “0”, so they are not included in INPUT0. The fifth through eighth data bytes of the response packet are in the register SIC0INBUF (SI Channel 0 Input Buffer Low).
[0107] The characteristics of the polling of the controllers are determined in accordance with registers in SIPOLL (SI Poll Register). With reference to the register map, SIPOLL includes an X lines register and a Y times register. The X lines register determines the number of horizontal video lines between polling (“the polling interval”). The polling interval begins at the beginning of vertical blanking as shown in FIG. 12.0x07 is the minimum setting for the X lines register as determined by the time required to complete a single polling of the controller in the example system. The maximum setting depends on the current video mode (the number of lines between vertical sync signals) and the Y times register. Of course, the invention is not limited to any particular maximum or minimum settings. The Y times register determines the number of times the controllers are polled in a single frame. This is also shown in FIG. 12.
[0108] Thus, in the controller polling process, main processor 110 writes a command to one or more of the output buffers and sets the X line and Y times registers. When main processor 110 sets one or more enable registers EN0, EN1, EN2 and EN3 of the SI Poll Register to “1”, continuous polling of the corresponding controllers is started. The polling of the enabled channels is started at the same time and serial interface 1000 starts to poll at the beginning of vertical blanking and polling is repeated Y times per one frame. As noted above, the interval between pollings is determined in accordance with the setting of the X line register and the relationship between X line interval and Y times per frame is illustrated in FIG. 12. When main processor 110 sets the X line register, the Y times register and the enable register(s), controller access is started at the next vertical blanking. In the example implementation, the default setting for the Y times register is “0”. Therefore, main processor 110 must set this register to use the controllers. To stop polling of a particular controller, its enable bit is set to 0; polling is stopped immediately after the current transaction.
[0109] As mentioned above, input/output buffer 1016 is actually a double buffer. The output buffer is comprised of 3 bytes for each of the four channels as described above. With reference to FIG. 8, the output data is copied from output buffer 1 to output buffer 0 of the double buffer when main processor 110 finishes writing to output buffer 1. A WR register of SISR (SI Status Register) controls and indicates whether the SICnOUTBUFs have been copied to the double buffered output buffers. The bit is set to “1” when the buffer is not yet copied and is cleared to “0” when copying is completed. Thus, if “0” is returned when main processor 110 reads WR, the copy operation is complete. If “1” is returned, the copy operation is not complete. Thus, this register must be “0” before main processor 110 writes to buffer 1. While data is transmitted from buffer 0 to the controller, copy from buffer 1 to buffer 0 is locked.
[0110] The input buffer is 8 bytes for each of the four channels and input data is copied from input buffer 0 to input buffer 1 after the controller data is received. Main processor 110 reads input buffer 1 directly per 32 bits. If new data were to be written to the low 32 bits while main processor 110 is reading the high 32 bits, the data may be incorrect. Accordingly, when main processor 110 is reading the upper 32 bits, input buffer 1 is locked. When main processor 110 starts to read the lower 32 bits, buffer 1 is unlocked.
[0111] Ordinarily, output data is copied from buffer 1 to buffer 0 immediately after it is written to output buffer 1 by main processor 110. However, the copying may also be timed to start with vertical blanking in order to control the timing of commands to 3D LCD shutter glasses connected to display controller 164. To enable such timing, VBCPY may be set to “1” so that copies to buffer 0 occur only upon vertical blanking. The default value for the VBCPY bits is “0”.
[0112] The size of the data involved in the polling is fixed. However, there are occasions on which it is desirable to transfer larger amounts of data between main console 54 and controllers 52 (e.g., writing game data to a nonvolatile memory built-in or attached to controller 52). Example serial interface 1000 provides the capability of transferring larger amounts of data in accordance with a process that is explained with reference to FIG. 11. SICOMCSR (SI Communication Control Status Register) includes a register OUTLNGTH for setting the communication channel output length (in bytes); INLNGTH for setting the communication channel input length (in bytes); and CHANNEL for determining which serial interface channel will be used. The minimum transfer that may be designated by OUTLNGTH and INLNGTH is 1 byte. A value of 0×00 will transfer 128 bytes. To transfer data, command and output data is set to communication RAM 1014 and main processor 110 sets the OUTLNGTH, INLNGTH and CHANNEL registers. The setting (“1”) of the TSTART bit register causes execution of the current communication transfer. The transfer begins immediately after the current transaction on the designated channel is completed. When read, the TSTART bit represents the current transfer status. Once a communication transfer is executed, polling resumes at the next vertical blanking interval if the channels EN bit is set.
[0113] When main processor 110 sets the TSTART bit to “1”, the transfer mode of the channel designated in the CHANNEL register is changed to Communication RAM mode by selector circuit 1408 (see FIG. 8) which controls the appropriate selector circuit to connect that channel to communication RAM 1014. In the example of FIG. 11, channel 1 is the designated channel. Output data is then transmitted from communication RAM 1014 and is output to controller 52 via modem 1404. Controller 52 may also transmit input data to channel 1 and this data is communicated to communication RAM 1014 via selector 1412a.The input data is pushed from communication RAM 1014 to main processor 110. Modem 1404 automatically clears the TSTART bit when the transfer is complete.
[0114] During Communication RAM transfer mode on channel 1, the remaining channels (i.e., channels 2, 3 and 4) continue to transfer data using input/output buffer 1016. During communication RAM transfers, main processor 110 generates an Addr CRC and transmits the CRC to the controller. The controller processes the Addr CRC to check that the data has been correctly received. In the case of a communication RAM transfer, the controller returns Data CRC. The main processor 110 generates a data CRC and compares this with the controller returned Data CRC.
[0115] FIG. 13 illustrates an example light gun connectable to connector port 1002(0) or 1002(1) of main console 54. Various types of light guns may be used and two of these types are discussed below. A first type detects a target point within one frame and generally requires that the screen and/or the target point be a bright color. A second type requires two frames to detect the target point because main processor 110 flashes the screen after detection of the trigger button and starts to detect the target point at the next frame. This second type of gun typically does not require the screen to be as bright as is needed for guns of the first type. HV counter latch circuit 1406 is usable in connection with either type of light gun. The light gun includes a gun trigger 1702. If gun trigger 1702 is pulled, a trigger signal input is transmitted for one frame. A flash signal input passing through lens 1720 is detected by a photodetector 1722, amplified by an amplifier 1724 and supplied to logic circuit 1706 as the flash signal. Interface circuit 1704 controls whether the flash signal is passed via logic gate 1706 by controlling the signal level on the flash signal control line. If the flash signal control line is high, the flash signal is passed to HV counter latch circuit as a counter latch signal. Interface circuit 1704 controls whether the trigger signal is passed. A trigger control switch 1708 is selectively connected to power source 1710 or the trigger signal line.
[0116] In the first type of light gun, as soon as trigger 1702 is pulled, the gun starts to detect the flash signal and, if the flash signal is detected, the counter latch signal is transmitted. In the second type of light gun, when trigger 1702 is pulled, main processor 110 starts to flash the screen at the next frame. The flash signal is detected during this frame and the counter latch signal is transmitted. With a light pen, the flash signal is detected per frame and the counter latch signal is transmitted per frame.
[0117] A Gun Trigger Mode register determines the gun trigger mode and enables the counter latch register for each of channels 1 and 2. An “always” mode is set so that the gun detects the flash signal per frame. This mode may be set for the first type of light gun and the light pen. A “1 frame” and “2 frame” mode is set so that the gun detects a flash signal for 1 or 2 frames. These modes may be set for the second type of light gun.
[0118] The HV latch counter circuit receives a counter latch signal transmitted from the light gun. In this case, the position of the flash signal is latched to the HV counter latch register. The register is shared by the 2 channels.
| HV counter latch | 32 bits (R) | |
| Horizontal count | [10 . . . 0] bits | |
| Vertical count | [20 . . . 12] bits | |
| Field | bit 24 | |
| Counter latch signal | bit 31 | |
[0119] FIG. 14A depicts the output timing of the counter latch signal for the light gun of the first type. As noted above, the screen should preferably be bright for this type of light gun because the gun needs to detect a flash signal at any time. For this gun type, the trigger signal controller is always connected to the trigger side. When the trigger is pulled, flash signal detection is started. If the flash signal is detected within one frame, the counter latch signal is transmitted and the counter latch register gets the position of the flash signal. The action that results from pulling the trigger is drawn at the next frame.
[0120] FIG. 14B depicts the output timing of the counter latch signal for the light gun of the second type. For this gun type, the trigger signal controller is always connected to the power side. When the trigger is pulled, the screen is a bright color at the next frame and flash signal detection is started. When the flash signal is detected, the counter latch signal is transmitted and the counter latch register gets the position of the flash signal. The action that results from pulling the trigger is drawn at the next frame.
[0121] FIG. 14C depicts the output timing of the counter latch signal for the light pen. The screen is preferably bright for this type of light gun because the gun needs to detect a flash signal at any time. The trigger signal controller is always connected to the power side and the flash signal control line is always set to 1. The flash signal is detected per frame. The counter latch signal is transmitted and the counter latch register gets the position of the flash signal. The action that results from touching the pen on the screen is drawn at the next frame.
[0122] Example Signal Form
[0123] The signal form of the data is made up of a separation signal, a bit signal, an end signal and a continue signal.
[0124] FIG. 15(A) depicts a separation signal that is used to distinguish the end of transmission. The separation signal is transmitted before the transmitter (main unit 54) transmits a command and the receiver (controller 52) distinguishes the start of the command. Thus, it is important that the receiver distinguishes this signal.
[0125] FIGS. 15(B) and 15(C) depict bit signals that are transmitted using the DATA line. The bit signals are duty-cycle (pulse-width) modulated as shown in FIGS. 15(B) and 15(C).
[0126] FIG. 15(D) depicts an end signal for indicating the end of the bit signal transmission. The bit signal ends by falling from high level to low level so the data line is still at low level. However, to release the data line, the transmitter must return the data line to high level. The end signal is used for this purpose.
[0127] FIG. 15(E) depicts a continue signal used to change the direction of transmission. The transmitter returns the data line to high level and next the transmitter starts to transmits the Bit signal after a few intervals. The interval between the End signal and the Bit signal is the Continue signal. This signal is controlled by the next transmitter and is used when the receiver replies to a command of the transmitter.
[0128] Example Communication Protocol
[0129] FIGS. 16A and 16B depict frame units in which communication over the communication path occurs. The transmitter transmits the Command frame shown in FIG. 16A and the receiver responds to the transmitter with a Response frame shown in FIG. 16B. As shown in FIG. 16A, the Command frame includes a separation signal, data and an end signal. As shown in FIG. 16B, the Response frame includes a continue signal, data and an end signal. The data is 8-bit aligned.
[0130] Example Channel Lines
[0131] FIG. 17 depicts the lines for the channels of serial interface 1000. A GND line is connected to a ground terminal and a PWR line connected to a VDD terminal is used to supply power from main console 54 to controller 52. The DATA line is used to transfer data between main console 54 and controller 52. DATA line is bi-directional and half-duplex. DATA line includes a wired-OR circuit and the transmitter pulls it to High level. The receiver may also pull it to High level. When the transmitter transmits signals, it pulls the DATA line to low level for certain times. The mechanical GND line and the mechanical PWR line are used when power is supplied to an external device coupled to the controller such as a motor. Finally, the counter latch line is used to transfer the flash signal detected from a light gun, a write pen, etc.
[0132] Other Example Compatible Implementations
[0133] 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.
[0134] 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.
[0135] 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.
[0136] FIG. 18A illustrates an example overall emulation process using a host platform 1201, an emulator component 1303, and a game software executable binary image provided on a storage medium 62. Host 1201 may be a general or special purpose digital computing device such as, for example, a personal computer, a video game console, or any other platform with sufficient computing power. Emulator 1303 may be software and/or hardware that runs on host platform 1201, and provides a real-time conversion of commands, data and other information from storage medium 62 into a form that can be processed by host 1201. For example, emulator 1303 fetches “source” binary-image program. instructions intended for execution by system 50 from storage medium 62 and converts these program instructions to a target format that can be executed or otherwise processed by host 1201.
[0137] 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).
[0138] 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.
[0139] FIG. 18B illustrates an emulation host system 1201 suitable for use with emulator 1303. System 1201 includes a processing unit 1203 and a system memory 1205. A system bus 1207 couples various system components including system memory 1205 to processing unit 1203. System bus 1207 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. System memory 1207 includes read only memory (ROM) 1252 and random access memory (RAM) 1254. A basic input/output system (BIOS) 1256, containing the basic routines that help to transfer information between elements within personal computer system 1201, such as during start-up, is stored in the ROM 1252. System 1201 further includes various drives and associated computer-readable media. A hard disk drive 1209 reads from and writes to a (typically fixed) magnetic hard disk 1211. An additional (possible optional) magnetic disk drive 1213 reads from and writes to a removable “floppy” or other magnetic disk 1215. An optical disk drive 1217 reads from and, in some configurations, writes to a removable optical disk 1219 such as a CD ROM or other optical media. Hard disk drive 1209 and optical disk drive 1217 are connected to system bus 1207 by a hard disk drive interface 1221 and an optical drive interface 1225, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules, game programs and other data for personal computer system 1201. In other configurations, other types of computer-readable media that can store data that is accessible by a computer (e.g., magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), read only memories (ROMs) and the like) may also be used.
[0140] 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.
[0141] 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.
[0142] 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.
[0143] While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims.
Claims
We claim:
1. A video game system, comprising:
a game program executing system executing a game program;
one or more controllers supplying user inputs to the game program executing system;
an interface between the controllers and the game program executing system, the interface being programmable to periodically poll the controllers without involvement of the game program executing system, wherein the interface comprises:
a double buffer for storing data transferred between the game program executing system and the controllers; and
a status register comprising one or more bits which are indicative of a status of a copy operation for copying data from one buffer to another of the double buffer.
2. The video game system according to claim 1, wherein the interface is programmable to poll the controllers a predetermined number of times between each vertical blanking interval.
3. The video game system according to claim 1, wherein the interface is programmable to poll the controllers based on a number of video lines.
4. The video game system according to claim 1, wherein the interface polls a status of the controllers.
5. The video game system according to claim 4, wherein the status of the controllers includes data indicative of player inputs.
6. The video game system according to claim 5, wherein the player inputs comprise button presses.
7. The video game system according to claim 5, wherein the player inputs comprise positions of a user manipulable joystick.
8. The video game system according to claim 4, wherein the status of the controllers includes error data.
9. The video game system according to claim 8, wherein the error data is indicative of no response from a controller in response to a transfer of data thereto.
10. The video game system according to claim 8, wherein the error data is indicative of a data collision.
11. The video game system according to claim 8, wherein the error data is indicative of the game program executing system receiving more than a predetermined amount of data from the controller.
12. The video game system according to claim 8, wherein the error data is indicative of the game program executing system receiving less than a predetermined amount of data from the controller.
13. The video game system according to claim 1, the interface further comprising:
selectors for selectively connecting the controllers to either the double buffer or the communication RAM.
15. The video game system according to claim 1, the controller including a vibration circuit for vibrating a housing of the controller.
16. The video game system according to claim 1, the controller including a read/write memory.
17. The video game system according to claim 1, further comprising:
a communication RAM for storing data transferred between the game program executing system and the controllers.
18. The video game system according to claim 17, further comprising:
a switching device for selectively connecting either the double buffer or the communication RAM to the controllers.
19. A video game system, comprising:
a game program executing system executing a game program;
a controller supplying user inputs to the game program executing system; and
an interface interfacing between the game program executing system and the controller, the interface including communication circuitry operable in a first mode in which data of a fixed size is communicated between the game program executing system and the controller and in a second mode in which data of variable size is communicated between the game program executing system and the controller, wherein the interface further comprises:
a communication memory for storing the variable size data;
a double buffer for storing the fixed size data; and
a switching device for selectively connecting either the double buffer or the communication memory to the controller.
20. The video game system according to claim 19, the interface further comprising:
selectors for selectively connecting the controllers to either the double buffer or the communication RAM.
22. The video game system according to claim 19, further comprising:
a status register comprising one or more bits indicative of a status of a copy operation for copying data from one buffer to another of the double buffer.
23. A video game system, comprising:
a game program executing system having connectors connectable to one or more game controllers; and
an interface between the connectors and the game program executing system, the interface comprising a double buffered input register and a double buffered output register corresponding to each connector, each double buffered output register comprising first and second output registers for storing data from the game program executing system for output to a controller connected thereto and each double buffered input register comprising first and second input registers for storing data from a controller connected thereto for input to the game program executing system.
24. The video game system according to claim 23, wherein copying of data from the first output register of one or more of the double buffered output registers to the second output register thereof is timed to start with vertical blanking of a display connected to the video game system.
25. The video game system according to claim 23, wherein the second output registers are locked while data stored therein is output to the controllers connected thereto.
26. The video game system according to claim 23, wherein data written to the first output register from the game program executing system is copied to the second output register.
27. The video game system according to claim 23, wherein data output to each controller comprises a command packet and one or more data packets.
28. The video game system according to claim 23, wherein data input from each controller comprises input data and status data.
29. The video game system according to claim 23, wherein the interface further comprises status registers, each status register indicating a status of a copy operation for copying data from the first output register to the second output register of a corresponding double buffered output register.
30. A video game system, comprising:
a game program executing system supplied with user inputs from one or more game controllers; and
an interface between the controllers and the game program executing system, the interface comprising first and second different storage devices for storing data transferred between the game program executing system and the controllers, and selector circuitry for selectively connecting the controllers to either of the first or second storage devices.
31. The video game system according to claim 30, wherein one of the first and second storage devices is adapted for storing variable size data and the other of the first and second storage devices is adapted for storing fixed size data.
32. The video game system according to claim 30, wherein the first storage device comprises double buffered input and output registers.
33. The video game system according to claim 32, wherein output data from the game program executing system is copied from a first register of the output buffer to a second buffer of the output buffer after the output data is written to the first buffer.
34. The video game system according to claim 32, wherein input data from the controllers is copied from a first buffer of the input buffer to a second buffer of the input buffer after the input data is written to the first buffer.
35. The video game system according to claim 30, further comprising:
a modem connected to the selector circuitry.
36. A method of supplying data to a game program executing system of a video game system from controllers connected thereto, the method comprising:
receiving data from the controllers;
supplying the received data to selector circuitry;
supplying the received data from the selector circuitry to a first storage device accessible by the game program executing system if the selector circuitry is in a first state; and
supplying the received data from the selector circuitry to a different, second storage device accessible by the game program executing system if the selector circuitry is in a second state.
37. The method according to claim 36, wherein fixed-size data received from the controllers is supplied to the first storage device and variable-size data received from the controllers is supplied to the second storage device.
38. A method of supplying data from game program executing system of a video game system to controllers connected thereto, the method comprising:
selectively storing data from the game program executing system in first and second different storage devices connected to selector circuitry;
supplying stored data from the first storage device to the controllers if the selector circuitry is in a first state; and
supplying stored data from the second storage device to the controllers if the selector circuitry is in a second state.
39. The method according to claim 38, wherein fixed-size data from the game program executing system is stored in the first storage device and variable-size data from the game program executing system is stored in the second storage device.
40. A video game system, comprising:
a game program executing system;
a connector for connecting to a peripheral device; and
an interface between the connector and the game program executing system, the interface comprising a double buffered input register and a double buffered output register, wherein
output data from the game program executing system is copied from a first output register to a second output register of the double buffered output register after the output data is written to the first output register, and copying from the first output register to the second output register is selectively lockable, and
input data from the peripheral device is copied from a first input register to a second input register of the double buffered input register after the input data is written to the first input register, and copying from the first input register to the second input register is selectively lockable.
41. The video game system according to claim 40, wherein the interface further comprises a status register comprising one or more bits indicative of a status of a copy operation for copying data from the first output register to the second output register.
42. A video game system, comprising:
a game program executing system;
a connector for connecting to a peripheral device; and
an interface between the game program executing system and the connector, the interface comprising a first storage device for storing data of a first type which is transmitted to or received from a peripheral device connected to the connector; a different, second storage device for storing data of a second type which is transmitted to or received from a peripheral device connected to the connector; and a switching device for selectively connecting the peripheral device to either the first storage device or the second storage device.
43. The video game system according to claim 42, wherein the data of the first type is variable-size data and the data of the second type is fixed-size data.
Patent Citations (450)
| 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 | Grossman | 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 |
| US5586234(A) | 1996-12-01 | Sakuraba et al. | Applicant |
| US5593350(A) | 1997-01-01 | Bouton et al. | Examiner |
| 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. | Examiner |
| US5638535(A) | 1997-06-01 | Rosenthal et al. | Examiner |
| 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 |
| US5852451(A) | 1998-12-01 | Cox 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 | MacInnis 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 | Alcorn 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. | Examiner |
| 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 | Examiner |
| 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 | Examiner |
| 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. | Examiner |
| 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 |
| 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 |
| US6264558(B1) | 2001-07-01 | Nishiumi et al. | Examiner |
| 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 | Powell, III | Applicant |
| US6329997(B1) | 2001-12-01 | We et al. | Applicant |
| US6331856(B1) | 2001-12-01 | Van Hook et al. | Applicant |
| 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. | Applicant |
| 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 |
| 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 | |
| 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 | |
| JP1125971 | 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 | |
| JP200-182077 | 2000-06-01 | Applicant | |
| JP2000-156875 | 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 | |
| WO94/10641 | 1994-11-01 | Applicant |
Non-Patent Literature (159)
- 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
- Whitepapers: “Texture Addressing,” Sim Dietrich, Jan. 6, 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
- 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. application Ser. No. 09/337,293, filed Jun. 21, 1999, Multi-Formate Vertex Data Processing Apparatus and Method [issued as U.S. Patent 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
- ZDNet Reviews, from PC Magazine, “Other Enhancements,” Jan. 15, 1999, wysiwyg://16/http://www4.zdnet.com . . . ies/reviews/0,4161,2188286,00.html.Applicant
- 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
- 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
- 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
- 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
- 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 Algoritms,” 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
- Raskar, Ramesh et al., “Image Precision Silhouette Edges,” Symposium on Interactive 3D Graphics1999, 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
- 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 Interfrace for Sketching 3D Scenes,” Computer 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
- 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
- The RenderMan Interface Version 3.1, (Sep. 1989).Applicant
- “Renderman Artist Tools, PhotoRealistic RenderMan Tutorial,” Pixar (Jan. 1996).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
- “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 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, Annual 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
- Photograph of Sony PlayStation II System.Applicant
- Photograph of Sega Dreamcast System.Applicant
- Photograph of Nintendo 64 System.Applicant
- Whitepaper: 3D Graphics Demystified, Nov. 11, 1999, www.nvidia.com.Applicant
- Whitepaper: “Z Buffering, Interpolation and More W-Buffering”, Doug Rogers, Jan. 31, 2000, www.nvidia.com.Applicant
- Whitepaper: Using GL_NV_vertex_array and GL_NV_fence, posted Aug. 1, 2000, www.nvidia.com.Applicant
- Whitepaper: Anisotropic Texture Filtering in OpenGL, posted Jul. 17, 2000, www.nvidia.com.Applicant
- Whitepaper: Mapping Texels to Pixels in D3D, posted Apr. 5, 2000, www.nvidia.com.Applicant
- Whitepaper: Guard Band Clipping, posted Jan. 31, 2000, www.nvidia.com.Applicant
- Whitepaper: Cube Environment Mapping, post Jan. 14, 2000, www.nvidia.com.Applicant
- Whitepaper: Color Key in D3D, posted Jan. 11, 2000, www.nvidia.com.Applicant
- Whitepaper: Vertex Blending Under DX7 for the GeForce 256, Jan. 5, 2000, www.nvidia.com.Applicant
- Whitepaper: Optimizing Direct3D for the GeForce 256, Jan. 3, 2000, www.nvidia.com.Applicant
- Whitepaper: Dot Product Texture Blending, Dec. 3, 1999, www.nvidia.com.Applicant
- Whitepaper: Technical Brief: AGP 4X with Fast Writes, Nov. 10, 1999, www.nvidia.com.Applicant
- Technical Brief: Transform and Lightning, Nov. 10, 1999, www.nvidia.comApplicant
- 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 Subsidaries”, Mar. 9, 1999.Applicant
- AM News: Japanese Developers Not All Sold on PS2, Next Generation, Mar. 16, 1999.Applicant
- Sony To Turn PlayStation Maker Into Wholly Owned Unit-Nikkei, Dow Jones News Service, Mar. 8, 1999.Applicant
- Yumiko Ono, Sony Antes Up Its Chips In Bet On New Game System, Dow Jones News Service, Mar. 4, 1999.Applicant
- MacWeek.Com Gets Inside Story on Connectix VGS for Windows; Controversial Emulator of Sony PlayStation Games Cureently Available for Macs Only, Business Wire, Mar. 12, 1999.Applicant
- “DexDrive Bridges Gap”, The Tampa Tribune, Mar. 12, 1999.Applicant
- A Microprocessor With a 128b CPU, 10 Floating-Point MAC's, 4 Floating-Point Dividers, and an MPEG2 Decoder, 1999 IEEE International Solid-State Circuits Conference, Feb. 16, 1999.Applicant
- Dreamcast Instruction Manual, Sega Enterprises, Ltd., ©1998.Applicant
- “Sega To Launch Video Camera for Dreamcast”, Reuters Business News, Feb. 16, 2000.Applicant
- David Pescovitz, “Dream On”, Wired, Aug. 1999.Applicant
- Randy Nelson, “Dreamcast 101: Everything You Ever Wanted To Know About Sega's Powerful New Console”, Official Sega Dreamcast Magazine, Jun. 1999.Applicant
- 2D/3D Graphics Card User Manual, Guillemot ©1999.Applicant
- Nintendo 64 Instruction Booklet, Nintendo of America, 1998.Applicant
- Steven Levy, “Here Comes PlayStation II”, Newsweek, Mar. 6, 2000.Applicant
- David Sheff, “Sony Smackage: Test Driving The PlayStation II”, Wired, Nov. 1999.Applicant
- Introducing The Next Generation PlayStation, Sony Computer Entertainment Inc., ©1999.Applicant
- Leadtek GTS, Aug. 3, 2000, www.hexus.net.Applicant
- Voodoo 5 5500 Review, Jul. 26, 2000, www.hexus.net.Applicant
- ATI Radeon 64 Meg DDR OEM, Aug., 19, 2000, www.hexus.net.Applicant
- Microsoft Xbox—The Future of Gaming, Microsoft Xbox Performance Sheet, www.xbox.com.Applicant
- Robert L. Cook, “Shade Trees”, Computer Graphics, vol. 18, No. 3, Jul. 1984.Applicant
- Wang et al., “Second-Depth Shadow Mapping”, Department of Computer Science, Univ N.C, Chapel Hill, N.C. pp. 1-7.Applicant
- Peercy et al., “Efficient Bump Mapping Hardware”, Computer Graphics Proceedings, Annual Conference Series, 1997.Applicant
- Gustavo Oliveira, “Refractive Texture Mappig, Part One”, www.gamasutra.com, Nov., 10, 2000.Applicant
- John Schlag, Fast Embossing Effects on Raster Image Data, Graphics Gems IV, Edited by Paul S. Heckbert, Computer Science Department, Carnegie Mellon University, Academic Press, Inc., 1994,pp. 433-437.Applicant
- James F. Blinn, “Simulationof Wrinkled Surfaces,” Caltech/JPL, pp. 286-292, SIGGRAPH 78 (1978).Applicant
- Tomas Möller and Eric Haines “Real-Time Rendering”, AK Peters, Ltd., ® 1999, pp. 127-142.Applicant
- Technical Presentation: Vertex Buffers, posted Jun. 12, 2000, www.nvidia.com.Applicant
- Technical Presentation: Hardware Transform and Lightning, www.nvidia.com, posted Jun. 12, 2000.Applicant
- Technical Presentation: Hardware Bump-mapping Choices and Concepts, Jun. 7, 2000, www.nvidia.com.Applicant
- Technical Presentation: How to Bump Map a Skinned Polygonal Model, Jun. 7, 2000, www.nvidia.com.Applicant
- Technical Presentation: Computations for Hardware Lighting and Shading, Mar. 17, 2000, www.nvidia.com.Applicant
- Technical Presentation: Practical Bump-mapping for Today's GPUs, Mar. 17, 2000 www.nvidia.com.Applicant
- Technical Presentation: Shadows, Transparency, & Fog, Mar. 17, 2000 www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 Register Combiners, Mar. 17, 2000,www.nvidia.com.Applicant
- Technical Presentation: TexGen & The Texture Matrix, Mar. 15, 2000 www.nvidia.com.Applicant
- Technical Presentation: Toon Shading, Mar. 15, 2000, www.nvidia.com.Applicant
- Technical Presentation: D3D 7 Vertex Lighting, Mar. 15, 2000, www.nvidia.com.Applicant
- Technical Presentation: Per-Pixel Lighting (by S. Dietrich) Mar. 14, 2000 www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 and RIVA TNT Combiners, Dec. 8, 1999, www.nvidia.com.Applicant
- Technical Presentation: Vertex Cache Optimization, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Vertex Blending, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Hardware Transform and Lighting, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: GeForce 256 Overview, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: DirectX 7 and Texture Management, Nov. 12, 1999 www.nvidia.com.Applicant
- Technical Presentation: Dot Product Lighting, Nov. 12, 1999, www.nvidia.com.Applicant
- Technical Presentation: Texture Coordinate Generation, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Phong Shading and Lightmaps, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: The ARB_multitexture Extension, Nov. 3, 1999 www.nvidia.com.Applicant
- Technical Presentation: Multitexture Combiners, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Emboss Bump Mapping, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Hardware Accelerated Anisotropic Lighting, Nov. 3, 1999, www.nvidia.com.Applicant
- Technical Presentation: Guard Band Clipping, Nov. 3, 1999, www.nvidia.com.Applicant
- The RenderMan Interface, Stephan R. Keith, Version 3.1, Pixar Animation Studios, Sep. 1989.Applicant
- The RenderMan Interface, Version 3.2, Pixar Animation Studios, Jul. 2000, www.pixar.com.Applicant
- NVIDIA Product Overview, “GeForce2Ultra”, NVIDIA Corporation, Aug. 21, 2000, www.nvidia.com.Applicant
- Duke, “Dreamcast Technical Specs”, Sega Dreamcast Review, Sega, 2/99, www.game-revolution.com.Applicant
- Marlin Rowley, “GeForce 1 & 2 GPU Speed Tests”, May 11, 2000, www.g256.com.Applicant
- “Dreamcast: The Full Story”, Next Generation, Sep. 1998.Applicant
- DirectX 7.0 Programmer's Reference, Microsoft Corporation, 1995-1999 (as part of the DirectX 7.0 SDK on the Companion CD included with “Inside Direct3D”, Microsoft Programming Series, Peter J. Kovach, Microsoft Press, 1999).Applicant
- “Inside Direct3D”, Microsoft Programming Series, Peter J. Kovach, Microsoft Press, 1999.Applicant
- “OpenGL Programming Guide, The Official Guide to Learning OpenGL, Release 1”, Jackie Nieder, Tom David, Mason Woo, Addision-Wesley Publishing Co., 1993.Applicant
- “Procedural Elements for Computer Graphics,” Second Edition, David F. Rogers, McGraw Hill,1998.Applicant
- “Real-Time Rendering,” Tomas Molleir, Eric Haines, AK Peters, 1999.Applicant
- “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