search

jrossignol / ContractConfigurator

A config file based solution for creating new contracts for Kerbal Space Program.
https://forum.kerbalspaceprogram.com/index.php?/topic/91625-1
Other
64 stars 67 forks source link

Problems with vessel tracking across decoupling #467

Open jrossignol opened 8 years ago

jrossignol commented 8 years ago

Problem is in the RP-0 lunar landing contract, as reported by chrisl on the forums:

In my RO/RSS/RP-0 game, I'm running the "Moon/1" landing contract. The craft I used was basically the "FASA Saturn V Apollo Lunar" that comes with RO, though I did make a couple of tweaks to it. I've already flown the CSM+LM to the moon and landed the LM in the correct biome. My mission timer says I've effectively completed the mission. Now all I need to do is separate the Ascent stage from the Descent, rendezvous with the CSM, fly home and spash down. Trouble is, every time I decouple the Ascent stage to take off, the timer is mission timer is resetting itself. After a bit of trial and error, I think the problem stems from the fact that the LM is built backwards. I.E., to build the LM "under" the CSM on the Saturn V, you put a decoupler into the "FASASaturnSLA", then attach the descent engine, then the descent stage, then the decoupler ring, then the ascent engine and then the ascent stage (plus landing gear and such). So when you look at the VESSEL in your save game, the first part listed is the Descent Engine. From what I can tell, when you activate the decoupler ring, the parts below it on the original vessel (in this case the Ascent Engine, Ascent Stage, LM Antenna and my science stuff) become a new vessel and the contract's completion status doesn't link to this "new" vessel. Is there any way to make it so that contact status applies to the main vessel plus any vessels that "break off" from the main?

ale260382 commented 8 years ago

Hi, i'm also having this problem with a few RP0 missions (ksp 1.0.5 linux64), including lunar flyby. Mission timer resets when command module is detached from service module and lem on reentry. I'm not using FASA apollo but a similar ship made with various rp0 components. I suspect the problem is due to the apollo-style LEM capture. The LEM is a subassembly and it's fixed on rocket separately from the command/service module assembly. After launch, the command/service module undocks then turn back, it docks with the LEM and the entire command/service/LEM undocks from upper stage, which i suppose changes the core of the ship to one of the LEM parts (i think it's the engine that is fixed to the upper stage). So when the LEM is jettisoned on reentry the core part is lost...

NathanKell commented 8 years ago

Tagging so I stay apprised.