Don't want to see articles from a certain category? When logged in, go to your User Settings and adjust your feed in the Content Preferences section where you can block tags!
We do often include affiliate links to earn us some pennies. See more here.
tagline-image
Hooray for Techland! Dying Light is finally playable on Linux, so you can join us in having some cake. It's not perfect, but far far better!

It took them quite a long time to get here, but they got here, so let’s be thankful!

After we (GOL) paid about £80 for myself and Samsai to have a copy, I finally feel like they are earning our money, well, sort of. The game was obviously not tested on Linux before release, but hey...anyway.

My first trial run of the new patch forced me to quit as it popped up saying Dying Light has become unresponsive, good start. I waited, and it died on its own.

Second launch was fine, and the game has a MUCH better overall FPS, and it now feels VERY smooth and responsive, finally!

Testing it on High textures, Medium shadows, and High foliage now gives between 45-80FPS, considering before that gave 15-30FPS that's a solid improvement.
It's no way near perfect, but it's better for now. When you consider I'm on an Nvidia 970 I should still be getting a fair bit more.

Update: I re-tested the Proteus laptop from Entroware that we have, and it's even playable on it. Check the updated review on page 2 for the screenshot as well.

Update 2: It will still crash to the desktop for me when scrolling through the keybind menus, I did report this to Techland before, and have done, again. It happens on the third screen of the keybinds menu, every time.

Update 3: The game will crash to the desktop a lot for me now, so I am still recommending anyone who hasn't picked it up, to wait.

Release notes:
QuoteFeatures:

* Hard Mode added
* National outfits added
* 4 outfits as a reward for finishing the story campaign added
* Over 50 new weapons added
* New weapon rarity level – extremely rare Gold weapons added

Gameplay:

* Various balance tweaks of weapons, loot chests, shops and crafting
* Various improvements to game quests
* Improvements in natural movement flow

Technical:

* Resolved various stability issues including co-op
* Improved overall game performance

Visuals:

* Various improvements in world and character art

Be the Zombie:

* New option to enable zombie invasions with co-op disabled added

Linux specific improvements:

* Added AMD Radeon support (Please note - the NPC dialogue lip-sync will be enabled in a future patch)
* Improved performance significantly
* Fixed glitch when changing resolution
* Improved mouse scroll speed in map menu
* Disabled SSAO and AA options (TBD)
* Fixed minor rendering issues
* Fixed screenshots capturing
* Fixed crashed related to audio driver


Finally I can enjoy the experience! Or so I thought, the game crashes to the desktop quite often now.

You can find Dying Light on Steam. It's still pretty flaky though! Article taken from GamingOnLinux.com.
0 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
60 comments
Page: «6/6
  Go to:

EKRboi Mar 11, 2015
Quoting: vulturewhy do i think that all the people that got it working now just got over threshold of cpu bottlenecking to the next level?

especially the... no change on resolution or settings is suspicious and the fact that people with same cpus say same things while gpu seems to not play any special role or at least nowhere near as it should. these are most obvious signs when cpu is bottlenecked.

can anyone with problems check core utilization? usually in this case one core should be 100% non stop

i plan on buying it if i was correct, my cpu is more than good enough it seems. still, they better fix this

It seems to spread out the CPU load pretty well. I just grabbed the following shot. Frame rate is certainly more stable when you use the performance governor. I didn't have it turned on just now, but I was just grabbing this shot. I was curious to how it was utilizing the CPU after you said something and I had not checked before so I figured I would share. I also normally game in Openbox but wasn't going to switch just to grab the screenshot. It is certainly using a TON of RAM too. (nearly 6gb)

[

Settings:
[

In openbox with FAR less things going on and without compton also stepping in it is not unusual to see 60fps standing still like I was in that shot. It may drop into the high 40's sometimes while running around and especially while running past fire.

EDIT* I also just notice how much VRAM it is utilizing looking at my SS. 3.6gb-ish. That is absurd for a game running @ 1080p with no AA. It uses that much in Windows running 3 screens plus some AA. Around 500mb of that VRAM is the desktop but my comment still stands with the 3gb-ish the game is using. So maybe VRAM is what people are struggling with?
Cybolic Mar 12, 2015
I recommend waiting for more fixes before buying it.
Right now I'm stuck with not being able to start a campaign (single player story mode) and also not having online play working - it's essentially just the menu I can look at. The issue seems to be a b0rked Steam cloud save since even wiping my local files doesn't let me play.
It might not happen to you, but you could end up essentially throwing your money out the window :(
EKRboi Mar 12, 2015
Quoting: CybolicI recommend waiting for more fixes before buying it.
Right now I'm stuck with not being able to start a campaign (single player story mode) and also not having online play working - it's essentially just the menu I can look at. The issue seems to be a b0rked Steam cloud save since even wiping my local files doesn't let me play.
It might not happen to you, but you could end up essentially throwing your money out the window :(

You can test out the cloud save theory by going to steam->settings->cloud and disabling "Enable Steam Cloud sync. for apps. that support it". Then wipe your local game save @ ~/.local/share/Steam/userdata/<somenumberhere>/239140/
Then the next time you launch the game it won't pull your save from the cloud and If it works then you know a borked save was the problem. Then once you have a new save made you can re-enable the steam cloud and when you launch the game again it will tell you your local and cloud save are different and ask you which you would like to use/keep. I've done it as switching from Linux to windows (or vice versa) with this game causes save problems.

EDIT* you should probably wipe <path-to-game>/DW/out/Settings/ as well for good measure.
Cybolic Mar 12, 2015
Thanks EKRboi. I ended up just wiping both "Steam/userdata/<user_id>/239140/" and "Steam/SteamApps/common/Dying Light" and reinstalling, which fixed it :)
I think the issue might in fact have been the custom configuration (the "i_shadows_sun_on" one) which didn't mix with the 1.5 patch.
If I make it past the first mission (change clothes), which broke the game for me before, I'll give it a recommendation - my FPS are much better in 1.5 (on a GTX 660 Ti).
coryrj19951 Mar 12, 2015
Quoting: GenericUserRemember Antegros uses the pacman packaging system so if you want steam just type "sudo pacman -S steam" in the terminal.And remember to update me if the open source driver also doesn't work out for you.

Sorry for the delay, having troubles getting Antegros to install, need an internet connection for the installer and ndis wouldn't build right. I installed Manjaro, going to test the open source drivers out tonight or tomorrow.
GenericUser Mar 15, 2015
Quoting: coryrj19951Sorry for the delay, having troubles getting Antegros to install, need an internet connection for the installer and ndis wouldn't build right. I installed Manjaro, going to test the open source drivers out tonight or tomorrow.

Well,Does it Work?.
coryrj19951 Mar 15, 2015
Quoting: GenericUserWell,Does it Work?.

It does not, I am cannot get it to launch with the open source drivers. :(
GenericUser Mar 15, 2015
Quoting: coryrj19951
Quoting: GenericUserWell,Does it Work?.

It does not, I am cannot get it to launch with the open source drivers. :(
Well then,Sorry for wasting your time.But keep using the open source drivers as they are better for your card than Catalyst and they also give you the benifit of using gallium nine with playonlinux.
GenericUser Mar 16, 2015
Quoting: coryrj19951
Quoting: GenericUserWell,Does it Work?.

It does not, I am cannot get it to launch with the open source drivers. :(
Wait a minute,I suddenly remembered that the last time I used Manjaro it did not detect my AMD card properly.First thing you should do is check if you are using the AMD driver by installing mesa-demos "sudo pacman -S mesa-demos" and put "glxinfo | grep OpenGL" without the quotation marks in your Terminal and report back the output.
coryrj19951 Mar 16, 2015
Quoting: GenericUserWait a minute,I suddenly remembered that the last time I used Manjaro it did not detect my AMD card properly.First thing you should do is check if you are using the AMD driver by installing mesa-demos "sudo pacman -S mesa-demos" and put "glxinfo | grep OpenGL" without the quotation marks in your Terminal and report back the output.

Yeah, I dont think it is...

Quoting: MyTerminalOutputError: couldn't find RGB GLX visual or fbconfig

Fixed that part, re-installed the system (though I lost my Mint GRUB entry, had to manually re add it)
Now to test a few games!

Quoting: MyNewTerminalOutputOpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD PITCAIRN
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.4.2
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.4.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.4.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.0
OpenGL ES profile extensions:

-----
EDIT: Well, I change to the catalyst driver to check performance as I still couldn't launch Dying Light (sorry ;) ) I can play! It runs fairly playable out side with out crashes every 2 minutes :D !
I find it amazing how two differant distros can run a game very differantly on the same hardware.
(I did however find that the open source drivers can play a variety of games very well (BL2 at max settings) )
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.