With the announcement and trailer of Dying Light 2 [Official Site] shown off during E3, we reached out to Techland to see if the sequel will be on Linux.
Considering the original is one of my favourite games, I was hoping they would eventually confirm it for Linux again. Sadly though, they haven't yet made a decision.
Here's what they said to us when we emailed them:
About your question: I am afraid it is too early to give the definitive answer yet as our development team is working hard on Dying Light 2. Confirmed platforms are Xbox One, PlayStation 4 and PC, but knowing that we have devoted Dying Light community on Linux, this version is definitely in their consideration.
So if you do want it on Linux, you should probably let them know.
You can see some gameplay below:
Direct Link
Once you have the Graphics API sorted out then the rest can then fall into place in due time, if they just use DX11 or 12 for example, then its far from ready for porting to other platforms!
Also there are plenty of wrapping solutions for the other components that a developer can look at using.
The graphics API is the BIG thing that controls how well a game will run on a platform, we have seen DOOM work almost 1:1 windows performance with Wine, yet it ONLY has vulkan/opengl API's and NONE of the other components sorted out!
Last edited by TheRiddick on 29 June 2018 at 10:34 pm UTC
Quoting: F.UltraQuoting: GuestI bought Dying Light one year ago. Actual play time 0 minutes, it never worked on my machine, neither with Mesa or Mesa-git. So if they release it for Linux, they hopefully make it work as well. Otherwise I can't see what's the difference to a Windows only release. I paid the full price for this game, but so far I got 0 fun and 0 service. Technology wise I hope they go Vulkan only for Dying Light 2 to reduce bugs.
Did you change the Launch Options in Steam to "MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%"? This is needed for it to start on Mesa since it tries to open v4.5 of the compat profile instead of the proper core profile.
I did, I did strace, gdb and no luck at all, I was thinking even use a disassembler like ida to look into source code and find what they did wrong but assembly language is my Achilles tendon, my BASIC and Pascal languages knowledge it won't help at this moment :(, after Mesa 17 the Chrome Engine 6 itself stopped work and nothing based on same engine will work, in all logs that I got it fails to detect graphics card and memory, fills up around 700mb ram and crash to desktop.
Anyone else is getting [0] vram detected in game logs "$HOME/.local/share/Steam/steamapps/common/Dying Light/DW/out/logs/"?
Last edited by eddie-foss on 29 June 2018 at 10:36 pm UTC
I'd say this is a AMD driver issue, either your driver isn't the right version (amdgpu is best one) or mesa is not updated.
I intend to move back to a AMD graphics card once a 1080ti beater comes out, one day.
(could take a while since AMD seems to have shrunk their GPU engineer department to a hair string).
Last edited by TheRiddick on 29 June 2018 at 11:20 pm UTC
Quoting: lejimsterWell. I always love Linux support. But Dying Light doesn't even work on my Arch distro. I get further into the game using DXVK.
This an AMD issue and probably will be fixed on Mesa 18.2
https://lists.freedesktop.org/archives/mesa-dev/2018-June/198824.html
And also a user confirmation:
QuoteHi
I can confirm Dying Light is still working great with this series, it
doesn't require any overrides and changes to the graphical settings no
longer cause crashes
https://lists.freedesktop.org/archives/mesa-dev/2018-June/198844.html
Game works for Nvidia like since it is out , because Nvidia driver always had compat profiles while AMD open source driver wasn't until last year.
But wait they said coming to PC I to have a PC, what was I thinking of course I mean how else am I writing this comment, on my PC that runs an awesome distro called Linux mint on PC :)
Last edited by Tuxgamer on 30 June 2018 at 1:00 am UTC
Quoting: liamdaweQuoting: JarnoNot a crime perhaps in certain countries, but ethical or even moral? That's a different story.Quoting: PatolaQuoting: jensPlease grow up. It doesn't matter at all what you do with the game. If you use it for whatever purpose you'll have to pay, anything else is theft/piracy or what you prefer to call it.Unauthorized copy. Or piracy.
But it is not theft. There is no subtraction. Even if it is a crime, it is a different crime.
Tired response? Yeah, for a tired argument.
Well, in here where I live it isn't even crime to download.
At GOL, we firmly believe you should support developers if you intended to use their software, regardless of it natively supporting Linux or not. The fact is, if you're "pirating" it to play it in Wine, you should really still be buying it. You're not entitled to anyone's work for free if they require a purchase for it.
Well, is not so simple. When you pay for a game you are not only paying for a license to play, you're also paying for support, something that you'll never get if you play with Wine. Also, in many countries (as mine) paying the price they ask for a game that will certainly not work well is not fun at all and a big problem for our wallets (in fact, when I first payed for DL, I had to make a refund due that it wasn't working with Mesa. As soon as I checked that it was working with Mesa, I rebuyed).
Long story short: give support to my platform and you'll get my money. Don't give support to my platform, you'll never see my money. And with this assumption, that someone play a pirated version or not of a Windows game won't make any difference for the publisher as we aren't the market they are pointing towards (and I can support my statement based the actions and statements of darkwood devs).
See more from me