Oolite Bulletins

I have been getting an excess of errors in my log files, all about the same kind of error but quoting differing numbers. Here is an example:

15:33:27.901 [Total_patrol]: Adding additional police.
15:34:16.701 [strings.conversion.vector]: ***** ERROR: cannot make vector from '0.3, 0.3, 0.33, 1.0': could not scan a float value.

Sometimes there are repeats of maybe ten or fifteen lines.
Can a coder think what might be wrong? Is it expecting a value and getting a word 'string'? How can I correct it?

Malcul

Malcul wrote:

I have been getting an excess of errors in my log files, all about the same kind of error but quoting differing numbers. Here is an example:

15:33:27.901 [Total_patrol]: Adding additional police.
15:34:16.701 [strings.conversion.vector]: ***** ERROR: cannot make vector from '0.3, 0.3, 0.33, 1.0': could not scan a float value.

Sometimes there are repeats of maybe ten or fifteen lines.
Can a coder think what might be wrong? Is it expecting a value and getting a word 'string'? How can I correct it?

Malcul

It would be better to post earlier part of your log file, for us to see which OXP's you have. If it is an OXP Error, there must be a line following the error stating which JS file has the error.

Hi Okti, the log is rather large to include here but can be found below:

http://dl.dropbox.com/u/11051197/Excessive%20errors.log

There is no oxp to be found either prior to, or at the end of each bunch of error lines. I also have 285 oxps in the game, which makes it difficult to pinpoint a guilty one.

I have been able to correct obvious but minor errors in some oxps, or I wait until an update comes out.
I have been waiting for someone else to mention it, thinking that I can't be the only one.
Has everyone else corrected it for themselves? ... but I'm a slow learner. I knew some BBC basic a long time ago but it has all gone.

Loved the way you named the OXP's , I think you Uninstall half of them and check for the log again, if you get errors you remove half of them again. If not restore the other half and continue the process till you end up with about 5 OXP's that may be causing problems. Otherwise it will take a long time for us to download the OXP's you have.

By the way I noticed log messages from my GalaxyInfo and will update it soon to get rid of those.

I'm pretty certain it's Shady Sungs...

Yes, see here: https://bb.oolite.space/viewtopic.php?f=4&t=8644

Malcul wrote:

15:33:27.901 [Total_patrol]: Adding additional police.

This one is not an error. Its the Total Patrol OXP reporting that it is adding more police, usually for the witchspace buoy-sun/sun-planet routes.

JazHaz wrote:

Malcul wrote:

15:33:27.901 [Total_patrol]: Adding additional police.

This one is not an error. Its the Total Patrol OXP reporting that it is adding more police, usually for the witchspace buoy-sun/sun-planet routes.

That is not error game wise, but what I realized from the logs, even one of my OXP's left a log message which I used for debugging purposes. For the release versions I think we must delete the log entries not to confuse the players.

I have updated GalaxyInfo for this purpose.

Thanks for the help, fellers, I have to say Mauiby de Fug was right, it was Shady Sung, and I should have searched harder to find the right forum topic. Okti, you were helpful in pointing out the way to identify the culprit oxp, thanks for that. I hope no-one (JazHaz?) was upset by my including the Total patrol line with the error, I didn't think it had a problem, but I know nothing, and hoped someone else would see that the error was unlikely to come from there and point to somewhere else.
Okti's suggestion was a logical but laborious solution, and ultimately successful, However it highlit some other persistent errors which someone may, perhaps, have an answer for.

1.15:24:19.242 [escapePodLocator.js]: Range in normal space modifier: default. Range in interstellar space modifier: default.

2. 15:24:30.813 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "asad_gunship_player" does not have a corresponding shipdata.plist entry, ignoring.
I can't find any oxp with mention of the word 'asad-gunship' in it.

3. 15:25:12.090 [station.launchShip.failed]: Cancelled launch for a [VARIOUS SHIPS] with role [VARIOUS ROLE], as it is too large for the docking port of the [VARIOUS DOCKABLES].

If anyone is interested .... ?

Malcul wrote:

1.15:24:19.242 [escapePodLocator.js]: Range in normal space modifier: default. Range in interstellar space modifier: default.

This just looks like information and can safely be ignored.

Malcul wrote:

2. 15:24:30.813 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "asad_gunship_player" does not have a corresponding shipdata.plist entry, ignoring.
I can't find any oxp with mention of the word 'asad-gunship' in it.

Look to HERE for the ship.

Malcul wrote:

3. 15:25:12.090 [station.launchShip.failed]: Cancelled launch for a [VARIOUS SHIPS] with role [VARIOUS ROLE], as it is too large for the docking port of the [VARIOUS DOCKABLES].

This means there are ships too big for the docking port to launch. These sould be posted to the thread of the particular ship. But you can safely ignore it. It wont do anything bad.

Thanks for the info Fatleaf, mostly reassuring.

No3 is a puzzler because it is on occasion refering to Cobras, which are not huge, and other similar small type ships.

Yeay, again thanks
Malcul

Malcul wrote:

No3 is a puzzler because it is on occasion refering to Cobras, which are not huge, and other similar small type ships.

Is it the Super Cobra by any chance, with the Rock Hermits?

Fatleaf wrote:

Malcul wrote:

No3 is a puzzler because it is on occasion refering to Cobras, which are not huge, and other similar small type ships.

Is it the Super Cobra by any chance, with the Rock Hermits?

I got one of those warnings yesterday about KW's Cobra 6 and a rock hermit. Yet I've docked with rock hermits using that ship. Curiouser & curiouser.

someone else mentioned that King Cobra/Hermit issue. i don't get what the issue is, as the MkVI is not much bigger than the normal Cobras etc and shouldn't have that problem. i've just quickly checked the bounding box and that looks fine too, so i can't think what's up.

It was I who mentioned it. I found the log entry and posted to your thread. Maybe a Dev can shed light on the issue as the Imperial Courier has the same log entry yet you can dock with it as well. Might be a good question to ask in Testing and Bug Reports.

Don't get hung up on the idea of cobras and rock hermits folks, see some actual errors below and notice all the different ships and different dockables, including coriolis and icosahedron stations!

15:06:53.287 [station.launchShip.failed]: Cancelled launch for a Urutu Mk III with role defense_ship, as it is too large for the docking port of the Rock hermit.
14:57:11.064 [station.launchShip.failed]: Cancelled launch for a Hauler P30 with role trader, as it is too large for the docking port of the Black Monk Monastery.
14:56:30.128 [station.launchShip.failed]: Cancelled launch for a Hawk with role pirate, as it is too large for the docking port of the Icosahedron Station.
14:27:37.323 [station.launchShip.failed]: Cancelled launch for a Cobra AC with role scavenger, as it is too large for the docking port of the Rock hermit.
12:18:10.981 [station.launchShip.failed]: Cancelled launch for a Caiman with role escort, as it is too large for the docking port of the Coriolis Station.
12:00:09.907 [station.launchShip.failed]: Cancelled launch for a Boa Class Cruiser with role trader, as it is too large for the docking port of the Icosahedron Station.