Hello,

I recently acquired the game through GOG and it doesn't start at all. One of the problem being that there's absolutely no log to work with either..

Starting the game through command line gives only this:
» ~/GOG Games/Dead Cells ./start.sh
Running Dead Cells
Loading assets... done.

And that's it. I tried updating, disabling the AMD graphics card, updating from ubuntu 14 to ubuntu 16... Nothing changed.

I am running Ubuntu 16.04 on a Thinkpad T400, if anyone could help, that would be marvelous.

I had, just the graphic card booting up. Being AMD graphics on linux not working well, I thought of disabling the graphics card and I'm only using intel integrated now. Nothing shows up in dmesg anymore and exact same behaviour

for drivers :
*-display UNCLAIMED
description: VGA compatible controller
product: RV620/M82 [Mobility Radeon HD 3450/3470]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:01:00.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list
configuration: latency=0
resources: memory:c0000000-cfffffff ioport:2000(size=256) memory:bfff0000-bfffffff memory:bff00000-bff1ffff
*-display
description: Display controller
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: msi pm bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:30 memory:fc000000-fc3fffff memory:d0000000-dfffffff ioport:1800(size=8)

do you also want the modinfo of the driver?

for OpenGL version :
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset
OpenGL version string: 2.1 Mesa 18.0.5
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

Hope this is complete enough, I'd be infinitely grateful if we can find a solution :)

Hey!

At least the Intel-driver provides only OpenGL 2.1 for your card, while the game seem to need at least OpenGL 3.2.

Maybe you are able to force AMD-card-only and look if you get higher OpenGL support.
If not there might be another way to test if it is related to the OpenGL-version.
Export these variables before starting the game:
LIBGL_ALWAYS_SOFTWARE=true

maybe also

GALLIUM_DRIVER=llvmpipe

to see if this works.

Incredible, it does work! The game is unplayable (super low framerate and stuttering) but it launches!
I guess I'll have to play around seeing if I can make this amd card work.

Thank you very much!

Trying to launch the most recent version (1.0.2) on Linux Mint 17, no effect. It just prints the following:

~/tools/Games/Dead Cells $ ./start.sh
Running Dead Cells
Loading assets... done.

A window blinks and that's it. Nothing else in the console. It's the same on either Intel HD or Nvidia card (using optirun/primusrun).The advice above does not help. I've also tried rebooting the system and reinstalling the game.

dmesg shows a bunch of possibly related segfaults:

[ 1867.022867] steam.hdll[9004]: segfault at 0 ip 00007ffb4d1b6141 sp 00007fffae4d26d8 error 4 in steam.hdll[7ffb4d1a3000+2a000]
[ 1874.882882] sdl.hdll[9006]: segfault at 1 ip 0000000000000001 sp 00007fffa33252a8 error 14 in sdl.hdll[7f7c7a4d2000+e000]
[ 1889.739899] sdl.hdll[9008]: segfault at 1 ip 0000000000000001 sp 00007fff6e875918 error 14 in sdl.hdll[7fc45ccf7000+e000]
[ 1938.710346] ui.hdll[9025]: segfault at 1 ip 0000000000000001 sp 00007fff38b14718 error 14 in ui.hdll[7f110269c000+2000]
[ 1987.712712] libogg.so.0[9051]: segfault at 1 ip 0000000000000001 sp 00007fff0ce6a1a8 error 14 in libogg.so.0[7f89526fb000+7000]
[ 2065.404247] libhl.so[9114]: segfault at 0 ip 00007fab12605ea9 sp 00007fff1066e070 error 4 in libhl.so[7fab125ee000+4e000]

So apparently some of the Haxe libs are broken?

EDIT: The same with 1.1.10, except no Haxe-related messages in dmesg

EDIT 2: I've written to the support and they say it's a hardware issue with GeForce 520 Mobile (admittedly, not top of the line card). If anyone else comes here with a similar problem looking for a solution, well, there isn't one.