Very interesting and informational. Does she work for 343 industries? If so I'm definitely going to be interested how 343's first game stacks up graphically to the industry powerhouses.

yes, she works there. I think the call the people working on the game members of the Halo team, thus her title.

oh no how wrong can someone can be? Cell was different from nay platforms developers were used to work with 1-4 cores,

the ps3 though have 1 PPU and 6 SPUS, 360 its not easier because multithreading  but because they are libraries already done it was easier to harrass it power.

and PPU can be threaded too. as far floating point calculation and threading u should know which cpu it's better. since all spus are 3.2ghz, while u thread 360 u get 6 1.6ghz threads

So THAT'S why MGS hired her. I was completely lost during 70% of this, but I can hear her passion, optimism and competence in what she was talking about. Not sure how 343 gameplay will turn out, but I'm extremely confident in whatever graphics engines they design for the 360 and beyond now.

Obviously you didnt listen to the 35 minute question and answer in the op. If all you got from my comment was that.

In a nutshell. You are missing the point.

PS3 has a weak GPU. First party developers have been showing many 3rd parties how to use the Cell to it's advantage. They have had to learn quick how to utilise multi thread programming.

Now the 360 has had developers be lazy. Now this lady Corrinne tells us that engines on the 360 have not been optimizing the 360 architecture. It was designed with multicore and multithread computing in mind. Yet the 360 produces great results with familiar single core programming. Hence devs aren't bothering with the 360 to utilize new ways. Thats her major point. She wants to see developers building new engines from the ground up. Tghey aren't even using VMX units.

Dont get all butthurt in here because the 360 has much more potential. This isnt a thread for you to downplay 360. This girl has over 20 years experiencing in building game engines. And has worked and is friends with Tim Sweeney and John Carmack. I think I'll listen to her thanks.

I don't think you deserve a response, but here goes.

Sure cell is different. Fine there

Sure the cell has 1 ppu and 6 spu, so what?

No 360 is easier because it has full cores with normal caches.

Sure 360 has better tools.

PPU can be threaded too? Sure the same way the 360 cores can be. Care to complain about that?

Floating Point performance? Sure if you have perfect data structures; sure if you have perfect vectorization; sure if you have perfect pipelining; sure if you have perfect DMA queuing; sure if you are doing simple floating point calculations, The spu's don't have a dot product, cross product,  or fnma instructions.  See how much work can go into getting the Cell's performance up?

That last part is just a joke right?

I'm not going to pretend to be able to follow half of what she said, but her enthusiasm for her work is certainly admirable.

It sounds like she's bursting with information! She doesn't know where to start!!

Glad a lady with this much passion for gaming resides in the Halo world

I like Tina.  I think she works well with Corrine.

XBOX 360 CPU Specifications

* 90 nm process[4], 65 nm process upgrade in 2007[5] (codenamed "Falcon")
* 165 million transistors
* Three symmetrical cores, each two way SMT-capable and clocked at 3.2 GHz[4]
* SIMD: VMX128 with 2× (128×128 bit) register files for each core.[4]
* 1 MB L2 cache[4] (lockable by the GPU) running at half-speed (1.6 GHz) with a 256-bit bus
* 51.2 gigabytes per second of L2 memory bandwidth (256 bit × 1600 MHz)
* 21.6 GB/s Front-Side Bus[4]
* Dot product performance: 9.6 billion per second
* 96.0 GFLOPS theoretical peak performance (single-precision)
* 57.6 GFLOPS theoretical peak performance (double-precision)
* Restricted to in-order code execution[4]
* eFuse 768 bits[6].
* ROM (and 64 kbytes SRAM) storing Microsoft's Secure Bootloader[1], and encryption hypervisor[6].
* Big endian architecture.