All Training Missions start EXCEPT Asteroid Redirect Part 1

[Keithustus]

I started playing KSP just a few days ago. Based on some Youtube videos and reading the wiki and elsewhere I installed pretty common mods: KAS, Kerbal Engineer Redux, KIS, NavyFish's Docking Port Alignment Indicator, and the Surface Lights mod. The game works fine in Career mode. Before starting Career I played through and completed all the Training scenarios including Asteroid Redirect Part 1.

But I would like to replay that scenario and it won't begin. All the others work when I press Start. For Asteroid Redirect Part 1, the Start button does nothing; it depresses and returns to normal when I release my mouse button, but nothing else happens. When I try to click or double-click on the name of the scenario and its green clipboard icon, the mouse clip goes through the window and instead activates the text behind, so I am continually being directed to the "About Making History Expansion" website.

I have restarted my computer and checked for Windows updates.

I have moved the mods out of the KSP directory.

Still, that training scenario won't begin again.

 

What should I do now?

[OHara]

Welcome to the forum.  

I have not seen this problem, but I remember that the ARM scenarios are different to the others in that they cannot be saved and resumed.

You might try deleting the scenarios/ARM_Asteroid1/ directory, because on first install of KSP the scenarios directory has no subdirectories saving the state of the (partially) completed scenarios.  It looks like at right.

Or, maybe your KSP.log will make the problem obvious.  When I start the ARM scenario, my KSP writes to that file:
 

[LOG 23:33:25.676] Loading banner texture from C:/KSP191/KSP_x64_Data/../saves/scenarios/banners/Refuel at Minmus.png

[LOG 23:33:25.757] Loading banner texture from C:/KSP191/KSP_x64_Data/../saves/scenarios/banners/Space Station 1.png

[LOG 23:33:26.013] Loading banner texture from C:/KSP191/KSP_x64_Data/../saves/scenarios/banners/Transmissions.png

[LOG 23:33:26.095] Scenario #autoLOC_1200000 is non-resumable.

[LOG 23:33:26.095] Scenario #autoLOC_1200000 is non-resumable.

[LOG 23:33:28.121] Scenario #autoLOC_1200000 is non-resumable.

[LOG 23:33:28.122] Scenario #autoLOC_1200000 is non-resumable.

[LOG 23:33:34.474] Scenario #autoLOC_1200000 is non-resumable.

[LOG 23:33:34.513] [KSPUpgradePipeline]: ARM_Asteroid1 updated from 1.2.0 to 1.9.1.

[LOG 23:33:34.529] [ScenarioTypes]: List Created 21 scenario types loaded from 1 loaded assemblies.

[LOG 23:33:34.530] [MessageSystem] Load Messages

[LOG 23:33:34.560] Game State Saved to saves/scenarios/ARM_Asteroid1/persistent

[LOG 23:33:34.594] [UIMasterController]: HideUI

 

[Keithustus]

7 hours ago, OHara said:

Welcome to the forum.  

I have not seen this problem, but I remember that the ARM scenarios are different to the others in that they cannot be saved and resumed.

You might try deleting the scenarios/ARM_Asteroid1/ directory, because on first install of KSP the scenarios directory has no subdirectories saving the state of the (partially) completed scenarios.  It looks like at right.

Or, maybe your KSP.log will make the problem obvious.  When I start the ARM scenario, my KSP writes to that file:

Thanks for the suggestions.

First I moved my scenario directory, renaming it from Kerbal Space Program\saves\scenarios to Kerbal Space Program\saves\scenarios-backup. This was not effective. IMMEDIATELY when KSP is launched from Steam that directory is rebuilt with new files (same old creation dates) and the same problem occurs.

Next I moved from doing that to that directory to instead the Kerbal Space Program\saves\training directory. By renaming that to Kerbal Space Program\saves\training-backup, the same results occurred: another folder is generated with the files.

Similarly, by deleting individual files \saves\scenariosARM_Asteroid1.sfs and \saves\trainingI_Asteroid1.sfs, again same results (not surprising).

 

As for KSP.log, if I launch KSP and try the scenario and then quit and close KSP without trying anything else, the log is very long but does not include word "asteroid" anywhere.

 

.....

 

SUCCESS.

Apparently two things conspire to create this bug: (1) there is some incompatibility between that mission and one or more of the mods I have installed, AND (2) I insufficiently removed the mods previously.

This time, instead of simply moving all of the mod folders from their particular \GameData folders into a \GameData\backup folder, which probably did not disable them, this time I moved them all from their particular \GameData folders into a new \Kerbal Space Program\GameData-Backup folder. Running the program and booting directly into the training mission works.

 

Lesson learned: don't think that moving mods simply within the \GameData\ folder to other subfolders disables them....the game still finds and activates them.