Tuckins

How does one properly remove the AmpYear mod? I'm running 0.13a with x64 KSP 0.90 on Linux, and just deleting any craft that use AmpYear parts and then deleting the folder doesn't work - the next time I load the game up, I am unable to select any craft from the space center: the list of ships still appears, but clicking on one does not select that ship or activate the buttons for interacting with it. I'm running a lot of mods, but I am able to reliably reproduce this issue by deleting the REPOSoft folder in GameData, and I am also able to reliably fix it by restoring the REPOSoft folder. This section from the KSP.log suggests that, even when I have removed the AmpYear mod, the game is still trying to find it when I open the Space Center and select a ship, and its failure to find it is leading to an error condition. How do I remove the game's expectation that AmpYear will be there? [LOG 10:34:41.709] 6/28/2015 10:34:41 AM,KerbalAlarmClock,Found 0 Maneuver Nodes to deserialize [ERR 10:34:41.710] Cannot find a Module of typename 'AmpYear' [ERR 10:34:41.710] ScenarioModule is null. [LOG 10:34:41.808] 6/28/2015 10:34:41 AM,KerbalAlarmClock,Setting App Button True [LOG 10:34:41.843] StnSciScenario started

I've just had this exact same problem, except that Flight Computer also stopped trying to hold any particular heading after the node burn time was met, and instead tumbled wildly through space with engines on full blast until the stage's fuel was completely expended. Also, I wasn't able to queue any actions for after the node was finished (though that might be my fault since I'm not quite sure I understand how to queue stuff yet). And once the burn started, I was unable to access the command queue at all - clicking the button to make it show up just caused the Flight Computer window to disappear; after it was done, the Flight Computer window stopped showing up at all. Still haven't gotten control back, since I need to wait for Mission Control to come over the horizon and I can't timewarp since the ship's still throttled up. It seems like Flight Computer just didn't turn the throttle off after it was done carrying out the maneuver node.