Oolite 1.77 deployment build issues

[JazHaz]

NB: Please use this thread for reporting of issues with the new release of Oolite v1.77 deployment build.

[JazHaz]

First issue. The changelog notes this:

Bug fixes:
==========

* Added missing new keyboard controls to the BBC keyconfig.plist

However the BBC keyconfig.plist is not included in the distribution.

I checked Berlios and found the correct version, and the wiki now has the correct download locations for it, here.

[another_commander]

It is not exactly an issue. The Windows version of Oolite never came packaged with the BBC keyconfig file. Thanks for pointing this out though, we can consider for inclusion in future releases.

[Eric Walch]

However the BBC keyconfig.plist is not included in the distribution.

It is included in the Mac distribution.

But it is a file that is not part of normal Oolite, so we tend to forget this file. And seeing the last modification date, we probably forgot to add the new 'b' key to that file.

[another_commander]

And seeing the last modification date, we probably forgot to add the new 'b' key to that file.

Actually, it is in there and it was added by you, Eric.

[Cody]

<chuckles at the seeming disarray at the Admiralty>

Okay - playing which version is most useful to you lot - 1.77 deployment or trunk nightlies? I can't split my play-time between the two.

[Disembodied]

Problem with the Mac version of 1.77 deployment build. I've downloaded version 1.77 (twice, now, in case of a corrupt download) and have received the same crash report for both downloads:

Code: Select all

Date/Time:      2013-01-08 14:13:55.469 +0000
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: Oolite
Path:    /Users/duncanjones/Desktop/Oolite 1.77/Oolite.app/Contents/MacOS/Oolite
Parent:  WindowServer [55]

Version: Oolite version 1.77 (1.77)

PID:    221
Thread: Unknown

Link (dyld) error:

Symbol not found: ___stack_chk_guard
  Referenced from: /Users/duncanjones/Desktop/Oolite 1.77/Oolite.app/Contents/MacOS/Oolite
  Expected in: /usr/lib/libSystem.B.dylib

One other thing slightly awry is that the icon shown is generic, not the Oolite one. As the game fails to open at all, though, I can't comment on the rest ...

[another_commander]

Problem with the Mac version of 1.77 deployment build. I've downloaded version 1.77 (twice, now, in case of a corrupt download) and have received the same crash report for both downloads:

Code: Select all

Date/Time:      2013-01-08 14:13:55.469 +0000
OS Version:     10.4.11 (Build 8S2167)
Report Version: 4

Command: Oolite
Path:    /Users/duncanjones/Desktop/Oolite 1.77/Oolite.app/Contents/MacOS/Oolite
Parent:  WindowServer [55]

Version: Oolite version 1.77 (1.77)

PID:    221
Thread: Unknown

Link (dyld) error:

Symbol not found: ___stack_chk_guard
  Referenced from: /Users/duncanjones/Desktop/Oolite 1.77/Oolite.app/Contents/MacOS/Oolite
  Expected in: /usr/lib/libSystem.B.dylib

One other thing slightly awry is that the icon shown is generic, not the Oolite one. As the game fails to open at all, though, I can't comment on the rest ...

Not a Mac person here, so please feel free to ignore this if it is for any reason incorrect, but your report indicates that you are running OS version 10.4.11, while in the release announcement we have:

System requirements:
====================

Mac-specific
------------
* Oolite now requires an Intel processor and Mac OS X 10.5 or later.

I'll leave it to the Mac maintainers to confirm, though.

Also, I really think each bug report should be going to its own thread. That's why we have the Testing and Bug Reports forum. If we throw everything in the same thread it will get really messy really quickly.

[Disembodied]

Not a Mac person here, so please feel free to ignore this if it is for any reason incorrect, but your report indicates that you are running OS version 10.4.11, while in the release announcement we have:

System requirements:
====================

Mac-specific
------------
* Oolite now requires an Intel processor and Mac OS X 10.5 or later.

I'll leave it to the Mac maintainers to confirm, though.

That probably nails it, though, right enough! Looks like it's time for me to get the hammer out and play "hunt the piggy bank" ...

[Cody]

Also, I really think each bug report should be going to its own thread. That's why we have the Testing and Bug Reports forum. If we throw everything in the same thread it will get really messy really quickly.

<nods> Re-title the thread?

[Diziet Sma]

However the BBC keyconfig.plist is not included in the distribution.

It is included in the Mac distribution.

'Tis not included in the Linux version either..

I've added the 'b' key to the  Oolite Keyboard Controls page on the wiki, and updated the entry for the Energy Bomb also.

[JazHaz]

My Windows desktop shortcut icon for launching the game doesn't work. I think its because of the parameters I used to pass to the game:

Code: Select all

C:\Oolite\oolite.app\oolite.exe -nosplash -fullscreen -load c:\oolite\oolite.app\oolite-saves\Poseidon.oolite-save

The only way I can get the game to run is to execute oolite.exe from within the oolite.app window.

Are any of these parameters not working for deployment builds now?

[another_commander]

JazHaz: It looks like the backslashes in the path for the savegame are not appreciated with the new Oolite. Not sure why this is, will have to investigate. Try changing

Code: Select all

C:\Oolite\oolite.app\oolite.exe -nosplash -fullscreen -load c:\oolite\oolite.app\oolite-saves\Poseidon.oolite-save

to

Code: Select all

C:\Oolite\oolite.app\oolite.exe -nosplash -fullscreen -load "c:/oolite/oolite.app/oolite-saves/Poseidon.oolite-save"

Hopefully this should be able to fix the shortcut problem. At least it allowed me to launch a savegame from a shortcut on my system.

[JazHaz]

JazHaz: It looks like the backslashes in the path for the savegame are not appreciated with the new Oolite. Not sure why this is, will have to investigate.

Hopefully this should be able to fix the shortcut problem. At least it allowed me to launch a savegame from a shortcut on my system.

Yes that worked. Strange though. It used to work with trunk fine.

[JazHaz]

I have Povray planets installed, the planetary textures display when up close to a planet, however at long range all you can see is the cloud layer. This doesn't look right to me.


Oolite 1.77 planet textures by JazHaz, on Flickr