Difference between revisions of "Sega Dreamcast"

From Sega Retro

Line 56: Line 56:
 
Sega released an [[arcade]] board, using the same technology as the Dreamcast, called [[Sega NAOMI]], leading to many Dreamcast-exclusive games with a high level of arcade quality. The NAOMI has the same [[wikipedia:Central processing unit|CPU]], the [[SuperH|Hitachi SH-4]], at the same clock rate, but is more powerful in other ways, with the [[wikipedia:PowerVR|PowerVR CLX2]] having a higher [[wikipedia:Graphics processing unit|GPU]] clock rate, additional [[RAM]] and [[VRAM]], higher [[Byte|bandwidth]], and faster [[ROM]] [[cartridge]] storage. The NAOMI was, in turn, the basis for two significantly more powerful arcade systems, the [[Hikaru]] (debuted 1999) and [[NAOMI 2]] (debuted 2000). Sega later packaged the Dreamcast into an arcade board as the [[Atomiswave]]. While the Dreamcast is not as powerful as 1997–1999 Sega arcade hardware, including the [[Sega Model 3|Model 3 Step 2]] (debuted 1997), NAOMI, and Hikaru, the Dreamcast surpassed the [[Sega Model 3|Model 3 Step 1]] (debuted 1996).
 
Sega released an [[arcade]] board, using the same technology as the Dreamcast, called [[Sega NAOMI]], leading to many Dreamcast-exclusive games with a high level of arcade quality. The NAOMI has the same [[wikipedia:Central processing unit|CPU]], the [[SuperH|Hitachi SH-4]], at the same clock rate, but is more powerful in other ways, with the [[wikipedia:PowerVR|PowerVR CLX2]] having a higher [[wikipedia:Graphics processing unit|GPU]] clock rate, additional [[RAM]] and [[VRAM]], higher [[Byte|bandwidth]], and faster [[ROM]] [[cartridge]] storage. The NAOMI was, in turn, the basis for two significantly more powerful arcade systems, the [[Hikaru]] (debuted 1999) and [[NAOMI 2]] (debuted 2000). Sega later packaged the Dreamcast into an arcade board as the [[Atomiswave]]. While the Dreamcast is not as powerful as 1997–1999 Sega arcade hardware, including the [[Sega Model 3|Model 3 Step 2]] (debuted 1997), NAOMI, and Hikaru, the Dreamcast surpassed the [[Sega Model 3|Model 3 Step 1]] (debuted 1996).
  
The Dreamcast (DC) was the most powerful home system during 1998–1999, outperforming high-end [[wikipedia:PC game|PC]] hardware at the time. The DC's [[SuperH|SH-4]] [[wikipedia:Geometry Engine|geometry engine]] calculates 1.4 [[wikipedia:FLOPS|GFLOPS]] and more than 10 MPolys/s,{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} higher than a PC with [[wikipedia:PIII|PIII 800]] (1999's strongest PC CPU) and [[wikipedia:Nvidia|Nvidia]] [[wikipedia:GeForce256|GF256]] (1999's strongest PC GPU) which calculates 800 MFLOPS{{ref|1=[https://books.google.co.uk/books?id=ZyZPAQAAMAAJ&q=pentium+iii+800+mflops ''Automatic Performance Tuning of Sparse Matrix Kernels'', Volume 1, page 14]}}{{ref|1=[https://books.google.co.uk/books?id=Zi8lBAAAQBAJ&pg=PA9 ''Cluster Computing'', page 9]}} and 6.7 MPolys/s.{{ref|[https://www.beyond3d.com/content/articles/50/ Benchmarking T&L in 3DMark 2000], Beyond3D}} The DC's CLX2 has an additional 200 MFLOPS for [[wikipedia:Tiled rendering|tiled rendering]], and has a [[fillrate]] of 3.2 [[Pixel|GPixels/s]] with opaque polygons{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} and 500 [[Pixel|MPixels/s]]{{fileref|Edge UK 067.pdf|page=11}} (500 [[Texel|MTexels/s]]) with [[wikipedia:Alpha blending|translucent]] polygons, higher than the [[wikipedia:Voodoo3|V3 TV SE]]'s 200 MPixels/s (400 MTexels/s) and GF256's 480 MPixels/s (480 MTexels/s). The DC's 800 [[Byte|MB/s]] CPU–GPU transmission bus{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} is faster than the V3's 533 MB/s [[wikipedia:Accelerated Graphics Port|AGP]] bus (2x AGP 2.0) and has a higher effective bandwidth than the 1064 MB/s transmission bus from a PIII 800EB (133 MHz [[wikipedia:Front-side bus|FSB]]) to GF256 (4x AGP 2.0){{ref|[http://www.playtool.com/pages/agpcompat/agp.html AGP Peak Speeds]}} due to the DC's more efficient bandwidth usage, including its lack of CPU overhead (from [[wikipedia:Operating system|operating system]]), and the CLX2's tiled rendering architecture: 32 bytes per polygon (less than standard 40 bytes per polygon), [[wikipedia:Texture mapping|textures]] sent directly to VRAM (freeing up CPU–GPU transmission bus for polygons), 8:1 [[wikipedia:Vector quantization|VQ]] [[wikipedia:Texture compression|texture compression]] (higher than V3's 4:1 compression and GF256's 6:1 [[wikipedia:S3TC|S3TC]] compression), on-chip tile buffer (no need for [[wikipedia:Z-buffer|Z-buffer]]), and [[wikipedia:Deferred shading|deferred rendering]] (no need to draw, [[wikipedia:Shading|shade]] or texture overdrawn polygons). The CLX2 was also the first GPU to support [[wikipedia:Normal mapping|Dot3 normal mapping]], which the V3 lacked and a year before the GF256.{{ref|''[[wikipedia:PC Magazine|PC Magazine]]'', [https://books.google.co.uk/books?id=90OvoBUqQoIC&pg=PA193 December 1999, page 193]}} The CLX2's rendering throughput is 7 MPolys/s,{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} with game engine performance peaking at 5 MPolys/s;{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} in comparison, a [[wikipedia:Celeron|Celeron 300A]] 450 MHz{{ref|[http://www.extremetech.com/computing/183039-20th-anniversary-pentium-specs-leak-ahead-of-launch-will-this-be-the-modern-eras-celeron-300a 20th anniversary Pentium specs leak – will this be the modern era’s Celeron 300A?] ([[wikipedia:ExtremeTech|ExtremeTech]])}} (100 MHz FSB,{{ref|[http://gamepilgrimage.com/content/95-99-pc-comparisons '95-'99 PC Comparisons]}} 364 MFLOPS){{ref|1=[https://books.google.co.uk/books?id=nXs4u5ODdPAC&pg=PA301 ''Recent Advances in Parallel Virtual Machine and Message Passing Interface'', page 301]}} with V3 TV (183 MHz) renders 750,000 polys/s,{{ref|[http://gamepilgrimage.com/content/3dmark-2001se-benchmarks 3DMARK 2001SE Benchmarks]}} a PIII 800 (800 MFLOPS) with V3 TV SE (200 MHz) renders 1.8 MPolys/s, and a PIII 800 with GF256 has a peak rendering throughput of 6.7 MPolys/s{{ref|[https://www.beyond3d.com/content/articles/50/ Benchmarking T&L in 3DMark 2000], Beyond3D}} and peak game engine performance of 2.9 MPolys/s.{{ref|[http://ixbtlabs.com/articles/gf2hwtl/ Actual HW T&L perfomance of NVIDIA GeForce/GeForce2 chips], IXBT Labs}} DC game engines rendered 50,000–166,666 polys per scene (3–5 MPolys/s),{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} while PC game engines of 1999 rendered 10,000–15,000 polys per scene (1–1.6 MPolys/s).{{ref|1=''[[wikipedia:PC Magazine|PC Magazine]]'', [https://books.google.co.uk/books?id=90OvoBUqQoIC&pg=PA203 December 1999, page 203]}}{{ref|[http://gamepilgrimage.com/content/95-99-pc-comparisons '95-'99 PC Comparisons]}}
+
The Dreamcast (DC) was the most powerful home system during 1998–1999, outperforming high-end [[wikipedia:PC game|PC]] hardware at the time. The DC's [[SuperH|SH-4]] [[wikipedia:Geometry Engine|geometry engine]] calculates 1.4 [[wikipedia:FLOPS|GFLOPS]] and more than 10 MPolys/s,{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} higher than a PC with [[wikipedia:Pentium III|PIII 800]] (1999's strongest PC CPU) and [[wikipedia:Nvidia|Nvidia]] [[wikipedia:GeForce256|GF256]] (1999's strongest PC GPU) which calculates 800 MFLOPS{{ref|1=[https://books.google.co.uk/books?id=ZyZPAQAAMAAJ&q=pentium+iii+800+mflops ''Automatic Performance Tuning of Sparse Matrix Kernels'', Volume 1, page 14]}}{{ref|1=[https://books.google.co.uk/books?id=Zi8lBAAAQBAJ&pg=PA9 ''Cluster Computing'', page 9]}} and 6.7 MPolys/s.{{ref|[https://www.beyond3d.com/content/articles/50/ Benchmarking T&L in 3DMark 2000], Beyond3D}} The DC's CLX2 has an additional 200 MFLOPS for [[wikipedia:Tiled rendering|tiled rendering]], and has a [[fillrate]] of 3.2 [[Pixel|GPixels/s]] with opaque polygons{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} and 500 [[Pixel|MPixels/s]]{{fileref|Edge UK 067.pdf|page=11}} (500 [[Texel|MTexels/s]]) with [[wikipedia:Alpha blending|translucent]] polygons, higher than the [[wikipedia:Voodoo3|V3 TV SE]]'s 200 MPixels/s (400 MTexels/s) and GF256's 480 MPixels/s (480 MTexels/s). The DC's 800 [[Byte|MB/s]] CPU–GPU transmission bus{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} is faster than the [[wikipedia:Voodoo3|V3]]'s 533 MB/s [[wikipedia:Accelerated Graphics Port|AGP]] bus (2x AGP 2.0) and has a higher effective bandwidth than the 1064 MB/s transmission bus from a [[wikipedia:Pentium III|PIII 800EB]] (133 MHz [[wikipedia:Front-side bus|FSB]]) to GF256 (4x AGP 2.0){{ref|[http://www.playtool.com/pages/agpcompat/agp.html AGP Peak Speeds]}} due to the DC's more efficient bandwidth usage, including its lack of CPU overhead (from [[wikipedia:Operating system|operating system]]) and the CLX2's tiled rendering architecture: 32 bytes per polygon (less than standard 40 bytes per polygon), [[wikipedia:Texture mapping|textures]] sent directly to VRAM (freeing up CPU–GPU transmission bus for polygons), 8:1 [[wikipedia:Vector quantization|VQ]] [[wikipedia:Texture compression|texture compression]] (higher than V3's 4:1 compression and GF256's 6:1 [[wikipedia:S3TC|S3TC]] compression), on-chip tile buffer (no need for [[wikipedia:Z-buffer|Z-buffer]]), and [[wikipedia:Deferred shading|deferred rendering]] (no need to draw, [[wikipedia:Shading|shade]] or texture overdrawn polygons). The CLX2 was also the first GPU to support [[wikipedia:Normal mapping|Dot3 normal mapping]], which the V3 lacked and a year before the GF256.{{ref|''[[wikipedia:PC Magazine|PC Magazine]]'', [https://books.google.co.uk/books?id=90OvoBUqQoIC&pg=PA193 December 1999, page 193]}} The CLX2's rendering throughput is 7 MPolys/s,{{ref|[http://web.archive.org/web/20000823204755/computer.org/micro/articles/dreamcast_2.htm Sega Dreamcast: Implementation (IEEE)]}} with game engine performance peaking at 5 MPolys/s;{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} in comparison, a [[wikipedia:Celeron|Celeron 300A]] 450 MHz{{ref|[http://www.extremetech.com/computing/183039-20th-anniversary-pentium-specs-leak-ahead-of-launch-will-this-be-the-modern-eras-celeron-300a 20th anniversary Pentium specs leak – will this be the modern era’s Celeron 300A?] ([[wikipedia:ExtremeTech|ExtremeTech]])}} (100 MHz FSB,{{ref|[http://gamepilgrimage.com/content/95-99-pc-comparisons '95-'99 PC Comparisons]}} 364 MFLOPS){{ref|1=[https://books.google.co.uk/books?id=nXs4u5ODdPAC&pg=PA301 ''Recent Advances in Parallel Virtual Machine and Message Passing Interface'', page 301]}} with [[wikipedia:Voodoo3|V3 TV]] (183 MHz) renders 750,000 polys/s,{{ref|[http://gamepilgrimage.com/content/3dmark-2001se-benchmarks 3DMARK 2001SE Benchmarks]}} a PIII 800 (800 MFLOPS) with V3 TV SE (200 MHz) renders 1.8 MPolys/s, and a PIII 800 with GF256 has a peak rendering throughput of 6.7 MPolys/s{{ref|[https://www.beyond3d.com/content/articles/50/ Benchmarking T&L in 3DMark 2000], Beyond3D}} and peak game engine performance of 2.9 MPolys/s.{{ref|[http://ixbtlabs.com/articles/gf2hwtl/ Actual HW T&L perfomance of NVIDIA GeForce/GeForce2 chips], IXBT Labs}} DC game engines rendered 50,000–166,666 polys per scene (3–5 MPolys/s),{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} while PC game engines of 1999 rendered 10,000–15,000 polys per scene (1–1.6 MPolys/s).{{ref|1=''[[wikipedia:PC Magazine|PC Magazine]]'', [https://books.google.co.uk/books?id=90OvoBUqQoIC&pg=PA203 December 1999, page 203]}}{{ref|[http://gamepilgrimage.com/content/95-99-pc-comparisons '95-'99 PC Comparisons]}}
  
Compared to the rival PS2, the PS2 is better at untextured polygons, [[wikipedia:Particle system|particles]], and [[wikipedia:Computer graphics lighting|lighting]], while the DC is better at textures, [[wikipedia:Spatial anti-aliasing|anti-aliasing]], and [[wikipedia:Image quality|image quality]]. The PS2 has a more powerful CPU geometry engine (6.2 GFLOPS [[wikipedia:Emotion Engine|Emotion Engine]]), higher translucent fillrate (2.4 GPixels/s), and more main RAM (32 [[Byte|MB]], compared to DC's 16 MB), while the DC has more VRAM (8 MB, compared to PS2's 4 MB), higher opaque fillrate (3.2 GPixels/s), and more GPU hardware features, with CLX2 capabilities like tiled rendering, [[wikipedia:Supersampling|super-sample anti-aliasing]], Dot3 normal mapping, and texture compression, which the PS2's [[wikipedia:Graphics Synthesizer|Graphics Synthesizer]] GPU lacks hardware support for. The DC's VRAM is twice as large; with tiled rendering, it could render a larger [[wikipedia:Framebuffer|framebuffer]] at a higher native [[resolution]] (without needing a Z-buffer), and with texture compression, it could compress around 20–60 MB of texture data in its VRAM. Because the PS2 has only 4 MB VRAM, it relies on the main RAM to store textures, but the PS2's CPU–GPU transmission bus for transferring polygons and textures has a bandwidth of 1.2 [[Byte|GB/s]]; while 50% faster than the DC's 800 MB/s CPU–GPU transmission bus, the DC has textures sent directly to VRAM (freeing up the CPU–GPU transmission bus for polygons) while texture compression gives it around 2–6 GB/s of effective texture bandwidth. DC games were effectively using 20–30 MB of texture memory{{ref|[http://farm6.staticflickr.com/5471/12172411045_18bfc5912f_c.jpg Hideki Sato Sega Interview (Edge)]}} (compressed to around 5.8 MB),{{ref|[http://segatech.com/technical/polygons/index.html How Many Polygons Can the Dreamcast Render?] (Dreamcast Technical Pages)}} while PS2 games up until 2003 peaked at 5.5 MB of texture memory (average 1.5 MB). PS2 game engines up until 2003 peaked at 7.5 MPolys/s (145,000 polys per scene), with most PS2 games rendering 2–5 MPolys/s (average 52,000 polys per scene);{{ref|[http://gamepilgrimage.com/sites/default/files/SystemSpecs/PS2/HowFarHaveWeGot.pdf Reaching for the Limits of PS2 Performance: How Far Have We Got?], [[wikipedia:Sony Computer Entertainment|SCEE]], 2003}} in comparison, DC game engines peaked at 5 MPolys/s (166,666 polys per scene), with most DC games rendering 2–4 MPolys/s (average 50,000 polys per scene).{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} The DC is more user-friendly for developers, making it easier to develop for, while the PS2 is more difficult to develop for; this is the reverse of the [[32-bit era]], when the PlayStation was easier to develop for and the Saturn was more difficult to develop for.
+
Compared to the rival PS2, the PS2 is better at untextured polygons, [[wikipedia:Particle system|particles]], and [[wikipedia:Computer graphics lighting|lighting]], while the DC is better at textures, [[wikipedia:Spatial anti-aliasing|anti-aliasing]], and [[wikipedia:Image quality|image quality]]. The PS2 has a more powerful CPU geometry engine (6.2 GFLOPS [[wikipedia:Emotion Engine|Emotion Engine]]), higher translucent fillrate (2.4 GPixels/s), and more main RAM (32 [[Byte|MB]], compared to DC's 16 MB), while the DC has more VRAM (8 MB, compared to PS2's 4 MB), higher opaque fillrate (3.2 GPixels/s), and more GPU hardware features, with CLX2 capabilities like tiled rendering, [[wikipedia:Supersampling|super-sample anti-aliasing]], Dot3 normal mapping, and texture compression, which the PS2's [[wikipedia:Graphics Synthesizer|Graphics Synthesizer]] GPU lacks. With larger VRAM tiled rendering, the DC can render a larger [[wikipedia:Framebuffer|framebuffer]] at higher native [[resolution]] (without needing Z-buffer), and with texture compression, it can compress around 20–60 MB of texture data in its VRAM. Because the PS2 has only 4 MB VRAM, it relies on the main RAM to store textures, but the PS2's CPU–GPU transmission bus for transferring polygons and textures has a bandwidth of 1.2 [[Byte|GB/s]]; while 50% faster than the DC's 800 MB/s CPU–GPU transmission bus, the DC has textures sent directly to VRAM (freeing up the CPU–GPU transmission bus for polygons), only requires 32 bytes per polygon, and texture compression gives it around 2–6 GB/s of effective texture bandwidth. DC games were effectively using 20–30 MB of texture memory{{ref|[http://farm6.staticflickr.com/5471/12172411045_18bfc5912f_c.jpg Hideki Sato Sega Interview (Edge)]}} (compressed to around 5–6 MB),{{ref|[http://segatech.com/technical/polygons/index.html How Many Polygons Can the Dreamcast Render?] (Dreamcast Technical Pages)}} while PS2 games up until 2003 peaked at 5.5 MB of texture memory (average 1.5 MB). PS2 game engines up until 2003 rendered up to 7.5 MPolys/s (145,000 polys per scene), with most rendering 2–5 MPolys/s (average 52,000 polys per scene);{{ref|[http://gamepilgrimage.com/sites/default/files/SystemSpecs/PS2/HowFarHaveWeGot.pdf Reaching for the Limits of PS2 Performance: How Far Have We Got?], [[wikipedia:Sony Computer Entertainment|SCEE]], 2003}} in comparison, DC game engines rendred up to 5 MPolys/s (166,666 polys per scene), with most rendering 2–4 MPolys/s (average 50,000 polys per scene).{{ref|[http://planetdc.segaretro.org/games/reviews/testdrivelemans/index.html Test Drive: Le Mans], Planet Dreamcast, [[wikipedia:IGN|IGN]]}} The DC is more user-friendly for developers, making it easier to develop for, while the PS2 is more difficult to develop for; this is the reverse of the [[32-bit era]], when the PlayStation was more user-friendly, and the Saturn more difficult, for developers.
  
 
===Models===
 
===Models===

Revision as of 13:30, 21 September 2016

Dreamcast.jpg
Sega Dreamcast
Manufacturer: Sega
Variants: Sega NAOMI, Atomiswave, Sega Aurora
Release Date RRP Code
Sega Dreamcast
JP
¥29,80029,800 HKT-3000
Sega Dreamcast
US
$199.99199.99 HKT-3020
Sega Dreamcast
DE
DM 499,-499,-[4] HKT-3030
Sega Dreamcast
ES
HKT-3030
Sega Dreamcast
FR
1,690F1,690[3] HKT-3030
Sega Dreamcast
UK
£199.99199.99[2] HKT-3030
Sega Dreamcast
AU
$499.00499.00
Sega Dreamcast
BR
R$899.00899.00
Sega Dreamcast
KR
HKT-3010
Sega Dreamcast
AS
HKT-3010

The Sega Dreamcast (ドリームキャスト) is a home video game console manufactured by Sega as a successor to the Sega Saturn. It was originally released in November 1998, becoming first machine to be released in what is now known as the sixth generation of video game consoles, sharing a platform with the PlayStation 2, Nintendo GameCube and the Xbox.

The Dreamcast was Sega's last home video game console, and was discontinued in early 2001. Roughly 10.6 million Dreamcast consoles have been sold worldwide.

An arcade counterpart to the Dreamcast exists as the Sega NAOMI.

Hardware

The Dreamcast is a small, white box with aesthetics designed to appeal to a wide-ranging audience. It was envisioned as an "128-bit" "super console", designed to leapfrog "32-bit" and "64-bit" contemporaries in the form of the PlayStation and Nintendo 64, respectively (although from a technical standpoint, its main processor deals in 32-bit or 64-bit instructions, with the 128-bit figure coming from the graphics hardware). Incidentally the Dreamcast was the last home console to use "bits" as a selling point, with processing capabilities now typically measured in other ways.

Taking design cues from the Nintendo 64 and the Sega Saturn, the Dreamcast contains four control ports, a removable modem, disc drive and an extension port (as well as the expected AV and power inputs). It is not backwards compatible with any prior Sega hardware or software (although its controller derives from the Saturn's 3D Control Pad), and operates in much the same way as the Saturn (and PlayStation) does, with a configurable settings and memory management accessed through a BIOS screen.

The Dreamcast uses a proprietary format of storage called GD-ROMs for games in order to circumvent software piracy, a strategy that ultimately backfired when the first run of discs had a high rate of defects. The format was also cracked fairly quickly (and in some cases, the pirated games were released before the legitimate versions). Sega largely had themselves to blame for the high levels of Dreamcast piracy—their use of the GD-ROM format was completely undermined by the console's support for the Mil-CD format, which allowed the console to boot from a standard CD-R. Mil-CD support was removed from the final Dreamcast revisions toward the end of the console's life.

The GD-ROM format also put the console at a disadvantage when competing against the PlayStation 2 - the PS2 used DVDs, and could therefore run DVD videos making it an inexpensive DVD player as well as a video game console. DVD-ROMs also have more storage space, allowing for bigger games (though the initial run of PS2 games used a blue CD-ROM format). Sega looked into DVD technology during the Dreamcast's development but claimed it was too expensive.

The Dreamcast was the first video game console to ship with a built-in 56k modem, with broadband adapters being made available later on in certain regions. This allowed the system to connect to the internet using a custom, fully-functional web browser and e-mail client. Many games released for the Dreamcast shipped with online play modes, the most popular being Phantasy Star Online and the Sega Sports lineup (now published under the ESPN label). Although other consoles before the Dreamcast had network gaming support, such as the Sega Saturn's NetLink and the Sega Mega Drive's XB∀ND, the Dreamcast was the first game console to include this ability out of the box and is therefore considered the first internet-enabled home game system.

The Dreamcast has a modest hacking enthusiast community. The availability of Windows CE software development kits on the Internet—as well as ports of Linux (LinuxDC) and dreamcast NetBSD operating systems to the Dreamcast—gave programmers a selection of familiar development tools to work with, even though they do not really support the high speed graphics. A homebrew minimal operating system called Kallistios offers support for most hardware, while not offering multi-tasking, which is superfluous for games. Many emulators and other tools (MP3, DivX players, and image viewers) have been ported to or written for the console, taking advantage of the relative ease with which a home user can write a CD which is bootable by an unmodified Dreamcast.

Sega released an arcade board, using the same technology as the Dreamcast, called Sega NAOMI, leading to many Dreamcast-exclusive games with a high level of arcade quality. The NAOMI has the same CPU, the Hitachi SH-4, at the same clock rate, but is more powerful in other ways, with the PowerVR CLX2 having a higher GPU clock rate, additional RAM and VRAM, higher bandwidth, and faster ROM cartridge storage. The NAOMI was, in turn, the basis for two significantly more powerful arcade systems, the Hikaru (debuted 1999) and NAOMI 2 (debuted 2000). Sega later packaged the Dreamcast into an arcade board as the Atomiswave. While the Dreamcast is not as powerful as 1997–1999 Sega arcade hardware, including the Model 3 Step 2 (debuted 1997), NAOMI, and Hikaru, the Dreamcast surpassed the Model 3 Step 1 (debuted 1996).

The Dreamcast (DC) was the most powerful home system during 1998–1999, outperforming high-end PC hardware at the time. The DC's SH-4 geometry engine calculates 1.4 GFLOPS and more than 10 MPolys/s,[6] higher than a PC with PIII 800 (1999's strongest PC CPU) and Nvidia GF256 (1999's strongest PC GPU) which calculates 800 MFLOPS[7][8] and 6.7 MPolys/s.[9] The DC's CLX2 has an additional 200 MFLOPS for tiled rendering, and has a fillrate of 3.2 GPixels/s with opaque polygons[6] and 500 MPixels/s[10] (500 MTexels/s) with translucent polygons, higher than the V3 TV SE's 200 MPixels/s (400 MTexels/s) and GF256's 480 MPixels/s (480 MTexels/s). The DC's 800 MB/s CPU–GPU transmission bus[6] is faster than the V3's 533 MB/s AGP bus (2x AGP 2.0) and has a higher effective bandwidth than the 1064 MB/s transmission bus from a PIII 800EB (133 MHz FSB) to GF256 (4x AGP 2.0)[11] due to the DC's more efficient bandwidth usage, including its lack of CPU overhead (from operating system) and the CLX2's tiled rendering architecture: 32 bytes per polygon (less than standard 40 bytes per polygon), textures sent directly to VRAM (freeing up CPU–GPU transmission bus for polygons), 8:1 VQ texture compression (higher than V3's 4:1 compression and GF256's 6:1 S3TC compression), on-chip tile buffer (no need for Z-buffer), and deferred rendering (no need to draw, shade or texture overdrawn polygons). The CLX2 was also the first GPU to support Dot3 normal mapping, which the V3 lacked and a year before the GF256.[12] The CLX2's rendering throughput is 7 MPolys/s,[6] with game engine performance peaking at 5 MPolys/s;[13] in comparison, a Celeron 300A 450 MHz[14] (100 MHz FSB,[15] 364 MFLOPS)[16] with V3 TV (183 MHz) renders 750,000 polys/s,[17] a PIII 800 (800 MFLOPS) with V3 TV SE (200 MHz) renders 1.8 MPolys/s, and a PIII 800 with GF256 has a peak rendering throughput of 6.7 MPolys/s[9] and peak game engine performance of 2.9 MPolys/s.[18] DC game engines rendered 50,000–166,666 polys per scene (3–5 MPolys/s),[13] while PC game engines of 1999 rendered 10,000–15,000 polys per scene (1–1.6 MPolys/s).[19][15]

Compared to the rival PS2, the PS2 is better at untextured polygons, particles, and lighting, while the DC is better at textures, anti-aliasing, and image quality. The PS2 has a more powerful CPU geometry engine (6.2 GFLOPS Emotion Engine), higher translucent fillrate (2.4 GPixels/s), and more main RAM (32 MB, compared to DC's 16 MB), while the DC has more VRAM (8 MB, compared to PS2's 4 MB), higher opaque fillrate (3.2 GPixels/s), and more GPU hardware features, with CLX2 capabilities like tiled rendering, super-sample anti-aliasing, Dot3 normal mapping, and texture compression, which the PS2's Graphics Synthesizer GPU lacks. With larger VRAM tiled rendering, the DC can render a larger framebuffer at higher native resolution (without needing Z-buffer), and with texture compression, it can compress around 20–60 MB of texture data in its VRAM. Because the PS2 has only 4 MB VRAM, it relies on the main RAM to store textures, but the PS2's CPU–GPU transmission bus for transferring polygons and textures has a bandwidth of 1.2 GB/s; while 50% faster than the DC's 800 MB/s CPU–GPU transmission bus, the DC has textures sent directly to VRAM (freeing up the CPU–GPU transmission bus for polygons), only requires 32 bytes per polygon, and texture compression gives it around 2–6 GB/s of effective texture bandwidth. DC games were effectively using 20–30 MB of texture memory[20] (compressed to around 5–6 MB),[21] while PS2 games up until 2003 peaked at 5.5 MB of texture memory (average 1.5 MB). PS2 game engines up until 2003 rendered up to 7.5 MPolys/s (145,000 polys per scene), with most rendering 2–5 MPolys/s (average 52,000 polys per scene);[22] in comparison, DC game engines rendred up to 5 MPolys/s (166,666 polys per scene), with most rendering 2–4 MPolys/s (average 50,000 polys per scene).[13] The DC is more user-friendly for developers, making it easier to develop for, while the PS2 is more difficult to develop for; this is the reverse of the 32-bit era, when the PlayStation was more user-friendly, and the Saturn more difficult, for developers.

Models

Main article: Dreamcast consoles.

Japanese Dreamcasts can be identified by the triangle at the front of the unit. Though the power LED is identical across all regions, the piece of plastic attached to the lid of the Japanese model is transparent, while in North America it is grey.

For a full list of special edition Dreamcasts, see Special Dreamcast Models.

Technical specifications

CPU

  • Main CPU: Hitachi SH-4 (RISC, 2‑way Superscalar)[6][23]
    • Operating frequency: 200 MHz
    • Units: 128‑bit SIMD vector unit with graphic functions, 64‑bit floating‑point unit, 32‑bit fixed‑point unit
    • 128‑bit SIMD @ 200 MHz: Vector unit, geometry processor, graphic functions, DMA controller, interrupt controller[24]
    • 128‑bit graphic computational engine: Calculates geometry and lighting of polygons, creates display lists of polygons for tiling, DMA allows SH4 access to VRAM and PowerVR2 access to Main RAM, store queue mechanism (allowing high‑speed packet transfers between Main RAM and VRAM)[25]
    • Bus width: 128‑bit internal, 64‑bit external
    • Bandwidth: 3.2 GB/s internal, 1.6 GB/s external
  • Fixed‑point performance: 360 MIPS
  • Floating‑point performance: 1.4 GFLOPS (7 MFLOPS per 16 MB/s)
  • Geometry performance: More than 10 million polygons/sec, with lighting calculations (140 FLOPS per polygon)

Graphics

Graphical specifications of the Dreamcast:[26][25][27]

  • GPU: 2 graphics processors (SH‑4 SIMD, PowerVR2)
    • Cores: 6 cores (SH‑4 SIMD, 5 PowerVR2 cores)
  • GPU Geometry Processor: Hitachi SH‑4 SIMD @ 200 MHz (1.4 GFLOPS)
  • GPU Rasterizer: NECVideoLogic PowerVR2 CLX2 (PVR2DC/HOLLY) @ 100 MHz
  • PowerVR2 Cores: Tile Accelerator (TA), Image Synthesis Processor (ISP), Texture & Shading Processor (TSP), Triangle Setup FPU, RAMDAC[28]
    • TA: Tile renderer, partitions infinite strip polygon data, divides polygons into tiles, performs tile clipping, generates object lists, retrieves display lists from SH4 (through store queues and DMA), generates ISP/TSP parameters
      • Tile buffer: 600 tiles, 128 bytes per tile, 75 KB tile buffer[29]
    • ISP: Rasterizer, depth‑sorting, RLE tile/polygon compression, parallel‑processing of tiles/polygons at high speeds (1 clock cycle per vector, 32 pixels per clock cycle)
      • ISP units: ISP Precalc Unit, ISP PE Array, Depth Accumulation Buffer, Span RLC, Span Sorter
    • TSP: Shader and texture‑mapping unit, avoids shading/texturing overdrawn pixels/tiles and back‑facing polygons to maximize bandwidth for on‑screen pixels/tiles and front‑facing polygons
      • TSP units: TSP Precalc + Param Cache, Texture Cache, Iterator Array, Pixel Processing Engine, Micro Tile Accumulation Buffer
    • Triangle Setup FPU: 2 FPU rendering units, 200 MFLOPS[28]
      • ISP Setup FPU: 100 MHz, 100 MFLOPS, 14 cycles per polygon, 7,142,857 polygons/sec
      • TSP Setup FPU: 100 MHz, 100 MFLOPS
    • RAMDAC: 230 MHz[30]
  • PowerVR2 Buses: 2 buses at 100 MHz, 64-bit TA Bus for transferring polygons and textures (800 MB/s), 32-bit PVRIF Bus for register memory (400 MB/s), 96-bit total bus width (1.2 GB/s total bandwidth)[31]
  • PowerVR2 Capabilities:
  • Display Resolution: 320×240 to 800×608 pixels, interlaced and progressive scan, TV and VGA
    • Internal resolution: 320×240 to 1600×1200 pixels[30]
  • Frame rate: 30-60 frames/sec
  • Color Depth: 16‑bit RGB to 32‑bit ARGB, 65,536 colors (16‑bit color) to 16,777,216 colors (24‑bit color) with 8‑bit (256 levels) alpha blending, YUV and RGB color spaces, color key overlay[37]
  • Framebuffer: Optional (raster method can be used)[38]
    • Strip/Tile buffer: 32×32×16‑bit (4 KB) to 32×32×32‑bit (8 KB) in local tile buffer cache memory[25]
    • Full framebuffer: Up to 1600×1200×24‑bit (5625 KB) in VRAM (optional)
    • Note: Due to deferred rendering, framebuffer only needs to be filled once per frame for opaque polygons, while translucent polygons can overdraw with up to 100 MPixels/s (200–300 MB/s).
  • Floating-Point Performance: 1.6 GFLOPS
    • SH-4 SIMD: 1.4 GFLOPS geometry
    • PowerVR2: 200 MFLOPS rendering
  • Vector Performance:
    • Geometry: 23 million vertices/sec (60 FLOPS per vertex)[39]
    • Rendering: 21,428,571 vertices/sec (14 ISP FPU cycles per 3 vertices)[40]
  • Polygon Geometry: Effective performance, including overdrawn and back‑facing polygons not drawn on screen
    • 11 million polygons/sec (130 FLOPS per polygon)
    • More than 10 million polygons/sec: Lighting (under 140 FLOPS per polygon)[6]
  • Rendered On‑Screen Polygons: Front‑facing polygons drawn on screen, not including overdrawn and back‑facing polygons (including them, effective performance is more than than 10 million polygons/sec)[6][41]
    • 7,142,857 polygons/sec (14 ISP FPU cycles per polygon)[40]
    • 7 million polygons/sec: Lighting, textures, shadows[30]
    • 7 million polygons/sec: Textures, trilinear filtering[42]
    • 6 million polygons/sec: Lighting, textures, trilinear filtering, Gouraud shading (243 FLOPS per polygon)
    • 4.2 million polygons/sec: Lighting, textures, anisotropic filtering
    • 3.3 million polygons/sec: Lighting, textures, trilinear filtering, Gouraud shading, bump mapping (430 FLOPS per polygon)[43]
  • Rendering Fillrate:[6][25]
    • 3.2 GPixels/s: Opaque polygons (32 pixels per clock cycle)
    • 500 MPixels/s: Translucent and opaque polygons[10]
    • 100 MPixels/s: Translucent polygons with hardware sort depth of 60 (1 pixel per clock cycle)
    • 100 MPixels/s to 3.2 GPixels/s, depending on opacity/translucency of polygons (1–32 pixels per clock cycle)[27]
  • Texture Fillrate:
    • 500 MTexels/s: Effective fillrate (including overdrawn and back‑facing textures)
    • 100 MTexels/s: Front‑facing textures drawn on screen
  • VRAM: 8 MB (unified framebuffer and texture memory,[44][25][45] effectively 21–63 MB with texture compression)
    • Framebuffer: Up to 5625 KB (optional), 1200 KB (640×480, 16-bit color, double-buffered)
    • Polygons: Up to 7840 KB (10 million textured polygons/sec with Gouraud shading and modifier volumes, 48 bytes per polygon, 60 frames/sec, 166,666 polygons per frame), 3646 KB (7 million textured polygons/sec with Gouraud shading, 32 bytes per polygon, 60 frames/sec, 116,666 polygons per frame), 5334 KB (5 million textured polygons/sec with Gouraud shading, 32 bytes per polygon, 30 frames/sec, 166,666 polygons per frame)[46]
    • Textures: Up to 8 MB (effectively 21–63 MB with texture compression),[32] average 2–6 MB (effectively 20–30 MB with texture compression),[20] 3.2 MB (7 million textured polygons/sec with Gouraud shading, 640×480 framebuffer, 60 frames/sec, effectively 8.5–25 MB with texture compression), 1.6 MB (5 million textured polygons/sec with Gouraud shading, 32 bytes per polygon, 30 frames/sec, effectively 4.2–12 MB with texture compression)[32]
    • Note: Main RAM also used to store polygon display lists. Textures transferred directly to VRAM. Main RAM can also optionally be used to store textures.
  • VRAM bandwidth: 800 MB/s (effectively up to 6.3 GB/s with texture compression)
    • Framebuffer: Up to 300 MB/s (100–3200 MPixels/s, 24-bit color), 200 MB/s (100–3200 MPixels/s, 16-bit color)
    • Polygons: Up to 471 MB/s (10 million textured polygons/sec with Gouraud shading and modifier volumes, 48 bytes per polygon), 224 MB/s (7 million textured polygons/sec with Gouraud shading, 32 bytes per polygon), 160 MB/s (5 million textured polygons/sec with Gouraud shading, 32 bytes per polygon)
    • Textures: Up to 800 MB/s (effectively up to 6.3 GB/s with texture compression), average 200–600 MB/s (effectively 2–3 GB/s with texture compression), 376 MB/s (7 million textured polygons/sec with Gouraud shading, 100–3200 MPixels/s, effectively 1–2.9 GB/s with texture compression), 440 MB/s (5 million textured polygons/sec with Gouraud shading, 100–3200 MPixels/s, effectively 1.1–3.4 GB/s with texture compression)
  • Full Motion Video: MPEG decoding, video compression, 320×240 to 640×320 and 320×480 video resolutions, 3D polygons can be superimposed over FMV video[6]

Sound

Memory

  • System RAM: 26.125 MB
    • Main RAM: 16 MB SDRAM (Hyundai HY57V161610D)
      • Can be used for storing textures and polygon display lists, accessible by SH4 and PowerVR2 (via SH4 DMA)[25]
    • VRAM: 8 MB SDRAM (unified framebuffer and texture memory)[44]
      • Accessible by Power VR2 and SH4 (via DMA and store queues)
    • Sound RAM: 2 MB SDRAM
    • GD-ROM buffer RAM: 128 KB[26]
  • System ROM: 2 MB[26]
  • Flash Memory: 128 KB[25]
  • Internal Processor Memory: 150,216 bytes (147 KB)[25]
    • SH4: 26,178 bytes (8 KB instruction cache, 16 KB data cache, 64 bytes store queue cache,[48] 1538 bytes registers)
    • PowerVR2: 91,258 bytes (128 bytes ISP cache, 1 KB texture cache, 509 bytes fog table, 4093 bytes palette RAM, 8.25 KB registers,[49] 256 bytes FIFO buffer, 75 KB tile buffer)
    • AICA: 32,780 bytes (32 KB sound registers, 8 bytes RTC registers,[26] 4 bytes FIFO buffer)
  • GD-ROM Drive: 12× maximum speed (when running in Constant Angular Velocity mode)[26][25]
    • Disc formats: GD‑ROM, CD‑ROM, CD‑DA, , Photo CD, Video CD, CD Extra, CD+G, CD+EG
    • Storage capacity: 1 GB per GD‑ROM, 656 MB per CD‑ROM

Bandwidth

  • System RAM Bandwidth: 1.75 GB/s (4 buses, 160-bit bus width)[26]
    • SH4, PVR2 <‑> Main RAM — 800 MB/s (64‑bit, 100 MHz)[50]
    • PVR2 <‑> VRAM — 800 MB/s (64‑bit, 100 MHz, 7 ns, 2x 32-bit buses)[51][52]
    • AICA <‑> Sound RAM — 132 MB/s (16‑bit, 66 MHz)
    • SH4 <‑> GD‑ROM buffer — 13.3 MB/s (16‑bit)
  • System ROM Bandwidth: 20 MB/s (16‑bit, 10 MHz)
  • Transmission Bandwidth: 1.4 GB/s[31]
    • SH4 <‑> PVR2 — 800 MB/s (64‑bit, 100 MHz)
    • SH4IF <-> PVRIF — 400 MB/s (32‑bit, 100 MHz)
    • SH4 <-> Root Bus — 200 MB/s (32‑bit, 50 MHz)
  • Internal Processor Memory Bandwidth: 3.06 GB/s
    • SH4: 1.6 GB/s (64‑bit, 200 MHz)
    • PowerVR2: 1.2 GB/s (96‑bit, 100 MHz)
    • AICA: 256 MB/s (32‑bit, 67 MHz)
  • GD‑ROM Drive: 1.8 MB/s transfer rate, 250 milliseconds access time

BIOS

BIOS Revisions
BIOS Version Machine Download
1.004 Sega Dreamcast (Commercial-Early) 1.004 (Japan) (info) ("Jp_dc_1.004.7z" does not exist)
1.01d Sega Dreamcast (Commercial) 1.01d (North America) (info) ("Us_dc_1.01d.zip" does not exist)
1.01d (Europe) (info) ("Eu_dc_1.01d.zip" does not exist)
1.01d (Japan) (info) ("Jp_dc_1.01d.zip" does not exist)
1.011 Sega Dreamcast (HKT-0120 Devbox) 1.011 (HKT-0120 Devbox) (info) ("Jp_dc_1.011(dev).7z" does not exist)

Other specifications

  • Operating Systems:
  • Inputs: Four ports that can support a digital and analog controller, steering wheel, joystick, keyboard, mouse, and more
  • Dimensions: 189mm x 195mm x 76mm (7 7/16" x 7 11/16" x 3")
  • Weight: 1.9kg (4.4lbs)
  • Modem: Removable; Original Asia/Japan model had a 33.6 Kbytes/s; models released after 9 September 1999 had a 56 Kbytes/s modem
  • Sega Dreamcast Broadband Adapter: these adapters are available separately and replace the removable modem
    • HIT-400: "Broadband Adapter", the more common model, this used a RealTek 8139 chip and supported 10/100mbit
  • HIT-300: "Lan Adapter", this version used a Fujitsu MB86967 chip and supported only 10mbit
  • Storage: "Visual Memory Unit" (VMU) 128 Kb removable storage device
  • Input devices: (4 custom controller ports)
  • Output devices:
  • Add-ons:

History

Main article: History of the Sega Dreamcast.

Games

List of games

Main article: List of Dreamcast games.

Launch titles

Japan

North America

Europe

[53]

Brazil

[5]

Magazine articles

Main article: Sega Dreamcast/Magazine articles.

Promotional material

Print advertisements

Logo-pdf.svg
Print advert in Official Dreamcast Magazine (US) #1: "September 1999" (1999-08-24)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Official Dreamcast Magazine (US) #1: "September 1999" (1999-08-24)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Official Dreamcast Magazine (US) #1: "September 1999" (1999-08-24)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Official Dreamcast Magazine (US) #1: "September 1999" (1999-08-24)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Arcade (UK) #10: "September 1999" (1999-07-27)
Logo-pdf.svg
Logo-pdf.svg
Print advert in DC-UK (UK) #1: "September 1999" (1999-09-02)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Official Dreamcast Magazine (UK) #preview: "Taster" (1999-xx-xx)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Consoles Max (FR) #2: "Juillet/Août 1999" (1999-0x-xx)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Dreamcast: Das Offizielle Magazin (DE) #1: "Oktober 1999" (1999-10-14)
Logo-pdf.svg
Logo-pdf.svg
Print advert in Dreamcast: Das Offizielle Magazin (DE) #1: "Oktober 1999" (1999-10-14)
Logo-pdf.svg
Logo-pdf.svg
Print advert in MAN!AC (DE) #1999-11: "11/99" (1999-10-06)
Logo-pdf.svg
Logo-pdf.svg
Print advert in MAN!AC (DE) #1999-12: "12/99" (1999-11-03)
Logo-pdf.svg

Retailers

Logo-pdf.svg
Print advert in Arcade (UK) #10: "September 1999" (1999-07-27)
Logo-pdf.svg

Television advertisements

Other advertisements

Artwork

Hardware diagrams

Logos

References

  1. File:CVG UK 216.pdf, page 52
  2. File:CVG UK 215.pdf, page 59
  3. File:ConsolesMicro FR 01.pdf, page 15
  4. File:NextLevel DE 1999-0910.pdf, page 6
  5. 5.0 5.1 http://www.tectoy.com.br/unshock/prop.htm (Wayback Machine: 2000-03-03 16:07)
  6. 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 6.11 6.12 Sega Dreamcast: Implementation (IEEE) (Wayback Machine: 2000-08-23 20:47)
  7. Automatic Performance Tuning of Sparse Matrix Kernels, Volume 1, page 14
  8. Cluster Computing, page 9
  9. 9.0 9.1 Benchmarking T&L in 3DMark 2000, Beyond3D
  10. 10.0 10.1 File:Edge UK 067.pdf, page 11
  11. AGP Peak Speeds
  12. [ ]
  13. 13.0 13.1 13.2 Test Drive: Le Mans, Planet Dreamcast, IGN
  14. 20th anniversary Pentium specs leak – will this be the modern era’s Celeron 300A? (ExtremeTech)
  15. 15.0 15.1 '95-'99 PC Comparisons
  16. Recent Advances in Parallel Virtual Machine and Message Passing Interface, page 301
  17. 3DMARK 2001SE Benchmarks
  18. Actual HW T&L perfomance of NVIDIA GeForce/GeForce2 chips, IXBT Labs
  19. [PC Magazine, December 1999, page 203 PC Magazine, December 1999, page 203]
  20. 20.0 20.1 20.2 Hideki Sato Sega Interview (Edge)
  21. How Many Polygons Can the Dreamcast Render? (Dreamcast Technical Pages)
  22. Reaching for the Limits of PS2 Performance: How Far Have We Got?, SCEE, 2003
  23. File:SH-4 Software Manual.pdf
  24. File:SH-4 datasheet.pdf
  25. 25.00 25.01 25.02 25.03 25.04 25.05 25.06 25.07 25.08 25.09 25.10 File:DreamcastDevBoxSystemArchitecture.pdf
  26. 26.0 26.1 26.2 26.3 26.4 26.5 File:Dreamcast Hardware Specification Outline.pdf
  27. 27.0 27.1 File:PowerVR2DCFeaturesUnderWindowsCE.pdf
  28. 28.0 28.1 File:DreamcastDevBoxSystemArchitecture.pdf, page 94
  29. File:DreamcastDevBoxSystemArchitecture.pdf, page 165
  30. 30.0 30.1 30.2 VideoLogic's 100 MHz PowerVR Series2, Dreamcast Technical Pages
  31. 31.0 31.1 File:DreamcastDevBoxSystemArchitecture.pdf, page 42
  32. 32.0 32.1 32.2 File:PowerVR2DCFeaturesUnderWindowsCE.pdf, page 9
  33. Tiling Accelerator Notes
  34. Zombie Revenge (21 January 2000)
  35. PowerVR (Dreamcast Hardware)
  36. Dreamcast Comparison
  37. Neon 250 Specs & Features (Wayback Machine: 2007-08-11 10:20)
  38. File:DreamcastDevBoxSystemArchitecture.pdf, page 13
  39. Computer Graphics: Principles and Practice (Page 868)
  40. 40.0 40.1 File:DreamcastDevBoxSystemArchitecture.pdf, page 95
  41. Floating-Point Calculations
  42. Vintage Game Consoles: An Inside Look at Apple, Atari, Commodore, Nintendo, and the Greatest Gaming Platforms of All Time (Page 277)
  43. File:PowerVR2DCFeaturesUnderWindowsCE.pdf, page 11
  44. 44.0 44.1 File:Dreamcast Hardware Specification Outline.pdf, page 18
  45. Polygon Calculations
  46. File:DreamcastDevBoxSystemArchitecture.pdf, page 201
  47. Dreamcast & Saturn Specifications
  48. File:SH-4 Software Manual.pdf, page 25
  49. File:DreamcastDevBoxSystemArchitecture.pdf, page 17
  50. File:Dreamcast Hardware Specification Outline.pdf, page 14
  51. File:Dreamcast Hardware Specification Outline.pdf, page 6
  52. File:DreamcastDevBoxSystemArchitecture.pdf, page 49
  53. File:DreamcastMagazine UK 03.pdf, page 7
Sega Home Video Game Systems
83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 00 01 02 03 04 05 06 07 08 09 10 11
SG-1000 SG-1000 II Mega Drive Mega Drive II
SC-3000 Mega-CD Mega-CD II Genesis 3
Sega Mark III 32X Dreamcast
Master System Master System II
AI Computer Game Gear
Saturn
Pico Beena


Sega Dreamcast
Topics Technical specifications (Hardware comparison) | History (Development | Release | Decline and legacy | Internet) | List of games | Magazine articles | Promotional material | Merchandise
Hardware Japan (Special) | Western Europe | Eastern Europe | North America | Asia | South America | Australasia | Africa
Add-ons Dreamcast Karaoke | Dreameye
Controllers Controller | Arcade Stick | Fishing Controller | Gun (Dream Blaster) | Race Controller | Maracas Controller (Third-party) | Twin Stick | Keyboard | Mouse | Third-party
Controller Add-ons Jump Pack (Third-party) | Microphone | VMU (4x Memory Card | Third-party)
Development Hardware Dev.Box | Controller Box | Controller Function Checker | Sound Box | GD-Writer | C1/C2 Checker | Dev.Cas | GD-ROM Duplicator
Online Services/Add-ons Dreamarena | SegaNet | WebTV for Dreamcast | Modem | Modular Cable | Modular Extension Cable | Broadband Adapter | Dreamphone
Connector Cables Onsei Setsuzoku Cable | RF Adapter | Scart Cable | S Tanshi Cable | Stereo AV Cable | VGA Box

Dreamcast MIDI Interface Cable | Neo Geo Pocket/Dreamcast Setsuzoku Cable | Taisen Cable

Misc. Hardware Action Replay CDX | Code Breaker | Kiosk | MP3 DC | MP3 DC Audio Player | Official Case | Treamcast
Third-party accessories Controllers | Controller converters | Miscellaneous
Unreleased Accessories DVD Player | Zip Drive | Swatch Access for Dreamcast | VMU MP3 Player
Arcade Variants NAOMI | Atomiswave | Sega Aurora