Win10 doesn't even support ARM without UEFI.I don't know if the UEFI thing is on ARM devices too
If they show Magic Ball 2 running at 60fps then I'm interested...Honestly that video doesn't show anything that couldn't have been done with Exagear Desktop and WINE and the same SoC, prob get better performance without the Windows bloat.
I wouldn't call that video playback particulary smooth - there's a pause at the beginning, and a slight regular stutter in the framerate to my eyes. I don't think it's this machine's playback of that video, though I may be wrong.
Instead of implementing a sophisticated emulation for running classic Xbox games on the Xbox360, most games just run with a downloaded ported version - and many still don't run at all. Did that really change with their newest Xbox?They managed to emulate a 3-core 3.2GHz PowerPC CPU on an 8-core 1.6GHz AMD x64 CPU and make it playable.
Instead of implementing a sophisticated emulation for running classic Xbox games on the Xbox360, most games just run with a downloaded ported version - and many still don't run at all. Did that really change with their newest Xbox?
That's a contradiction, you can't virtualize different CPU architectures. Unless they actually included a fully featured Xenon CPU talking about VMs is plain wrong.They're emulating the full Xbox 360 as a VM.
The approach that we've taken is to actually emulate the full Xbox 360 hardware layer. So the [operating system] for the 360 is actually running when you run the game, [...] If you watch the game's boot you'll see the Xbox 360 boot animation come up. From a performance standpoint it allows [emulation] to work. We're able to get frame by frame performance equivalents.
The 360 games think they're running on the 360 OS, which they are. And the 360 OS thinks its running on the hardware, which it's not, it's running on an emulated VM. On the other side, the Xbox One thinks it's a game. That's why things like streaming, game DVR, and screenshots all work, because it thinks there's just one big game called 360.
You download a kind of manifest of wrapper for the 360 game, so we can say 'hey, this is actually Banjo, or this is Mass Effect. The emulator runs exactly the same for all the games.
I was around when we did the original Xbox [backwards compatibility] for Xbox 360 where we had a shim for every game and it just didn't scale very well. This is actually the same emulator running for all of the games. Different games do different things, as we're rolling them out we'll say 'oh maybe we have to tweak the emulator.' But in the end, the emulator is emulating the 360, so it's for everybody.
If they own the game as a disc, they'll have to download the game to their Xbox One hard drive, and the system will then check for the disc before launching the game.
I'd be more concerned about the different GPU architecture, things ought to be a lot more low level than just providing a different D3D driver.My guess it's a high level emulation, it's not actually trying to emulate the PPC architecture.
My guess it's a high level emulation, it's not actually trying to emulate the PPC architecture.
as we're rolling them out we'll say 'oh maybe we have to tweak the emulator.'
Well if it wasn't HLE, there would probably be some kind of workaround and "could" run every 360 game.Yep, when they say:
That sounds very much to me like HLE. If they were actually emulating all of the chips they'd say 'as we're rolling them out we'll find a bug and fix it'. A tweak is very much less than a fix, and only really applicable if you don't know exactly what you're targetting from the off, in an HLE situation.
What? That's nonsense. You can "virtualise" anything. If you're talking about a hypervisor, well, that's different... but a hypervisor is not required for a virtual machine.That's a contradiction, you can't virtualize different CPU architectures. Unless they actually included a fully featured Xenon CPU talking about VMs is plain wrong.