Page 2 of 2

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 5:31 am
by hiran
:roll:
mcarans wrote: Tue Jul 01, 2025 9:53 pm
The good news on the Linux front is that the release here https://github.com/OoMrFlibble/oolite/releases works.
Is that qualifyable? Where did it work?

I tried on my Ubuntu 24 LTS and it did not come up. Some required library (libgnustep 1.28) is not present. Well Ubuntu comes with 1.29 and higher nowadays.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 8:15 am
by MrFlibble
hiran wrote: Wed Jul 02, 2025 5:31 am
:roll:
mcarans wrote: Tue Jul 01, 2025 9:53 pm
The good news on the Linux front is that the release here https://github.com/OoMrFlibble/oolite/releases works.
Is that qualifyable? Where did it work?

I tried on my Ubuntu 24 LTS and it did not come up. Some required library (libgnustep 1.28) is not present. Well Ubuntu comes with 1.29 and higher nowadays.
Are you using my latest pre-release? If you are, I'll roll up an Ubu 24 to find out what's occurring. libgnustep-base.so.1.28 should appear in ~/GNUstep/Applications/Oolite/oolite-deps/lib.

If it's built with 1.28, then bundling 1.28 should sort it even if a newer version is installed locally, or none at all.

In my fork of Linux-deps, I've hijacked x86_64/lib_linker/make_so_links.sh (also the 32, though I've not tried building that) to also collect the library bundle. It should be stable into the near future, as it allows for varying library versions on the build host, and therefore newer/older build distros.

I need to re-preen what remains in my version of the old static stuff. I'm not entirely sure that everything ancient that I'm including is still relevant. I'll chew over ExternalLibrariesSourceCodeChanges.txt again.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 5:30 pm
by hiran
MrFlibble wrote: Wed Jul 02, 2025 8:15 am
Are you using my latest pre-release? If you are, I'll roll up an Ubu 24 to find out what's occurring. libgnustep-base.so.1.28 should appear in ~/GNUstep/Applications/Oolite/oolite-deps/lib.

If it's built with 1.28, then bundling 1.28 should sort it even if a newer version is installed locally, or none at all.

In my fork of Linux-deps, I've hijacked x86_64/lib_linker/make_so_links.sh (also the 32, though I've not tried building that) to also collect the library bundle. It should be stable into the near future, as it allows for varying library versions on the build host, and therefore newer/older build distros.

I need to re-preen what remains in my version of the old static stuff. I'm not entirely sure that everything ancient that I'm including is still relevant. I'll chew over ExternalLibrariesSourceCodeChanges.txt again.
Ok, go again with all the details. I am downloading
https://github.com/OoMrFlibble/oolite/r ... x86_64.run

After installation to my home directory I have (among others) this file:
GNUstep/Applications/Oolite/oolite-deps/lib/libgnustep-base.so.1.28

So I am running
cd GNUstep/Applications/Oolite; ./oolite

Whoops, I get a startup screen, hear the music and can even launch one of my savegames. Obviously all the OXPs are missing - something that OoliteStarter can take care of.

And all this happened on Ubuntu 24.04.2 LTS.

Well done! Just bring it in to the main branch. :D
But there is a drop of bitterness: Sound output can get stuttery, and that impacts controlling the ship. Not good when lots of bad guys are around.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 6:09 pm
by MrFlibble
hiran wrote: Wed Jul 02, 2025 5:30 pm
Well done! Just bring it in to the main branch. :D
I'll do a new PR after one more pass at it.
hiran wrote: Wed Jul 02, 2025 5:30 pm
But there is a drop of bitterness: Sound output can get stuttery, and that impacts controlling the ship. Not good when lots of bad guys are around.
So assuming you're on a test system, please try:

Code: Select all

rm ~/GNUstep/Applications/Oolite/oolite-deps/lib/libopenal.so.1
If you get a bunch of fail, you may need to:

Code: Select all

apt install liopenal1
Please let me know whether that helps reduce jitters, or fails in some new and interesting way.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 6:27 pm
by MrFlibble
Looks like I already removed that, so you'd have had to install it anyway. viewtopic.php?p=301103#p301103

Another one to try might be SDL. Try:

Code: Select all

cd ~/GNUstep/Applications/Oolite/oolite-deps/lib/
mv libSDL-1.2.so.0 libSDL-1.2.so.0.hidden
apt install libSDL-1.2-compat
If we can figure which libraries can be used 'native' on (same as build host) or newer os'es, then it'll be easy to reduce the bundle. Maybe even write a script to run at first start to check for missing deps, then suggest apt/rpm/apk/whatever install lines. I know this goes against my original hope of not needing users to install anything else, but it may be the most balanced solution when using the SE-installer.

Some of the libraries have been twisted to work for Oolite, and cannot be replaced with 'native'.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 7:13 pm
by hiran
MrFlibble wrote: Wed Jul 02, 2025 6:09 pm
hiran wrote: Wed Jul 02, 2025 5:30 pm
But there is a drop of bitterness: Sound output can get stuttery, and that impacts controlling the ship. Not good when lots of bad guys are around.

So assuming you're on a test system, please try:

Code: Select all

rm ~/GNUstep/Applications/Oolite/oolite-deps/lib/libopenal.so.1
If you get a bunch of fail, you may need to:

Code: Select all

apt install liopenal1
Please let me know whether that helps reduce jitters, or fails in some new and interesting way.
I can confirm libopenal.so.1 is not in that directory.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 7:20 pm
by hiran
MrFlibble wrote: Wed Jul 02, 2025 6:27 pm
Looks like I already removed that, so you'd have had to install it anyway. viewtopic.php?p=301103#p301103

Another one to try might be SDL. Try:

Code: Select all

cd ~/GNUstep/Applications/Oolite/oolite-deps/lib/
mv libSDL-1.2.so.0 libSDL-1.2.so.0.hidden
apt install libSDL-1.2-compat
If we can figure which libraries can be used 'native' on (same as build host) or newer os'es, then it'll be easy to reduce the bundle. Maybe even write a script to run at first start to check for missing deps, then suggest apt/rpm/apk/whatever install lines. I know this goes against my original hope of not needing users to install anything else, but it may be the most balanced solution when using the SE-installer.

Some of the libraries have been twisted to work for Oolite, and cannot be replaced with 'native'.
I renamed the existing file. But installing the other one seems to fail:

Code: Select all

$ sudo apt install libSDL-1.2-compat
[sudo] password for hiran: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package libSDL-1.2-compat
E: Couldn't find any package by glob 'libSDL-1.2-compat'
$ 
But what is that? Despite libSDL-1.2.so.0 is renamed, I can start Oolite?
I cannot tell why that should work at all. But I can say the stutter increased. :-(

Some good news: I can decrease the stutter again by renaming back libSDL-1.2.so.0

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 7:54 pm
by hiran
So I pressed Ctrl-F to activate the FPS display. After launching from the station I get between 60 to 75 FPS.
But when times get hot, it can drop down to 20. This is where it gets unplayable. The rate drops intermittently - just when I am ready to shoot.
Sometimes small corrections (even with pressing Ctrl) lead to the opposite effect. Is this all connected to the game loop?

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 9:58 pm
by mcarans
hiran wrote: Wed Jul 02, 2025 5:31 am
:roll:
mcarans wrote: Tue Jul 01, 2025 9:53 pm
The good news on the Linux front is that the release here https://github.com/OoMrFlibble/oolite/releases works.
Is that qualifyable? Where did it work?
Kubuntu 25.04. I did not notice any sound issues running the tutorial.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 10:45 pm
by MrFlibble
hiran wrote: Wed Jul 02, 2025 7:20 pm
MrFlibble wrote: Wed Jul 02, 2025 6:27 pm
Looks like I already removed that, so you'd have had to install it anyway. viewtopic.php?p=301103#p301103

Another one to try might be SDL. Try:

Code: Select all

cd ~/GNUstep/Applications/Oolite/oolite-deps/lib/
mv libSDL-1.2.so.0 libSDL-1.2.so.0.hidden
apt install libSDL-1.2-compat
If we can figure which libraries can be used 'native' on (same as build host) or newer os'es, then it'll be easy to reduce the bundle. Maybe even write a script to run at first start to check for missing deps, then suggest apt/rpm/apk/whatever install lines. I know this goes against my original hope of not needing users to install anything else, but it may be the most balanced solution when using the SE-installer.

Some of the libraries have been twisted to work for Oolite, and cannot be replaced with 'native'.
I renamed the existing file. But installing the other one seems to fail:

Code: Select all

$ sudo apt install libSDL-1.2-compat
[sudo] password for hiran: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package libSDL-1.2-compat
E: Couldn't find any package by glob 'libSDL-1.2-compat'
$ 
My bad. I should have fumbled the package name. Should be:

Code: Select all

sudo apt install libsdl1.2-compat.
hiran wrote: Wed Jul 02, 2025 7:20 pm
But what is that? Despite libSDL-1.2.so.0 is renamed, I can start Oolite?
I cannot tell why that should work at all. But I can say the stutter increased. :-(

Perhaps your setup had pulled in that library for some reason. Have a look at:

Code: Select all

dpkg | grep libsdl
hiran wrote: Wed Jul 02, 2025 7:20 pm
Some good news: I can decrease the stutter again by renaming back libSDL-1.2.so.0
That's odd. Perhaps the libSDL-1.2 bundled in the old deps is in some way modified, so it might be one that should remain in the bundle, at least for now.

Re: How to encourage more developers to be involved

Posted: Wed Jul 02, 2025 10:46 pm
by MrFlibble
hiran wrote: Wed Jul 02, 2025 7:54 pm
So I pressed Ctrl-F to activate the FPS display. After launching from the station I get between 60 to 75 FPS.
But when times get hot, it can drop down to 20. This is where it gets unplayable. The rate drops intermittently - just when I am ready to shoot.
Sometimes small corrections (even with pressing Ctrl) lead to the opposite effect. Is this all connected to the game loop?
Good question. I've seen that as long as I can remember. Anyone know?

Re: How to encourage more developers to be involved

Posted: Thu Jul 03, 2025 2:28 am
by another_commander
MrFlibble wrote: Wed Jul 02, 2025 10:45 pm
That's odd. Perhaps the libSDL-1.2 bundled in the old deps is in some way modified, so it might be one that should remain in the bundle, at least for now.
The SDL bundled in the Linux port was never modified. Only the Windows one was.