Magic Refueling bug, cause (maybe found)

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
Frame
---- E L I T E ----
---- E L I T E ----
Posts: 1477
Joined: Fri Mar 30, 2007 8:32 am
Location: Witchspace

Magic Refueling bug, cause (maybe found)

Post by Frame »

When i first played oolite i started out with 1.65
I then offcourse installed the 1.68 test version installer found in the PC section..

Im not particulary sure what happend, but here goes...

i recently did a fresh install of oolite 1.68, i noted the difference of the directory structure at once..

Now :

Standard non oxp Resources are now found in oolite.app/resources

Then

i had two directories for resources

oolite.app/contents/resources/*.*
and
oolite.app/resources/*.*

I think what happend then, was that i installed 1.68 ontop of 1.65, without actually uninstalling 1.65

i know, bad of me.. but maybe a blessing since that may had me stumple upon the cause of this bug...

At least i have not had a magic refuel when station aegis came up, since the fresh 1.68 install

I cant recall who it was who also had this "problem", but confirmation of my theory would be nice....

I´ll do a checkup with a new install of 1.68 ontop of 1.65 later.... since i have no time atm due to some Real life issues that has come up...

unpleasent ones i might add, but enough about that...
Bounty Scanner
Number 935
User avatar
Commander McLane
---- E L I T E ----
---- E L I T E ----
Posts: 9520
Joined: Thu Dec 14, 2006 9:08 am
Location: a Hacker Outpost in a moderately remote area
Contact:

Post by Commander McLane »

I did a fresh install of 1.68 in a different subdirectory right from the beginning and didn't have the Magic Refueling Bug at all.

So maybe you're right here.
User avatar
JensAyton
Grand Admiral Emeritus
Grand Admiral Emeritus
Posts: 6657
Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:

Post by JensAyton »

That’s weird. Anyway, I’d like to know whether anyone experiences this bug after doing a fresh 1.68 install.
Post Reply