• Windows 10 19H1 Update may allow for Xbox One games to be installed
    50 replies, posted
https://www.thurrott.com/xbox/200140/microsofts-evolving-gaming-strategy-takes-a-giant-step-forward
RDR2 on PC sooner than expected? But do you have to have an Xbox One as well?
if i could play KH3 on my computer that would be great thx
So this also means we Get Halo 3 and Reach for PC. https://media1.tenor.com/images/66286c21e00a4ef6707abb4bfe19dcb3/tenor.gif?itemid=5093088
something tells me the mysterious suits that keep games off the PC will build in some digital rights management preventing that.
I don't know if 360 emulation would be possible. I believe the Xbox One does have specific emulation hardware that deals with 360 shaders.
I might finally get to finish the fight.
And this format will exclusively be available on the Windows store, just like UWP.
We need the optimistic rating back
Reading into it, its not actually emulation, its essentially Wine but for xbox binaries. Meaning it should work pretty well, wait and see though.
The way I understand it, Xbone games shouldn't need emulation to run, they just need the right software environment to run in. It's not like it's a different architecture or anything, the CPU is x86-64 and the GPU is good ol' Radeon GCN. My question is whether it's more like an interpretive layer or a VM.
Its exactly that, while the arch is exactly the same, they use different languages per say so it'll need something to essentially translate it to to what the OS can understand and thus pass it onto the CPU. Like said, its basically Wine but for xbox.
Interesting. I'd think that something like that shouldn't even be necessary, considering the Xbox One is already running Windows anyway, but hey, you're the one who read the paper.
If Wii U emulation is as far along as it is, then 360 emulation is definitely possible. After all, a Wii U is essentially just a suped-up 360 at the most basic level. As for the headline itself, I'm not surprised. I've been saying for months now that Microsoft is transitioning Xbox to a device-agnostic software platform rather than just a specific line of consoles (the consoles will instead serve as the "Surfaces" - Microsoft's own reference hardware). With the rumors that Xbone games will soon be available on Switch of all things, this is a logical expectation that they'd also move to Microsoft's other big platform, Windows.
Different builds compiled against different binaries, its like saying a PS4 game should run on Windows because they use x86-64 as well, but its all down to the OS that its fed through, yeah the arch is the same but the actual language they use to communicate is hugely different depending on what its running/compiled against. Plus there is bound to be specific changes done to the consoles to make them more effective with x86-64 which either don't exist or exist in a different form in Windows, so it needs something there to translate those calls. Long story short is basically OS's can run on the same arch, but they all call to the arch differently and because of that, the program needs to either be compiled to use those calls or the OS needs something to convert them to the calls it can use. This is why Wine exists for Linux, giving Linux a compatability layer to translate Windows calls to something Linux understands, this is basically the same but for Xbox to Windows.
Why Xbox One Backward Compatibility Took So Long Preliminary tests showed that support for key Xbox middleware XMA audio and texture formats was extremely taxing to do in software alone, with the former, Gammill noted, taking up two to three of the Xbox One's six CPU cores. But a SOC (system on chip) -- basically an Xbox 360 chip inside every Xbox One, similar to how Sony put PS2 hardware inside the launch-era PS3s -- would've not only been expensive, but it would've put a ceiling on what the compatibility team could do. "If we'd have gone with the 360 SOC, we likely would've landed at just parity," he said. "The goal was never just parity." So they built the XMA and texture formats into the Xbox One chipset... The XMA format encoding would've been taxing on Jaguar's cores, but we see similar theories already working on the fly in PC games and programs without the silicon.
360 emulation through this as it stands wouldn't be possible, the backwards compatibility system Microsoft uses requires them to process the game through one of their proprietary systems to make it playable on console. This is why even with a 360 disc, you still end up downloading it's title from the server on xbox one. The shader system allows them to do shit like Xbox One Enhanced titles, I don't think it's a limitation, but a bonus. I still hope Microsoft do something really great for pc gamers with this system and not just put seven thousand limits on it
I'd like to add that the rumored disc-to-digital trade in program at the Microsoft Stores lines up quite nicely with all this.
I've never been able to justify buying an actual Xbox One simply due to how many games I've bought on PS4, but if they do this I'll absolutely be buying the Xbox One exclusives for PC.
But he was asserting that Xbox runs on Windows, and you didn't properly respond to that at all.
I'm not really sure that the goal for this is Xbox One games on Windows 10 - you certainly can't install Xbox One games currently (the encryption key is different, I already tried it with a few Xbox One XVCs). I feel that it's more for getting the Xbox One specific features (like picking which languages you want, what parts of the game you want like the campaign or multiplayer, and so forth) onto Windows and making the installation process more simple, for better reliability. The XVDD driver simply mounts the XVC as a folder on the filesystem, so no real installation actually occurs. I'd certainly like to be proved wrong, but from a quick glance through what is actually installed by Gaming Services (the package on the Store that installs the Xbox One stuff) it only installs stuff relating to the filesystem.
I did respond to that, the Xbox's Windows is compiled to completely different binaries compared to bog standard retail/enterprise Windows that everyone uses, so it will be using different OS calls or even lacking ones which standard Windows experiences. Its like going Windows 10 Mobile is the same as desktop Windows, which while they share the same codebase, they are not compiled to the same binaries (or even arch in some cases) and it still requires something like UWP for it to be crossplatform. Might want to re-read what I said before trying to spin it.
heck yes now i can play the remaster of perfect dark on pc
All current versions of Windows are built on OneCore -- which is the kernel, networking, storage, etc and OneCore runs on all those platforms (minus the 360, which is also ARM and why it's more difficult to emulate). The Xbox One was specifically updated to the newer OneCore based version of Windows a few years ago and is X64, so we got both of those covered. So the only thing left is the Xbox APIs that games use for probably discs or... whatever... but those still hit the OneCore API at some point. That API could be ported to Windows on the desktop, which is pretty much what this is.
If Xbone game compatibility is coming, then it's more likely that The Master Chief Collection is coming first. And there is supposed to be a large MCC announcement in May, at SXSW....
Then Microsoft be like, 'you need a controller" Developers now can also add support for kb/m on the console though, which would help when bringing xbox builds to pc
...SXSW is in 10 days.
Woops, you are right. https://www.reddit.com/r/halo/comments/aio26e/hcs_invitational_at_sxsw_march_1517_but_weve_also/
If microsoft wanted to be real good boy's they'd stop selling pc/xbox games and just sell them as "microsoft" games and you'd be able to play them on both.
They are tearing down the wall and I love it.
Sorry, you need to Log In to post a reply to this thread.