[fearsomepirate]

Farid, formerly Vysez, said something about such a thread here. Having followed the thread since the beginning, I thought I'd summarize:

There have been a couple interviews, both translated, one from Nintendo and one with Ubisoft (not the spurious one I posted a while ago, sorry about that) that indicated that the WiiGPU does not have modern shaders. We are likely dealing, then, with either a fixed-function T&L or something programmable, but not as powerful as a vertex shader.

As for games, every Wii game that was introduced in some clip or another with advanced-looking self-shadowing completely lacked it in the final build, and we are seeing way more bullshots than we ever saw for Gamecube (a bullshot meaning a devshot that isn't even running on the game engine with game assets, not just something in high-res with 16x FSAA). The devs of Heatseeker claim that the final build will have self-shadowing; likely it will be Factor5's implementation--or the devs could be BSing us. We have yet to see more than a few effects in Wii games that we haven't seen in Gamecube games, and what few we have seen have mostly been in Red Steel. But what we have seen are substantially more fillrate-burning effects like motion blur, depth of field, light bloom, and various transparency effects that make use of indirect texturing, more than we'd expect from a 50% overclock. We're seeing pretty consistent 480p and widescreen, and framerates are mostly OK. Unfortunately, we're not seeing FSAA or AF. We're not seeing fully-normal-mapped (or even detail mapped) scenes, and we likely won't. IGN has been rather useless, as Matt C seems to be completely unaware of what Gamecube was capable of in the first place. Julian Eggebrecht has expressed disappointment and just how poorly developers seem to understand the hardware.

Fanbois continue to crawl out of the woodwork with dreams about GPUs in USB dongles, extra RAM in flash cards, secret untapped potential to be unlocked in a future firmware update, advanced vertex shader effects being magically done with a texture unit, and so on. They are summarily ignored.

The big mystery in all this is what the extra transistors in Hollywood are for. Flipper was 106 mm^2 on a 180 nm process. Hollywood is 72 mm^2 on a 90 nm process, making it too big for just a process shrink. So what's in there? Extra pipelines and texture units? A more complex T&L engine? Registers for 32-bit color? We don't know. Upcoming titles to look at are Heat Seeker and Metroid Prime 3. Also, at 19 mm^2, Broadway has a little more die space than the 16 mm^2 PPC 750CL.

Edit: This prose summary has been followed by charts, facts 'n' figures, pictures, links, quotes, and other stuff by StefanS below. Think of this as an abstract.

[StefanS]

I'll do a proper summary once I've finished browsing the big one, so stay tuned.

EDIT: page 82 phew...

[TheChefO]

Originally Posted by StefanS

I'll do a proper summary once I've finished browsing the big one, so stay tuned.

Thank you both for your efforts! Much appreciated.

[StefanS]

Ok, I never want to do that again. I need to forget that thread or I'll have nightmares about it... Another thing I want to point out beforehand: this is just the bare summary and I tried to stick to the "facts" as close as possible

I'll start off with the hard facts (100% confirmed), followed by the nearly 100% confirmed (if possible I'll try to cite multiple sources). So let's start:

A look inside Wii



Wii dismantled:
http://pc.watch.impress.co.jp/docs/2...1/nintendo.htm
http://pc.watch.impress.co.jp/docs/2...9/nintendo.htm

Nikkei article (thanks to Mmmkay)

From the article:
Broadway - 4.2mm × 4.5mm (18.9mm2)

Hollywood:
GPU - 9.0mm x 8.0mm (72mm2)
1T-SRAM - 13.5mm x 7.0mm (94.5mm2)

compared The "Gekko" (CPU) in the first GameCube occupied 43mm2.@ 180nm
Flipper 110 mm2@180nm


Schematics
Scheme

source Goto article on future revisions; see also http://www.beyond3d.com/articles/futureconsole/


Memory:
64 MB GDDR3 + 24 MB 1T-SRAM + embedded RAM (most likely 3 MB like Flipper)
Specs of the GDDR3 (found by zeckensack)

Originally Posted by Maxconsole Net

External Main Memory (MEM2)
Wii uses 64 megabytes of GDDR3 (MEM2) as external main memory. Like internal main memory, MEM2 can be accessed directly from Broadway and the GPU at high speed and has a peak bandwidth of 4 gigabytes/sec. Programs can also be placed in MEM2.

Broadway:
Official:
SOI by IBM
90nm

Goto:
http://pc.watch.impress.co.jp/docs/2.../kaigai301.htm
* "Broadway based on Gekko" & customized 750CXe; theafu claims to have insider knowledge and it's a 750CL LINK; my money is on Goto, though

Maxconsole Net
Maxconsole Net's specs
Note: the maxconsole net specs have been backed up by at least 2 other sources (
Different source backing up the Max Console specs).

Originally Posted by Maxconsole Net

• Operating speed: 729 MHz
• Bus to main memory: 243 MHz, 64 bits (maximum bandwidth: 1.9 gigabytes/sec)
• 32-kilobyte 8-way set-associative L1 instruction cache
• 32-kilobyte 8-way set-associative L1 data cache (can set up 16-kilobyte data scratch pad)
• Superscalar microprocessor with six execution units (floating-point unit, branching unit, system regis
ter unit, load/store unit, two integer units)
• DMA unit (15-entry DMA request queue) used by 16-kilobyte data scratch pad
• Write-gather buffer for writing graphics command lists to the graphics chip
• Onboard 256-kilobyte 2-way set-associative L2 integrated cache
• Two, 32-bit integer units (IU)
• One floating point unit (FPU) (supports single precision (32-bit) and double precision (64-bit))
• The FPU supports paired single floating point (FP/PS)
• The FPU supports paired single multiply add (ps_madd). Most FP/PS instructions can be issued in
each cycle and completed in three cycles.
• Fixed-point to floating-point conversion can be performed at the same time as FPU register load and
store, with no loss in performance.
• The branch unit supports static branch prediction and dynamic branch prediction.
• When an instruction is stalled on data, the next instruction can be issued and executed. All instructions
maintain program logic and will complete in the correct program order.
• Supports three L2 cache fetch modes: 32-Byte, 64-Byte, and 128-Byte.
• Supports these bus pipeline depth levels: level 2, level 3, and level 4.
Reference Information: Broadway is upward compatible with Nintendo GameCube’s CPU (Gekko).

Hollywood
Official:
Hollywood designed by ATI
90nm
embedded DRAM
LSI

Goto:
http://pc.watch.impress.co.jp/docs/2.../kaigai301.htm
* GPU lacks shaders -> TEV texture combiners

Maxconsole Net

Originally Posted by Maxconsole Net

Hollywood GPU

Hollywood is a system LSI composed of a GPU and internal main memory (MEM1). Hollywood is clocked at 243 MHz. Its internal memory consists of 3 megabytes of embedded graphics memory and 24 megabytes of high speed main memory.

Hollywood includes the following.
• Graphics processing unit (with 3 megabytes of eDRAM)
• Audio DSP
• I/O Bridge
• 24 megabytes of internal main memory
• Internal main memory operates at 486 MHz.
Maximum bandwidth between Hollywood and internal main memory: 3.9 gigabytes per second
• Possible to locate a program here
Reference Information: Hollywood is similar to Nintendo GameCube’s Flipper and Splash components.

Engadget (Comments section)
Different source backing up MaxConsole

* GPU has no shaders, fixed function, nothing new (it is an upgraded flipper)
..

Matt from IGN also pointed to no shaders (Disclaimer: It's Matt!)


so far we've also seen dithering problems in Wii titles -> GCN legacy 24bit incl. alpha???. See post here



about the TEV
Old GCN article on the features of the TEV
old thread on TEV with comments from ERP
Ingenu post with old Flipper patents incl TEV

[TheChefO]

Stupid question:
Why didn't they take the same silicon design they have here and clock it higher for better performance?
or
Simply take the same GC and overclock it using the latest process shrinks to achieve better performance and near zero R&D?

I know they wanted a small quiet box, but 65nm was/is right around the corner which would enable a smaller quieter box while at the same time providing a more significant bump in ability over GC.

From looking through the thread and following a few links it seems Wii certainly has a decent advantage over GC but it just seems odd that they would invest as much into R&D as they did only to match what would seem possible by just Oc'ing their current designs.

Am I missing something?

*outside of memory systems*

[swaaye]

They didn't need a much better process for more speed. The chips are limited by 1) the eDRAM 2) plain design. That PowerPC isn't designed for super high clock, for example. It's not a matter of simple size reduction. The design itself must be tailored with a clock speed in mind. I bet there's also a sizable amount of clock speed shied away from simply to maximize yields.

Plenty of vastly more powerful and larger GPUs have been built on even 150 nm.

My view is that they built Wii to be extremely cheap. They put some R&D into the new controller though. But, still.... And, of course, their campaign calls for warm fuzzies about developer ease, low prices, etc.

[ninzel]

The only reference I could find on Ubisoft speaking about shaders.
"Ubisoft’s Ancel on Wii’s Graphics: “In terms of visuals, if it’s fluid, if you can understand the picture, that’s enough. The number of polygons does not make you laugh or cry. We did a lot of good looking games on this generation of graphics processors. The Wii hardware is more powerful than those, so that’s good enough for us. We’re using our energy on gameplay and new ideas more than on shaders and things like that…The hardware capabilities aren’t a limitation. It’s more a question of coming up with new ideas than worring about technical specifications. With the Wii, it’s all about having fun.”

[pc999]

Very nice, I would just add that the CPU is also bigger than expected and we are certain of this because Broadway is 19mm^ and the 750CL, which is already a superset of Gekko , does have a die size of just 16mm^, so the Wii CPU is also upgraded. We dont know what are the upgrades in it.

[Urian]

I have a question.

Is possible that Gamecube-Wii graphical part is more dependant of the exclusive graphics API for GCN than the hardware itself?

[Corwin_B]

I seem to remember a dev (from Konami ?) speaking about accelerated physics in the Wii hardware ?

Here it is : Elebits Interview

Konami: Yes, the structure is very similar to GameCube, but you already knew that. The development was not that difficult, as the Wii system has built in physics simulation. That helped the process.

[Shifty Geezer]

He didn't say about accelerated physics. He was asked about development. Development is easy - the Wii system has built in physics simulation. By that I understand the development system, Software tools, has a physics library included. Thus adding physics to a game built on an existing GC-style development kit is easy. Talking about hardware accelerated physics makes no sense in a question about development difficulty. The presence of physics accelerating hardware makes no difference. It's the software to implement the physics on whatever hardware is there that matters to development difficulty.

[compres]

I agree with shifty. The tools are what provide easiness for developers. However at this point we can't exclude the possibility that the extra transistors are in some way related to physics acceleration.

I have been considering this a likely possibility given the lack of performance or effects in the Wii titles.

[fearsomepirate]

Originally Posted by compres

However at this point we can't exclude the possibility that the extra transistors are in some way related to physics acceleration.

Yes, we can. The only hardware physics accelerator out there right now is basically a large chip full of large vector units. The extra die space in Broadway is nowhere near large enough for this kind of hardware.

[pc999]

Originally Posted by fearsomepirate

Yes, we can. The only hardware physics accelerator out there right now is basically a large chip full of large vector units. The extra die space in Broadway is nowhere near large enough for this kind of hardware.

What would stop them of puting a single vector unit, on them certanly it would boost physics (relatevely to just the CPU) and it wouldnt be expensive.

I do not expect it, but it is possible.

[Shifty Geezer]

I guess it's the idea of specific physics acceleration that makes no sense. If you're going to put acceleration hardware in there, but only a small amount, you may as well just put in versatile vector units for accelerating physics or anything else. If Broadway includes any 'acceleration' hardware, my guess is it's some sort of VMX units, at which point we can't really call it a physics accelerator, unless it's left inaccesible to the developers except through the physics component of the SDK.

[Ooh-videogames]

This thread will eventually to be just as large as the previous one. For every visually great looking Wii title, there will and must be a discussion. There's GFX features that may appear that were previously believed not possible appear on Wii. Just like fur rendering or per-pixel lighting on GC. It has now become a part of the appeal of Wii, its a mystery console technically.

I expect to read some pretty interesting arguments and discussions.

[ATI-liens]

Considering they have used a G5 processor,which is more then likely or even common sense, at 729Mhz and 90nm the processor is bound to be atleast twice the performance of the Gekko. I don't think they are going to reduce the number of transistors in a G5 to match the 750CL, makes no sense, none of the technology in the system is old, the 1T-Sram even has faster latencies then the NGC's.

750CL a power consumption is just under 2 watts.

The whole Game Cube uses 39 watts
The Wii uses 53 Watts

If the aim of the game was to use the same number of transistors as the NGC but just clock it slightly faster in 90nm the Wii would consume about the same power as the NGC which is not the case.

http://tomshardware.co.uk/2006/10/04...erpc_lowpower/

"The chips could also find their way into independent game consoles" Toms Hardware. (The PS3 already uses a 970 for the PPE)

The 750CL and 970GX are the mian low power cpu's so the Wii is most "likely" to use the 970GX.

The 970Gx consumes 10 watts of power @ 729Mhz, and im sure we have all seen news of the ATI mobility GPU's low power consumptions,

My Nvidia Quadro 3400 uses about 85 Watts,

Radeon mobility X1000 series are designed to operaten laptops that total to aound 80 Watts. (Powerplay 6.0 technology, sounds ideal for the Wii)

So realistically it's more likely that Nintendo has chosen to use a downscaled G5 and Radeon X1000 in the making of the Wii.

Just an opinion!

[ERP]

Matt from IGN also pointed to no shaders (Disclaimer: It's Matt!)

I've said this before but Matts sources are actually very good..... You do have to read around his interpretation sometimes, but the basic information is usually accurate.

[pc999]

Originally Posted by Shifty Geezer

I guess it's the idea of specific physics acceleration that makes no sense. If you're going to put acceleration hardware in there, but only a small amount, you may as well just put in versatile vector units for accelerating physics or anything else. If Broadway includes any 'acceleration' hardware, my guess is it's some sort of VMX units, at which point we can't really call it a physics accelerator, unless it's left inaccesible to the developers except through the physics component of the SDK.

Overall I agree with this, which also lead to expect even less any accelaration of whatever.

Originally Posted by ERP

I've said this before but Matts sources are actually very good..... You do have to read around his interpretation sometimes, but the basic information is usually accurate.

I think what the disclaimer should be mainly because the way things are presented can lead to incorrect information, ie having no shaders dont mean that there will be no shading at all on any form in any game on the Wii (which had been the imediate conclusion of most people).

It is just a warning before one read to much into what Matt says.

[fearsomepirate]

Originally Posted by ATI-liens

So realistically it's more likely that Nintendo has chosen to use a downscaled G5 and Radeon X1000 in the making of the Wii.

No, that's not realistic. Broadway's die is way too small, and the clockspeed is way to low to be just a G5 variant. Hollywood's die, although bigger than a shrunken Flipper would be, is also pretty small. And then there are the multiple "no shaders" comments from developers and industry insiders. Your imagined hardware was realistic before we learned as much as we know now. Now, we're about 95% sure it's an improved variant of Gamecube hardware.

[StefanS]

Originally Posted by ERP

I've said this before but Matts sources are actually very good..... You do have to read around his interpretation sometimes, but the basic information is usually accurate.

No disagreement here. It's just he mixes things up a bit all the time. As you said his sources are usually good. He was the first to unveil the clock numbers, for example. I just wanted to make sure nobody bites my head off.

[StefanS]

Originally Posted by ATI-liens

"The chips could also find their way into independent game consoles" Toms Hardware. (The PS3 already uses a 970 for the PPE)

The 750CL and 970GX are the mian low power cpu's so the Wii is most "likely" to use the 970GX.

The 970Gx consumes 10 watts of power @ 729Mhz, and im sure we have all seen news of the ATI mobility GPU's low power consumptions,

If MaxconsoleNet specs are to be believe - and so far there's zero reason to doubt them - Broadway is definitely not a 750GX. 750 GX has 1MB L2 cache for starters. It's either a customized 750CXe or a slightly customized 750CL.

[Megadrive1988]

Originally Posted by StefanS

I'll do a proper summary once I've finished browsing the big one, so stay tuned.

EDIT: page 82 phew...

hehe, blame me for starting the biggest thread of my B3D career, and one of the longest threads here in recent times i think

[ninzel]

Are there actually quotes from devs saying that the Wii has no shaders? I've never read that from anyone besides Matt.

[StefanS]

Originally Posted by ninzel

Are there actually quotes from devs saying that the Wii has no shaders? I've never read that from anyone besides Matt.

Goto said the same (check the summary).