During the ongoing Google for Games Developer Summit 2022 Keynote, one of the Google team just did a talk on "How to write a Windows emulator for Linux from scratch" to help Stadia.
They already have some existing work available to developers who want it, including their "Stadia Porting Toolkit" which actually uses DXVK to translate Direct3D to Vulkan (since Stadia is a Linux system). However, this translator seems to be their newer approach to running Windows games on Stadia.
With only three people working on it, presenter Marcin Undak said they were able to get some games to run but it's still in the R&D phase and not production ready yet with it taking considerable time to work per-game. However, work is ongoing to hook it all up together with Wine and Proton (for 32-bit games specifically they said) which is one of the paths they will be considering going forwards.
There's already Wine and Proton, which are mentioned in the talk as well but it seems Google wanted something different. Why though? One major reason is how thin Stadia is as a platform. While it is Linux, it's stripped down to the core and doesn't have everything Wine needs to build. There's also a ton of things they don't have to care about that normal desktops do and so "90%" of Wine is simply not needed they said. Additionally, Wine is also apparently challenging when it comes to the build system and debugging.
Quite a technical talk but it's quite nicely presented, to give you a basic overview of what they're doing without going into super tech-heavy details to fry your brain if you're not a developer.
Direct Link
They are also finally about to open the Stadia store without the need to be signed in, so you will be able to actually look around. Incredible it took them this long to do such a basic thing, I can't imagine how many people that put off. Just think if Steam didn't let you view store pages or anything without a login.
Article taken from GamingOnLinux.com.
Quoting: elmapulwhy the Meta tag?Presumably meta as in news tangential to gaming but not about a game. Not Meta as in Facebook.
another thing to consider is, unlike wine and most open source projects that are made mostly by volunteers after work in their spare time, this one is made by full time employees.
imagine coding 8 hours to pay the bills, then going home and still having enough energy to reverse enginering windows and re implement its apis...
Last edited by elmapul on 15 March 2022 at 8:18 pm UTC
Same as stuff like eON and Feral's wrapping code basically will be lost to history.
Last edited by Shmerl on 15 March 2022 at 8:45 pm UTC
Quoting: GuestQuoting: tohurIf people for one second thinks Google wrote their own Windows layer you are highly mistaken as WINE has been in development since the 90s and took them YEARS to be able to run basic stuff let alone games... reverse engineering windows is nothing you just do overnight on a whim no matter how large your company is so thus the fact is they are using a wine code base rather you want to believe it or not.
Not true. They're not reimplementing Windows, but instead just enough of it to run the games. DXVK allows them to cut a huge amount of effort out, along with other libraries (FAudio was mentioned). In this way it's similar to eON; they're not after the same goals as WINE, they're limiting the translation to gaming.
It's not exactly an overnight effort of course, but getting some initial games running in a timeframe of months is certainly viable, and then once the core is ready they can more quickly expand out the supported interfaces.
And if I remember right the Witcher 2 binary was disassembled which uses eON and guess what was found.. mostly WINE related code.. fact is Google can hide this fact cause its on their servers but even for games you are NOT reverse engineering Windows on a whim even to a point of just enough to run games..
Last edited by tohur on 15 March 2022 at 8:57 pm UTC
Quoting: tohurAnd if I remember right the Witcher 2 binary was disassembled which uses eON and guess what was found.. mostly WINE related code.. fact is Google can hide this fact cause its on their servers but even for games you are NOT reverse engineering Windows on a whim
That's exactly what I was thinking. Are they building it from the ground up or they are trimming down Wine?
The fact that they are using dxvk and faudio shows they aren't into complete from scratch approach.
Last edited by Shmerl on 15 March 2022 at 8:58 pm UTC
Quoting: ShmerlQuoting: tohurAnd if I remember right the Witcher 2 binary was disassembled which uses eON and guess what was found.. mostly WINE related code.. fact is Google can hide this fact cause its on their servers but even for games you are NOT reverse engineering Windows on a whim
That's exactly what I was thinking. Are they building it from the ground up or they are trimming down Wine?
The fact that they are using dxvk and faudio shows they aren't into complete from scratch approach.
Hard to believe ANY company outside of Microsoft can do so considering how many years it took WINE to even be usable and let alone THREE devs from Google.. no they are most certainly using WINE and won't admit it because they would have to abide by the GPL
Quoting: tohurwon't admit it because they would have to abide by the GPLLGPL and no. If it's internal to the company they can do whatever they want. (L)GPL covers distribution of the software.
Quoting: elmapulwhy the Meta tag?It covers everything not solely about a specific game.
Quoting: whizseQuoting: tohurwon't admit it because they would have to abide by the GPLLGPL and no. If it's internal to the company they can do whatever they want. (L)GPL covers distribution of the software.
well regardless only a 0.1% chance they are not using wine code but they will never admit it. just rubs me the wrong way
Patreon
PayPal
See more from me