[general.error.inconsistentState]: DEBUG Universe removeEntity:<ShipEntity 0xb8fada8>{"Fuel Silo" ID: 0 position: (15, 0, 0) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT} ENTITY IS NOT IN THE RIGHT PLACE IN THE ZERO_DISTANCE SORTED LIST -- FIXING...
[general.error.inconsistentState]: DEBUG Universe removeEntity:<ShipEntity 0xb8fada8>{"Fuel Silo" ID: 0 position: (15, 0, 0) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT} ENTITY IS NOT IN THE ZERO_DISTANCE SORTED LIST -- CONTINUING...
[ship.subentity.sanityCheck.failed]: ***** VALIDATION ERROR: <ShipEntity 0xb8fada8>{"Fuel Silo"} thinks it's a subentity of <ShipEntity 0xc3940f8>{"Naga"}, but the supposed parent does not agree. This is an internal error, please report it.
Also i am receiving those AI errors (they may be totaly irrelevant with the fuel silo error)
[ai.error.recursion]: ERROR: AI reactToMessage: recursion in AI escortAI.plist, state FLYING_ESCORT, aborting. It is not valid to call reactToMessage: FOO in state FOO.
[ai.error.recursion]: ERROR: AI reactToMessage: recursion in AI escortAI.plist, state FLYING_ESCORT, aborting. It is not valid to call reactToMessage: FOO in state FOO.
[ai.error.recursion]: ERROR: AI reactToMessage: recursion in AI escortAI.plist, state FLYING_ESCORT, aborting. It is not valid to call reactToMessage: FOO in state FOO.
[general.error.inconsistentState]: DEBUG Universe removeEntity:<ShipEntity 0xb8fada8>{"Fuel Silo" ID: 0 position: (15, 0, 0) scanClass: CLASS_CARGO status: STATUS_IN_FLIGHT} ENTITY IS NOT IN THE RIGHT PLACE IN THE Z....
I never saw those errors while testing but position: (15, 0, 0) is definitely the position of the woma silo as subentity.
These are some pretty weird errors. The escortAI.plist one certainly doesn’t make sense, unless you have a custom version of the file.
Standard really-weird-behaviour cop-out: did you by any chance run a full Windows install on top of an existing Oolite install? (It’d be nice if the installer was fixed to deal with that, cough cough)
The escortAI.plist one certainly doesn’t make sense, unless you have a custom version of the file.
Nop (and also i do not have an oxp that has a file with the same name)
Ahruman wrote:
Standard really-weird-behaviour cop-out: did you by any chance run a full Windows install on top of an existing Oolite install? (It’d be nice if the installer was fixed to deal with that, cough cough)
I never use the updater and always uninstall the previous version of oolite before installing the new one
The most weird think is that i only had that message once. Since then i am playing the game in order to replicat it with no luck so far. I even encounter a woma several time but no message about the silo
Huh. In that case, I’m going to guess it was a random effect of some sort of in-memory corruption, which no doubt manifests in various other strange one-off ways. Worst kind of bug, gimme a consistent crasher any day. :-/
Huh. In that case, I’m going to guess it was a random effect of some sort of in-memory corruption, which no doubt manifests in various other strange one-off ways.
In other words BAD LUCK!!!!!!! removing flying dutchman oxp from addons folder
In other words BAD LUCK!!!!!!! removing flying dutchman oxp from addons folder
It actually isn't scripted to cause trouble on this level. (Moriarty was expected to be a match for Data's character, not for Data, from which I learned (for the geeks among you.))
