Onrira inaccessable in 1.75.1?

[Gnudoll]

I tried jumping into Onrira in G1 from both Larais and Erlaza both of which are in easy jump range, and when I came out of the witchspace tunnel I ended up with no controls, no station, no planet, no nothing. I could not even pause the game to quit. (Had to hit <F12> to put the game in a window and quit that way. Onrira shows up in the galactic chart, but I cannot jump in to it from any direction.

Oolite version: 1.75.1
OS : Linux Debian
CPU : pentium M @ 2.13Ghz
RAM : 2Gb
GPU : ATI Radeon Mobility (M22) /64Mb VRAM

Average FPS: 16-50

I can list my OXPs if that is needed to reproduce this?
I tried to go to the bug tracker, but that is not responding. . .

[Commander McLane]

A list of your OXPs would certainly be helpful.

Obvious question: have you tried without OXPs? And to which result?

[JensAyton]

Sounds like an unhandled exception. This is one of those cases where the log would actually be useful.

[Gnudoll]

have not gone in without OXPs, will try that as well. I'll go in again to produce a log (if I can) and post it here?

[Gnudoll]

from pastebin (I know better than to copy the whole thing *here* :



http://pastebin.com/YNSH9gqm

[JensAyton]

An OXP, presumably Famous Planets, is trying to change the planet texture, but it appears to be misspelled in a config file or script (“Onria.png” instead of “Onrira.png”). Oolite’s fallback behaviour is then breaking.

I’m downloading the current version of Famous Planets to try to recreate the situation, but I’m not going to wait up forty minutes.

[Gnudoll]

It is only happening if I have Famous Planets and System Redeux both installed. If I take either of them out it works fine. . .

[JensAyton]

Apparently this was already fixed in trunk; there are log messages, but instead of throwing an exception and breaking the game, all colours are set to white. I’ve checked in slightly more graceful behaviour in r4527.

The triggering bug (misspelled texture name) is in Famous Planets and persists in version 2.5.

[Gnudoll]

Thanks, I'll fix the file on my computer, and we can leave it to the OXP author to fix it upstream.