Because of of those games offers improvements over the original only possible through an evolution of the design process. Either that $200 game would have to be launched at the beginning of the cycle and so be a 'first-gen title' that's not amazingly fantastical++, or it released later when the developers have had more experience with the hardware. Oh. Which they won't have had. So basically, you'd be constricting games to low efficiency.
I don't agree with this. First of all although working on 3 games in parallel is different than working on one game three times as big as one today (additional level of management) at the same time you have some benefits. Having one technology base utilized by more people is a huge plus: more people, more bugs fixed. Instead of developing 3 engines, you develop one. Middleware market is growing for this exact reason.
There's no reason why huge game cannot be completed on the same schedule a small one would as long as team is proportionally larger.
Also not everyone wants all three WWII shooters. They'd rather spend $60 n a WWII shooter, $60 on a racer, and $60 on Madden. If they can only have one of those games at $200, no matter how good it is, that'll not offer the diversity of gaming they want.
This is true and that's why low budget games won't die. That's why we have an increased activity of Indie developers. I was referring strictly to the AAA titles. More on that below.
There have been a few consoles with very expensive 'super experience' games, and they all tanked. People aren't going to spend $200 per title on gaming. Anyone pursuing that model won't last long!
Some specific examples?
The other possibility is that DVD-sized games live on in the form of downloadables.
This is something I'm not sure about. It's valid for US market, even more valid for Japanese market, but not valid for others. Broadband connection assumption doesn't work for most emerging markets and currently markets with fast connection are pretty much saturated with consoles. In order to grow and achieve 100mln+ consoles sold you need low price tag and a huge variety of cheap titles available. About 75% of PS2s were sold after the price dropped to $200. You need "epic", expensive titles for hardcore gamers and people who love certain type of games and a huge amount of inexpensive ones for the majority of "late" customers. In order to satisfy the first group I believe the way they get developed should change (described previously). The second group mostly cares about volume and less about quality (gameplay experience matter though).
Sorry for dblpost - can't edit own messages.
Great name, seriosly. Xbox 3K became my bet for the next Xbox.
a single x86 system would allow MS to have one developer system rather than need to develop and maintain two - XNA for x86 and XNA for console
Not entirely true. .NET Framework on the console is something MS would bring to 360 sooner or later anyway. It makes perfect sense: MS invested a lot of resources in .NET and C# despite the huge problems with Windows 200x .NET idea.
Maintaining XNA on both platforms isn't really that much of a problem because a lot of the differences are "hidden" below the CLR. Well, not a problem for XNA, problem for app developers - you get a lot of performance problems using XNA on 360.
There's yet another problem with x86: it's a general purpose CPU. In order to make it good for the console AMD (or whoever) would have to strip all the unnecessary extensions. CPU should do the state machine type of logic and number-crunching should be entirely pushed to the GPU. So I believe that with x86 one would go back to early x86 CPUs and strip all the SIMD extensions trying to improve out of order execution at the same time. Multiple simple cores with deep pipe and branch prediction, large cache, separating code and data, CPU even closer to GPU - that's something I would bet on. I don't think anyone will go as multicore as Sony did with PS3. 4 cores seems to be a safe bet.
At the same time I believe consoles would benefit from some of the virtualization technologies of modern x86 CPUs. Back-compat would be a little bit easier (and safer).
The only negative side to going to an x86 derivative is the cost-reduction, part management thing, which I'm sure some sensible lawyers and eager IHVs could work out to everyone's benefit. The whole concept of the XBox was a box to run DirectX, and taking that forwards, the most sensible box is one using the same hardware as the most widespread DirectX platform, the PC.
You assume that 5 years down the line PC will still be a large gaming platform. I don't think that's our future.