Oolite Bulletins

Yep EV, it was indeed directed at you, thanks!

Now, if you could remember which vanilla system(s) you jumped to just before the CTDs, that would help a lot in replicating that problem at this end!

This suggests that my system populator refactoring didn't go as well as I hoped.

Did the crashes happen before the spinning cobra at the very beginning?

To further expand on the previous answers: In homage to Bell & Braben, & Giles (praise be! * ) Default is just an alias for RP English . And, to be honest, the fact that 'a few' of the dev team are UK based (or close enough - go europe! :P) kind of helped too. Granted, eSpeak isn't terribly ...

He probably fell victim to rev5283... (hi!) it's all visible again as of rev5287 though!

EDIT: jinx !

Update: as of trunk rev5285, the position and number of hermits in any system is still subject to change over time (hermits come, hermits go... same old, same old). However, hermit population changes are now dependent on the game clock, rather than being totally random as before... :) Provided I've ...

I'm not quite sure what you mean there: I've repainted a texture file as just one block of colour - bright orange, to make it stand out - and Oolite seems to create my orange monstrosity without any problem.

What steps are you taking in order to create monochromatic ships?

Thread necromancy powers, go!


And - to keep with the horror theme - Renfield mode, activated: ooh, this looks like a juicy bug!

please stay tuned...

I seem to remember cim made an OXP that adds  new cargo types which would only bring profit if brought to the right planet.

Shipbuilder, have you tried that out? And how does it compare to what you have in mind?

Since no-one has answered so far: quite simply no developer felt the need for the kind of joystick setup you're talking about, so you could call it an oversight! :) Most of us devs seem to be happier controlling Oolite with either keyboard or - apparently - their mouse. As a result joystick support ...

From the better- very -late-than-never department: the most likely cause of a segfault in oolite is trying to dereference a pointer that's already null, and/or trying to use an uninitialised pointer... it does fall under the dreaded memory management catch-all, and it's more-or-less the opposite to ...

Ok, the emergency launch code behaviour might well have been a mistook I maed way back then... I suppose I'll have a proper look at some point!

Well, since cim has bravely waded into the GUI code the F5F5 screen is probably as good as it's going to get, but I'll see if I can add some extra info to the map screen ( "35 t computers expected by xxx:xxxx" / "J'dft Arrtew to arrive by xxxxxx:xxx" ) when a contract destination...

Hmm, without interstellar undocking, the behaviour is supposed to be consistent with 1.65, which didn't have interstellar undocking: the player could still launch at will, but upon launch they'd find themselves in a nearby system, rather than in interstellar space. The assumption was that the carrie...

Capt. Murphy wrote:

But there is no way in 1.76.1 (or in trunk as yet) to reliably validate that that the entity in question is definitely a Griff ship

Have you tried testing for its unique role? If (ship.hasRole('uniqueRole')) should do the trick...

Hmm, both commodity definition and savegame stuff can be sorted out relatively painlessly, retaining the old canonical names recognition for old save games - as when we switched to a proper equipment list in savegames... Anyway, definitely dangerous, expecially the incomplete / broken way it's in tr...