OoliteStarter

[MrFlibble]

I'll look at whether I can do something to reduce need to update. Did my previous builds work? It may just be the version of Java I'd switched up to (as the previous one was no longer getting updates).

I'm not blaming you. Your work on resurrecting gubbins for the AppleMac is superb. And I presume that it is the fault of the software you are using to transmogrify everything for the Apple. But I feel that it is a sad commentary on how things are being changed...

Your previous but one version seemed to work just fine (as proclaimed earlier). I never tried the immediately previous one.

Then I know the culprit. Am between pubs for a snack, so not tonight. No guarantees.

FWIW, MacOS versions <12 are no longer getting support from Apple. Chances are a lot of software will not be built to work on those versions as that would require using obsolete libraries etc. It may be that OpenJDK is not going to work on a now outdated OS.

[MrFlibble]

I'll look at whether I can do something to reduce need to update. Did my previous builds work? It may just be the version of Java I'd switched up to (as the previous one was no longer getting updates).

I'm not blaming you. Your work on resurrecting gubbins for the AppleMac is superb. And I presume that it is the fault of the software you are using to transmogrify everything for the Apple. But I feel that it is a sad commentary on how things are being changed...

Your previous but one version seemed to work just fine (as proclaimed earlier). I never tried the immediately previous one.

Here's latest starter built using OpenJDK 20.0.2, which AFAIK is the last version of OpenJDK that might work on OS 10.15. Please let me know if it works for you.

If anyone else needs to use this for MacOS below 11, please drop a note here so I can get an idea of user numbers.

These links will self-destruct in a month.

OoliteStarter-0.1.32-gelsemium.12-MacOS-JDK_20.0.2-x86_64.zip (61.5 MB)

OoliteStarter-0.1.32-gelsemium.12-MacOS-JDK_20.0.2-x86_64.pkg (60.88 MB)

[hiran]

The positive side of being offline was that I checked OoliteStarter and the build process' behaviour when no network resources are available. And yes, there was room for improvement.

This latest build will behave meaningful if oolite.space is not there:
- No OXPs can be installed - but you can still see and remove those that are already installed.
- An empty flavors list will be displayed

OoliteStarter v0.1.32-gelsemium.13

That should bring the gelsemium branch to an end. If no problems are detected for a week I will merge to the main branch.

[MrFlibble]

The positive side of being offline was that I checked OoliteStarter and the build process' behaviour when no network resources are available. And yes, there was room for improvement.

This latest build will behave meaningful if oolite.space is not there:
- No OXPs can be installed - but you can still see and remove those that are already installed.
- An empty flavors list will be displayed

OoliteStarter v0.1.32-gelsemium.13

That should bring the gelsemium branch to an end. If no problems are detected for a week I will merge to the main branch.

Looks like there were no problems

I've built a real-metal MacOS 10.15 (Catalina) x86_64 hack, where I've found it's do-able to build with OpenJDK 21.02, but alas not 22.x... so the end is nigh for MacOS 10.15. Even the Homebrew devs won't take bug reports about anything Catalina any more. I'll try to keep 'nigh' vague for as long as is sane, since it's not much different building on Catalina vs. Ventura, and the output is forward compatible.

I've uploaded x86_64 Catalina compatible builds to https://github.com/OoliteProject/Oolite ... ag/v0.1.32

@Cholmondely : Would you sanity check please? I found I had to delete the previous one from Applications or it didn't actually update on install.

@hiran : Might be an idea to make this an increment like 0.1.33 on the next update, as the same issue applies with debs, i.e. : "same version already installed". Difference being we get told, and get the option to 'do it anyway', whereas on the Mac it just 'looked like it worked', and hadn't.

One notable difference running this on Catalina is that is fails quite badly to launch Oolite. On Ventura starter launches Oolite fine, though of course it can't push the save file. On Catalina it chokes as shown below.

Perhaps a note should be put on the releases and readme to the effect "For now, starter on Mac can manage OXPs, but nothing else will work as expected. The 1.90 debugger on MacOS is hard-wired, and 1.90 cannot accept arguments to launch a save game."

And/Or detect that it's <=1.90 and pop up a note to say "all I can do is launch it" (assuming <=1.90 is sans the cli args to load a save game on all platforms). Clearly the debug block is Mac <=1.90 only.

Code: Select all

java.io.FileNotFoundException: /org.oolite.hiran.OoliteStarter.oxp/manifest.plist (No such file or directory)
	at java.base/java.io.FileOutputStream.open0(Native Method) ~[?:?]
	at java.base/java.io.FileOutputStream.open(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at oolite.starter.util.Util.unzip(Util.java:188) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.injectExpansion(Oolite.java:1955) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:769) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:677) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel$6.run(StartGamePanel.java:347) [OoliteStarter-0.1.32.jar:0.1.32]
                                                                                                                                                                                                                                              
mrflibble@HPSSF Logs % cat oolite-starter.log
2024-07-14 21:32:38,377 INFO oo.st.MainFrame [main] Args: []
2024-07-14 21:32:38,381 INFO oo.st.MainFrame [main] JVM: OpenJDK Runtime Environment 21.0.2+13-58
2024-07-14 21:32:38,381 INFO oo.st.MainFrame [main] OS: Mac OS X x86_64 10.15.7
2024-07-14 21:32:38,388 INFO oo.st.MainFrame [main] OoliteStarter 0.1.32  starting up...
2024-07-14 21:32:39,621 INFO oo.st.MainFrame [SwingWorker-pool-2-thread-1] Initialize UI...
2024-07-14 21:32:39,976 WARN oo.st.Oolite [Thread-0]   found 0 expansions in /Users/mrflibble/Library/Application Support/Oolite/Managed Addons
2024-07-14 21:32:39,976 WARN oo.st.Oolite [Thread-0]   found 0 expansions in /Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns
2024-07-14 21:32:39,977 WARN oo.st.Oolite [Thread-0]   found 0 expansions in /Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns
2024-07-14 21:32:40,676 INFO oo.st.Oolite [Thread-0] HTTP status for https://addons.oolite.space/api/1.0/overview/: 200
2024-07-14 21:32:41,123 WARN oo.st.Oolite [Thread-0] Performed getAllExpansions() on 771 expansions in PT1.148319S
2024-07-14 21:32:44,615 INFO oo.st.MainFrame [SwingWorker-pool-2-thread-1] Check for new version...
2024-07-14 21:32:44,697 INFO oo.st.GithubVersionChecker [SwingWorker-pool-2-thread-1] Update check skipped until 2024-07-21T19:08:53.727282Z
2024-07-14 21:32:44,702 INFO oo.st.OoliteVersionChecker [SwingWorker-pool-2-thread-1] Update check skipped until 2024-07-21T19:08:53.275959Z
2024-07-14 21:32:48,226 INFO oo.st.MainFrame [AWT-EventQueue-0] stateChanged(javax.swing.event.ChangeEvent[source=javax.swing.JTabbedPane[,0,0,1069x873,invalid,layout=com.formdev.flatlaf.ui.FlatTabbedPaneUI$FlatTabbedPaneLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=201326944,maximumSize=,minimumSize=,preferredSize=,haveRegistered=false,tabPlacement=TOP]])
2024-07-14 21:33:23,847 INFO oo.st.ut.HttpUtil [SwingWorker-pool-2-thread-2] HTTP status for https://wiki.alioth.net/img_auth.php/7/7d/Oolite.oxp.Thargoid.FuelStation.oxz: 200
2024-07-14 21:33:26,510 INFO oo.st.MainFrame [AWT-EventQueue-0] stateChanged(javax.swing.event.ChangeEvent[source=javax.swing.JTabbedPane[,0,0,1069x873,invalid,layout=com.formdev.flatlaf.ui.FlatTabbedPaneUI$FlatTabbedPaneLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=201326944,maximumSize=,minimumSize=,preferredSize=,haveRegistered=false,tabPlacement=TOP]])
2024-07-14 21:33:27,289 INFO oo.st.Oolite2 [ExpansionFolderAlterationListenerThread] Removing phantoms []
2024-07-14 21:33:32,907 INFO oo.st.Oolite [Thread-3] installing /org.oolite.hiran.OoliteStarter.oxp
2024-07-14 21:33:32,909 ERROR oo.st.ui.StartGamePanel [Thread-3] Could not run game
java.io.FileNotFoundException: /org.oolite.hiran.OoliteStarter.oxp/manifest.plist (No such file or directory)
	at java.base/java.io.FileOutputStream.open0(Native Method) ~[?:?]
	at java.base/java.io.FileOutputStream.open(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at oolite.starter.util.Util.unzip(Util.java:188) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.injectExpansion(Oolite.java:1955) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:769) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:677) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel$6.run(StartGamePanel.java:347) [OoliteStarter-0.1.32.jar:0.1.32]

[hiran]

I've built a real-metal MacOS 10.15 (Catalina) x86_64 hack, where I've found it's do-able to build with OpenJDK 21.02, but alas not 22.x... so the end is nigh for MacOS 10.15. Even the Homebrew devs won't take bug reports about anything Catalina any more. I'll try to keep 'nigh' vague for as long as is sane, since it's not much different building on Catalina vs. Ventura, and the output is forward compatible.

I've uploaded x86_64 Catalina compatible builds to https://github.com/OoliteProject/Oolite ... ag/v0.1.32

Great! You are even industrializing the builds.

@hiran : Might be an idea to make this an increment like 0.1.33 on the next update, as the same issue applies with debs, i.e. : "same version already installed". Difference being we get told, and get the option to 'do it anyway', whereas on the Mac it just 'looked like it worked', and hadn't.

Somehow I like to keep the semver counting. But what we can do is to use a different name for experimental packages -> everything that stems from branches other than master. I'll look into that.

One notable difference running this on Catalina is that is fails quite badly to launch Oolite. On Ventura starter launches Oolite fine, though of course it can't push the save file. On Catalina it chokes as shown below.

Perhaps a note should be put on the releases and readme to the effect "For now, starter on Mac can manage OXPs, but nothing else will work as expected. The 1.90 debugger on MacOS is hard-wired, and 1.90 cannot accept arguments to launch a save game."

And/Or detect that it's <=1.90 and pop up a note to say "all I can do is launch it" (assuming <=1.90 is sans the cli args to load a save game on all platforms). Clearly the debug block is Mac <=1.90 only.

Looks like the MacOS build has started becoming peculiar years ago. How else would command line switches differ for the versions but noone would notice? Adding up, with less and less Catalina support we cannot help it's getting more and more peculiar.
How is it with compiling Oolite on a post-catalina OS? I guess that would make use of the new CPU and requires lots of porting effort. Then there is the question how much it makes sense to offer OoliteStarter for that platform.

Yes, the best we can do right now is to mention it in the readme. Feel free to add a meaningful comment, as right now I'd simply copy any of your suggestions verbatim anyway. Maybe we should also add something to the UI, but what exactly, and where? By patching the main branch you'd automatically get the version number change you asked for.

Code: Select all

java.io.FileNotFoundException: /org.oolite.hiran.OoliteStarter.oxp/manifest.plist (No such file or directory)
[/quote]

This is a strange error. Could you post your $HOME/.oolite-starter.conf?

[MrFlibble]

I think Catalina will have to be put out to pasture soon-ish, though for now, what gets built there ought to work for that "and up", whereas building on 'latest' will often have backwards compatibility issues.

Yes, the best we can do right now is to mention it in the readme. Feel free to add a meaningful comment, as right now I'd simply copy any of your suggestions verbatim anyway. Maybe we should also add something to the UI, but what exactly, and where? By patching the main branch you'd automatically get the version number change you asked for.

WIlco. When I''m sure of the situation above. Also.. does 1.90 take that args to load save games on the other platforms? I've not tried it.

This is a strange error. Could you post your $HOME/.oolite-starter.conf?

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<OoliteStarter logging="/Users/mrflibble/.Oolite/Logs" starter-version="0.1.32" stored="2024-07-14T19:51:17.961114Z">
    <ExpansionManager>
        <manifestUrl>https://addons.oolite.space/api/1.0/overview/</manifestUrl>
        <updateCheckInterval>PT168H</updateCheckInterval>
    </ExpansionManager>
    <Installations>
        <Installation active="true">
            <HomeDir>/Applications/Oolite.app</HomeDir>
            <Version>1.90</Version>
            <Executable>/Applications/Oolite.app/Contents/MacOS/Oolite</Executable>
            <SaveGameDir>/Users/mrflibble/Documents</SaveGameDir>
            <AddonDir/>
            <DeactivatedAddonDir>/Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns</DeactivatedAddonDir>
            <ManagedAddonDir>/Users/mrflibble/Library/Application Support/Oolite/Managed Addons</ManagedAddonDir>
            <ManagedDeactivatedAddonDir>/Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns</ManagedDeactivatedAddonDir>
            <DebugCapable>false</DebugCapable>
        </Installation>
    </Installations>
</OoliteStarter>

I confess it is the debug version, but I didn't tell Starter, 'cos it shouldn't have any effect, or point.

Building with OpenJDK on Ventura does exactly the same.

Zapping starter config it tried to create a directory "".

Here's the log from a fresh-ish start including the baffling directory creation.

Code: Select all

2024-07-14 23:17:01,534 INFO oo.st.MainFrame [main] Args: []
2024-07-14 23:17:01,537 INFO oo.st.MainFrame [main] JVM: OpenJDK Runtime Environment 21.0.2+13-58
2024-07-14 23:17:01,537 INFO oo.st.MainFrame [main] OS: Mac OS X x86_64 10.15.7
2024-07-14 23:17:01,541 INFO oo.st.MainFrame [main] OoliteStarter 0.1.32  starting up...
2024-07-14 23:17:02,465 INFO oo.st.MainFrame [SwingWorker-pool-2-thread-1] Initialize UI...
2024-07-14 23:17:05,292 ERROR oo.st.Oolite [Thread-0] Could not load local expansions
java.lang.IllegalStateException: No active installation
	at oolite.starter.Configuration.getAddonDirs(Configuration.java:474) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getLocalExpansions(Oolite.java:1356) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getAllExpansions(Oolite.java:1194) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite2.lambda$initialize$2(Oolite2.java:280) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]
2024-07-14 23:17:05,346 WARN oo.st.ui.StartGamePanel [SwingWorker-pool-2-thread-1] Could not update
java.lang.IllegalStateException: No active installation
	at oolite.starter.Configuration.getSaveGameDir(Configuration.java:386) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getSaveGames(Oolite.java:484) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.update(StartGamePanel.java:131) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.setOolite(StartGamePanel.java:97) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame.<init>(MainFrame.java:299) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame$InitFrameSwingWorker.doInBackground(MainFrame.java:76) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame$InitFrameSwingWorker.doInBackground(MainFrame.java:61) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at java.desktop/javax.swing.SwingWorker$1.call(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
	at java.desktop/javax.swing.SwingWorker.run(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]
2024-07-14 23:17:05,373 WARN oo.st.ui.StartGamePanel [SwingWorker-pool-2-thread-1] Could not update
java.lang.IllegalStateException: No active installation
	at oolite.starter.Configuration.getSaveGameDir(Configuration.java:386) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getSaveGames(Oolite.java:484) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.update(StartGamePanel.java:131) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.setOolite(StartGamePanel.java:126) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame.<init>(MainFrame.java:299) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame$InitFrameSwingWorker.doInBackground(MainFrame.java:76) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.MainFrame$InitFrameSwingWorker.doInBackground(MainFrame.java:61) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at java.desktop/javax.swing.SwingWorker$1.call(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
	at java.desktop/javax.swing.SwingWorker.run(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]
2024-07-14 23:17:05,778 INFO oo.st.Oolite [Thread-0] HTTP status for https://addons.oolite.space/api/1.0/overview/: 200
2024-07-14 23:17:06,117 INFO oo.st.MainFrame [SwingWorker-pool-2-thread-1] Check for new version...
2024-07-14 23:17:06,148 INFO oo.st.GithubVersionChecker [SwingWorker-pool-2-thread-1] Update check skipped until 2024-07-21T19:08:53.727282Z
2024-07-14 23:17:06,153 INFO oo.st.OoliteVersionChecker [SwingWorker-pool-2-thread-1] Update check skipped until 2024-07-21T19:08:53.275959Z
2024-07-14 23:17:06,309 ERROR oo.st.Oolite2 [Thread-0] Problem in deferred initialization
java.lang.NullPointerException: Cannot invoke "oolite.starter.model.Installation.getVersion()" because the return value of "oolite.starter.Configuration.getActiveInstallation()" is null
	at oolite.starter.Oolite.validateCompatibility(Oolite.java:145) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getAllExpansions(Oolite.java:1225) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite2.lambda$initialize$2(Oolite2.java:280) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at java.base/java.lang.Thread.run(Unknown Source) [?:?]
2024-07-14 23:17:06,310 WARN oo.st.ui.StartGamePanel [AWT-EventQueue-0] Could not update
java.lang.IllegalStateException: No active installation
	at oolite.starter.Configuration.getSaveGameDir(Configuration.java:386) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.getSaveGames(Oolite.java:484) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.update(StartGamePanel.java:131) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel.statusChanged(StartGamePanel.java:53) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite2.fireStatusChanged(Oolite2.java:201) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source) ~[?:?]
	at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source) ~[?:?]
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source) ~[?:?]
	at java.desktop/java.awt.EventQueue$4.run(Unknown Source) ~[?:?]
	at java.base/java.security.AccessController.doPrivileged(Unknown Source) [?:?]
	at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) [?:?]
	at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) [?:?]
	at java.desktop/java.awt.EventDispatchThread.run(Unknown Source) [?:?]
2024-07-14 23:17:06,564 INFO oo.st.MainFrame [AWT-EventQueue-0] stateChanged(javax.swing.event.ChangeEvent[source=javax.swing.JTabbedPane[,0,0,1069x887,invalid,layout=com.formdev.flatlaf.ui.FlatTabbedPaneUI$FlatTabbedPaneLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=201326944,maximumSize=,minimumSize=,preferredSize=,haveRegistered=false,tabPlacement=TOP]])
2024-07-14 23:17:18,339 DEBUG oo.st.ui.InstallationForm [AWT-EventQueue-0] btExecutableActionPerformed(java.awt.event.ActionEvent[ACTION_PERFORMED,cmd=Browse,when=1720995438325,modifiers=Button1] on javax.swing.JButton[,506,65,74x23,alignmentX=0.0,alignmentY=0.5,border=com.formdev.flatlaf.ui.FlatButtonBorder@242326c7,flags=288,maximumSize=,minimumSize=,preferredSize=,defaultIcon=,disabledIcon=,disabledSelectedIcon=,margin=javax.swing.plaf.InsetsUIResource[top=2,left=14,bottom=2,right=14],paintBorder=true,paintFocus=true,pressedIcon=,rolloverEnabled=true,rolloverIcon=,rolloverSelectedIcon=,selectedIcon=,text=Browse,defaultCapable=true])
2024-07-14 23:21:02,078 INFO oo.st.ui.InstallationsPanel [AWT-EventQueue-0] something was selected - we want this value /System/Volumes/Data/Applications/Oolite.app
2024-07-14 23:21:02,078 INFO oo.st.Oolite [AWT-EventQueue-0] version
2024-07-14 23:21:02,102 INFO oo.st.Oolite [AWT-EventQueue-0] executable
2024-07-14 23:21:02,102 INFO oo.st.Oolite [AWT-EventQueue-0] savegamedir
2024-07-14 23:21:02,103 INFO oo.st.Oolite [AWT-EventQueue-0] addondir
2024-07-14 23:21:02,103 INFO oo.st.Oolite [AWT-EventQueue-0] deactivatedaddondir
2024-07-14 23:21:02,103 INFO oo.st.Oolite [AWT-EventQueue-0] managedaddondir
2024-07-14 23:21:02,103 INFO oo.st.Oolite [AWT-EventQueue-0] manageddeactivatedaddondir
2024-07-14 23:21:02,104 INFO oo.st.Oolite [AWT-EventQueue-0] population done
2024-07-14 23:21:02,104 INFO oo.st.ui.InstallationsPanel [AWT-EventQueue-0] offering for edit Installation{excecutable=/System/Volumes/Data/Applications/Oolite.app/Contents/MacOS/Oolite, version=1.90, homeDir=/System/Volumes/Data/Applications/Oolite.app, savegameDir=/Users/mrflibble/Documents, addonDirs=null, deactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns, managedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/Managed Addons, managedDeactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns, debugCapable=false, mqtt=null}
2024-07-14 23:21:05,600 INFO oo.st.ui.InstallationsPanel [AWT-EventQueue-0] adding installation...
2024-07-14 23:24:17,077 WARN oo.st.Configuration [AWT-EventQueue-0] activateInstallation(Installation{excecutable=/System/Volumes/Data/Applications/Oolite.app/Contents/MacOS/Oolite, version=1.90, homeDir=/System/Volumes/Data/Applications/Oolite.app, savegameDir=/Users/mrflibble/Documents, addonDirs=, deactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns, managedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/Managed Addons, managedDeactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns, debugCapable=false, mqtt=null})
2024-07-14 23:24:17,077 ERROR oo.st.ui.StartGamePanel [AWT-EventQueue-0] activatedInstallation(Installation{excecutable=/System/Volumes/Data/Applications/Oolite.app/Contents/MacOS/Oolite, version=1.90, homeDir=/System/Volumes/Data/Applications/Oolite.app, savegameDir=/Users/mrflibble/Documents, addonDirs=, deactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns, managedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/Managed Addons, managedDeactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns, debugCapable=false, mqtt=null})
2024-07-14 23:24:17,136 WARN oo.st.Oolite [AWT-EventQueue-0] Listener oolite.starter.ui.StartGamePanel[Start Game,0,33,1069x854,invalid,hidden,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=9,maximumSize=,minimumSize=,preferredSize=] took PT0.058183S to process activatedInstallation(...)
2024-07-14 23:24:17,136 ERROR oo.st.ui.StartGamePanel [AWT-EventQueue-0] activatedInstallation(Installation{excecutable=/System/Volumes/Data/Applications/Oolite.app/Contents/MacOS/Oolite, version=1.90, homeDir=/System/Volumes/Data/Applications/Oolite.app, savegameDir=/Users/mrflibble/Documents, addonDirs=, deactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns, managedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/Managed Addons, managedDeactivatedAddonDir=/Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns, debugCapable=false, mqtt=null})
2024-07-14 23:24:17,175 WARN oo.st.Oolite [Thread-2]   found 1 expansions in /Users/mrflibble/Library/Application Support/Oolite/Managed Addons
2024-07-14 23:24:17,176 WARN oo.st.Oolite [Thread-2]   found 0 expansions in /Users/mrflibble/Library/Application Support/Oolite/ManagedDeactivatedAddOns
2024-07-14 23:24:17,176 WARN oo.st.Oolite [Thread-2]   found 0 expansions in /Users/mrflibble/Library/Application Support/Oolite/DeactivatedAddOns
2024-07-14 23:24:17,295 INFO oo.st.Oolite [Thread-2] HTTP status for https://addons.oolite.space/api/1.0/overview/: 200
2024-07-14 23:24:17,565 WARN oo.st.Oolite [Thread-2] Performed getAllExpansions() on 771 expansions in PT0.403211S
2024-07-14 23:25:02,537 INFO oo.st.MainFrame [AWT-EventQueue-0] stateChanged(javax.swing.event.ChangeEvent[source=javax.swing.JTabbedPane[,0,0,1069x887,invalid,layout=com.formdev.flatlaf.ui.FlatTabbedPaneUI$FlatTabbedPaneLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=201326944,maximumSize=,minimumSize=,preferredSize=,haveRegistered=false,tabPlacement=TOP]])
2024-07-14 23:25:05,864 INFO oo.st.Oolite [Thread-4] installing /org.oolite.hiran.OoliteStarter.oxp
2024-07-14 23:25:05,865 ERROR oo.st.ui.StartGamePanel [Thread-4] Could not run game
java.io.FileNotFoundException: /org.oolite.hiran.OoliteStarter.oxp/manifest.plist (No such file or directory)
	at java.base/java.io.FileOutputStream.open0(Native Method) ~[?:?]
	at java.base/java.io.FileOutputStream.open(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at oolite.starter.util.Util.unzip(Util.java:188) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.injectExpansion(Oolite.java:1955) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:769) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:677) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel$6.run(StartGamePanel.java:347) [OoliteStarter-0.1.32.jar:0.1.32]
2024-07-14 23:25:13,718 INFO oo.st.Oolite [Thread-6] installing /org.oolite.hiran.OoliteStarter.oxp
2024-07-14 23:25:13,719 ERROR oo.st.ui.StartGamePanel [Thread-6] Could not run game
java.io.FileNotFoundException: /org.oolite.hiran.OoliteStarter.oxp/manifest.plist (No such file or directory)
	at java.base/java.io.FileOutputStream.open0(Native Method) ~[?:?]
	at java.base/java.io.FileOutputStream.open(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at java.base/java.io.FileOutputStream.<init>(Unknown Source) ~[?:?]
	at oolite.starter.util.Util.unzip(Util.java:188) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.injectExpansion(Oolite.java:1955) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:769) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.Oolite.run(Oolite.java:657) ~[OoliteStarter-0.1.32.jar:0.1.32]
	at oolite.starter.ui.StartGamePanel$5.run(StartGamePanel.java:304) [OoliteStarter-0.1.32.jar:0.1.32]

[hiran]

WIlco. When I''m sure of the situation above. Also.. does 1.90 take that args to load save games on the other platforms? I've not tried it.

See here: viewtopic.php?p=291772#p291772

This is a strange error. Could you post your $HOME/.oolite-starter.conf?

Code: Select all

<AddonDir/>

This is what I was after. You configured the addons directory to be empty and that's where the dodgy path comes from.
I'm not sure how to prevent that. OoliteStarter checks whether that directory exists (at that time it points to the current directory). And later, when more is appended it turns into an absolute path.

Maybe the field must contain at least two characters?

[MrFlibble]

WIlco. When I''m sure of the situation above. Also.. does 1.90 take that args to load save games on the other platforms? I've not tried it.

See here: viewtopic.php?p=291772#p291772

This is a strange error. Could you post your $HOME/.oolite-starter.conf?

Code: Select all

<AddonDir/>

This is what I was after. You configured the addons directory to be empty and that's where the dodgy path comes from.
I'm not sure how to prevent that. OoliteStarter checks whether that directory exists (at that time it points to the current directory). And later, when more is appended it turns into an absolute path.

Maybe the field must contain at least two characters?

The directory exists, and I'll leave it there for this test. Surely it shouldn't have to exist, I mean the rest of them don't at the outset do they? edit: see next post

Removing the starter config, and scanning anew, the addons directory is indeed blank. I shoved 'void' in that field and accepted the invitation to create it.

Piccies:

Spoiler

(I added the 'void' to replace the blank)

'find / 2>/dev/null | grep void$' showed that nothing had been created by anyone with my permissions.

Oolite still won't run, so I expect that's a separate issue.

I had in a previous run used starter to add 'fuel station'. That's still in the list of installed add-ons. If I run the game of course, I can't see that (short of going for a fly), as I've not done the add-ons fix, and can't download the list. I intend to do as much as I can in Joe Sixpack mode so we learn something about uninitiated user experience.

Code: Select all

find $HOME 2>/dev/null | grep -i ox[pz]$ | sort
/Users/mrflibble/Library/Application Support/Oolite/Managed Addons/oolite.oxp.Thargoid.FuelStation.oxz
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/src/test/resources/data/Oolite.oxp.UK_Eliter.Ferdelance_3G.oxz
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/src/test/resources/data/PHKB_Folder.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/src/test/resources/data/PHKB_Folder.oxp/Asteroids3D1.2.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/src/test/resources/data/PHKB_Folder.oxp/Galactic_Navy 5.4.3.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/src/test/resources/data/oolite.oxp.Norby.Addons_for_Beginners.oxz
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/target/test-classes/data/Oolite.oxp.UK_Eliter.Ferdelance_3G.oxz
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/target/test-classes/data/PHKB_Folder.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/target/test-classes/data/PHKB_Folder.oxp/Asteroids3D1.2.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/target/test-classes/data/PHKB_Folder.oxp/Galactic_Navy 5.4.3.oxp
/Users/mrflibble/starter/build/OoliteStarter-0.1.32/target/test-classes/data/oolite.oxp.Norby.Addons_for_Beginners.oxz

That's odd. I never installed most of those, only FuelStation which is where we'd expect.

Does starter oxp only manifest during a run? Sometimes (on both MacOS) I get a grumble about it being a duplicate.

Perhaps if I'd done the in-game download manager fix, and grabbed an oxp this would not occur, but then not having to do that is supposed to be a starter feature. Though above, we see an OXZ installed, yet starter didn't get it right on scanning. edit: Perhaps this would not occur if I'd added an oxz into the manual add-ons folder, though starter could help Joe Sixpack out with that, 'cos he won't have put anything there!

Let me know what to prod next.

[MrFlibble]

Ah!! Looking at my somewhat more weathered Linux setup, we're talking about the 'manually installed' addons!

On Linux by default (for me) it's $HOME/GNUstep/Applications/Oolite/AddOns

So... Does that have a default location on the Mac, and if so, should it not get pre-populated by starter?

I'm unclear how the paths are defined in multi Oolite install setups. I clearly need to know right now, so is it an edit to a plist in the installation path? Can you give me a clue please to save me a random deep dive?

I note from  OXP that the manual oxp dir is not always a single location, which is fun!

[MrFlibble]

A couple of observations. (back on my well-lived in Linux setup)

I've just updated to the latest dev build of Oolite. Starter noticed something had changed, but I see no easy 'refresh this entry' button to simply update the version. I could copy and paste it somehow, although there's no --version arg to oolite command, at least not one listed by --help.

I found a simple-ish clicky-userland solution: Edit the installation listed in "Oolite Versions". Hit "Select" for home directory. Re-accept as-is. This re-populates the version field properly, but that's not obvious to n00b.

 OXP says

AddOns and Managed AddOns folders

All versions of Oolite have an AddOns folder. Only versions 1.79 (2013) and onwards have the Managed AddOns folder.

The contents of the AddOns folder must not be zipped if they are to be recognised by Oolite - so OXZs will not work if they are in there.

The contents of the Managed AddOns folder must contain a Manifest.plist if they are to be recognised by your Expansions Manager (or by Oolite Starter). The Expansions Manager only checks this folder, not the AddOns folder.

oxz's DO work there. At least for current 1.91. If anyone knows when that changed, perhaps the wiki could be adjusted.

I have Oolite.oxp.KillerWolf,Spara.SothisTC.oxz in unmanaged. Starter complains Spara.Sothis.TC is required for my save and disabled yet lists Sothis.TC (sans Spara!) enabled in Expansions. Oolite is happy with it. I switched the comma for a dot in the filename, but it made no difference. Presumably an oxz fault?

Expansions shows Planetfall 2.9 in red:

Planetfall 2.9
Title
Planetfall
Description
Allows landing on planets and moons in the system at various locations.
Version
2.9
Category
Dockables

Size
1.86 MB
Author
Thargoid, phkb

Local File
/home/user/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/oolite.oxp.Thargoid.Planetfall.oxz
Download URL
https://wiki.alioth.net/img_auth.php/1/ ... tFall2.oxz

Wiki Page Information
■ Missing Dependencies
This expansion will not work properly due to these missing dependencies:
PlanetFall2 Resources 1.0
■ Required by
Do not remove. Otherwise the following other expantions will not work correctly due to missing dependencies:
Feudal States 1.16.3
Feudal PlanetFall Customisations 1.2

Couple of things there.

• "expantions" .. spell check.
• oolite.oxp.phkb.PlanetFall_Resources.oxz is present in Managed, though absent in the list. Again, this seems to work anyway, so starter is giving what appears again to be a false negative.

[hiran]

Does starter oxp only manifest during a run? Sometimes (on both MacOS) I get a grumble about it being a duplicate.

You guessed right: It gets injected by OoliteStarter just before Oolite is fired up, and it gets removed right after Oolite terminates.

Let me know what to prod next.

Not sure. You are thining outside the box and I like it. What odd ideas do other players have? As a developer I hoped to have foreseen enough situations but I am happy to learn.

[hiran]

Ah!! Looking at my somewhat more weathered Linux setup, we're talking about the 'manually installed' addons!

On Linux by default (for me) it's $HOME/GNUstep/Applications/Oolite/AddOns

So... Does that have a default location on the Mac, and if so, should it not get pre-populated by starter?

I'm happy to add such detection if only I knew what to look for. Am poking at nothing since I do not have the target machine.
If someone knows a good way to find the addons directory for a Mac please shout.

[hiran]

A couple of observations. (back on my well-lived in Linux setup)

I've just updated to the latest dev build of Oolite. Starter noticed something had changed, but I see no easy 'refresh this entry' button to simply update the version. I could copy and paste it somehow, although there's no --version arg to oolite command, at least not one listed by --help.

I found a simple-ish clicky-userland solution: Edit the installation listed in "Oolite Versions". Hit "Select" for home directory. Re-accept as-is. This re-populates the version field properly, but that's not obvious to n00b.

After all you were able to match OoliteStarter's message with the fact that your Oolite installation has changed. That's already something.
Where would you like such a button to sit? Does the user first have to select the installation, or should there be a button to rescan them all?

I have Oolite.oxp.KillerWolf,Spara.SothisTC.oxz in unmanaged. Starter complains Spara.Sothis.TC is required for my save and disabled yet lists Sothis.TC (sans Spara!) enabled in Expansions. Oolite is happy with it. I switched the comma for a dot in the filename, but it made no difference. Presumably an oxz fault?

That is difficult to tackle as these addons can be anything a user dropped into the directory. If you can zip up the relevant expansion directories and send it to me I can have a closer look.

Expansions shows Planetfall 2.9 in red:

[...]

Couple of things there.

• "expantions" .. spell check.
• oolite.oxp.phkb.PlanetFall_Resources.oxz is present in Managed, though absent in the list. Again, this seems to work anyway, so starter is giving what appears again to be a false negative.

The red color means that (un)installing this OXP will break something. Caused by conflicts or required expansions not being installed.
I will correct the typo though.

[MrFlibble]

A couple of observations. (back on my well-lived in Linux setup)

I've just updated to the latest dev build of Oolite. Starter noticed something had changed, but I see no easy 'refresh this entry' button to simply update the version. I could copy and paste it somehow, although there's no --version arg to oolite command, at least not one listed by --help.

I found a simple-ish clicky-userland solution: Edit the installation listed in "Oolite Versions". Hit "Select" for home directory. Re-accept as-is. This re-populates the version field properly, but that's not obvious to n00b.

After all you were able to match OoliteStarter's message with the fact that your Oolite installation has changed. That's already something.
Where would you like such a button to sit? Does the user first have to select the installation, or should there be a button to rescan them all?

The version fields be automatically re-populated, if that's not a resource hungry thing to do. I mean, starter prompts the user to do updates, so maybe it could handle that the user did what they were told to .. Else I suppose highlighting installations with diffs, highlighting within them that the version is the diff, and having a button in each to re-scan version, next to the version field. Minimally, a button to rescan version, but not all users will know that that's what triggered the alert.

I have Oolite.oxp.KillerWolf,Spara.SothisTC.oxz in unmanaged. Starter complains Spara.Sothis.TC is required for my save and disabled yet lists Sothis.TC (sans Spara!) enabled in Expansions. Oolite is happy with it. I switched the comma for a dot in the filename, but it made no difference. Presumably an oxz fault?

That is difficult to tackle as these addons can be anything a user dropped into the directory. If you can zip up the relevant expansion directories and send it to me I can have a closer look.

I'll give it a go downloading that from the relevant place onto a clean install first, and upload the minimal mess if that has the same issue before I dream of dumping my whole oxHell at you .

Expansions shows Planetfall 2.9 in red:

[...]

Couple of things there.

• "expantions" .. spell check.
• oolite.oxp.phkb.PlanetFall_Resources.oxz is present in Managed, though absent in the list. Again, this seems to work anyway, so starter is giving what appears again to be a false negative.

The red color means that (un)installing this OXP will break something. Caused by conflicts or required expansions not being installed.
I will correct the typo though.

All good. Apart from that it says "This expansion will not work properly due to these missing dependencies: PlanetFall2 Resources 1.0".. which is not missing.

[MrFlibble]

Does starter oxp only manifest during a run? Sometimes (on both MacOS) I get a grumble about it being a duplicate.

You guessed right: It gets injected by OoliteStarter just before Oolite is fired up, and it gets removed right after Oolite terminates.

Let me know what to prod next.

Not sure. You are thining outside the box and I like it. What odd ideas do other players have? As a developer I hoped to have foreseen enough situations but I am happy to learn.

Presumably the alarming "You need to sort this duplicate" type alert (which I ignore) is due to starter exiting less than cleanly on the previous run?