By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Adinnieken on 06 April 2014
Edit Thread
haxxiy said:
torok said:
 

People are with the wrong focus. CPU isn't the big problem. X360 CPU isn't much different of a Wii CPU in steroids with multiple cores. Problem is GPU. Wii uses a simple fixed function GPU that has all the functions implemented on hardware in a pretty predictable way. That's why lightning on the Wii is bland, because it has only one algorithm to do it and it is hardcoded. 360 GPU is programmable. Lightning is done with shaders so it can apply different lightning algorithms to any material. It's complex. This is what makes emulating any console after PS360 another level of challenge.

I think some might have read somewhere about CPU issues in emulation and taken it the wrong way. The problem doesn't falls squarely on the X360 CPU as much as on the XOne's. A huge part of both the CPU and GPU instructions of the X360 would fall as CPU work if it were to be emulated. The XOne and the PS4 don't have the juice to do it.

It would be amazing if it did, but then, a lot of things would be amazing and simply won't happen, so yeah.

The focus on frequency and not on Flops is where others fail to understand the power of the newer consoles.

The GPU of the Xbox 360 is .24TF.  The GPU of the Xbox One's GPU is 1.31TF.  More than 5X the processing power.  The Xbox 360 processor is capable of 0.06TF at 64-bit precision.  The Xbox One's processor is twice as powerful at 0.12TF at 64-bit precision.  With the Xbox One's GPU capable of handling CPU tasks, that puts the total processing power of the console at 1.43TF vs. the Xbox 360's 0.3TF.  Roughly 5x the processing power. 

If Microsoft is developing a VM for the console, they have 5x the original Xbox 360's power to do so with.  However, as I pointed out earlier in this thread, most likely they're developing it for an online service as this would provide a greater return on investment as well as long-term benefit.