Trunk nightly

[spara]

Is this because they use the old commodities.plist definitions

Specifically, because they only use the old definitions. The old and new definitions use completely different shipdata keys so you can safely put both in the same file and have it work in 1.80 and 1.81 - for now, though, 1.81 makes no attempt to parse the old format and set prices and quantities from it.

Indeed . It has nothing to do with setShortComment. There's no market there to start with . I'll better make some js-markets first and then continue with my experiments.

I'll sort out the escort role and investigate the JS error messages later - at the moment I've got a giant mess which doesn't even compile in my Oolite folder, as I try to make planetinfo.plist static, so it's not a good time to be working on other stuff and forgetting where I've got up to with that.

Sure, no problem. That escort role needs to be corrected from 1.80 too.

[cim]

I'll sort out the escort role and investigate the JS error messages later

Done now for tonight's build. Assuming this works I'll put them into the 1.80 maintenance branch tomorrow.

[Cody]

I presume my personal equipment.plist is responsible for more of those 'unable to save' problems?
I hadn't removed it, but I have now - just thought I'd mention the errors again.

Oh yeah - should any Adders head straight for the planet after launching?

[cim]

So long as they avoid the witchbuoy, yes, that's fine. Adders have always had "shuttle" role, I think.

[Cody]

Ho-hum! This is probably down to me, but I've had that 'unable to save' problem again. Thing is, I'd had no problem saving all evening (or recently), and I have no personal equipment.plist installed this time. It happened right after crossing the Rift too - damn! Same error as before, I think:

Code: Select all

00:23:43.343 [exception]: ***** Exception in pollDockedControls [GUI keys]: NSInvalidArgumentException : Tried to add nil value for key 'aft_weapon_type' to dictionary
00:23:43.354 [gnustep]: 2014-11-06 00:23:43.354 oolite[2712] [GSMutableString-stringByAppendingPathExtension:] cannot append extension 'oolite-save' to empty string

[cim]

When you say that you'd had no problem saving - had you successfully saved since you last loaded that commander?
Presumably your ship doesn't have an aft weapon fitted?
Can you confirm that EQ_WEAPON_NONE is present in your equipment.plist?

[Cody]

#1 Yes, I'd cruised down through the Rift Worlds, saving at every stop, made the crossing - no save.
#2 Mercurial Amethyst has mil lasers on all four mounts.
#3 Yes, EQ_WEAPON_NONE is present in my core equipment.plist (I no longer have a personal one).

I've just crossed the Rift again, as it happens, and this time I had no problem saving. <scratches head>

[cim]

This is strange, then... presumably F5 or aft view was reporting the presence of the aft laser normally? (If you get this again, you should be able to launch and try to fire it...)

[Cody]

... presumably F5 or aft view was reporting the presence of the aft laser normally?

Both were and are, yes - and if it occurs again, I'll attempt to fire it.

Would crosshairs have anything to do with it? I use the pulse laser crosshair, you see.

[cim]

Crosshairs shouldn't have anything to do with it, though do make it more important to test fire it to make sure it still works.

[SirArian]

I occasionally have the same problem. I'll try to remember to check my log next time it happens and post it here.

[another_commander]

Probably just as important as providing a log in this case, would be to try to remember exactly what happened between the last successful save and the failed one: anything of notice during the game, anything done differently before saving, autosave or not, anything you can think of, even if of very minor apparent importance, could help in tracking this.

[Venator Dha]

I too have had an occasional problem with saves, using the latest Mac build (141016). I have been focused on other things so haven't looked deeply at it but my impression was that it is specific to the system, jumping to the next system all was fine again. I cannot save at a rock hermit or the main station (can't remember about extra stations) if I cannot save. I'll try to look into this a bit more to see if a specific scenario causes it.

[Cody]

Another aegis oddity - a Python (appropriately named Goodnight) launched from the Torus at Quandixe and headed more or less straight for the planet.

Had another of these the other night - a Python plus one escort dived straight into the planet and burned.
Once again, it had launched from a Torus station - possible connection?

As an aside, unplanned encounters in interstellar space are working well.

[Venator Dha]

Oolite hangs when attempting to jump from Lemaed to Ausis in Gal2, last entry in log below. Reporting as asked.

Code: Select all

15:01:13.931 [system.description.error]: getPropertiesForCurrentSystem called while player in interstellar space. This is an internal error. Please report it.
15:01:13.934 [system.description.error]: getPropertiesForCurrentSystem called while player in interstellar space. This is an internal error. Please report it.
15:01:13.950 [system.description.error]: getPropertiesForCurrentSystem called while player in interstellar space. This is an internal error. Please report it.

Code: Select all

Opening log for Oolite development version 1.81-141108 (x86-64 test release) under Mac OS X Version 10.10 (Build 14A389) at 2014-11-08 14:00:11 +0000.
Machine type: iMac11,2, 12288 MiB memory, 2 (4 logical) x x86 (Westmere) @ 3200 MHz.
Build options: OpenAL, new planets, JavaScript console support, Debug plug-in support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.