Log error in interstellar space

[Cody]

I just followed an npc through its wormhole, and it mis-jumped, leaving us both in interstellar space.
Got about 40 of these in the log:

Code: Select all

[general.error.inconsistentState]: ***** No sun set in Universe getSunSkimStartPositionForShip:

1.75.2-beta... no effect on game-play.

[Switeck]

You happen to have sunskimmer missile OXP loaded?

[Cody]

You happen to have sunskimmer missile OXP loaded?

Nope.

[Eric Walch]

I just followed an npc through its wormhole, and it mis-jumped, leaving us both in interstellar space.
Got about 40 of these in the log:

Strange, did you follow a special oxp ship through a wormhole? The only core ships that use the command "setSunSkimStartCoordinates" are the sunskimmers. And follow them through their wormhole is a bit tricky. (I never managed to do so without cheating). This AI was never prepared for misjumps. And even when they do, there should only be one single error message in your log. After that it should switch to a route1traderAI.plist.

[Cody]

It was a normal Cobra Mk I that launched soon after me from the station, and jumped as soon as it could.

[JensAyton]

The game assumes no AI will ever call setSunSkimStartCoordinates when in interstellar space, which isn’t the sort of assumption it should be making at that level. I’m changing it to send the AI a new message, NO_SUN_FOUND (for consistency with NO_STATION_FOUND, and because NOTHING_FOUND is normally for target methods rather than coordinates methods). setSunSkimEndCoordinates will do the same thing; setSunSkimExitCoordinates already does nothing at all if called in interstellar space.

[Cody]

That was the second npc mis-jump I've followed since I installed 1.75.2 last night... how often should that occur?