OK Diziet, that is very very good news.
However, before lighting up the fireworks, there are still a few points in this thread that confuse me.
Musmula wrote:...
The name was NumericHUDv1.3.3.oxp, but I have changed it toNumericHUD and it kind of solved the problem
but it still isnt ideal, I have some garbled text on it... quite a lot garbled text, I would send you a screenshot
but PrntScr isnt working
...
I am a bit confused, I have deleted the oxps and reinstalled them into home/GNU.../Oolite/AddOns and thy didnt
work but I have then put them into home/.Oolite/AddOns (which i made) and then it all worked but that bug with
the garbled text
...
and
Diziet Sma wrote:Since we've managed to end up with two separate issues in the one thread
here, I'll describe mine in more detail for you, Getafix..
Musmula had links too?!? What about the garbled text, right Musmula?
Is there a NumericHUDv1.3.3.oxp or was this just a typo?
Renaming to NumericHUD solved the oxp-not-loading!?!... (Smivs commented about the mandatory .oxp
extension there, but even with this correction, the case is still not consistent.)
I need more iiiiiiiinput! (Johnny Five)
Reading the thread again, I also had an
spara wrote:...My memory might fail me, but I think I needed to create AddOns folder to ~/.Oolite myself.
and
Diziet Sma wrote:When I ran the oolite-update script, the script noticed that not only should the executable
be updated, but that the AddOns symlink was not a proper folder.. so it overwrote the
symlink by creating an empty folder with the same name.
Spara is right; the oolite installation (at least the one from oolite.org) does not create a .Oolite/AddOns folder.
oolite-update
is not aware of this folder, so it does not synchronize it. Perhaps, Diziet, you could
avoid having the same case at the next oolite-update execution by setting up the symlinks in there.