It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
JudasIscariot: Hi guys,

A new version of Objects in Space has been published. Please take a look and see if it works now :)
I just installed 1.0.5 and no library workarounds were necessary on my system (Arch Linux). Font rendering still works for me.
Thanks guys! I hope it works for others as well :]
Yep, game now launches okay in Pop 18.10 too, so that is good progress! Font rendering is still broken and I get parts of the text cut out.
avatar
JudasIscariot: Hi guys,

A new version of Objects in Space has been published. Please take a look and see if it works now :)
~/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)
And then back to the prompt.

Being a software developer and system administrator myself, I would normally blame my system as it seems to work for others, but the fact is that every other Linux Native game I have (on GOG and Steam) works perfectly fine on this system. These games go from simple stuff like Axes & Acres, Kingdom: New Lands to Euro Truck, Transport Fever, XCOM, XCOM 2...
Post edited March 18, 2019 by scippie75
avatar
JudasIscariot: Hi guys,

A new version of Objects in Space has been published. Please take a look and see if it works now :)
avatar
scippie75: ~/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)
And then back to the prompt.

Being a software developer and system administrator myself, I would normally blame my system as it seems to work for others, but the fact is that every other Linux Native game I have (on GOG and Steam) works perfectly fine on this system. These games go from simple stuff like Axes & Acres, Kingdom: New Lands to Euro Truck, Transport Fever, XCOM, XCOM 2...
What version of the libc6 library do you have on your system, if you don't mind my asking? From the looks of the error message you may be running an older version of the libc6 library while the game was compiled against a newer one...
avatar
JudasIscariot: What version of the libc6 library do you have on your system, if you don't mind my asking? From the looks of the error message you may be running an older version of the libc6 library while the game was compiled against a newer one...
$ /lib/x86_64-linux-gnu/libc.so.6
GNU C Library (Ubuntu GLIBC 2.23-0ubuntu11) stable release version 2.23, by Roland McGrath et al.

I realize that my version is lower. Mint doesn't give me newer updates for these libraries.
That's why I would expect the game to ship with it like it did before (even though that gave other/similar problems). They 'solved' the issue by removing their version of the file from their libs folder, but in my case, that only makes it worse.

I've never distributed closed software on Linux before, so I don't know what is the best practice in packaging it, but my other games seem to do it fine.

Maybe the devs could also look into supporting lower versions of libc? It can't be that necessary to really need 2.25 for this game, right?
avatar
JudasIscariot: What version of the libc6 library do you have on your system, if you don't mind my asking? From the looks of the error message you may be running an older version of the libc6 library while the game was compiled against a newer one...
avatar
scippie75: $ /lib/x86_64-linux-gnu/libc.so.6
GNU C Library (Ubuntu GLIBC 2.23-0ubuntu11) stable release version 2.23, by Roland McGrath et al.

I realize that my version is lower. Mint doesn't give me newer updates for these libraries.
That's why I would expect the game to ship with it like it did before (even though that gave other/similar problems). They 'solved' the issue by removing their version of the file from their libs folder, but in my case, that only makes it worse.

I've never distributed closed software on Linux before, so I don't know what is the best practice in packaging it, but my other games seem to do it fine.

Maybe the devs could also look into supporting lower versions of libc? It can't be that necessary to really need 2.25 for this game, right?
I have to agree there, it should work, in part because the store page says so.
The store page lists Ubuntu 16.04, which according to this page ships libc6 2.23: https://packages.ubuntu.com/search?keywords=libc6

The equivalent page for mint doesn't work for me, but AFAIK it's based on Ubuntu and should be identical for core packages like this one.
I'm still curious as to why font rendering works for me but not others. The most obvious font related libraries the game links to and their versions on my system are:
fontconfig 2:2.13.1+12+g5f5ec56
freetype2 2.10.0

EDIT: then again I am currently using the shipped libraries, including fontconfig and freetype, so the difference should be somewhere else. Maybe the resolution? I use 1080p.

I tried to figure out where the specific glibc dependency comes from and it looks to me as if there is no strict requirement from cocos2d, it might simply be from the System it was built on. Their github page states Ubuntu 14.04+, CMake 3.1+ and their script for pulling in Linux dependencies was tested on Ubuntu 16.04.
I can't say without testing of course but it's possible that the glibc issue could be solved by building on that version of Ubuntu or there are likely some other means to build against this specific version.
Post edited March 19, 2019 by hollunder
It does now load fine as of the latest version but the font rendering is still absolutely terrible on Ubuntu 18.10.
avatar
hollunder: I'm still curious as to why font rendering works for me but not others. The most obvious font related libraries the game links to and their versions on my system are:
fontconfig 2:2.13.1+12+g5f5ec56
freetype2 2.10.0

EDIT: then again I am currently using the shipped libraries, including fontconfig and freetype, so the difference should be somewhere else. Maybe the resolution? I use 1080p.

I tried to figure out where the specific glibc dependency comes from and it looks to me as if there is no strict requirement from cocos2d, it might simply be from the System it was built on. Their github page states Ubuntu 14.04+, CMake 3.1+ and their script for pulling in Linux dependencies was tested on Ubuntu 16.04.
I can't say without testing of course but it's possible that the glibc issue could be solved by building on that version of Ubuntu or there are likely some other means to build against this specific version.
This is a bit baffling issue. It isn’t resolution related, because my Thinkpad has 1080p screen. I also tested the game with other resolutions and in windowed mode and the result is same. As the game renders stuff on the screen just fine otherwise, I think the problem is related to libraries used. I will inspect this issue more at some point, when I have time.
avatar
liamdawe: It does now load fine as of the latest version but the font rendering is still absolutely terrible on Ubuntu 18.10.
Hey Liam. Is it cut off for you or does it just look bad?
I think bad looking fonts are normal, it's the combination of a bad pixel art font upscaled and looked at with a angled 3D camera. Screenshot of "normal" bad font rendering attached, although it doesn't look as bad in the title screen as on some others since the camera angle is almost normal.

Can someone with cut off font try with turned off camera motion and restart?
Attachments:
avatar
hollunder: Can someone with cut off font try with turned off camera motion and restart?
It is still cut off for example in the Options menu's checkbox text. Most normal texts are fine.

It looks like the fonts are placed 1 pixel too low and then have one more pixel cut off below. Together there are the two lowest pixel rows missing from the texts.

By the way: It loads now fine under Linux Manjaro. Well done.

My graphics card is Intel HD Graphics 620 with the video-linux driver. The game runs fine, the only thing wrong are the cut-off fonts.

Fontconfig is 2.13.1+12+g
Freetype 2.9.1

Could freetype be it? Hollunder has 2.10. What is OIS expecting?
Post edited March 20, 2019 by petov
avatar
floccipocci: I'm not sure if this will help but I ran the start.sh script (and also runois.sh) through gdb and I managed to get an exit error code 0213:

./runois.sh: line 3: 2274 Segmentation fault LD_LIBRARY_PATH=${PWD}/libs/ ./ois
[Inferior 1 (process 2254) exited with code 0213]

It's a consistent error code 0213 so I hope it might mean something to the developers.

What I did:
"gdb --args bash ./start.sh"
then "run" in gdb

also tried
"gdb --args bash ./runois.sh"
avatar
scippie75: Just for the record: not for me!
avatar
floccipocci: Yeah I just realized you mentioned that your libraries are the older versions.
This seems related, so I'm posting it here.

I've had limited success on Ubuntu 18.04 (x64) as it runs. But I've had crashes (seg fault) as noted by floccipocci upon returning to my ship after accepting cargo for a quest across multiple saves and on different quests. Once the seg fault occurs, it repeats every time, making the quest incompletable.
avatar
floccipocci: I'm not sure if this will help but I ran the start.sh script (and also runois.sh) through gdb and I managed to get an exit error code 0213:

./runois.sh: line 3: 2274 Segmentation fault LD_LIBRARY_PATH=${PWD}/libs/ ./ois
[Inferior 1 (process 2254) exited with code 0213]

It's a consistent error code 0213 so I hope it might mean something to the developers.

What I did:
"gdb --args bash ./start.sh"
then "run" in gdb

also tried
"gdb --args bash ./runois.sh"

Yeah I just realized you mentioned that your libraries are the older versions.
avatar
Jeakle: This seems related, so I'm posting it here.

I've had limited success on Ubuntu 18.04 (x64) as it runs. But I've had crashes (seg fault) as noted by floccipocci upon returning to my ship after accepting cargo for a quest across multiple saves and on different quests. Once the seg fault occurs, it repeats every time, making the quest incompletable.
I believe that's another unrelated segmentation fault bug that some other folks are having when it comes to returning to the ship. There's a good number of threads created in this forum. It affects windows users too, I think.

This bug is regarding the game crashing when trying to start it up.

I've stopped playing it on Linux for now, because I'm having problems with the text on the UI buttons being displayed poorly.
Post edited March 20, 2019 by floccipocci
avatar
hollunder: Can someone with cut off font try with turned off camera motion and restart?
avatar
petov: It is still cut off for example in the Options menu's checkbox text. Most normal texts are fine.

It looks like the fonts are placed 1 pixel too low and then have one more pixel cut off below. Together there are the two lowest pixel rows missing from the texts.

By the way: It loads now fine under Linux Manjaro. Well done.

My graphics card is Intel HD Graphics 620 with the video-linux driver. The game runs fine, the only thing wrong are the cut-off fonts.

Fontconfig is 2.13.1+12+g
Freetype 2.9.1

Could freetype be it? Hollunder has 2.10. What is OIS expecting?
I don't think this is it, or rather it shouldn't be since the game ships said two libraries. I don't know what else it could be. Maybe the game doesn't actually use the shipped version for some reason? Just a wild guess, I didn't check, wouldn't know how.
So, I just tried running 1.0.5 on my arch setup and I still have segfault when trying to start it. Segfaults with code 9367, and if I remove every lib except libGLEW and libfmod, I get a 9367 segfault. I wonder why some users got it working since the last update, but not me?