Slashdot Mirror


Revolution Horsepower Revealed

Revo writes "IGN.com unveiled leaked specs for Nintendo's upcoming Revolution console today. The system really is about twice as powerful as a GameCube and a far cry from the Xbox 360 and PS3. Of course, the focus is on the innovative controller and the affordable price."

8 of 774 comments (clear)

  1. Different processors by ggareau · · Score: 5, Informative

    Is it just me, or are they completely ignoring that the Gamecube had a PPC chip, and Xbox had an x86 chip?

    On paper clock speed doesn't put the Revolution between the Gamecube and Xbox. It easily puts it above.

    Also, if I recall correctly, the 360 and PS3's processors need to be passed data sequentially, and because of that it makes it much harder to avoid bottlenecks and lag in code, whereas the Revolution's does not.

    It could just be me, but looking at stats on paper mean nothing when you're comapring different architectures and chipsets.

  2. before bashing the controller... by Anonymous Coward · · Score: 5, Informative
  3. Spec Point... Re:Price Point by eonlabs · · Score: 5, Informative

    I'm sorry, but in my opinion, the specs given are still pretty much useless.
    This isn't like the Intel/AMD argument, because each of the chipsets has a different ISA
    It isn't necessarily true that every command executed in the 3.2GHz cores of an XBox 360 will
    constitute one clock cycle. In fact, I'm sure that a method of achieving those awesome frequencies
    is by removing as much functionality as possible from each command the 'core' of the CPU performs.

    The ON-GPU memory is really significant. 3MBs of in chip memory is more valuable than 15MBs of off
    chip memory. It immediatly means that the GPU is able to concurrently manipulate the 3MBs of memory
    as close to 'free of charge' as possible.

    Since it's a gaming machine and doesn't need an independant os for much more than thread management,
    This also means that those 3MBs will probably be dedicated to what is currently on screen.

    From a texture memory perspective, one texel (texture pixel) is 4 bytes, assuming 32 bit color with
    no compression. This means theres room for a million pixels in that memory at one time, or just shy
    of a 1024x1024 pic. That memory can be manipulated quickly too!

    For clarification, that is a REALLY COOL THING!!! That is the amount of data that can be played
    with for FREE internally.

    I don't know about anyone else, but judging by the 'spec' comparisons in the past, Nintendo plays
    their resources to the fullest, and compared to the price tags of the other machines, I'm still
    thinking Nintendo's box is probably going to be pretty nuts.

    On a side note, I'm still not sure I like the idea of the controller...
    I'm a 'reality' gamer, so if my natural habit of diving around while playing is a bad thing to have
    while using a SDoF controller, the system is going to really let me down...
    We'll find out, this is up for grabs for me

    --
    I wouldn't consider the mad hatter mad. Just reality impaired. He sure can make a mean cup of tea.
  4. Re:Price Point by be-fan · · Score: 5, Informative

    All that's been released is the clockspeed of the processors.

    And the fact that the architectures are identical to the Gamecube ones. That means the CPU is basically a 730MHz Gecko and the GPU is a 240 MHz Flipper. The per clock performance of the Gecko chip (which is basically a G3 with integrated cache and the ability to use its 64-bit FPU as a 2x32-bit SIMD engine) is probably quite a bit better than the Xenon, but enough to make up for the enormous clockspeed difference.

    The G3 is a very ancient chip. It has almost no OOO capability. Per-clock, its probably going to be faster than Cell, but considering that the per-clock of the PIII-based core in the XBox is in line with the G4, it won't match up even to the older console in CPU performance. As for graphics chips --- clockspeed times the number of pipelines is an excellent predictor of GPU performance. Only in a relatively small number of cases (eg: the Geforce FX debacle for NVIDIA), has pure fill-rate proved to be a poor predictor of overall performance in the case of conventional GPUs. The integrated memory helps the Flipper chip quite a bit, but given that it h as about the same clock-rate and the same number of pipelines as the XBox GPU, I wouldn't expect much more than that level of performance out of it. Overall, expect the Revolution to perform somewhat like a slightly improved XBox. Between the 1T-SRAM and the familiarity of developers with the GC architecture, Revolution developers should be able to wring substantially more out of the Revolution than they did out of the XBox, but I'd be surprised if the improvement was more than 50%.

    --
    A deep unwavering belief is a sure sign you're missing something...
  5. Re:Ugh, this bullshit again. by kerrle · · Score: 5, Informative

    Yes, but the Art-X team behind the gamecube's graphics chip went on to be heavily involved in modern ATI GPUs. There's definitely a relationship between the two.

    This isn't a case where ATI bought a team just to slap a sticker on the cube; they bought a team and actually integrated it into their development process, and actually used their tech.

  6. Re:Price Point by indil · · Score: 5, Informative

    This includes 16:9 mode.

    Actually, Revolution will be quite capable of 16:9, as is the current GameCube hardware:

    Matt responds: Certainly the capability for progressive-scan and 16:9 widescreen games will be there on Revolution. You can do that on GameCube now.

    Source

  7. Re:Why are you misquoting? by davidmb · · Score: 5, Informative
    Check out the Mirrordot mirror of the story. The original text was:
    IBM's "Broadway" CPU is clocked at 729MHz, according to updated Nintendo documentation. By comparison, GameCube's Gekko CPU ran at 485MHz. The original Xbox's CPU was clocked at 733MHz. Meanwhile, Xbox 360 runs three symmetrical cores at 3.2GHz.
    Seems someone has edited the article.
  8. MHZ myth by cgenman · · Score: 5, Informative

    I've worked on all three platforms. And while I haven't didn't do the coding myself, I have worked with the coders who did.

    The rule of thumb was that if you could do it on the Xbox, you could do it on the GameCube and you would probably have to shave it down to get it to work on the PS2. The problem child you have to worry about in a cross-platform title is always PS2.

    I don't know where Casamassina is getting his assertion that GC polygon peaks were less than the PS2. Does he mean untextured polys? Again the PS2 is generally the platform that you have to optimize for.

    Using MHz numbers to compare the speed of different processors is like comparing the speed of cars by looking at how much gas they consume. There is a relationship there, but it isn't the primary one. And it isn't the one you care about.

    There are all sorts of reasons for performance numbers, such as the PS2's surprisingly fast cache but low ram, etc. I hope someone will do a detailed technical breakdown, because I really should remember this stuff. And also financial pressures play a part: you add optimization time for the Xbox if you think you will sell in North America, and optimization time for the GameCube if you have the possibility of Japan sales. But in general, the Xbox and Game Cube are similar in power, and the PS2 runs to catch up.

    I can't really talk about the Revolution, partially because I don't have one, but I've heard other developers use the "2x more powerful than the GC" figure. That puts it somewhere between the Xbox 1 and the Xbox 360.