Kotaku: It’s awesome that Microsoft added backwards compatibility for (some) Xbox 360 games to Xbox One, but it’s hardly a perfect situation. One of most demanded games for compatibility, Halo: Reach, comes with a crappy frame rate.
Well that sucks. Hope it's sorted out soon
I'm sure it will.
Some backward compatible games don't run as good as the 360 version and I see no sign of them getting fixed. Maybe it's just going to be a mixed bag with software driven backward compatibility tiles. Another words performance may vary title by title which sucks.
@The_Infected One of the reason's why I decided to keep my old console's just in case BC didn't work that well. Always good to have a plan B. I still have the first Xbox.Hopefully they work it out though because Halo Reach is a great game.
Gears of War 2 and 3 still run rather poor through emulation. I agree, it's best to keep your Xbox 360 if you want to re/visit older games.
@shadowknight I kept my 360 and ps3, even though I don't play games on them very much anymore. It's nice to know if I ever want to go back I can, but my backlog is ridiculous as it is with current gen titles...I even have games through psplus and xbox live gold like God of War Ascension and The Witcher 2 sitting there, waiting to be played, and I have no idea when I'll find time for them. I guess it's a good problem to have, all things considered.
@Genuine-user my favorite games on the 360, it was sad to see them with bad frame rate issues thru bc.
I don't remember it running particularly well on 360?
for the most part it did but there were certain sections in the campaign where frame rate got super choppy. particularly at the end of the sword base mission where you shoot banshees out of the sky with a rocket launcher. and final waves of firefight. even the bonus rounds with grunts only in firefight.
Yep haven't played through it again yet because of the frame issues, hopefully this can be fixed with an update or patch
If the guy in the 2nd video is saying its unplayable then why did he continue playing it if its that bad , that doesn't make sense
I have seen other videos that state that the deeps occur at certain areas. Reach always had deeps on 360 during certain battles/set pieces. Oddly digital foundry is not doing framerate tests on 360 emulation.
They actually did a video praising it while playing Fallout 3 via BC. OT: I was going to purchase this since I haven't played it, but I'll hold off for a bit.
So i guess you can't ask questions on here about something from the article going by the disagrees
? He made the video to demonstrate how poorly the game was running.... How on earth is he going to do that if he isn't playing the game?
The point that it's not in the MCC at 1080/60 really is too bad. Game had such a beautiful art direction, it really would have shined. My favorite story and would have been fun to play co-op on dedicated.
The single player has constant hitches but the five multiplayer matches I have played ran very smoothly
Hope they just add it to MCC at 60fps
Its not as horrible as they make it sound.
Hopefully they iron out all the issues.. I want the xb1 to be fully patched up and ready to game whenever i decide to buy a slim model.. If they make a slim model
its not just reach. I've had major issues running gears 3 and judgement. horde is almost unplayable in gears 3. super bummer
Horde is playable. I've been playing with no issues
is the frame rate absolutely locked to 30fps and is butter smooth? or does it get choppy?
Its still playable nevertheless. I haven't really noticed them, that doesn't mean they're not there
It does not run smoothly, but it does run alright.
This happened when 360 emulated the original Xbox games. One of the reasons I stopped KOTOR 2 on 360 was the glitches
N4G is a community of gamers posting and discussing the latest game news. It’s part of NewsBoiler, a network of social news sites covering today’s pop culture.