Hi,
I installed this game via Heroic Games Launcher: Got Linux Mint 20.3 and Nvidia 970 Gtx.

Game Log:

Running BEAUTIFUL DESOLATION

Set current directory to /home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game

Found path: /home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game/desolation.x86_64

Mono path[0] = '/home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game/desolation_Data/Managed'

Mono path[1] = '/home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game/desolation_Data/Mono'

Mono config path = '/home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game/desolation_Data/Mono/etc'

Preloaded 'ScreenSelector.so'

Preloaded 'libsteam_api.so'

Player data archive not found at `/home/christian/Games/Heroic/BEAUTIFUL DESOLATION/game/desolation_Data/data.unity3d`, using local filesystem

Launch command: ['/home/christian/Games/Heroic/BEAUTIFUL DESOLATION/start.sh']

Hi, yes i do think this is the error too.... :-)

But what can I do to fix this error?

This is not the error. That simply says that there is no packed data in a file called "data.unity3d", and it uses the unpacked files in "desolation_Data" instead. This is misleading and happens in case of problems with OpenGL preventing the launch of the game. This happens here when I try to force the use of vulkan, as well as when trying to start something requiring a higer OpenGL version than my graphics chip can handle.

Well, as I said, it is misleading: the file isn't there, was never there, and is not required to run the game.

As I understand it, you can either have the game data packed in this file, or leave it unpacked in subdirectories in the file system. The Unity engine allows both. This game is not „packed“, so it is normal that the file isn't there.

What I've observed is:
IF the game data is unpacked AND IF there is a problem with OpenGL on your machine, you'll get to read this error message.
In fact, you'll get the message also if everything is fine with OpenGL, you normally just won't notice it.

To pack the data would not help, however.

To make it clear: all the messages in the posted log are normal.
If the game doesn't start, the problen is something else!

Hello, sorry for necroing but I've been searching for a whole week already and trying stuff... but getting the same error as shown in this thread:

hanzen  pop-os  ../Beautiful-Desolation  ./start.sh
Running BEAUTIFUL DESOLATION
Set current directory to /mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game
Found path: /mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation.x86_64
Mono path[0] = '/mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation_Data/Managed'
Mono path[1] = '/mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation_Data/Mono'
Mono config path = '/mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation_Data/Mono/etc'
Preloaded 'ScreenSelector.so'
Preloaded 'libsteam_api.so'
Player data archive not found at `/mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation_Data/data.unity3d`, using local filesystem./start.sh: line 17: 42294 Aborted (core dumped) ./"desolation.x86_64"


The game seems to be trying to open (and the cursor even change to the "ingame one" over the screen but nothing is shown, only the image of the last desktop visualisation like windowed and at some poing the game closes itself after not being able to fully launch.

hanzen@pop-os
-------------
OS: Pop!_OS 22.04 LTS x86_64
Host: Z370M DS3H
Kernel: 6.8.0-76060800daily20240311-g
Shell: bash 5.1.16
Resolution: 1920x1080 @ 60.00Hz
DE: GNOME 42.5
WM: Mutter
WM Theme: Pop
Theme: Pop [GTK2/3]
Icons: Pop [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i5-8500 (6) @ 4.1GHz [42.0
GPU: NVIDIA GeForce GTX 1650 SUPER
Memory: 2848MiB / 15937MiB (17%)


I am running it on Pop_OS which is almost the same as Ubuntu for this matter, but no luck until now.
Please I need some help...

The last message says that the programme aborts, and a memory dump is written.
It doesn't tell the reason for the crash. I guess there are requirements missing, something like libraries not installed, or the wrong version thereof.

You can do a check with "ldd":

ldd /mnt/BackUp/Juegos-Linux/Beautiful-Desolation/game/desolation.x86_64

This is a normal output:
linux-vdso.so.1 (0x00007ffe37c55000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdca2797000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdca2776000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fdca276c000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fdca259f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fdca241c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fdca2402000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdca2240000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdca2806000)

It would tell you about missing libc files, but not, for instance, whether your graphics hardware's OpenGL version is too low. You must of course use the path where YOU have installed the game.

Hello, first of all, thanks A LOT for an answer, I wasn't able to really advance with this issue.
I checked just now and this is what I get, with also the OpenGL version:

hanzen > pop-os > ../game > ldd desolation.x86_64
linux-vdso.so.1 (0x00007ffd4619b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x000072ab7332a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x000072ab73325000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x000072ab73320000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x000072ab73000000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x000072ab73239000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000072ab72fe0000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000072ab72c00000)
/lib64/ld-linux-x86-64.so.2 (0x000072ab73348000)

hanzen > pop-os > ../game > glxinfo | grep "OpenGL version"
OpenGL version string: 4.6.0 NVIDIA 550.67

I don't know what should I be looking for since it looked quite similar to the normal output you mentioned before

Hello, nothing obvious is missing, and OpenGL version more than sufficient.

You can try to call the programme with "strace" and/or "ltrace" to see if there is something going wrong.

Example:

strace /path/to/desolation.x86_64

This will produce a LOT of output, and probably not everything looking like an error actually is.
You'll probably see something like the programme trying X, then fail, and try Y afterwards.

This will also make everything running slower, so you can avoid or produce (other) "race conditions".

If you can see the error at all, it is not necessarily at the end of the output.

Good luck, Christoph