For information and discussion about Oolite.
https://bb.oolite.space/
Code: Select all
15:31:13.339 [LogEvents]: Player will enter witchspace due to wormhole
15:31:13.515 [LogEvents]: Player exited from the vicinity of [Planet position: (0, 0, 533880) radius: 44490 m]
15:31:14.564 [LogEvents]: Player will exit witchspace
15:31:14.618 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (BroadcastCommsMFD 1.0.18): TypeError: myRoute is null
15:31:14.941 [LogEvents]: Player alert condition changed from 2 to 1
15:31:15.066 [LogEvents]: Hyperjumping 27215 spawned at 0 km
15:31:15.066 [LogEvents]: Thargoid Warship 25820 spawned at 22 km
15:31:15.066 [LogEvents]: Behemoth Type 4 10412 spawned at 23 km
15:31:15.066 [LogEvents]: Navy Asp Mark II 15000 from Behemoth Type 2 11098 spawned at 26 km
15:31:15.066 [LogEvents]: Navy Asp Mark II 3506 from Behemoth Type 4 10412 spawned at 25 km
15:31:15.067 [LogEvents]: Navy Viper 953 from Behemoth Type 4 10412 spawned at 20 km
15:31:15.067 [LogEvents]: Behemoth Type 2 11098 spawned at 26 km
15:31:15.067 [LogEvents]: Navy Viper 30202 from Behemoth Type 2 11098 spawned at 25 km
15:31:15.067 [LogEvents]: Thargoid Warship 14311 spawned at 18 km
15:31:15.067 [LogEvents]: Thargoid Warship 19357 spawned at 23 km
15:31:17.220 [LogEvents]: Player exited from witchspace
Well, when i exit into intersteller space, there's only some or more Thargoids, and often some GalCops as well, but no planet, and hence, no station.Cody wrote:I know zilch about GalNavy, as I've never used it. You should emerge into interstellar space in roughly the same position as with a normal witchpoint emergence - i.e. with the planet (a rather ugly one, in this case) more or less straight ahead. The station is easy enough to find, and is of non-standard design.
Yeah, that one's mine. Looks like my route planner doesn't work in interstellar space. Shouldn't impact on anything else, though.Mazur wrote:nd of a BroadcastCommsMFD error, which I can do nothing with
Bear in mind that the OXPs are to be considered as unofficial content to the game with various authors of which some are long gone from the forum. Some OXPs are really old and somewhat functional and there is no central quality control. The quality of a single mod is as good as the current maintainer makes it. Time is limited, there are a zillion on mods around and there aren't that many OXP maintainers.Mazur wrote:...I installed a lot of Expansion packs, some of which now appear not to be working together but produce bugs, which apparently noone has discovered before. I report those bugs, because I think people might want to know, and hopefully fix them, but since I only started playing a month ago and know blessedly little of Javascript anyway, I can't trace and/or fix those bugs on my own...
Code: Select all
"interstellar: 0 48 144"=...Code: Select all
"interstellar: 0 144 48"=...Ahh, that explains it... when I was testing this for Eric, it was fine from either direction. This time I only tested from Usle to Biorle.spara wrote:I have confirmed and identified the problem. The oxp set's the planet and the station in planetinfo.plist like this:With the current version of Oolite, that means that the interstellar space between Usle and Biorle is set. And direction matters. The mission strongly suggests to jump from Biorle to Usle and because of the direction, that produces an "empty" insterstellar space.Code: Select all
"interstellar: 0 48 144"=...
Lioning that in mind (I like the cat family more than the bear family), I do appreciate the time and effort invested by the global Internet community in keeping me entertained. On the other hand, as an ASS, I am pushed into literal interpretation of verbal communication, and get frustrated when I seem to be misunderstood or ignored. I've had a lot of that in my life and have become less patient with it, hence I may have been reacting a little terse just now. I'm also quite disappointed in having lost the ability to absorb new stuff easily, like javascript, and my inability to fix these problems I encounter myself.spara wrote:Bear in mind that the OXPs are to be considered as unofficial content to the game with various authors of which some are long gone from the forum. Some OXPs are really old and somewhat functional and there is no central quality control. The quality of a single mod is as good as the current maintainer makes it. Time is limited, there are a zillion on mods around and there aren't that many OXP maintainers.
You're a marvel! I'll just tackle it the other way round for now, something I was planning to try anyway, but kept forgetting to do as there were no ships going that way and thus making it an ordinary cargo run, as I'm close to buying my second ship at the 200k ₢ mark.spara wrote:In short, your reports are very much welcomed. Many OXP maintainers don't really play the game anymore and bug reports from players are much valued.
And to the point. I have confirmed and identified the problem. The oxp set's the planet and the station in planetinfo.plist like this:With the current version of Oolite, that means that the interstellar space between Usle and Biorle is set. And direction matters. The mission strongly suggests to jump from Biorle to Usle and because of the direction, that produces an "empty" insterstellar space.Code: Select all
"interstellar: 0 48 144"=...
The OXP would require a little bit of updating overall as it throws a few deprecation errors, but just to fix the problem above,need to be defined too.Code: Select all
"interstellar: 0 144 48"=...
Agreed.. doing it all one OXP at a time is seriously un-fun.. which is why we recommend using the Binary Method when tracking down problematic OXPs..Mazur wrote:Sure, I can help, following clear requests to find out more information, but I'm not going to remove the Expansion packs one by one to find out when things start working again, because that would take all the enjoyment out of playing Oolite for me.
Remove half the OXPs. If problem goes away, change to the other half of the set and try again.
Continue removing half the remaining OXPs each time, eliminating the half that are trouble-free. Repeat until you have identified the culprit.
Even if you have hundreds of OXPs, this method will let you identify the source of the trouble in less than 10 iterations.
Naturally. But even then, more experience and insight into the various OXPs beyond "What it says on the tin" helps immensly to speed things up.Diziet Sma wrote:Agreed.. doing it all one OXP at a time is seriously un-fun.. which is why we recommend using the Binary Method when tracking down problematic OXPs..Mazur wrote:Sure, I can help, following clear requests to find out more information, but I'm not going to remove the Expansion packs one by one to find out when things start working again, because that would take all the enjoyment out of playing Oolite for me.
Remove half the OXPs. If problem goes away, change to the other half of the set and try again.
Continue removing half the remaining OXPs each time, eliminating the half that are trouble-free. Repeat until you have identified the culprit.
Even if you have hundreds of OXPs, this method will let you identify the source of the trouble in less than 10 iterations.
Unless something has changed (it's been a while), you don't need to do that - simply misjump yourself to midway, and tank up at the station.CFK wrote:You have to sit around at Biorle waiting for someone to make the correct jump so you can follow them and screw it up.
Code: Select all
this.startUp = function (){
if (!missionVariables.erehwonReconnaissance) {
missionVariables.erehwonmisjumpInfo = "NULL";
missionVariables.erehwonReconnaissance = "START";
missionVariables.erehwonFotoShot = "NO";
missionVariables.erehwonGotStory = "NO";
} else if (missionVariables.erehwonReconnaissance == "FINISHED") {
this.cleanUp();
}
};
.
.
.
if (system.ID == 144 && missionVariables.erehwonmisjumpInfo == "NULL") {
missionVariables.erehwonmisjumpInfo = "BIORLE";
}
if (system.ID == 48 && missionVariables.erehwonmisjumpInfo == "BIORLE") {
missionVariables.erehwonmisjumpInfo = "USLE";
}
if (system.ID == 144 && missionVariables.erehwonmisjumpInfo == "USLE") {
mission.runScreen({
title: "Tionisla Chronicle",
messageKey: "erehwonReconnaissance_biorle"
});
missionVariables.erehwonmisjumpInfo = "GIVEN";
}
.
.
.
this.shipWillEnterWitchspace = function (cause) {
if (!system.isInterstellarSpace) {
missionVariables.showErehwon = "YES";
if (missionVariables.erehwonmisjumpInfo == "GIVEN" && (system.ID == 48 || system.ID == 144) && cause === "standard jump") {
if ((player.ship.targetSystem == 48 || player.ship.targetSystem == 144) && Math.random()< 0.2) {
player.ship.scriptedMisjump = true;
}
}
} else {
missionVariables.showErehwon = "NO"; // avoid adding planet on multiple misjumps.
}
};