A few details? OS, Kernel, GPU, maybe some stuff mentioned in this thread like glibc version etc?

Can you try "ldd game/ois"? In my case there is a library for everything but libfmod and libGLEW present. If something is missing and not in "game/libs" then you may be missing a required library that is assumed present.

I've played around with the runois.sh script a bit to see whether I find a problem with it. So far nothing, but I'm not a shell wizard and there could be subtleties that I missed (Does ${PWD} rather than $(pwd) cause issues on some systems?).

Anyway, effectively everything the game links to should be provided by the game, except glibc stuff, so it shouldn't be a library issue, provided setting LD_LIBRARY_PATH works.

While digging I found the dev has set the runpath to her local libraries. That probably shouldn't be there but is unlikely to hurt.
0x000000000000001d (RUNPATH) Library runpath: [/home/elissa/installers/cocos2d-x-3.17.1/tests/ois/./Libs/fmod/lib:/home/elissa/installers/cocos2d-x-3.17.1/t ests/ois/./Libs/raknet/lib:/home/elissa/installers/cocos2d-x-3.17.1/tests/ois/./Libs/steam/lib/linux64:/home/e lissa/installers/cocos2d-x-3.17.1/external/linux-specific/fmod/prebuilt/64-bit]

Whether that causes a problem on your system you can figure out by removing the runpath:
patchelf --remove-rpath game/ois

Here is some explanation: https://stackoverflow.com/questions/7967848/use-rpath-but-not-runpath



Apparently the ois binary is also hardened^^
0x000000006ffffffb (FLAGS_1) Flags: NOW PIE

Now I haven't dug deep enough to know for certain any of that is an issue. If anyone has issues make sure there is no LD_PRELOAD or LD_LIBRARY_PATH set in you environment, that likely would cause issues for ois, but not just for that.

Confirming that 1.0.5 still segfaults on launch with the same line seen before in this thread (except the 4 digit code changes every time I attempt it). Solus, kernel 4.20.16, glibc 2.29

The moving libraries workaround in the thread does allow the game to launch (thank you, posters) and text is legible, though maybe not quite on par with some of the screenshots.

However, I got to Lagrange station and now cannot attempt to leave without a crash. The last lines in the log are:

[23:15:41] [GAME]: Returning to player's own ship.
[23:15:41] [GAME]: Displaying room Airlock

It does not actually display anything in the ship at that point. Visually, it just crashes from the station. Good hopes for some bug fixes, because I think I would like the game.

Cheers.

Run it from a terminal and look at the output, it contains more information than the log (silly, I know).
It may be the exact same crash I get on Bodhi station.

Indeed. Interesting that the first game I started now does *not* crash from Lagrange and I can continue, but the second game I started after does crash from another station. So this is apparently intermittent, perhaps after a reboot? And it's a segfault. There are a lot of cocos2d warnings followed by:

libpng warning: iCCP: known incorrect sRGB profile
./runois.sh: line 3: 6251 Segmentation fault LD_LIBRARY_PATH=${PWD}/libs ./ois

The last line being the same as trying to run the game without the library workaround.

The libpng warning is almost certainly harmless, a lot of programs throw these.

As for the crash, from all I've seen I don't think there is anything we can do but hope that the devs will find the issue and fix it. If your current crash is only intermittent then you are lucky in a sense. There seems to be at least one reliable crash bug.

The native Linux build does not show all of my available screen resolutions. Only 1280x720 and 1920x1080. Also, some of the text is cut off as if the bottom row of pixels is not included. Primarily this occurs with text on buttons but it's also apparent in some other places. Changing the game resolution and/or my desktop resolution does not affect the text bugs. Running the windows version under wine works perfectly. I have more resolutions to choose from and the text is not cut off. I run the game at 1360x768 with wine which is the same as my desktop resolution.

Linux Mint 19
Kernel 4.15.0-46
Intel i5-4460 @3.20GHz x 4
8 GiB RAM
Nvidia GeForce GTX 750 driver version 418.56
17" 720p TV connected via HDMI cable.

EDIT: The text problem is not present on my laptop. Specs below.

Linux Mint 19
Kernel 4.15.0-43
AMD A6-5200 APU
6 GiB RAM
[AMD/ATI] Kabini [Radeon HD 8400 / R3 Series]
amdgpu driver

I tried to do the same on my Mint 18.3 but the game wouldn't start. I had an error during installation too.
Can you tell me a bit about your Wine version and settings?

I have wine-4.0-rc2 (Staging) with winetricks 20181203-next and a 64 bit wine prefix set to Windows 7 with dotnet40, vcrun2017 and dxvk installed.

I was able to run 1.0.5 by removing all libs from OiS/game/libs aside from libGLEW.so.2.0 and libfmod.so.10
I also had to manually create a ~/Documents folder as it appears the game does not check ~/.config/user-dirs.dirs for custom xdg paths and requires ~/Documents to exist or the game will segfault on run.
I noticed this as the console message indicated the game attempting to write logs to a folder that does not exist on my computer.

--
Running Objects In Space
Opened debug log at '/home/user/Documents/ObjectsInSpace/log/DebugLog_Game.txt'
./runois.sh: line 3: 7721 Segmentation fault LD_LIBRARY_PATH=${PWD}/libs ./ois
--

Hey, creating ~/Documents fixed the segfault for me! thanks for the tip. Now my only problem is the text being unreadable due to the letters being cropped.

Damn it... I already have a ~/Documents folder and I hoped that creating those subfolders in there would help, but still no luck.

1.06:

~/GOG Games/Objects In Space $ ./start.sh
Running Objects In Space
./ois: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /home/dirk/GOG Games/Objects In Space/game/libs/libexpat.so.1)
./ois: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /home/dirk/GOG Games/Objects In Space/game/libs/libbsd.so.0)