DavidHunter

Thanks; I'll check that out. - - - Updated - - - Because I live in communist Russia? Oh, yeah, and another feature request, if I can, please. When building my gigantic space station, I have the modules all arrive close to Station before ditching their liquid tanks and engines (so that only the part needed, plus docking ports, are what are actually attached to Station in order to save part count). This means that I have spacecraft hanging around basically with nothing but RCS to propel them. This isn't a problem when only docking. However, this morning I had a mis-hap with a launch and had a part in a different orbit to the Station altogether. I did the normal autonomous rendezvous to Station. Everything worked fine, it activated and used the RCS thrusters instead of the liquid engines (as they had fallen back to Kerbin). However, MJ hadn't compensated for the low-thrust of the RCS engines and, hence, all the burns took way longer than expected, so the rendezvous failed. TL;DR? Can we please have MJ consider how long it would take to do a burn if only using RCS thrusters, so that it starts the burns early enough to be successful? Thanks in advance, and thanks for a fantastic mod. It makes my sciencing so much easier.

While I'm here, I've got a feature request, if you don't mind, please. Is it possible to have MJ target a specific point in an orbit, compensating for rotation of the parent body? e.g. if in a 100km circular orbit, I'd like to put something into GSO directly above KSC, so the burn to go from 100km orbit to GSO needs to be timed exactly so that - by the time the spacecraft reaches GSO and begins circularisation burn - Kerbin has rotated so that KSC is directly beneath the circularisation burn point. The end result will be that MJ would allow users to put something into GSO directly above a specific location. Is that possible, by any chance, please?

Can confirm upgrading Real Chutes solved my docking AP problems. Thanks!

Is there any way I can try and figure out what the problem is...? Any useful logs I can post? Any detail you might need? This issue is still occurring. On another note, auto-ascent also has issues with going into a specific inclination or launching into the same plane as a target in orbit, too... but that's not a major problem for me so I'm not too worried about it... (I'm still using build 254) Ta.

My comment seems to have been ignored (other than Galane's comment, which I couldn't make sense of). Anyone else experiencing this glitch?

Do you mean to check the 'override safe distance' checkbox and set a safe distance? I did that with a 5m safe distance and it just took off into the never-ending cosmos again, despite being within 80m of the docking port. :/

Hi folks, Currently using MJ build 255 on KSP 0.23.5 on OS X 10.9 with the latest version of the Toolbar add-on. Unfortunately, when I use the docking autopilot (after getting within 100m of another spacecraft and selecting the target docking port and the port from which to control the current spacecraft), MJ seems to just keep backing away from the target indefinitely. I have had this issue since - I think - build 220 or so(?). Am I doing something wrong? Thanks in advance for your help, Dave

Never mind. Uninstalling a bunch of other mods and reinstalling Interstellar fixed the issue, so the problem must be in one of the other mods. Ignore me.

Completely uninstalling Interstellar also didn't fix the issue.

I just installed the latest version of the mod, but have a new issue that hasn't already been reported by above posters... Specifically, upon loading KSP, it never asked me to select the tech tree (i.e. as if TreeLoader wasn't installed properly... which it definitely is). So my save file has zero parts in it whatsoever. Nothing in the research centre at all. There are the research nodes, just no parts. The VAB and SPH are both empty, too, so upon loading KSP I lost all my current missions. D: (Interestingly, when I first loaded the save, and KSP did its usual "this ship has invalid parts, deleting it" routine, it deleted the asteroids introduced by vanilla KSP 0.23.5 as well...) Any suggestions, please? I tried completely uninstalling and reinstalling KSP Interstellar, and also tried installing the new version of TreeLoader, to no success. Thanks in advance.

^^This would be AWESOME.

Yup, removed a whole heap of mods and now everything works. Thanks again for your advice. Sadly, KSP ain't as fun as it used to be: had to remove NovaPunch and Deadly Re-entry. On the up-side, I might finally get to land on the Mun (I've been playing since v0.22 came out)... and beyond. Might remove TAC Life Support and make things easier again. I really needed the very big engines in NovaPunch to get all the science payload, plus life support and power, etc. on the one lander. Which ones? I've tried as many as I come across and they've never done anything for me... :/ Active Texture Management certainly didn't work...

10.9.1 (Mavericks).

Oh, dang. Good thing I didn't order the full 32GB I was planning on buying then.

But I haven't made any changes or installed anything new. In fact, this morning, I increased my RAM from 8GB to 14GB. Unfortunately the texture reduction mods don't work on Mac. :/ Nonetheless, I'll try to remove some non-essential mods and try again. Thanks for your advice.

Hello. Long time stalker, first time poster. Great mod. Unfortunately, last night, my KSP install stopped opening. It was working perfectly fine, then suddenly it started to hang at the very end of loading the plugins at the splash screen, i.e. while Interstellar was loading. (Screenshot attached). I hadn't made any changes, or installed any new mods, or anything... :S It keeps freezing here and gets no further. Removing the WarpPlugin folder from my GamaData folder allows KSP to load, but - of course - prevents Interstellar from loading. I have tried downloading and installing a fresh copy of all Interstellar files but to no success. Can you suggest any way I can fix this issue, please? Thanks in advance. Dave Following is my /WarpPlugin/Spaces/sci/internal.cfg file, just in case you need it: