Dear Reader,

First, thank you, developers, for such a game, really.

Installed via *.sh script so files and directories in game's folder:
docs game gameinfo start.sh support uninstall-Duskers.sh

When trying to launch start.sh it opens launcher well, but when clicking on "Ok" it blinks black window and terminates.

The launcher's window's attached.

After clicking "Ok" these lines are shown in terminal:
************************************************************************************
Running Duskers
Set current directory to /home/user/Games/Duskers/game
Found path: /home/user/Games/Duskers/game/Duskers_linux.x86_64
Mono path[0] = '/home/user/Games/Duskers/game/Duskers_linux_Data/Managed'
Mono path[1] = '/home/user/Games/Duskers/game/Duskers_linux_Data/Mono'
Mono config path = '/home/user/Games/Duskers/game/Duskers_linux_Data/Mono/etc'
displaymanager : xrandr version warning. 1.5
client has 2 screens
displaymanager screen (0)(LVDS-1): 1280 x 800
Using libudev for joystick management

Importing game controller configs
support/gog_com.shlib: line 94: 11608 Aborted ./"${bin_64}"
************************************************************************************

( about -force-opengl flag )
Btw, launching ...game/Duskers_linux.x86_64 -force-opengl works, but why ? Does this mean that Linux's driver doesn't support some features rather than window's one ?
Also, when playing there's no flashlight after drones when controlling them with arrow keys so everything is just dark, but drones and items. I've saw some gameplays and they had it. Is that because of graphics or something ?

GPU: GMA Intel's HD Graphics
Driver i915
glxinfo: http://termbin.com/4bmt

CPU: i7 M620

Best regards,
V7

Anyone ?

No clue. Works perfectly (without any special treatment or command-line options), and has worked perfectly since I got it, for me. I'm guessing it's a bug in the Intel drivers, much like the recent complaints I've been hearing about Divinity: OS EE (which also still works fine for me, as well). In any case, it's not mesa itself, but the i915 driver that's at fault (or so I beleive), since I also use mesa (but with amdgpu hardware/drivers).

One thing that the complaints about divos-ee have in common is that it "used to work" and now no longer does, so you might look into trying an older version of the drivers, as well. You might also have better luck filing a bug against mesa.