According to the Inquirer, all the initial release games on the XBox 360 will be single threaded.
Quote:
During a talk on multithreaded programming, Microsoft used the three core, two thread per core Xbox360 as an example.
The bombshell was that the first generation of Xbox titles, all of them, are single threaded. Not good.
I'm assuming the Microsoft Spokesperson is referring to first party titles, but this is interesting if it holds true, we could see a larger than normal gap in the quality of titles between the first gen/second gen release. Of course, this was from the Inquirer.
This isn't anything unexpected, and as the article mentions the PS3 launch titles are likely to be even worse. Most these games were already in development for the Xbox and just got shifted over to the 360. Then there's the learning curve for developing for the new system. This is why I'm in no rush to get a 360 at launch...
The inquirer is right way more than they are wrong... Plus if pgr3 looks and runs as good as everyone is saying then once they do start multithreading watch out!!!!
/of course once they start multithreading *** will come out with the quantum powered xbox2060p which will only be using one quantum..
__________________
Xboxlive Tag = Tennistoad2k7
N-PRO OPEN
Patriots 19-0
This is old news...Epic commented on this and the difficulties of coming up with a multithreading architecture. In fact they made it sound like even the best minds in the industry like Tim Sweeney and John Carmack are up against a formidable challange in coming up with multithreaded versions of their game engines.
Could be interesting...this may be a case where the technology is years and years ahead of the software.
In my efforts to write a multithreaded game engine it was very difficult coming up with a game loop that allowed for the concurrent access to the game data by the rendering, physics, and AI engines. Generally speaking the rendering engine is waiting on the physics engine which is waiting on the AI engine to update the game state.
Not an easy challange and we shouldn't be surprised if all these additional CPUs are spent doing nothing but loading level data to spare us those uncomfortable 20 second level load times.
In my efforts to write a multithreaded game engine it was very difficult coming up with a game loop that allowed for the concurrent access to the game data by the rendering, physics, and AI engines. Generally speaking the rendering engine is waiting on the physics engine which is waiting on the AI engine to update the game state.
My two cents....
My head just exploded.. It was already hurting after watching Primer last night and now you just finished it...
__________________
Xboxlive Tag = Tennistoad2k7
N-PRO OPEN
Patriots 19-0
I thought that this was already known considering that at E3 most major developers were saying that multithreading will not fully take hold for another 2 or 3 years. The problem is that devs are pretty much limiting their options right now if they choose to build an engine from the ground up based on multithreading, as their only real market would be the 360, and the investment is still too big too risk.
