@lundy86_4 said:
Plus, i'll add to this discussion... It didn't negate any point. Cows have said that BC was a waste ever since MS announced X1 BC.
Id doesn't negate the fact that lemmings didn't care for BC until MS was the only one with it.
And is documented here and you were HERE when that happen,the PS3 had the biggest BC ever for a console and lemmings didn't care.
Is a fact not my opinion.
@i_p_daily said:
And yet you can rent PS3 & PS2 games, so its BC only difference is that Sony charge you for it, the company that is "for the payers" lol.
You rent PS2,PS3 and PS4 games is not BC,saying something as stupid as that is like saying you are paying for backward compatibility with DVD,blu-ray and vhs when you pay for netflix or hulu.
It makes zero sense what so ever.
But hey MS charge you for xbox and xbox 360 games on gamepass so that means you are paying for BC as well,and is not my problem is you use the games or not they are included on a charge to play service.
Can't have it both ways you know.
@ronvalencia said:
PS4 CPUs can emulate PS3 games equivalent to Xbox 360's 3X PPEs usage level. Not all PS3 games has used the full six SPE cores.
If PS3 game used SPEs to patch the old RSX GPU's features on top of PPE+ two SPE units workload, then it's problematic for PS4's CPU to emulate.
Almost all PS3 games use cell SPE in one way or the other,again the Jaguar inside the PS4 not even the one inside the Pro can emulate Cell period it lack the power to do so.
Sony would have to move Cell process to GPU at least the ones that could not be emulated which mean it would be on a case by case and extremely cumbersome.
Just look at Naughty Dog article on how the ported The Last of US to PS4 they basically had to re write allot of the code to make the game run.
@ronvalencia said:
Xbox One's BC with Xbox 360 wasn't after though since XBO's GPU has semi-custom FP10 handling and Jaguar CPU already has server grade virtual machine instruction set.
Xbox One's GPU ROPS behaves like Xbox 360's ROPS in relation embedded memory access, but extra memory access (read/write) feature to DDR3 memory. XBO hardware feature is removed from Xbox One X and it's emulated or translated.
X86 Bswap instructions are big-endian (e.g. PowerPC, 68K) to little endian (e.g. x86) data format conversion instruction i.e. X86 world have been dealing with big endian CPUs since 68K vs X86 CPU wars.
https://blogs.oracle.com/solaris/optimizing-byte-swapping-for-fun-and-profit-v2
AMD64's Bswap instruction is faster. This is important for X86 CPU emulating big-endian CPU like PowerPC.
https://hardware.slashdot.org/story/17/10/23/229212/why-xbox-one-backward-compatibility-took-so-long
3rd generation Xbox design started back in 2007. Incidentally, this is a similar time period when Apple dumps PowerPC.
BC was NOT an after though of MS
Building PowerPC emulator is not easy.
Stop the bullshit MS damage control will not change anything.
BC was an after though on xbox one and it wasn't announce until summer 2015,if it was a feature that would be set to go it would have been announce since launch,lets not forget that MS announced features that were not on the console on launch why was BC any different?
Anything that was add latter and announce after 2013 was an after thought as simple as that.
The article you are linking there is MS bullshit damage control it was an after thought it was late and it was totally broken and support very few games from the complete library of 360 games.
Log in to comment