4A Games have confirmed in an official 10th anniversary update post today that Metro Exodus is still going to release for Linux and macOS as well.
They gave a small overview in the post about what's been going on like celebrating the first release of Metro 2033 which arrived back in March 2010. Not only that, they recently got acquired by Embracer Group who also control Koch Media, Saber Interactive, THQ Nordic and others. Specifically, 4A Games are now an independently run subsidiary of Saber Interactive.
For people waiting on official Linux support for Metro Exodus, there's good news. While it has been confirmed for a while now, they have been somewhat quiet on it. When mentioning about bringing it to the latest consoles with the Xbox Series X and the PlayStation 5 they also said this:
Aside from these enhanced versions for Gen 9, we recently brought Metro Exodus to more players through Amazon’s ‘Luna’ streaming service; and we’re also working on dedicated Linux* and Mac versions of the game. We’ll share more information about these closer to release.
*Emphasis ours.
Also confirmed is a new Metro game that is officially under development. They're not sharing anything on that, other than it being built for all modern tech as it's targeting PCs and the latest consoles. 4A also confirmed their commitment to "delivering a great story driven single player experience". On top of that, with Saber's help they're exploring a proper multiplayer Metro title but it's not clear if it will be part of the next Metro game or a title by itself.
Quoting: Alm888...If (when) the game is released with official Linux support, IMO it should not matter what technique was used as long as the quality is reasonably high...
This. Exactly my stance.
As for Wine Is Not an Emulator? It amazes me people still care about this recursive "joke" and the distinction it implies. It runs Windows software in Linux, with a performance hit. Who cares if it's actually a re-implementation of the underlying windows system calls? As Alm888 notes, if it looks like a duck, walks like a duck... we may as well call it a duck. No-one who isn't a pretty hard-core Linux nerd will care about whatever that distinction means in real terms.
Last edited by ziabice on 26 November 2020 at 6:29 pm UTC
I've been playing through the STALKER series and loving it. This gives me similar vibes, which I like.
Quoting: scaineMan, this is like the The Witcher 2 argument all over again. My personal view is that whatever is under the hood is largely irrelevant, provided it performs reasonably. That's a vague term, and dependent on your hardware, sure, but "native" for me is nothing to do with wine, dxvk, togl, indirectx or whatever is doing the translation. It's whether the developer is willing to put a Linux logo on the store front.You also probably think FPGA implementations are emulators? :p
As for Wine Is Not an Emulator? It amazes me people still care about this recursive "joke" and the distinction it implies. It runs Windows software in Linux, with a performance hit. Who cares if it's actually a re-implementation of the underlying windows system calls? As Alm888 notes, if it looks like a duck, walks like a duck... we may as well call it a duck. No-one who isn't a pretty hard-core Linux nerd will care about whatever that distinction means in real terms.
My favorite recursive acronym was MiNT, which initially stood for MiNT is Not TOS. Atari couldn't come up with their own mutitasking thing so snagged that and called it MiNT is Now TOS.
There is NO inherent performance hit with Wine. It is simply a matter of whether or not the APIs are are implemented correctly and they translate well to a performant equivalent in Linux. This is why somethings are faster and other things are slower. This is also why it is strictly NOT emulation. So you are calling a moose a duck just because it can quack.
Quoting: Alm888But what really irks me is that one can bash a Winelib-port (totally a full-fledged ELF executable) and go as far as accusing WINE to be an emulation, while at the same time praising a DXVK-wrapped port.
Apparently, WINE has a bad reputation here and even mentioning WINE is considered an insult (despite official support from the devs), while DXVK is perceived to be a god-sent for Linux games. So, even comparing usage of DXVK to WINE-wrapping is considered blasphemous by some.
If (when) the game is released with official Linux support, IMO it should not matter what technique was used as long as the quality is reasonably high.
And I completely agree with the last part you mention. But still, I also think that creating an specific build environment to get the game into our platform (i.e. working with native dependencies and a compiler for our platform) gives an extra value to their work as this means that game developers get away from their Windows building cage they usually live in.
BTW, I don't think that Wine is blasphemous, I just appreciate more one work than the other.
Quoting: slaapliedjeQuoting: scaineMan, this is like the The Witcher 2 argument all over again. My personal view is that whatever is under the hood is largely irrelevant, provided it performs reasonably. That's a vague term, and dependent on your hardware, sure, but "native" for me is nothing to do with wine, dxvk, togl, indirectx or whatever is doing the translation. It's whether the developer is willing to put a Linux logo on the store front.You also probably think FPGA implementations are emulators? :p
As for Wine Is Not an Emulator? It amazes me people still care about this recursive "joke" and the distinction it implies. It runs Windows software in Linux, with a performance hit. Who cares if it's actually a re-implementation of the underlying windows system calls? As Alm888 notes, if it looks like a duck, walks like a duck... we may as well call it a duck. No-one who isn't a pretty hard-core Linux nerd will care about whatever that distinction means in real terms.
My favorite recursive acronym was MiNT, which initially stood for MiNT is Not TOS. Atari couldn't come up with their own mutitasking thing so snagged that and called it MiNT is Now TOS.
There is NO inherent performance hit with Wine. It is simply a matter of whether or not the APIs are are implemented correctly and they translate well to a performant equivalent in Linux. This is why somethings are faster and other things are slower. This is also why it is strictly NOT emulation. So you are calling a moose a duck just because it can quack.
Yep. And, like, five people care about that distinction. Or fifteen. Hell, let's make it a couple of hundred. Ar we happy now? It's irrelevant!
Quoting: scaineThere is a thing called latency and it is real. People who use things such as the MiSTer can pretty much tell right away the differences to the Raspberry Pi. So just because you don't care, does not mean others do not.Quoting: slaapliedjeQuoting: scaineMan, this is like the The Witcher 2 argument all over again. My personal view is that whatever is under the hood is largely irrelevant, provided it performs reasonably. That's a vague term, and dependent on your hardware, sure, but "native" for me is nothing to do with wine, dxvk, togl, indirectx or whatever is doing the translation. It's whether the developer is willing to put a Linux logo on the store front.You also probably think FPGA implementations are emulators? :p
As for Wine Is Not an Emulator? It amazes me people still care about this recursive "joke" and the distinction it implies. It runs Windows software in Linux, with a performance hit. Who cares if it's actually a re-implementation of the underlying windows system calls? As Alm888 notes, if it looks like a duck, walks like a duck... we may as well call it a duck. No-one who isn't a pretty hard-core Linux nerd will care about whatever that distinction means in real terms.
My favorite recursive acronym was MiNT, which initially stood for MiNT is Not TOS. Atari couldn't come up with their own mutitasking thing so snagged that and called it MiNT is Now TOS.
There is NO inherent performance hit with Wine. It is simply a matter of whether or not the APIs are are implemented correctly and they translate well to a performant equivalent in Linux. This is why somethings are faster and other things are slower. This is also why it is strictly NOT emulation. So you are calling a moose a duck just because it can quack.
Yep. And, like, five people care about that distinction. Or fifteen. Hell, let's make it a couple of hundred. Ar we happy now? It's irrelevant!
Last edited by slaapliedje on 28 November 2020 at 3:46 pm UTC
Quoting: scaineQuoting: slaapliedjeQuoting: scaineMan, this is like the The Witcher 2 argument all over again. My personal view is that whatever is under the hood is largely irrelevant, provided it performs reasonably. That's a vague term, and dependent on your hardware, sure, but "native" for me is nothing to do with wine, dxvk, togl, indirectx or whatever is doing the translation. It's whether the developer is willing to put a Linux logo on the store front.You also probably think FPGA implementations are emulators? :p
As for Wine Is Not an Emulator? It amazes me people still care about this recursive "joke" and the distinction it implies. It runs Windows software in Linux, with a performance hit. Who cares if it's actually a re-implementation of the underlying windows system calls? As Alm888 notes, if it looks like a duck, walks like a duck... we may as well call it a duck. No-one who isn't a pretty hard-core Linux nerd will care about whatever that distinction means in real terms.
My favorite recursive acronym was MiNT, which initially stood for MiNT is Not TOS. Atari couldn't come up with their own mutitasking thing so snagged that and called it MiNT is Now TOS.
There is NO inherent performance hit with Wine. It is simply a matter of whether or not the APIs are are implemented correctly and they translate well to a performant equivalent in Linux. This is why somethings are faster and other things are slower. This is also why it is strictly NOT emulation. So you are calling a moose a duck just because it can quack.
Yep. And, like, five people care about that distinction. Or fifteen. Hell, let's make it a couple of hundred. Ar we happy now? It's irrelevant!
I care and I'm a rooster, so that counts for 10000000000000000 people.
On a serious note, the people behind Wine literally put Wine is not an emulator in the name, to prevent people from calling it an emulator. Because it is simply not an emulator. Yet you have people still calling it an emulator. Calling WINE an emulator is not far from calling DXVK an emulator.
Last edited by Shmerl on 27 November 2020 at 7:32 am UTC
See more from me