FiringSquad: Home of the Hardcore Gamer - Games, Hardware, Reviews and NewsSubmit your own or view users' CPU overclocking results!

  
 Home   News   THE MATRIX   Deals   Hardware   Games   Features   Media   Products   Forums   FS China 
AddThis Social Bookmark Button

Home : Features : Articles : Inside The Demise of 3dfx
» Join the Greatest Gaming Community NOW! (It's free)

Already a member? Login
 


Random Gallery >> 
Click to view high-res Image!
Medieval 2: Total War Review Screenshots [62] (3)

"I need a vacation..." (4) by ICDP
BioShock Review(Preliminary #2) (3) by Hyper
Guild Wars Gets a Bad Review (11) by Joluha
Call of Duty 4: Modern Warfare SP Review (prelim 2) (9) by jacobvandy
A Truely "Epic" Game: Unreal Tournament 3 Review (4) by Discobiscuits
An EVGA Collage (0) by Samuel71
First Entry (1) by Skippy989
Sins of a Solar Empire Beta Review [Prelim 2] (5) by Itchyeyes
War! Huh! Yeah! (aka Blatant Plagiarism) (1) by ICDP
Far Cry 2 SP Review (wip) (1) by jacobvandy

More Blogs >>




Inside The Demise of 3dfx
September 26, 2002   Brandon Sandman Bell > [View My Other Articles]
Product Info | User Reviews | Article Images(5) | Image Gallery | Comments | Forum Thread
Money/Rampage


More inside details

3dfx was notorious for spending money. In the last year or so, roughly $30-50,000 was spent monthly on lunches. This did not include the additional snacks and drinks that were provided to employees. Hiring didn’t stop until the last few weeks, with all of us keeping hope that the company would pull through. Of course this did not happen.

Could 3dfx have lasted? Perhaps. They were offered a line of credit, but the board opted not to accept it as they would not accept the terms. Rumors within the company also circulated that an investor had expressed strong interest in the company, but backed out from a simple "goof" on the boards’ part (specifically, it was said to be their mention to the investor the possibility of a buyout by another company). But what would the future have held for 3dfx?


Next generation parts

Daytona- 3dfx's first low-end OEM part. Daytona was effectively a VSA-100 part with a DDR memory controller and a 64-bit memory bus. The idea was to deliver a cheaper version of the VSA-100, with the 64-bit bus making a notable dent in cost. Daytona simply could not be finalized though. It would tape out and a bug would be found, then tape out again and another bug would be found. Fortunately, a chip was not made between each tape out with the final number being A7 silicon. In the end, this resulted in considerable delays and final Daytona silicon never coming to life.

Inside The Demise of 3dfx [ Rampage bringup @ 800 x 600 ] > View Full-Size in another window.
Rampage bringup

Inside The Demise of 3dfx [ This is what you got when your socket isn't connecting well @ 896 x 698 ] > View Full-Size in another window.
This is what you got when your socket isn't connecting well


Rampage (Spectre) - 3dfx's next high-end graphics part was capable of quad-chip support. Rampage silicon had come back from the fab just weeks before the announcement of 3dfx's demise. Sage, Rampage's geometry processor had recently taped out as well, so expectations were high. The first revision of Rampage silicon was able to achieve 200 MHz clock frequencies without active cooling. Originally, the expectation had been to ship it at 200 MHz, but with this capability, there was nothing limiting it from 250+ MHz clock speeds.

Inside The Demise of 3dfx [ Screenshot of Quake 3 running on Rampage @ 1024 x 751 ] > View Full-Size in another window.
Screenshot of Quake 3 running on Rampage

Inside The Demise of 3dfx [ Rocket fire @ 803 x 481 ] > View Full-Size in another window.
Rocket fire


Of interesting note are the two bugs that did exist in Rampage silicon. The first was the DAC being flipped, reversing the color channels. It is hard to be certain how this bug managed to slip through, but it did. One possible reason it was not detected is because this was one of the few places on the chip that had not been simulated. The temporary fix was an interesting little board that was attached between the monitor cable and VGA connector. It flipped all the color channels, making it display correctly.

The second bug was an AGP issue that had initially caused some problems but was corrected for bring up boards by fibbing the chips.

Inside The Demise of 3dfx [ One last shot of Quake 3 on Rampage @ 807 x 482 ] > View Full-Size in another window.
One last shot of Quake 3 on Rampage


Here are the specs on Rampage, and its companion chip, Sage:

Rampage
200+ MHz Core
Approximately 30 million transistors
4 Pixel Pipelines
8 textures per-pass
DX 8 Pixel Shader 1.0
Quad-Chip support

Sage
50 million triangles/sec sustained
150 million triangles/sec real world
DX8 1.0 Vertex Shader
Approx. 20 million transistors







Back! The competition heats up and Voodoo5 6000     Moving to DirectX 9 and beyond Next!
Blog + Share: Digg Del.icio.us Reddit SU furl • More: AddThis Social Bookmark Button
Send This Article to a Friend!  
Table of Contents
  Print Entire Article  

MATRIX CONTENT » RANDOM MEDIA BLOG More Blogs >>
No ratings yet
» Please rate this
I am an AMD AgentRead this Media-Blog entry!» Round 2 Rules! (20)
by fs-lyle (174) Talk with this user on their Shout Box (My other blogs) Posted 24 months ago


 Latest Headlines
AMD Life After DX11 Contest (4)
Analyst says game review scores least important factor for gamers (1)
Next Star Wars game teased (0)
Mass Effect 2 system requirements announced (0)
Get ready for Far Cry 3 (0)
Today's News >>
Today's Siteseeing >>


 Table of Contents


 Quick Fact
Did Sage ever REALLY tape out? Sure it was finished, but was it ever sent
to the fab? Probably not.

FiringSquad is powered by... Back to Top Site MapContact UsAdvertise With Us Privacy StatementAbout Us  
News RSSSiteseeing RSSArticle RSS   © 1998-2009 FS Media, Inc. All Rights Reserved