Page 1 of 2

OXP's and 1.75

Posted: Thu Mar 31, 2011 11:07 am
by lave
I am looking forward to upgrading to 1.75.
However I see that the oxp compatibillity list is still not yet complete. I understand that this is going to take time.

The main OXP's that I just can't live without, and that are currently not compatible with 1.75, are:

Black Monk Monastery
BlOomberg Markets
Dictators
ETT Homing Beacon
Feudal States
Galactic Navy
Interstellar Help
Lave
Oo-Haul missions and ships
Pelamis (I intend to buy one of these)
Save Anywhere (very important for me because I don't always want to have to be docked to save)
Special Interstellar Repair Facilities
Your Ad Here

Is anyone working on these to get them up to 1.75 standards?

Thanks.

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 11:35 am
by Lone_Wolf

Code: Select all

The "C" column indicates compatibility with Oolite beta 1.75:

"Y"=compatible, "Y*"=compatible (but the OXP is not in full working order), "N"=incompatible, blank=unknown/untested. 
Feudal States does work for me with 1.75.1 , and i'm pretty sure Ramirez already fixed a few bugs, see the thread in expansion packs.


ETT Homing beacon was originally written for oolite 1.62, so unless someone adopts/updates the oxp, it seems unlikely it will ever work in 1.75 or MNSR.

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 1:34 pm
by Fatleaf
lave wrote:
I am looking forward to upgrading to 1.75.
However I see that the oxp compatibillity list is still not yet complete. I understand that this is going to take time.

The main OXP's that I just can't live without, and that are currently not compatible with 1.75, are:

Black Monk Monastery
BlOomberg Markets
Dictators
ETT Homing Beacon
Feudal States
Galactic Navy
Interstellar Help
Lave
Oo-Haul missions and ships
Pelamis (I intend to buy one of these)
Save Anywhere (very important for me because I don't always want to have to be docked to save)
Special Interstellar Repair Facilities
Your Ad Here

Is anyone working on these to get them up to 1.75 standards?

Thanks.
If it is blank that means it is yet to be tested and reported as working fine without any errors in the logs. If you want to do that great . I went through the majority but have been distracted as of late. Must get back to testing the as yet unknown ones.

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 2:02 pm
by lave
Lone_Wolf wrote:
ETT Homing beacon was originally written for oolite 1.62, so unless someone adopts/updates the oxp, it seems unlikely it will ever work in 1.75 or MNSR.
That's a shame because I currently use it a lot.
It is ideal when I am mining and there is still loads of splinters floating around and I have a full hold. I can just drop the beacon, fly off to sell my cargo, then find my way back.

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 2:31 pm
by Okti
Hi Lave,

I had a look at the homing beacon. It does not work with 1.75.

The log messages are

Code: Select all

  [shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "beacon_torpedo" has a broken flasher definition (should have 8 tokens, has 7). This flasher will be ignored.
  [shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "beacon_torpedo" has a broken flasher definition (should have 8 tokens, has 7). This flasher will be ignored.
  [shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "beacon_torpedo" has a broken flasher definition (should have 8 tokens, has 7). This flasher will be ignored.
  [shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "beacon_torpedo" has a broken flasher definition (should have 8 tokens, has 7). This flasher will be ignored.
But if you are using to return to the splinters, you can use my cheat Oxp LongRangeScanner. :wink:

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 2:48 pm
by Commander McLane
The log messages aren't really significant. They mean that the device's flashers won't be there, but the device itself is fully functional.

Perhaps the flashers never worked with their faulty definition?

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 2:57 pm
by lave
Commander McLane wrote:
The log messages aren't really significant. They mean that the device's flashers won't be there, but the device itself is fully functional.

Perhaps the flashers never worked with their faulty definition?
Yes that's right. It has no flashers but the beacon itself works fine on 1.75

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 3:04 pm
by Smivs
lave wrote:
Commander McLane wrote:
The log messages aren't really significant. They mean that the device's flashers won't be there, but the device itself is fully functional.

Perhaps the flashers never worked with their faulty definition?
Yes that's right. It has no flashers but the beacon itself works fine on 1.75
So it's OK to amend the table entry to a Y* (OK but with faults)?

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 3:06 pm
by Commander McLane
Yep.

In general, all OXPs which work with 1.65 should be okay (the occasional bug which was already present when they worked with 1.65 notwithstanding).

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 3:08 pm
by Okti
Homing Beacon's readme file has the following Licence Information,

Licence:
This work is licensed under a Creative Commons License:
http://creativecommons.org/licenses/by-nc-sa/2.0/
You are free:
• to copy, distribute, display, and perform the work
• to make derivative works
Under the following conditions:
• Attribution. You must give the original author credit.
• Noncommercial. You may not use this work for commercial purposes.
• Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one.
For any reuse or distribution, you must make clear to others the license terms of this work.
Any of these conditions can be waived if you get permission from the copyright holder.
Your fair use and other rights are in no way affected by the above.

So some one can correct the mistakes and make it 1.75 compatible, as far as I can understand.

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 3:14 pm
by Lone_Wolf
I've checked the oxp files, corrected a typo in scan class and added an eight token to the flasher definitions ( the number 8 ).

Did a short test with the beacon and the beacon missile and it appears to work.
Requirement version is now 1.75 ,
you can download it here http://www.box.net/shared/rdbcxdcjz0 .

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 4:04 pm
by TGHC
Well done guys, that's what I call collaboration, posted at 11.07 and fixed by 3.14.

jellybabies all round

I love this board

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 4:54 pm
by Smivs
TGHC wrote:
Well done guys, that's what I call collaboration, posted at 11.07 and fixed by 3.14.
...and by 5.53, the Wiki table and OXP Wiki page download link had been updated. Job Done! :D

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 4:59 pm
by Commander McLane
Lone_Wolf wrote:
I've checked the oxp files, corrected a typo in scan class and added an eight token to the flasher definitions ( the number 8 ).
Did you throw two dice to choose a number, or how did you come to it? :wink:

Re: OXP's and 1.75

Posted: Thu Mar 31, 2011 5:13 pm
by Commander McLane
Hm. I haven't used the OXP in a long time, and only just now tested it, and there does seem to be another problem. When scooping a beacon created by a beacon launcher (not the missile), I am not awarded a beacon launcher again.

So all is not in order with the OXP. Need some further testing.