Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Perhaps optical drives are just not an option anymore? You can buy HDD for as low as $30 and it has more space and better speed than DVD. Back to SNES carts?Xbox: 2x-5x CAV (2.6MB-6.6MB/s); 64MB memory = 10-to-24 seconds
Xbox 360: 12x DVD (15.85MB peak); 512MB memory = 32 seconds (even higher at non-peak)
I think what we'll see from MS is GPU embracing some of the stuff CPUs do. Virtual memory (memory manager for GPU) is something Carmack's latest engine would benefit from.The next 2 years will tell us a lot. There are a lot of rumblings of embedded memory migrating into GPUs in more native/intuitive ways (i.e. more friendly that a large pool that may require software based tiling). I wouldn't be surprised if MS and Sony diverge some. e.g.
I disagree with that. It'll be more in MS's favour to use the 'x86' multicore architectures ofthe time giving developers another easy ride in PC friendly development. I think Xenon was a stop-gap to offer affordable multicore when there were no other viable solutions and never a long-term architecture like Cell. By the next console, Intel and AMD will both have architectures to choose from. AMD will probably do a sweet bundle deal of CPU+GPU, and at the moment that's my guess for the next XB's innards.XBOX360NG - 6 core Xenon with more cache, 1024MB RAM, 25MB EDRAM
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.Do we really have to buy 3 WWII games for $60 each? How is it better than one for $200?
I disagree with that. It'll be more in MS's favour to use the 'x86' multicore architectures ofthe time giving developers another easy ride in PC friendly development. I think Xenon was a stop-gap to offer affordable multicore when there were no other viable solutions and never a long-term architecture like Cell. By the next console, Intel and AMD will both have architectures to choose from. AMD will probably do a sweet bundle deal of CPU+GPU, and at the moment that's my guess for the next XB's innards.
hello Shifty!
Don't you think that it would be better for the sake of discussion clarity to merge this thread with the one opened an year earlier by Joshua?
I disagree with that. It'll be more in MS's favour to use the 'x86' multicore architectures ofthe time giving developers another easy ride in PC friendly development.
As nice as it would be for x86 to return to consoles, I have to keep in mind that MS does own the IP designs in the 360. It would make sense to develop that further. Factoring in the royalties and monies being paid out, I would think MS would rather keep going with what they already own.I think Xenon was a stop-gap to offer affordable multicore when there were no other viable solutions and never a long-term architecture like Cell. By the next console, Intel and AMD will both have architectures to choose from. AMD will probably do a sweet bundle deal of CPU+GPU, and at the moment that's my guess for the next XB's innards.
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.
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.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.
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.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.
Some specific examples?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!
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).The other possibility is that DVD-sized games live on in the form of downloadables.
Great name, seriosly. Xbox 3K became my bet for the next Xbox.XB3000
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.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
You assume that 5 years down the line PC will still be a large gaming platform. I don't think that's our future.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.