linuxgurugamer

@sarbian I'd like to be able to tell Mechjeb to start a launch, if the launch assistant is active. How would I be able to tell if it's active, and how to trigger the launch.

Tech required is either supersonicFlight or High altitude flight, category would be Utility

Enhancement suggestion: Have a way to simulate an antenna at an arbitrary location. To keep it simple, the arbitrary location would have to be either an existing vessel or planetary body.

Well, I just got it working Hope to get it out in a day or so, still some cleanup to do

You need to add one of 2 parts, EjectionModule, or EjectionCover2A

That would break every ship out there that uses it. Not going to happen If you are referring to the KW Simple Fairing, it's not my mod. and I don't do 3D modeling, so I'm afraid you're stuck on that, sorry

@AndyMt A minor addition to Gravity Turn would be a way for another mod to trigger the Launch button. I use a mod called Launch Countdown, which can trigger a launch by itself, but if I do that, then GT doesn't start. I can easily add the code to Launch Countdown to call GT instead of doing the launch itself. Edit: I was looking at the code, it seems that if I just call the Launch() method, it should work.

Two questions (ok, three) Is the above mentioned bug fixed? does this work in 1.3.0. as well as 1.3.1? Are you aware of any issues with Kopernicus and various planet packs? Thx

When you have a major update, let me know and I will demo it on my Twitch stream

What would you suggest?

Ummm, then you have a problem, because they should be in the Liquid Fuel category. Nuclear engine should be just the nukes Please show a screenshot and a log file

Ok, I'll take a look, thanks

New release, 1.3.2.1: Fixed node at bottom of Critter Crawler

New release, 1.5.8.1 Fixed harmless nullref which happened upon entering the editor (either VAB or SPH)

Next time it happens. do the following: Record what kind of vessel it is. Immediately exit the game, and pack up and send me the following: output_log.txt Complete save directory

You are seeing several different things. You can ignore this: UIList: RemoveItem didn't find any item to remove. it's not an error. If that error from NRAP only happens once, ignore it, it's probably an initialization error, although I will look into it. Then, you have errors from the AT_Utils: [EXC 06:59:59.794] NullReferenceException: Object reference not set to an instance of an object KSP.UI.Screens.PartCategorizer.AddCustomSubcategoryFilter (KSP.UI.Screens.Category mainFilter, System.String subFilterName, System.String subFilterdisplayName, RUI.Icons.Selectable.Icon icon, System.Func`2 exclusionFilter) AT_Utils.SimplePartFilter.add_filter () EventVoid.Fire () UnityEngine.Debug:LogException(Exception) EventVoid:Fire() KSP.UI.Screens.<SetInitialState>c__Iterator129:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) KSP.UI.Screens.PartCategorizer:Setup() EventVoid:Fire() KSP.UI.Screens.EditorPanels:ShowPartsList(Action) EditorLogic:SelectPanelParts(Boolean) EditorLogic:StartEditor(Boolean) <Start>c__Iterator32:MoveNext() UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

Looks like it's Kerbal Konstructs, try removing that

Soacedock has an expired SSL certificate, wait a day and try again

Sorry, but its necessary to be sure everything gets loaded in in the correct order Once this starts to be used, I’ll package the toolbar dll in the same zip file, and will set up ckan to not have a problem with that

Yes, but it can operate without blizzy

Minor update, 0.1.2 Fixed issue with stock toolbar not changing textures Replaced Debug.Log with logging class to reduce log spam

New release, 1.3.1.2 Added fields to context menu to show ignitor range (for launch clamps) and distance to engine Increased range for launch clamp ignitor from 2 to 3

Ok, I have been able to reproduce this. The problem is the sheer size of the Mainsail engine, it is very difficult to get the launch clamps close enough to the center of the engine, which is where the measurement is from. I'm going to increase the distance for the clamps a bit, as well as adding a couple of field to the right-click showing the ignitor distance and the distance to the engine. Note that you can already see if the engine is within range in the editor, there is a line in the context menu for the launch clamp called "Engines in range"

I'll say it again since you may not have seen the first one. I need the output_log.txt, NOT the KSP.log file. From my signature: Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/

I doubt it. I'll take a look later. However, please provide the output_log.txt, it has more information