You can sign up to get a daily email of our articles, see the Mailing List page!
Support us on Patreon to keep GamingOnLinux alive. This ensures we have no timed articles and no paywalls. Just good, fresh content! Alternatively, you can support us on Paypal and Liberapay!
  Go to:
Dying Light refuses to launch
stratus commented on 9 October 2017 at 7:15 am UTC

I wanted to chime in on this and say I am having problems lauching Dying Light on Arch after some update. I haven't played in a few months, previously I had played 27 hours.

I don't get any errors when running it from the terminal and there are not logs at all in DW/out.

I've spent maybe 3 hours so far trying to find a solution to this

Although I am not running mesa, I am running NVIDIA blobs 387.12 and a GTX 970

devland commented on 25 October 2017 at 7:19 am UTC

There seems to be a problem with the new libs that arch has.
Someone said on reddit that they managed to get it working on ubuntu on amd hardware by using mesa.

I'll see if I can compile a folder with all the dependencies and write a small script to launch it without using any of the arch libs.

This will be a problem with more and more games as time moves forward.
Game devs need to start using flatpaks and bundle the game with all the required libs.

stan commented on 25 October 2017 at 11:32 am UTC

devlandGame devs need to start using flatpaks and bundle the game with all the required libs.
No need to use flatpak for that, and some required libs must not be bundled (like glibc and libstdc++) which is partly why the Steam runtime often breaks games. But other than that yes, absolutely, games need to provide the libs they need…

https://github.com/solus-project/linux-steam-integration might help, if you can get it to work… (There is an AUR package for it.)

g000h commented on 25 October 2017 at 12:45 pm UTC

I have Dying Light: The Following Enhanced Edition on Debian 9 Stretch, with proprietary Nvidia driver. Launched it, and it started running the new Free DLC video (Axe, Revolver, etc). Then once the video finished, I went into the game, and whooped some zombies for a bit. Did that last night - All good for me.

kaymio commented on 28 October 2017 at 5:50 pm UTC

Bought the game today and got quite embarrassed in front of my Windows Fan Boys.

It has been told that mesa 17.2 should fix the issue. I run 17.2.3 on Arch and it still exists. Someone said kernel 4.14 might help with some memory issues.

Why are the developers not interested in fixing this issue?

DamonLinuxPL commented on 28 October 2017 at 8:11 pm UTC

kaymioBought the game today and got quite embarrassed in front of my Windows Fan Boys.

It has been told that mesa 17.2 should fix the issue. I run 17.2.3 on Arch and it still exists. Someone said kernel 4.14 might help with some memory issues.

Why are the developers not interested in fixing this issue?

First, Arch based distro is well know as game breaking distro. If you can, you can try other distro like Ubuntu - if issue still appears then it is not a distro / library bug.

Seconds, we know what Chrome Engine 6 games are broken on Mesa, this is because Mesa is buggy in someway. In Mesa 17.2 GIT we have confirmed that game work fine but after few new patches to Mesa, they broke game again. Even in stable Mesa 17.2 or new development 17.3 is still broken. Last time when I tested it on AMD with Mesa, it worked on 17.2 git but after month and few mesa git update - they broke it again.

Worth to ask Mesa developers about this Mesa regression.

tuubi commented on 28 October 2017 at 8:36 pm UTC

DamonLinuxPLSeconds, we know what Chrome Engine 6 games are broken on Mesa, this is because Mesa is buggy in someway.
In this case it was actually due to a known bug in the engine.

This isn't the first time I've heard about the game not running on Arch currently. Nothing to do with Mesa I think. And Techland doesn't seem interested as long as it runs on supported distributions, namely Ubuntu 14.04 or later. EDIT: All of this has been said earlier in this thread. I guess none of us actually read through the discussion very carefully.

DamonLinuxPL commented on 28 October 2017 at 9:16 pm UTC

tuubiIn this case it was actually due to a known bug in the engine.

Nope. When two young Techland developers porting Dying Light to Linux they follow with official Khronos Specification and they create two similar branch - one for NVIDIA and second very similar for closed source AMD driver. When they porting it, Mesa was not enough fast (poor performance) and lack of many opengl extansion. So they just following with khronos and not create third branch for mesa. Now, when Mesa is able to handle Dying Light, Mesa not have all features from official khronos spec. So for Mesa 17.2 git, mesa devs prepare patches to run game (patches allow mesa to compiling shaders). It also needed to use "MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command%" command. And it works for some time. After few new mesa patches, mesa devs broke it again, and it is still broken (until today).
Also calling this as game bug is misunderstanding. Even Mesa devs, sometimes ago considering adding missing features from khronos spec, but they chose to finish first more important things and in near future (maybe in next year) add missing features from khronos. So pls, don't blame game.

DamonLinuxPL commented on 28 October 2017 at 9:16 pm UTC

.

ysblokje commented on 28 October 2017 at 10:08 pm UTC

DamonLinuxPLAnd it works for some time. After few new mesa patches, mesa devs broke it again, and it is still broken (until today).

Not sure if you meant that it should work from today onward, but it's still broken for me today (29-10-2017) on arch.

  Go to:

Due to spam you need to Register and Login to comment.


Or login with...

Livestreams & Videos
Official Livestreams
Community Livestreams
  • RPGoodness: "Dragon Age Origins" (via Wine)
  • Date:
See more!
Popular this week
View by Category
Contact
Latest Forum Posts
Facebook