Project

General

Profile

Bug #18146

"To the Mun via Minmus", broke

Added by jclovis3 about 6 years ago. Updated about 6 years ago.

Status:
Updated
Severity:
Low
Assignee:
-
Category:
Gameplay
Target version:
-
Start date:
03/21/2018
% Done:

10%

Version:
Platform:
Windows
Expansion:
Making History
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Making History mission "To the Mun via Minmus", does not show objectives for Muna 2 operating around the Mun. Also, most of the time when crashing Muna 2 onto Mun, mission doesn't end. I verified the KSC was within line of site to Muna 2 because the comm network had direct connection to the KSC.

History

#1 Updated by diomedea about 6 years ago

  • Status changed from New to Need More Info

Can't get from the pictures if you actually performed as required about Muna1: you must crash it on Minmus for the mission to proceed further, allow to build Muna2 and state the new objectives. From one of the pictures, seems as if you actually renamed Muna1 to Muna2 instead.
Please provide a save of the mission to show its state.

#2 Updated by MechBFP about 6 years ago

The problem is the staging. If you decouple the mystery goo probe, the rest of the rocket ship gets called “Muna 2 Probe” and crashing it does nothing.
The missions specifically asks you to stage but you MUST NOT to actually complete the mission.

#3 Updated by jclovis3 about 6 years ago

I figured that out with the first ship on Minmus. For Mun, I did not decouple them. This also seems to be a fuel challenge as I find myself having to use RCS for the later course corrections and have yet to figure out how I'm going to hit that bonus marker before running out. Not sure if the crash has to be facing Kerbin or not as it doesn't seem to acknowledge the crash other than having "no target" afterward. It seems silly to me that the ship would be built with this extra probe if they were not meant for separation. Also, as you can see the option to rename vessels is still enabled. This might be a logic bug if the mission builder is looking for a ship by its name and not some other identity like a fixed UID for the probe or something. A player might either mess things up or cheat the challenge by renaming ships, like in the previous mission to rescue a broken ship. One of the ships has extra fuel, but only the broken ship gives you the bonus for landing it close to the KSC. Renaming them opposite of one another might allow the ship with more fuel and control to descend down onto the KSC for the bonus credit. So this really goes to show how UID on individual parts might be important with the mission creator and not just to help fix this bug.

#4 Updated by jclovis3 about 6 years ago

  • Status changed from Need More Info to Updated
  • % Done changed from 0 to 10

Also available in: Atom PDF