rokkerkory
Member
Just like it did on 360? lol
Just like the monthly OS updates on the X1 "lol"
Just like it did on 360? lol
Really? You don't? Maybe because the Xbox One isn't really a 360?I still don't understand why users have to download a new version of every game
lol, wasn't there a thread claiming ME was better than it was on 360 yesterday?
This is... very strange. It shouldn't be a huge deal to support output higher than 1080p, especially since it's already rendering at this resolution should it?
If even a good percentage become good quality experiences, it will not be 'pointless', c'mon.As expected. Software emulation is going to be a challenge for every game having different results. 5 to 10fps slower for Mass effect which already ran pretty bad in the citadel on 360 is just not even worth it just to say i can play it on XB1.
Throw in no enhancements like 4xMSAA like 360's OG Xbox emulation and its just pointless...and for what, how long is it going to take to say the limited amount of games all run at an 'acceptable' quality on XB1? Cause they probably aren't ever all going to run at full original speed just by the nature of how they are being played.
Because it's the only remotely impressive game on the compatibility list?
For anyone who missed it.
http://www.neogaf.com/forum/showthread.php?t=1066097
Hmm.
I trust DF more, but it's interesting how both reached such wildly different conclusions.
*Load times are usually faster (little better to 2-3 times shorter)
*Textures are usually instant compared on XB1 to the usual Unreal 3 pop-in
*XB1 has no screen tearing due to V-Sync but the framerate appears slower because the game waits for the full frame to draw because of it.
Yeah as in not via cloud streaming! Was pretty obvious what he meant imo.Yes, but he made sure to mention the word 'natively' on the Microsoft E3 press conference.
Viva Pinata's a much better looking game than Mass Effect.Because it's the only remotely impressive game on the compatibility list?
Really now. I would expect continued refinement and improvements to come along as the emulation matures. Just like all other OS improvements.
Yeah as in not via cloud streaming! Was pretty obvious what he meant imo.
Viva Pinata's a much better looking game than Mass Effect.
Native means it's running on the hardware, which it is.That's not what 'native' means though.
Right. People are going to nitpick this, but obvious there isn't actual X360 hardware in the system...Yeah as in not via cloud streaming! Was pretty obvious what he meant imo.
Why did Spencer even say that the Xbox 360 games run 'natively' on Xbox One? It was obvious from the get-go that it was emulation.
If even a good percentage become good quality experiences, it will not be 'pointless', c'mon.
Yeah as in not via cloud streaming! Was pretty obvious what he meant imo.
Native means it's running on the hardware, which it is.
Can someone post a less oblique angle screenshot of Viva Piñata on BC?Agreed and it works great and loads quicker than it did on 360.
Still so much salt over this though...
Well, before they announced backwards compatibility the conventional wisdom was the Xbox One's CPU was simply not nearly fast enough to emulate the 360's. When MS promised "hundreds" of games by this holiday that threw some doubt on the matter. But after seeing the performance they are currently getting with the oldest 360 games it probably turns out we were right in the first place. Now their E3 announcement comes across as borderline irresponsible. Pinning our hopes and dreams on another bottle of "special sauce" is as foolish now as it has been since the Xbox One's specs first leaked.
As long as the visualization works, that is a purely academic differentiation that has no bearing on any consumer-facing discussion.If this is another case of marketing changing established concepts to suit its needs, just like it did with "exclusive", then so be it. But let's not fool ourselves: emulated game do not run natively.
'Our' hopes and dreams? This is concern trolling at its finest.Well, before they announced backwards compatibility the conventional wisdom was the Xbox One's CPU was simply not nearly fast enough to emulate the 360's. When MS promised "hundreds" of games by this holiday that threw some doubt on the matter. But after seeing the performance they are currently getting with the oldest 360 games it probably turns out we were right in the first place. Now their E3 announcement comes across as borderline irresponsible. Pinning our hopes and dreams on another bottle of "special sauce" is as foolish now as it has been since the Xbox One's specs first leaked.
As expected. Software emulation is going to be a challenge for every game having different results. 5 to 10fps slower for Mass effect which already ran pretty bad in the citadel on 360 is just not even worth it just to say i can play it on XB1.
Throw in no enhancements like 4xMSAA like 360's OG Xbox emulation and its just pointless...and for what, how long is it going to take to say the limited amount of games all run at an 'acceptable' quality on XB1? Cause they probably aren't ever all going to run at full original speed just by the nature of how they are being played.
The games run natively in the OS, the OS is emulated to run within the X1.That's not what 'native' means though.
It's not emulation, it's virtualization.
Emulation translate old code to new hardware. Virtualization runs native code.
Native means it's running on the hardware, which it is.
However MS does with bc, I'd take it over lame PSnow streaming on PS4
apples to oranges, I know but still I applaud them for tackling this head-on
yay for competition
DF assumes that this is the source of the performance problems, but I don't think that is a completely safe assumption, either. May well be that they'd still run worse, but with tearing on top of it.Well reading through the article it seems obvious that they have to turn off V-Sync on games that didn't have it to begin with. It would have been interesting if that was an option in the emulated 360 guide.
Like I said above, the games run natively in the OS. The OS has been changed to run within the X1.If the original code wasn't designed for the Xbox One hardware, it's still not running natively. It's a misleading use of the word no matter how you slice it.
No offense meant, but doing that is obviously twisting the meaning of "running an application natively". Using an emulator to run a game locally, instead of streaming it from a server, is not "running it natively". If it were a native application, the game wouldn't need an intermediary layer between itself and the hardware to "translate" the game into something the Xbox One can read (which is exactly what emulation does).
If this is another case of marketing changing established concepts to suit its needs, just like it did with "exclusive", then so be it. But let's not fool ourselves: emulated game do not run natively.
No. "Native" means that it is written to run directly on the hardware. These games are emulated: they need another program that bridges their coding and the hardware, since they otherwise wouldn't "click" with each other. It's the difference between "software backwards compatibility" (i.e. an emulator) and "hardware backwards compatibility" (i.e. actual hardware from a previous console inside the newer box, as early model PS3s used to have).
If the original code wasn't designed for the Xbox One hardware, it's still not running natively. It's a misleading use of the word no matter how you slice it.
It's emulator enhancements.. emulation hardware so they need to fix that.
Like I said above, the games run natively in the OS. The OS has been changed to run within the X1.
One of the developers posted on the X1 reddit, saying they've had to do little to no changes to support each of the games.
I assumed it was part of the problem but I don't believe it's the only source of issues.DF assumes that this is the source of the performance problems, but I don't think that is a completely safe assumption, either. May well be that they'd still run worse, but with tearing on top of it.
If it ran natively, it wouldn't have required any changes at all and any Xbox 360 game would have worked.
Well if you've got a 360 game which is practically written in assembly, and its doing things slightly different to the last game, your going to need to add more logic within the virtualisation layer.If it ran natively, it wouldn't have required any changes at all and any Xbox 360 game would have worked.
If the original code wasn't designed for the Xbox One hardware, it's still not running natively. It's a misleading use of the word no matter how you slice it.
Gotcha.I assumed it was part of the problem but I don't believe it's the only source of issues.