Dexter_D

Thank you, for reporting these issues. I'll look into this and hopefully find a workaround for the mission breaking problem. Please just don't expect miracles. EDIT: Found a solution in the steam forum by Sausage847 and was able to finish the whole mission. What you need to do is edit the mission through mission builder. 1. Remove the "Spawn Launch site" node for Jiukuan (probably not necessary, but I did't want to leave it in the mission) 2. Edit the "Construct KAIJANG KHEN" node and change location Jiukuan to Launch Pad (KSC) I hope this helps a bit.

You guys can be proud of your work. Also, I've met a lot of great people over the years through the game. Therefore I wanted to express my gratitude. Thank you dear Squad-Team. Edit: My Gratitude also goes to so many Modders and Mission Builders, they must not be forgotten.

Sorry to hear that. How did you install the mission? Via Steam or manually? I'm asking because I finished the mission a few months ago on a stock ksp 1.10.1 install. The only thing I'm always altering on the mission is the amount of fuel in the supply probe. Last time I forgot to fill it up, but I still was able to use only the red rover to get to the ascend vehicle and use the fuel cell for power generation. Maybe the game can't handle it so good if you don't do things in order. Edit: Did the mission progress until the landing task?

Why ist that? Did you manage to crash the rovers?

Hi guys, I just wanted to let you know, that the mission still works just fine in KSP 1.10.1. And there are still no mods needed.

When you click on the missions tab on kerbal x, there is a list of 54 missions. Just click on one of the missions, there is a big download button. After downloading go to your Kerbal Space Program folder, which contains a Missions folder. Put your downloaded mission into it. You should be able to start the mission now. You can only filter the mission by destination in the missions tab on kerbal x.

I wanted to do this mission again since I've done it last time a couple of KSP-Versions ago. For some reason, when I launch the munar 2 vehicle, it doesn't recognize the 50 km height border where the M3_DIALOG5 should pop up after passing it and so the mission doesn't progress. I can even crash the rocket and the mission isn't failed, simply nothing is happen anymore. Maybe one of you guys has an idea how to workaround the issue or at least can confirm, that this is just another new bug. Edit: Nevermind, it works again in KSP 1.10.1.

Yeah right, it's about 600 m/s Deltav. You have to do the Iron ManTM!

@CamnewHi there, stupid question here! Are you certain that it isn't just a simple typo when naming the KAIJANG KHEN? I mean of course it's really unlikely that it happens twice but just to be sure you could have a look. Copy/paste -> KAIJANG KHEN

Could it be possible that you switched control to the docking-port of the dreamchaser? I believe that doesn't work because of some reason.

Hello beik, I would say it should be obvious that you are supposed to dock the supplyprobe to the kermes and not he other way around. Bring the Kermes to a normal or anti-normal position and let the dockingport face the probe/ship which you want to dock. Then switch to the probe/ship and dock it to the kermes. So I'd say, just practice a little more and all will be good. The crafts are very well balanced. The hard mode is to meet every objective without messing things up. You don't get all points when you fail to land the supply probe on duna close enough to the hab for example. Or if you mess up the duna encouters in a way that the kermes would have an earlier encouter than the supply probe for duna, you would be a little late for ascend and rendevous because the kermes would have already flown past duna, when you don't get to the ascend vehicle in time. So there already is some kind of easy- and hardmode if you like. The problem with delta-v is, that it depends on the initial kermes orbit which could be an elliptical orbit or already a hyperbolic trajectory, and that is different on every install I would say, but I also could be wrong.

After investigating the issue I found that when you collected the pathgrinder and are docked to the hab, you can't send the data when you still sitting in the command seat. So one has two options, either just board a crewcapsule and send the data from there or take out the data from the storage, board to the commandseat of the rover which is connected to the pathgrinder and then you can also send the data. weird But as you can see, there can always be a thousand possibilities why it won't work.

Well, there is a dead deep space kraken on bop. Maybe someone can make something out of it.

@Ashaman42Extra points for generating so much science. I have to admit here that I was simply to lazy to take the extra step to do more experiments, obviously because it wasn't critical for the mission. But now I feel challenged, hmmm. ...also Happy New Year!