1.69.1 crashes upon launch

nijineko · Post by **nijineko** » Tue Jul 17, 2007 5:04 pm

now if only i can manage to get it downloaded without the transfer rate dropping to 0!!! =D

JensAyton · Post by **JensAyton** » Tue Jul 17, 2007 5:44 pm

Commander McLane wrote:
I guess it won't try to load OXPs from another version's addons-folder, would it? Because I still do have 1.65, 1.68 and 1.69 in my applications.

It won’t try to load from the AddOns folder next to the application. If you have OXPs in ~/Library/Application Support/Oolite/AddOns/, it will load those. The log file (now at ~/Library/Logs/Oolite/Latest.log) should list all loaded OXPs by default.

Commander McLane · Post by **Commander McLane** » Tue Jul 17, 2007 6:47 pm

Ahruman wrote:
Commander McLane wrote:
I guess it won't try to load OXPs from another version's addons-folder, would it? Because I still do have 1.65, 1.68 and 1.69 in my applications.
It won’t try to load from the AddOns folder next to the application. If you have OXPs in ~/Library/Application Support/Oolite/AddOns/, it will load those. The log file (now at ~/Library/Logs/Oolite/Latest.log) should list all loaded OXPs by default.

No, don't have anything in those. Nothing in Latest.log as well.

nijineko · Post by **nijineko** » Tue Jul 17, 2007 8:48 pm

Ahruman wrote:
It won’t try to load from the AddOns folder next to the application. If you have OXPs in ~/Library/Application Support/Oolite/AddOns/, it will load those.

eh? do explain please. cause i have nothing in the ~/Library/.../AddOns/, and everything in the AddOns next to the app. ^^ course, since it's obviously loading them, i guess there are no problems. other than the ones i've already mentioned.... =D

~~edit: wooot! i can play again! the test fix seems to be working.~~ =D

JensAyton · Post by **JensAyton** » Tue Jul 17, 2007 11:10 pm

nijineko wrote:
Ahruman wrote:
It won’t try to load from the AddOns folder next to the application. If you have OXPs in ~/Library/Application Support/Oolite/AddOns/, it will load those.
eh? do explain please. cause i have nothing in the ~/Library/.../AddOns/, and everything in the AddOns next to the app.

Er, that is to say: it won’t try to load from the AddOns folder next to other versions of the application.

The bug seems to have been related to updating to libpng 1.2.18. Since that was a bug fix for a part of the library we’re not using, I switched back to the previous version, 1.2.16, for the secret test version I wasn’t mentioning in public (hint, hint). I’ll do an updater tomorrow.

nijineko · Post by **nijineko** » Wed Jul 18, 2007 12:57 am

nijineko wrote:
~~edit: wooot! i can play again! the test fix seems to be working.~~ =D

secret test version? what secret test version? *^^*

(whoops, my bad.)

(in any case, if there is a next time, it doesn't take smashing into the station more than once to pick up that kind of lesson.)

Post by **Cmdr James** » Mon Jul 23, 2007 9:41 pm

Ahruman wrote:
nijineko wrote:
Ahruman wrote:
It won’t try to load from the AddOns folder next to the application. If you have OXPs in ~/Library/Application Support/Oolite/AddOns/, it will load those.
eh? do explain please. cause i have nothing in the ~/Library/.../AddOns/, and everything in the AddOns next to the app.
Er, that is to say: it won’t try to load from the AddOns folder next to other versions of the application.

The bug seems to have been related to updating to libpng 1.2.18. Since that was a bug fix for a part of the library we’re not using, I switched back to the previous version, 1.2.16, for the secret test version I wasn’t mentioning in public (hint, hint). I’ll do an updater tomorrow.

Thats interesting, when I use 1.2.18, I get compile errors on the project, due to assigning a read only variable in pnggccrd.c

JensAyton · Post by **JensAyton** » Mon Jul 23, 2007 10:17 pm

Ahh, yes. I commented that bit out – it’s old do-nothing code to avoid unused variable warnings. I don’t think it’s related to the crash at the start of png_read_row that was causing the problem. The primary documented change between 1.2.16 and 1.2.18 is a vulnerability in reading of ‘tRNS’ chunks, which doesn’t affect the Mac build of Oolite (‘tRNS’ reading is disabled in pngusr.h).

Edit: the 1.2.16 source is available from SourceForge. I’ve updated the wiki.

Post by **Eric Walch** » Tue Aug 28, 2007 8:06 pm

Last weekend I downloaded the 1.69.1.1 updater and used it on version 1.65

On starting oolite it says : Faling to start up, unandled exeption occured:

OoliteOpenGLTooOldExeption

I don't know wat it means, but some file seems to be missing or not updated.

I run it under OSX.4.6

JensAyton · Post by **JensAyton** » Tue Aug 28, 2007 8:24 pm

This is a bug in Oolite 1.69-1.69.1.1 where the version check for OpenGL required OpenGL 1.2 instead of OpenGL 1.1. This has already been fixed in the mainline; I’m preparing a 1.69.1.2 updater which fixes this (and this only).

Post by **Eric Walch** » Fri Sep 07, 2007 7:45 am

On testing the trumbles yesterday I stumbled over another bug. On starting Oolite I always press "Y" for loading an old game. Yesterday I started a lot of "New" games. A few times I hit accidently the "Y" and used a cancel in the next "open file" dialog.

In version 1.65 this left you with a new captain.

In version 1.69.1 (Mac) you are brought back to the choice Y/N but it does not react on either and leaves no option but to quit oolite.

JensAyton · Post by **JensAyton** » Fri Sep 07, 2007 8:23 am

Actually, you’ve got a new captain and are on the F5 screen. This is a known bug, #11691.