BloodyRain2k

Could it be added that the addon won't multi deploy experiments? Like when there are 4 thermometers it will only deply 1 and not all 4 and also check for existing results in experiments and stashs to not deploy any that are already saved? Another smaller thing would be to make the window "snap" to the bottom of the screen if placed there, but I think making the window expand upwards as it changes height would be not exactly easy, though I haven't messed with the new UI yet, last time I modded was when it still ran U4.

Yeah of course, the only likeable submission is invalid : / Someone find that artist and make him enter himself xD While I don't like the idea of female kerbals do I really like this gal.

Will contracts for non-present parts finally stop constantly unfolding on condition change? Oh and transponder fitting is not covered by 100% recovery, is that intended? Also why can't I use the strategies to convert rep to fund and science and also funds to science?

That's KSP for you, not EE. Also if anyone cares: https://github.com/MachXXV/EditorExtensions/pull/4 <-- still waiting to be added since 21th Jul.

It should be mentioned at this point that the hovereffect is done by changing the buttons background image of the button, meaning that you will not get any at all should you make the mistake (like I did) of using a fully opaque image. Took me 2 days to figure this out now. It probably offers it's advantages by being able to use a custom hovereffect should you want to but given that this would require custom code for switching the image could the stock hovereffect as well be a layer on top of the button that get's turned visible when hovered and a setting to disable that. Just my feedback so far from trying to make ORDA use the toolbar. Aside of this little witch hunt for the reason why the hovereffect was missing is it very easy to use.

I was trying to add interstage nodes to the couplers so they can be used with the interstage adapter. Sadly the top node doesn't seem to serve a good purpose as it does attach as intended but does not trigger any effect on the fairing's size: That's the topnode 4m up with 2m or more extra height so the fairing doesn't cut as much into the engines. The node I added to the coupler is right in the middle of the 4 normal nodes and a size 2 one. Interstingly though does it also not trigger shrouds when attached to engines.

Having the choice between Nexus and Curse is like choosing between poo and a different colored poo. There's also KerbalStuff as alternative: [Moderator removed defunct website] Not that any of these would make TT change his mind as I'm pretty sure that he's not even checking in here anymore. Though he's free to prove me wrong anytime.

Would it be possible to add a docking nosecone? Something like the shielded docking port just not as flat and more noseconey?

Because due to the way how things work it will NEVER be fully inline with the CoM and always a fraction of a millimeter off and that's enough to confuse it. But you're right that it should use some kind of deadzone for these cases.

You know what, this as a plugin so you can watch that list ingame with the percantage of completion in the fields would be awesome. Now the problem is just finding someone who'd code that XD

It would be nice if the KM_Gimbal could read out the stock gimbal range parameter if yaw and pitch range aren't supplied. I want to use them as replacement (replacing them via MM) for stock gimbals to get roll authority but it defaults to 1° so not really that useful then. Edit: after some testing the next problem would be MJ compatibility so it doesn't matter that much. Though it's certainly easier to change the base class from PartModule to ModuleGimbal.

Did you fix the bug for 1.2 where when you use the double chute nosecone and have the drogue chutes out you get the option to cut the main chutes instead? Instead of showing the option to cut the drogue chutes (secondary) it showed the option to cut the main chutes, and it successfully cut them before they were even deployed. Also the settings parameter "Parts used" as in the amount of chutes, doesn't seem to account for symmetry because when I enter 4 when using them in 4x I get the results I want with the numbers I entered, but by default it's 1 so then it should result in a 4x as large chute as needed per chute. Didn't test that though.

Can you add some settings to the toolbar? The first is that newly added buttons from mods get added instead of needing manual adding. I think I already asked you in the chat about that, dunno anymore. The second is to allow mapview and inflight share their position. Size and buttons not since these can differ but I like to have them in the same place and moving them in the exact same place is a bit bothersome, especially after correcting their size, but if they're a few pixel differently placed my ocd ticks off, this setting could help with that :3 And maybe a third to tell it whenever it should prefer growing down or right when the size gets exhausted. Also it would make identifying which version of the toolbar is running if the dll's assembly version would reflect it. I have 1.7.1 and it's just showing the default 1.0.0.0.

Part Catalog

Why is Tab still the key to switch the mode? I always get stuck then in the description input box and so I need to recompile it myself and use Y (german layout) instead

What you're referencing is the player's input throttle. What MJ's doing is take that, or rather outright ignore it most of the time, and modify the vessel's throttle input. FlightGlobals.ActiveVessel.CtrlState.mainThrottle or so was the one for that.

Found a small bug: the settings for automatic node alarm setting won't save. It always defaults back to 3min for both. Also isn't the node saving and restoring redundant now that KSP does that?

Danny has his own use for them.

Translatron -> Keep Vert with Kill HS. Just get in a flat angle with low vertical speed to your target altitude and turn that stuff on, it will do the hovering thing while decelerating as much as it can. Atleast it should, I didn't try it yet with 1km/s horizontal speed. As for the overshooting a node: MJ starts burning half of the burntime ahead of the node because it will need to burn the other half after passing it, the result will still be very close to planned node. Unless your TWR is so low that you do like 1/2 of an orbit while burning, then it probably won't. About the rendevous thing: if it doesn't make a good Homann Transfer for my target I just use the fine tune or just plan the node myself. But I really should try to make it aim for a 0.1km fine tune.

Yeah, something seems to be wrong with the Landing AP on Moho, it seems to try to do an atmospheric landing but without the drag deceleration that fails and it just raises the PE above the surface again and then derps out.

I'm not sure about the cause of the problem and even though I spent 2min now writing down my theory about it do I not want to spread false information so meh, just this note about it. There is a damn simple solution to it however: the tolerance setting in the Maneuver Planner. The default 0.1 m/s work normally for all, but if you have a rather heavy ship that might tend to wobble a bit just from beginning to turn then it's likely that you need to raise the tolerance because at the 0.1 m/s point will the wobble be enough to knock the node marker all over the place. Why the hell it helped you Saint, to revert to 0.22 is beyond me, that setting is set to 0.1 m/s since it's in. Maybe something got changed in the Attitude controller, or it was the Tf setting of it, I'd bet on that. Anyways, try raising the tolerance and see if that helps. Also try playing with the Tf value in the Attitude window, auto tends to get it wrong for heavier ships, I usually go for 0.3 or 0.5 if it get's a little twitchy.

Your problem is either that you don't have enough torque, so either add more reaction wheels or turn on the RCS (or add more thrusters), OR if you know you have enough, the problem is that MJ isn't using it correctly. That is something that happens for me a few times. Open the Attitude module window and look what the Tf setting is, on Auto does MJ try to figure out a good value based on the mass of your craft. The problem with that is that it sometimes gets it wrong and lighter crafts wibble oscilize, or larger ones lag oscilize. I often found it then better to set it simply to manual with a value of 0.3 for smaller ones and 0.5 for the larger ones. Sarbian already told me that he needs to figure out a formula that's a bit better but well, math and stuff can take some time. What I don't know is if that value and setting are global or per craft saved but I'd guess for global.

The editor change with the description field and Tab was the reason why I changed it in my version to switch by Y. I still press Tab occasionally and then I'm stuck in the fields again...

If you're 10m away and lined up you might aswell finish it yourself...

My suggestion would be to read what the window says about the modules being locked until you unlocked them with science.