For information and discussion about Oolite.
https://bb.oolite.space/
I had decided to skip out of it first time around... But I lost him as soon as I made the GH jump...
Eric Walch wrote:Mission accomplished. Commander signing off.
Stressful. I did my part in defending the galaxies as we know. But it may be not enough. I think we need more commanders to fight those creatures when we ever want to win the battle against the thargoid menace.
This is not a bug in Cataclysm. It uses the command to launch the player from a station, but when this is done by a script the Vector will detect it before anything else can be executed by Cataclysm. Eric already told me about it and I'll change the Vector to check it later.Screet wrote:[Vector]: Vector: Warning: An other oxp has not cleared missionVariables.offering - CATACLYSM
Hmmm. Now I got the same complaint from UPS. This time, I wasn't properly docked! The station was still visible and rotating, no docking screen...I had then to hit 1 for launch and re-dock again which is when UPS told me about this.Svengali wrote:This is not a bug in Cataclysm. It uses the command to launch the player from a station, but when this is done by a script the Vector will detect it before anything else can be executed by Cataclysm. Eric already told me about it and I'll change the Vector to check it later.Screet wrote:[Vector]: Vector: Warning: An other oxp has not cleared missionVariables.offering - CATACLYSM
Code: Select all
[general.error.inconsistentState]: ERROR: status is STATUS_DOCKED, but dockedStation is nil; treating as not docked. This is an internal error, please report it.
[general.error.inconsistentState]: ERROR: status is STATUS_IN_FLIGHT, not STATUS_DOCKED, but dockedStation is not nil; treating as docked. This is an internal error, please report it.
In UPS I try to detect 3 different wrong situations. Two have to do with launching:Screet wrote:Hmmm. Now I got the same complaint from UPS. This time, I wasn't properly docked! The station was still visible and rotating, no docking screen...I had then to hit 1 for launch and re-dock again which is when UPS told me about this.
Code: Select all
"ups_warning" = "UPS-Courier detected that on the last launch the choice key was not reset. This probably means that an other script than UPS has forgotten to clear this choice.\\n\\nUPS has no means to determine if an other OXP has forgotten to reset it or still has to process it. This means that UPS would have suppressed his own choices offering screens when one was scheduled for the previous docking.";
"ups_warning3" = "UPS-Courier detected that on the last launch, the mission offer was not reset. This probably means that an other script than UPS has forgotten to clear this mission offer or that the player launched from out of an offer screen before making a choice.\\n\\nUPS has no means to determine what caused it and will reset itself and redo the offer when the right conditions are met again.\\n\\nJust one warning to the player when this was caused by launching from within an offer: UPS will reset properly but some other OXP's might not anticipate on this and could prohibit further offers when the player launched from within an offering screen. So never do this."; Yepp. The warning in Vector.oxp (and OXPConfig) is more or less meant as a helper for scripters. I don't think that 'normal' users will take a look in the log if they don't have problems. Erics approch is more a educational thing (and maybe a better way). My thought was that any offer has to be directly bound to the handling. Displaying the screen - the user chooses - and a reaction follows. But I hadn't thought about the oxps that are forcing the player to launch - it's not only Cataclysm. So this is also a bit educational - I have learned some more about Oolite and its AddOns .-)Eric Walch wrote:Vector writes its findings to a log for programmers only, UPS presents it's findings in a mission screen for all players visible so they know there could have been something wrong. (So they can do the next save under an other name).
What should I have done then? I didn't get a docked screen, but a frozen picture from flying together with the sight of a rotating station (which I wasn't properly docked to, see the log excerpt). The station kept rotating, being the only thing not "frozen".Eric Walch wrote:Especially using the 1 key from within a missionscreen is bad. Some oxp's will stop doing offers after that. The legacy version of oolites trumble offer was an example of things going wrong by launching this way. (Or you could do it intentionally to stop trumble offers).
Hehe, this happens from time to time, but I don't think that this is related to Cataclysm. Maybe I'm wrong, but I've had this too when I've had modelled the GRS station and tried to tweak the port_radius. And Random Hits user have had similiar things too. It's rare (or we would get more reports about it - and I'd bet not your fault .-)Screet wrote:What should I have done then? I didn't get a docked screen, but a frozen picture from flying together with the sight of a rotating station (which I wasn't properly docked to, see the log excerpt). The station kept rotating, being the only thing not "frozen".
Yes, this must be a real error that should be reported. I see them so often from the launch commands that I ignore them. But re-reading your log I see this one is different and even contradicting. It is not caused by the launch command like in your earlier report.Screet wrote:What should I have done then? I didn't get a docked screen, but a frozen picture from flying together with the sight of a rotating station (which I wasn't properly docked to, see the log excerpt). The station kept rotating, being the only thing not "frozen".