Oolite Bulletins

Oolite test release 1.69.1 - Argh, That Wasn’t Supposed to Happen Edition is now available from GURPO. This release focuses on severe bugs in 1.69. An updater is available in the form of a patch to update the 1.69 installer (“Oolite-1.69-test.exe”).

Changes since Oolite 1.69:

• Several crashes and other severe bugs fixed.
• Fix for a wide class of potential crashes and strange behaviours which were latent in earlier versions but obscured by an otherwise unhelpful caching mechanism.
• Fix for ship death_actions and script_actions not working.
• Fix for awardCredits: stealing all your money.
• Fix for shipyard refusing to sell ships whose price is less than your current trade-in value.
• Added notequal operator to legacy scripting system.
• Reduced trade-in values by 25% across the board to reduce market exploits.
• Temporarily disabled procedurally textured planets to avoid a crashing bug.
• Fix for problem with ships that have multiple common roles being created by scripts and having the wrong AI, as discussed here.
• Better handling of out-of-range numbers in property lists.
• Fix for JavaScript methods randomly not doing anything. Also fixed system.legacyAddShipsWithinRadius() ignoring radius parameter.
• Fix for scripts running while paused, if on a menu screen.
• Fix for wrong galaxy being shown when switching from Open screen to Map screen.
• Fix for out-of-range laser heat value in shaders on demo screen.
• Damaged equipment is now shown in orange as intended.
• Big yellow question mark is now shown as intended on the Open screen when selecting a saved game using an unavailable ship.

Just installed 1.69.1 and it refuses to start. It simply crashes and returns to the desktop before it's even got going.

If you have Orb.oxp installed this happened to me. I found 1.69 would not run at all with this in. But not everyone has had this problem.

I don't have Orb.oxp - I uninstalled it cos they were too chatty! The oxps I have are:
aegidian-special
Assassins
behemoth
clearskies
cobra3njx
cobdra35
Commie_vipers
Commies
Commissar Limousine
Dictators v1.2
Falcon
fuelpod
globestations
grass_snake
GrittyCoriolis
halsis
hOopyCasino
impcourier2
kleptohud
longway
marett_vol1
MildAudio
military
Missionaries
newships
nuke
outrider
Pirate_coves
Political Police
PTSF200
renegade_viper
renegades
santa
sunskimmers
supercobra
Thorgorn_Threat
tiger
tori
tugs
urutu_IV
wolfmk2
Worker's Commuter
x-ships

Are any of these known to pose a problem with 1.69.1?

Had same thing with Thorgorn_Threat. Try taking that out. Shame as its one of my favorite OXPs. Not everyone seems to hit this problem, but I did.

OK, that worked, thanks. As you say, squashing bugs won't be the same anymore

Now the crosshairs in the centre of the screen (from the kleptohud) don't appear, which is kind of annoying as it was so handy for targeting.

This version works a treat. No more freezing!
and that's on a vaio with 256mb ram !
great stuff !

any ideas to what may be causing the Thargorn-errors?
(DONT say it's bugs!)

Its complaining about:-
However, although it says its fixed it, Oolite exits to desktop before the rotating cobra III appears. (Windows XP - Oolite 1.69.1). Maybe its the extra content that is causing the bail?

I frequently have this error message when coding...it gives an error at a certain entry, completely identical to a previous one (save some superficial parameters and key) and it keeps giving this error untill I delete it and type it all fresh. (no copy/paste allowed)

I'm not quite sure what causes it.
Maybe a wrong sysntax option is set.
Maybe I keep making the same typo errors.
I'll look into it.

LB: The crash after Oolite says it will attempt to fix the broken plist was due to an incompatibility between GNUstep and NeXTstep and has been already fixed in the source trunk.

AH: The error in the Thorgorn OXP shipdata.plist is an extra '?' character at the beginning of the file. The shipdata.plist is UTF-8 format and you will have to convert it to ASCII using a text editor to see the problem (at least I had to). If you want, PM me and I can send you a fixed version of the plist.

[Edit: It was actually a '?', not a 'y']

I sometimes have some special characters at the header, I think two or three including a y with two dots on top.
edit: (  ) when I convert to ASCII from UTF-8 format.
removing them and saving in ASCII solves the CTD on bootup.

i get alot of these: really alot, for many locations.

The invalid enumerant message is a known issue. See here for a way to get rid of it, as it appears to be harmless. You don't happen to have an ATI graphics card by the way, do you?

hehe yep. RadeonX800ati

I just installed the new v1.69.1 version for PC.

I have a few problems, don't know whether from this new version or from changed setting in graficsdrivers since my 'reboot'.

1-I cannot make out the stalks of the scanner lollipops. At best they look like a lighten-layer was applied to the background console.

2-no ambient light. Very realistic and dark, however, as only the side facing the sun is lighted, and usually you are flying towards the sun/planet, objects are invisible. Thank Giles for the flashers in the dockingport, alse I'd be flying blind. (kinda like docking in the retro-times)

3-not critical, but nebulae and exhaust are added or something, causing some nebulae to be brighter if covered by the exhaust plume.

Arexack_Heretic wrote:

3-not critical, but nebulae and exhaust are added or something, causing some nebulae to be brighter if covered by the exhaust plume.

This is correct behaviour. It took effort and everything. :-)