Oolite Bulletins

Works for me too on Win7 64-bit. Can you please remove all other OXPs and test again whether your crash still occurs or not?

Edit: Tested both with the mission variable in the save file and without. Works on both cases.
Edit2: You are not using Notepad for editing by any chance, right?

Notepad++

After a reboot the behaviour is different.
First compile (which I was expecting to work) failed, subsequent recompiles are ok - even the cases which were failing.

Is there anything in the logcontrol.plist I can set to make it spit out any more info ?

I will try another reboot, then will try without the other oxps

Try seeing if there is any stderr.txt leftover in the oolite.app folder after the crash. If there is and is not 0 bytes in size, please post the contents.

In logcontrol.plist, switch script debug on by finding the line that reads (it is near the beginning of the file) and changing the no to a yes.

And Notepad++ is an excellent editor choice.

stderr.txt:- All very weird

So, is it crashing also without any other OXPs? If yes, would you mind sending the OXP as you currently have it to another_commander at oolite dot org? Could you also include the save file you are testing with?

As for the stderr.txt message, I was hoping to see something more in there, but don't worry about it. It's not related to the problem at hand.

Curiouser and Curiouser

I have renamed the AddOns folder, and the ManagedAddons folder - so NO oxps at all.

The FIRST shift-launch after a reboot fails, subsequent shift-launch is ok !

NB this is before I get as far as loading a save file so I don't think that is going to help you !

If I then un-rename my addons folders then it still doesn't fail - I can't force it to fail now - but I guess it might start happening again later on !

New version posted:-

If when it goes on the wiki - would anyone care to suggest a price?
and / or a name - is Galactic Sat Nav ok ??


v0.01
I have added support for system ID 0
I have made it non - damageabe (it is a software update after all!)
I have told it to reset itself if galaxy changes

https://www.dropbox.com/s/a6dwjsffba9nr ... v.oxz?dl=0

For some variety you can try the 32bit test version of Oolite 1.80. If the crash happen again then we will know that it is not 64bit related nor deployment version related. As a side effect you can use time acceleration to reduce waiting during testing: press p, shift+F then left-right arrows to change.

Equipment: the price can be cheap like 10cr and the name is ok imho.

Same behaviour.
First shift-run after a reboot it does not launch.
subsequent ones are fine

I don't get it. I can't reproduce this issue here and cannot understand why it's happening to you either.

Nope.

I am not going to worry too much though ! - Unless it becomes a problem.

That last attempt was 32bit test version, fresh reboot, NO OXPs shift-run - crash.
Then subsequent shift-runs are fine. Very strange.

Still I have managed to upload the SatNav oxz to the wiki, and a manifest to the oxp manager.

It all seemed to download / install ok for me through the oxp manager interface

One more dumb question - How do I start off a new wiki page - is there a folder / hierarchy or similar that I should put it in?

wyn_sleeman wrote:

How do I start off a new wiki page

My way is a forced exception: type an invalid page url like http://wiki.alioth.net/index.php/GalacticSatNav then click on the edit page link.

Norby wrote:

wyn_sleeman wrote:

How do I start off a new wiki page

My way is a forced exception: type an invalid page url like http://wiki.alioth.net/index.php/GalacticSatNav then click on the edit page link.

...which is indeed the right way. If you want spaces in there use underscores. The Oolite wiki is a MediaWiki installation. They have tons of info to get you started. Or just ask around here on the BB.