OoliteStarter

[hiran]

Oolitestarter is fantastic! I would like to see one small feature - the full date and time of saved games and possibly highlighting the latest saved game. I've made a feature request: https://github.com/OoliteProject/OoliteStarter/issues/7

Now that makes me smile. Here is an old screenshot from OoliteStarter: viewtopic.php?p=289596#p289596
You can see it displayed the full date/time for save games. Don't know when, but I was talked out of that idea.
It's easy to bring it back...

I do not see any need to highlight the latest game. Just click the column header and you get the savegames sorted by that column (this works reliably even if just the date is shown)

Check out v0.1.33-innocuous.4

[mcarans]

Now that makes me smile. Here is an old screenshot from OoliteStarter: viewtopic.php?p=289596#p289596
You can see it displayed the full date/time for save games. Don't know when, but I was talked out of that idea.
It's easy to bring it back...

I do not see any need to highlight the latest game. Just click the column header and you get the savegames sorted by that column (this works reliably even if just the date is shown)

Check out v0.1.33-innocuous.4

That's just what I wanted. Thanks so much!

[arquebus]

When I get some time I'll see if I can reproduce it again on video, and I'll zip up the settings etc.

[arquebus]

I've reproduced the issue on the current version 0.1.33. I've made a video that shows the problem in action. It's a combination of things: unclear UI and multiple versions of expansions being loaded into the game without any indication (in the UI) that this is or isn't going to happen. (It happens with some expansions but not with others and you can't tell ahead of time which ones it's going to happen to - you have to load the game and parse the error messages on the main menu screen.)

https://www.youtube.com/watch?v=jYzvPVsoDjc

[arquebus]

I'm still encountering the issue where removing the old version of an expansion also removes the newer one (usually - maybe not always.)

[arquebus]

Here's a video showing the second problem (removing old versions removes both versions):

https://www.youtube.com/watch?v=UXhrCuqmw_A

[hiran]

I've reproduced the issue on the current version 0.1.33. I've made a video that shows the problem in action. It's a combination of things: unclear UI and multiple versions of expansions being loaded into the game without any indication (in the UI) that this is or isn't going to happen. (It happens with some expansions but not with others and you can't tell ahead of time which ones it's going to happen to - you have to load the game and parse the error messages on the main menu screen.)

Any hints how I can reproduce this behaviour on my side?

Apart from that: OoliteStarter can check the files in the filesystem, but it cannot predict which or in what sequence they will get loaded in Oolite. I guess the best way of getting real information is to look at Oolite's logfile.

[arquebus]

Any hints how I can reproduce this behaviour on my side?

Honestly, I don't know, it's literally the only behavior I'm seeing - it's not like I'm doing anything specific to make it happen. I load OoliteStarter, update an expansion, start the game and see the duplicated expansion error. And after some further testing it does appear that every time (not only most of the time) I attempt to remove the older of two versions of an expansion, both get removed from the list in OoliteStarter. (I haven't yet checked to see if they are both removed from the expansion directory.)

Apart from that: OoliteStarter can check the files in the filesystem, but it cannot predict which or in what sequence they will get loaded in Oolite. I guess the best way of getting real information is to look at Oolite's logfile.

Are the different versions of the expansions being stored in the same directory that Oolite loads expansions from? Or are the old versions supposed to end up in another directory? If all versions are in the AddOns directory then I'd be surprised if Oolite *didn't* throw errors for everyone every time there were two versions in the loaded list.

[arquebus]

If I get some time this weekend I'll do the same steps again, and provide the OoliteStarter log file and the Oolite log file as well.

Behind the scenes, in the file/directory structure, what is the expected behavior for OoliteStarter? What does it do with the deprecated versions of expansions when a new one is installed from the list on the left?

[hiran]

Are the different versions of the expansions being stored in the same directory that Oolite loads expansions from? Or are the old versions supposed to end up in another directory? If all versions are in the AddOns directory then I'd be surprised if Oolite *didn't* throw errors for everyone every time there were two versions in the loaded list.

Expansion management is still done according to the diagram:



We decided to no longer offer enable/disable as it is too confusing for users. Thus the only directories in use are ManagedAddons and Addons.
The install operation will download expansions and drop them into MangagedAddons, the delete operation will remove the file from the filesystem.
Update is a combination of install/delete. No rocket science there.

To know where these directories are on disk just check the configuration:



For each of the expansions OoliteStarter also shows where on disk this expansion is to be found. Look for the LocalFile entry in the lower section. In this example it is null as the selected expansion is available for download but not installed:



I know you can have multiple oxz files in the ManagedAddons and Addons directories resembling the same OXP or different versions of it. All you need to do is rename one of the files, or copy them to the other directory - Oolite will load them regardless. The difficult bit is then to tell which of the OXPs will win or if all of them are active at the same time. If you want to know what is on disk extract all the manifest.plist files from the OXPs and compare the required keys.