1.77 and OXPs

[Halfhand]

Greetings Commanders,

I've encountered some more issues with OXPs ....
I'm using 1.77 release from http://prdownload.berlios.de/oolite-lin ... x86_64.tgz

these are from my Latest.log


----------------------------

01:35:17.315 [script.load.notFound]: ***** ERROR: Could not find script file galaxy_info.js.

GalaxyInfo.oxp/Scripts/galaxy_Info.js has a capital 'I'

NOTE: I renamed galaxy_info.js -> galaxy_Info.js and it complained about the capital I, i presume the script is referenced more than once, each with different caps.

----------------------------

Vortex is (i think) demanding debug console.

vortex_player.js 1.30
01:35:18.146 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'Connection refused' (outStream status: 7, inStream status: 7)."
01:35:18.146 [debugTCP.send.warning]: Error sending packet header, retrying.
01:35:18.170 [debugTCP.send.error]: The following packet could not be sent: {"Oolite version" = "1.77"; "packet type" = "Request Connection"; "protocol version" = 65792; }
01:35:18.171 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'bad stream.' (outStream status: 0, inStream status: 0)."
01:35:18.171 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.

-------------------------------

01:36:29.459 [files.notFound]: ----- WARNING: Could not find texture file "StarSeeker_wings.png".

AddOns/Executive Spaceways v2.4.oxp/Textures/Starseeker_wings.png has lowercase 's'

--------------------------------

01:35:27.596 [script.load.notFound]: ***** ERROR: Could not find script file galNavyTarget-Thargoid.js.

this .js file does not exist on my pc, so i'm not sure which OXP the game is complaining about.

---------------------------------

01:58:29.847 [strings.expand.invalidSelector]: ----- WARNING: Unpermitted legacy script method [commanderLegalStatus_number] in string.

Again, not sure which OXP.

---------------------------------


FYI, these are my OXP's taken from Latest.log, note that furball looks weird, there is only a readme in the root folder for it.

AddOns/griff_station_bundle_fullsize_tex_v1.1.oxp
AddOns/behemoth 2.6.oxp
AddOns/Commies.oxp
AddOns/Fuel Station 1.34.oxp
AddOns/UPS-courier v1.8.1.oxp
AddOns/griff_boa_prototype_normalmapped.oxp
AddOns/BlOomberg Markets v2.5.oxp
AddOns/Military Fuel Injectors 1.03.oxp
AddOns/Assassins.oxp
AddOns/BigShips 1.02.oxp
AddOns/Target Autolock Plus 1.12.oxp
AddOns/Shady_blackmonks_v1.46.oxp
AddOns/System_Redux.oxp
AddOns/Police_Scanner_Upgrade_1.3.1_2011-12-18.oxp
AddOns/Cabal_Common_Library1.7.oxp
AddOns/YOUR_AD_HERE_set_F_4.1.7.oxp
AddOns/Anarchies2.8.oxp
AddOns/ShieldEqualizer+Capacitors(v1.3).oxp
AddOns/Missiles and Bombs v2.5.oxp
AddOns/Executive Spaceways v2.4.oxp
AddOns/ClippersV1.3.1.oxp
AddOns/YOUR_AD_HERE_4.1.7.oxp
AddOns/Griff_Shipset_Resources_v1.2.25.oxp
AddOns/buoyRepair1.3.2.oxp
AddOns/Thargoid_Witchspace_Drive_0.9.4_2012.04.20.oxp
AddOns/YOUR_AD_HERE_set_B_4.1.7.oxp
AddOns/Griff_Shipset_Replace_v1.34.oxp
AddOns/YOUR_AD_HERE_set_D_4.1.7.oxp
AddOns/YOUR_AD_HERE_set_C_4.1.7.oxp
AddOns/AsteroidStorm 4.03.oxp
AddOns/YOUR_AD_HERE_set_A_4.1.7.oxp
AddOns/IronHide 2.00.oxp
AddOns/ExtraFuelTanksV1 .4.1.oxp
AddOns/TrophyCollector_2.1.oxp
AddOns/adcks_behemoths_v1.2.oxp
AddOns/Snoopers2.4.oxp
AddOns/YOUR_AD_HERE_set_E_4.1.7.oxp
AddOns/FTZ v0.15.oxp
AddOns/OXPConfig2.2.4.oxp
AddOns/Rock_Hermit_Locator1.3.3.oxp
AddOns/Target Reticle 1.2.1.oxp
AddOns/sell_equipment.oxp
AddOns/RepairBots 2.09.oxp
AddOns/Armoury 1.11.oxp
AddOns/BountyStatus 1.00.oxp
AddOns/GalaxyInfo.oxp
AddOns/SniperLockv1.oxp
AddOns/BGS-A1.6.oxp
AddOns/Vortex 1.30.oxp
AddOns/Tori2.01.oxp
AddOns/Aquatics 2.30.oxp
AddOns/Naval Grid 1.00.oxp
AddOns/Cargo Spotter 1.00.oxp
AddOns/hOopyCasino1.2.1.oxp
AddOns/Escort_Formations_1.1.oxp
AddOns/x-ships.oxp
AddOns/BountyScannerv2.0.oxp
AddOns/marketObserver_1.4.oxp
AddOns/LongRangeScanner v0.3.oxp
AddOns/SniperCameraSystemv1.1.oxp
AddOns/RandomHits1.4.18.oxp
AddOns/Furball-1.7.oxp
AddOns/Furball-1.7.oxp/Furball-1.7.oxp
AddOns/YOUR_AD_HERE_set_G_4.1.7.oxp


Edited to add...
I also got these after clearing out a furball...
03:18:22.197 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_ftzpirate5] in string.
03:18:22.197 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:18:31.744 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_ftzpirate13] in string.
03:18:31.744 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:19:23.131 [strings.expand.invalidSelector]: ----- WARNING: Unpermitted legacy script method [commanderLegalStatus_number] in string.
03:20:41.631 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_ftzpirate12] in string.
03:20:41.631 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:20:58.458 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_ftzpirate4] in string.
03:20:58.458 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:27:37.946 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_adck_b_cobra3_v2-pirate] in string.
03:27:37.946 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:28:14.699 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_gecko] in string.
03:28:14.699 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:29:04.601 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_griff_NPC_prototype_boa_decals_from_green_channel] in string.
03:29:04.601 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:29:17.526 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_gemini] in string.
03:29:17.526 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:29:53.447 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_gecko] in string.
03:29:53.447 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:30:17.738 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_cobramk1-alt] in string.
03:30:17.738 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:30:43.379 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_cobra3-pirate] in string.
03:30:43.379 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:31:25.284 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_griff_normalmapped_python_alt_pirate_NPC] in string.
03:31:25.284 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:33:04.097 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_asp] in string.
03:33:04.097 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:33:41.414 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_sidewinder-escort] in string.
03:33:41.414 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.
03:34:05.938 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_mw-asp] in string.
03:34:05.938 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.

[spara]

Looks like I've got some fixing to do with Trophy Collector. Will take a couple of days before I've got time to check it. Thanks for reporting.

[Thargoid]

Vortex is (i think) demanding debug console.

vortex_player.js 1.30
01:35:18.146 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'Connection refused' (outStream status: 7, inStream status: 7)."
01:35:18.146 [debugTCP.send.warning]: Error sending packet header, retrying.
01:35:18.170 [debugTCP.send.error]: The following packet could not be sent: {"Oolite version" = "1.77"; "packet type" = "Request Connection"; "protocol version" = 65792; }
01:35:18.171 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'bad stream.' (outStream status: 0, inStream status: 0)."
01:35:18.171 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.

I don't think it is. Those errors look more like debug OXP is in place but the console isn't running (or for reasons like a firewall or similar it can't be reached by the packets). The Vortex script may be just the last one that loaded previously - if possible can you post this snippet of your log again but going back a few more of the previous lines?

[another_commander]

Yup. As Thargoid says. The connection error messages are the standard response whenever the Debug OXP is found but the Debug Console is not and originate from the game core, not from any OXP.

[Diziet Sma]

Assuming you actually wish to use the debug console, since you're on Linux, you'll find some useful tips here.

[Eric Walch]

Yup. As Thargoid says. The connection error messages are the standard response whenever the Debug OXP is found but the Debug Console is not and originate from the game core, not from any OXP.

Although, these messages should not be present in a deployment build were no console will be available in the first place.

Could not find script file galNavyTarget-Thargoid.js.

This script used to be part of older versions of GalNavy.oxp. It is no longer part of that oxp. Weird thing is that I don't see the oxp at all in your list.

[another_commander]

Yup. As Thargoid says. The connection error messages are the standard response whenever the Debug OXP is found but the Debug Console is not and originate from the game core, not from any OXP.

Although, these messages should not be present in a deployment build were no console will be available in the first place..

You are right and at least on the Windows deployment version that is exactly what happens. This leads me to believe that most likely it is either a test configuration running, or there is something that must be addressed on the Linux port.

Edit: Funny thing, actually. Basic-debug.OXP is nowhere to be found in the list of OXPs shown in the first post. Is there another folder that OXPs are getting read from? I'd like to see the full log from a run of the game with Shift pressed at startup.

[Diziet Sma]

Yup. As Thargoid says. The connection error messages are the standard response whenever the Debug OXP is found but the Debug Console is not and originate from the game core, not from any OXP.

Although, these messages should not be present in a deployment build were no console will be available in the first place..

You are right and at least on the Windows deployment version that is exactly what happens. This leads me to believe that most likely it is either a test configuration running, or there is something that must be addressed on the Linux port.

I have the 32-bit Linux Deployment Build on my system, and there are no connection error messages in my logs.

[Diziet Sma]

FYI, these are my OXP's taken from Latest.log, note that furball looks weird, there is only a readme in the root folder for it.

AddOns/Furball-1.7.oxp
AddOns/Furball-1.7.oxp/Furball-1.7.oxp

This at least is just a packaging error by m4r35n357. It won't cause any actual problems, other than making the Furball-Readme.txt invisible to Mac users.

[Eric Walch]

It won't cause any actual problems, other than making the Furball-Readme.txt invisible to Mac users.

Yep, any folder with an '.opx' extension will be presented as a single file to the mac-user and not as folder.
You can open it through the contextual menu or just rename the extension. But as this is seldom needed for mac users, most won't even think about these options to look inside the oxp file.

[Halfhand]

@Thargoid && Eric && Another_Commander
You're right again I have oolite installed for all users, and i also have a dev version built from source in my home folder, they were both looking at ~/.Oolite/AddOns and it was picking up the Basic-debug.oxp from the dev version,

@Dizi
thanks for the info, I haven't used the debug console yet but I really should look in to it

@Eric
No, I don't have gal navy in my downloads folder either. Maybe someone cut and pasted from it?
I searched all .js files in my addons folder and galaxyinfo is the only one that contains "navy", it doesn't contain "galNavyTarget-Thargoid" though.
______________________

I have managed to clear all errors except for the trophy ones now,

GalaxyInfo
I made sure the galaxy_Info.js was consistent between equipment.plist and world-scripts.plist

Executive Spaceways
I renamed Starseeker_wings.png to StarSeeker_wings.png

Renaming ~/Oolite/AddOns folder to AddOns.temp fixed the rest. There were only Basic-debug and x-ships in there.
although that did mean x-ships was being loaded twice (?)

____________________________

Thanks for the responses, my game was freezing last night (3 times an hour) and it was upsetting me when it froze even f12 didn't work so i couldn't get out of fullscreen to quit the game, nor could i pkill it from another tty

Fixing these problems fixed that too HUZZAR!!!!!

[spara]

Code: Select all

03:34:05.938 [script.javaScript.warning.ooliteDefined]: ----- JavaScript warning (trophy_col 2.1): Unknown expansion key [trophy_mw-asp] in string.
03:34:05.938 [script.javaScript.warning.ooliteDefined]: AddOns/TrophyCollector_2.1.oxp/Config/script.js, line 41.

I actually didn't know this throws a warning. I have a descriptions.plist, that lists an odd number of key-value pairs (trophy_datakeys - ship_names to be exact). My script first tries to expandDescription against the descriptions.plist-file. If the string remains in the form of [foo], then I know there's no matching key. Apparently this check throws a warning. Is there some more sensible way of checking the existence of a matching key than this?

[Halfhand]

Also last night, which i failed to report because it was so late

If i launch Reprogrammed Thargon Drones from the Armoury oxp while i have a full cargo bay I can't recover them.

I have to eject some cargo so that they can be scooped (1 ton for each drone i want to scoop), then i can't scoop the ejected cargo because the hold is full. F8 shows 115 tons in my Python ET but adding up the tonnage comes up short. when i dock (anywhere) the hold is no longer full and everything is back to normal.

[Diziet Sma]

Also last night, which i failed to report because it was so late

If i launch Reprogrammed Thargon Drones from the Armoury oxp while i have a full cargo bay I can't recover them.

I have to eject some cargo so that they can be scooped (1 ton for each drone i want to scoop), then i can't scoop the ejected cargo because the hold is full. F8 shows 115 tons in my Python ET but adding up the tonnage comes up short. when i dock (anywhere) the hold is no longer full and everything is back to normal.

I've run into that same problem. Don't know if there's a workaround.

(Incidentally, the preferred place to report problems with an OXP is in the thread for that particular OXP. Most authors have a notify set on their threads so that they get a heads-up via email if a post is made to that thread.)

[Thargoid]

I don't think there is. Its how trunk deals with cargo and scripting. At least in flight anyway. It sorts itself out on docking.