Ixenzo

Is it intended behaviour that (some) single ignition engines can ignite multiple times? Situation: LR105-NA-5 sustainer with two LR89 (LR43-NA-3) boosters on the launchpad held together by clamps. LR89's have one unit of the TEATEB igniter, and promptly refuse to light up a second time. LR105 doesn't have the igniter, and lights up multiple times despite the ignitions remaining readout clearly showing zero. Is this a specific design of the real engine that allows it to be reignited on the launchpad on the spot? Edit: I should clarify that I cut thrust with X and the LR89's did not reignite the second time. However, shutting down the engine entirely, setting throttle to 100%, and then manually activating the engine again does reignite it despite not having TEATEB or ignitions remaining left. An engine that failed to ignite due to TestFlight completely removes its activate/shutdown button and as such cannot be replicated. KSP 1.3.1, mods mostly from the spreadsheet.

Is there a way to disable or reduce the impact of tooling in terms money and build time penalty?

KSP in its form is and has been a barebones physics engine with minimal and illogical (from realism standpoint) content. Mods add actual mechanics, gameplay, content and (for shame!) UI into it. I thank modders for making KSP a playable and enjoyable game.

@EXPERIMENT_DEFINITION[*]:HAS[#id[crewReport]] { @biomeMask = 31 } @EXPERIMENT_DEFINITION[*]:HAS[#id[evaReport]] { @biomeMask = 3 } That makes Crew Reports biome specific in low orbit and EVA Reports biome specific only when Landed or Splashed.

The GCMonitor.cfg is no longer created and stored, resulting in default font size and position on each game launch regardless of applied settings in a game session. Copying over a config from previous version works fine. 1.1.3, RP-0 suite, output log.

Everything's fine in that department. Interplanetary maneuvers also seem to work fine. Maybe it's a thing with only hyperbolic orbits.

Just chillin in my orbital pool, you know?

In 1.1.2 every left click on the window or outside of it closes Precise Node and deletes the node. Only input fields can be clicked on safely. Numpad and right click work fine. I've ntoiced this behavior in my 1.1.2 RP-0 playthrough. It works fine when I'm orbiting Earth and do a TLI but when I try to create a maneuver while on hyperbolic orbit around Moon, the aforementioned things happen. A complete game restart seems to fix this. There are no exceptions from Precise Node in the logs. Anyone had this one?

Nerd Force. Because very narrow specialization of technology which delivers a force. I'm not great with names

Eh, KER just doesn't show stage dV if it's currently firing. At least the only thing I've noticed, not that big of a deal; I should know what stage is what and how much by the time I completed the design. Besides, MJ's UI is horrible to my taste. What's wrong with toolbar? I haven't noticed anything weird with it and it certainly not going anywhere. Screen real estate is pretty valuable for me Also experience the "can't click on some buildings" every once in a while. I jsut click the buttons on the left side.

Is there anything more permanent than rebuilding ocean every time to fix this glitch? I tried the scatterer.dll posted a few pages back but it just reduced FPS to <1 while throwing NullReferenceException: Object reference not set to an instance of an object at scatterer.Core.Update () each second. RSS @ 1.1.2

Not really. The only thing you can do is preemptively copy your working setup to have something to play while waiting for the mods to update to new KSP version. Or, you know, YARR.

So yeah, something like this still happens in my RSS/RO/RP-0 save. All my craft use a single clamp from the side and more often than not it shifts the whole contraption (launch clamp included) up to 15 degrees to the side upon physics unpacking on the launchpad. It's a small inconvenience with gimballed engine designs but with sounding rockets it renders them much less efficient (and with KCT the issue is rather irritating). Do I have to use four clamps? I don't know why it procs only sometimes; output log is silent about KJR. Are there any known conflicts between KJR and mods from the RO suite? KSP 1.1.2.

I think I also have an issue with KSCSwitcher in my RSS/RO/RP-0 career. I've been launching from Kourou from the start and switched to Plesetsk to test a polar orbit launch. The thing is that simulation does not work properly: I don't have any control from the keyboard (WASDEQ, staging, etc.). Only mouse clicks on parts work. I don't know if non-simulation flights work though. Switched back to Kourou - simulation is still not working. Reloaded the game, seems to be working again. Started a simulation in orbit - again no keyboard controls. It started to happen just today, for no apparent reason.

I spent an hour manually installing the RO suite only to come here and find that the fight's over (at least for now). Mixed feelings. But thank you all.

Filter Extensions.

ckan.exe can be run from anywhere, it uses registry to find game folder.

I hear the time format is set by the localization which mono uses, correct? Then I think I'm looking in the wrong place since my OS (win7) follows the normal time format everywhere (time settings and all) but this mod in KSP. Would someone care to point me in the right direction?

Too bad to be CKAN, I guess.

You can just flip the switch manually. It adjusts thrust in real time automatically.

I've always used 50, been good. Usual ascent is 3200-3250 to 71x71, sometimes 3100. Circularization is never more than 25 m/s.

This is an incredible tool with so many possibilities... And once again I question myself why didn't I check it out sooner. Thank you for your effort!

Someone said it'd be great if this mod had a kill time warp on new available science option. I second that. It's the only thing that makes Science Alert valuable to me. Is it possible to implement?

HotSpot displays thermal information about each part in a craft and you can customize your degrees preferences in there. The thermometer should display the temperature of itself, so I guess it's the same as the temperature of the part "Thermometer".

Here's mine: https://drive.google.com/open?id=0B7AaFFbHPo5MVnVLaFh6MUlrbGc There are errors in the log, included the .mat file.