All the speculation indeed turned out to be true and, performance wise, the game plays exactly the same, if not better than on the original Xbox, with no slowdown or hiccups. Interestingly, the textures seemed more crisp, perhaps due to the more advanced anti-aliasing.
xbdestroya said:The fact that all the other titles they tried had some sort of issues though, that's what I found surprising. I was thinking that the number of games with issues would be a definitie minority.
_leech_ said:I don't know, this was exactly what i was expecting. It was pretty clear right from the start that Microsoft had no intention of adding backward compatibility to the X360 to begin with, they've been struggling to stitch it on after Sony's announcement.
xbdestroya said:I have to say though, if it was just going to be Halo and Halo 2, they might as well *not* have made it B/C. People prefer a non-feature to a poorly implemented one when reflecting on the quality of their purchase. Oh well whatever, like I said I'm sure they'll workit out eventually. At the very least I would hope Ninja Gaiden and the other 'biggies' get proper B/C.
Joe DeFuria said:Is there any reason to believe that game-pro's experience is going to be the actual initial OOTB experience when the actual product ships?
In all honesty I would say the answer is 'yes,' since at this point I have to consider Game-Pro for all intents and purposes as having an 'actual product.'
_leech_ said:I don't know, this was exactly what i was expecting. It was pretty clear right from the start that Microsoft had no intention of adding backward compatibility to the X360 to begin with, they've been struggling to stitch it on after Sony's announcement.
scooby_dooby said:You make it seem like MS was taken by surprise when Sony announced BC...
Qroach said:Well thats where you are wrong. They are using a "debug" kit, and not a retail xbox. it's for games that are in development, not finished games.
Sheesh calm down - I'm hardly raising a flag here - I was simply explaining my logic.
That being said though, what would inherently be different on the debug kit in relation to the retail when certainly the 360 B/C emulation via the hard drive must be locked in since several months ago? Patch downloads I can understand, but in that case the performance between the two - again - should not be too inherently different.
xbdestroya said:That being said though, what would inherently be different on the debug kit in relation to the retail when certainly the 360 B/C emulation via the hard drive must be locked in since several months ago?
Qroach said:There's a hardware and software difference between retail kits and debug kits. The software on debug kits needs to be manually updated by developers with each Xdk release. basically they blow everything on it away and give it a fresh install with each new Xdkversion. As I was saying before, it could be that this debug box has an older version of the emulation software...
Joe Defuria said:Why must it have been locked down several months ago?
Why should debug kits have all of the latest and greatest B/C libraries for all the games?
I just don't understand why "alarm bells" are going off. Certainly, there's going to be issues with many games and B/C upon launch. But we're just going to have to wait until final "off the shelf" kits are reviewed to find out.
Or maybe it's the Bleem effect where since it's running on an emulator it can use more advanced features from the new GPU._leech_ said:Probably a placebo effect, like N64 players who used the 4MB RAM expansion on games that didn't support it and claimed improvements.