Oolite Bulletins

i got it!



ha ha, the mighty Mac empire reaps its righteous reward.

@ Ahruman.
Where do you want crash reports, in Testing and Bug Reports or in Oolite - Mac?
Yes, I know it might seem obvious but I think it's a valid question.

Uh Oh

Ahruman wrote:

Also, Giles hasn’t responded to my query about another_commander’s Advanced Navigational Array. I think I’ll choose to interpret that as “not now”.

I just had a look at how this is progressing and - actually - I like it.

I'd like to see fastest/safest/most interesting (least safe) options presented as different coloured lines, please (simply supply different journey-cost formulae in the A* algorithm).

Go include it if you like!

aegidian wrote:

Ahruman wrote:

Also, Giles hasn’t responded to my query about another_commander’s Advanced Navigational Array. I think I’ll choose to interpret that as “not now”.

Actually, I really did mean “not no”. :-)

Uncle Reno wrote:

@ Ahruman.
Where do you want crash reports, in Testing and Bug Reports or in Oolite - Mac?
Yes, I know it might seem obvious but I think it's a valid question.

It’s not obvious, no. I suppose matters of game behaviour would be T&BR, while crashes should go with the respective platform.

I’ve found the old structure, which treats the Linux and Windows ports as weird, deviant variants, rather grating for a while. I assumed it was also getting to bother those weird deviants who use them. ;-) Oolite is very definitely a cross-platform thing now, though.

Ahruman wrote:

aegidian wrote:

Ahruman wrote:

Also, Giles hasn’t responded to my query about another_commander’s Advanced Navigational Array. I think I’ll choose to interpret that as “not now”.

Actually, I really did mean “not no”.

Fairy Nuff!

Good work - downloaded, updated. working. Hope the kludgy updater didn't cause you too much grief.

Ahruman wrote:

I’ve found the old structure, which treats the Linux and Windows ports as weird, deviant variants, rather grating for a while. I assumed it was also getting to bother those weird deviants who use them. Oolite is very definitely a cross-platform thing now, though.

I'd agree, berlios oolite-linux really ought to be berlios oolite. Perhaps a nice email to the berlios mods can arrange this, especially now we're GPL.

Whatever - you're in the pilot's chair Ahruman, you decide where to jump next...

aegidian wrote:

Whatever - you're in the pilot's chair Ahruman, you decide where to jump next...

Oh, dear. I wonder what this button does…

YeeeHaaa

^5 Giles

Cmdr. Maegil wrote:

It says it's for Mac OS... I'm a poor Windows user!

As for this… yes, well. I can’t really help you there, unless you feel like buying me one of those new Intel Macs and a copy of Windows. :-) (Actually, a second-hand one will do, I’m not picky…)

Barring that, well, dajt is suffering from a bout of Real Life at the moment, and Winston has evaporated. Any volunteers?

Ready...Yep, Willing...you betcha, Able...oh, so far from it.

Arexack_Heretic wrote:

Ahruman wrote:

people to stop distributing OXPs with debugOn/debugOff (or bugs) in.

That would be ideal yes.

Yes, that would (especially the one in brackets). However, there are even some examples in the scripts within Oolite (e.g. the death_actions of the cloaking device).

But there is another thing that bothers me. I've come across one method that doesn't seem to work (at least in script_actions) without being debugged. addShipsAtPrecisely seems to produce a CANNOTADDSHIPAT-error in my logfile when standing by itself, but works fine when included in debugOn/debugOff. I have no idea whatsoever why, but it is reproducable.

BTW, for my own debugging while playtesting I prefer commsMessages above debugOn/Off, because I can immediatly see the information I want to know (the state of some variable, whether a certain part of the script is run at all, or whatever) without having to switch to the console first. My 15-inch-display does not seem particularly small to me, but it isn't big enough to have Oolite and the console in non-overlapping windows.

Commander McLane wrote:

But there is another thing that bothers me. I've come across one method that doesn't seem to work (at least in script_actions) without being debugged. addShipsAtPrecisely seems to produce a CANNOTADDSHIPAT-error in my logfile when standing by itself, but works fine when included in debugOn/debugOff. I have no idea whatsoever why, but it is reproducable.

Can you send me a test case OXP?

@ Ahruman: I'll try to assemble a small test-oxp. Have to remember first how the bug exactly occured.

But I have a general question (or worry) as well. If it is stupid, just tell me so.

You are overhauling the Oolite.app here, and Dajt is--as far as I understand--doing the same, but differently, for the Oolite.exe in this thread.

Now does that mean that eventually Oolite for Mac and Oolite for Windows will drift apart, or will there be a re-integration of the developments later? I mean, we don't have a Master and Commander again.

Again sorry if that sounds like a stupid question. But I feel compelled to ask anyway.