Baythan

Welcome back, Director! Another successful mission in the record books! And what a monument you've found! The figure looks a little like a Kerbal, but what's with the squid mouth? This is repeated 5 times before the final message is stated. After the first repetition I kinda laughed, like maybe something about the monument had affected Dr. Keri. By the fourth repetition I was getting concerned and annoyed. When the final message came up I was just confused, like maybe I was affected by the monument and missed half the conversation with Dr. Keri in a fugue state. I think this is a bug, but maybe something about it deserves to be left in after the fix, to remind us all of this weird little glitch.

I recently added Kethan to my game to go along with Extraplanetary Launchpads, so it's taken me a bit to figure things out. Now I have a question: Are the two scanners really supposed to be at the same tech level or am I the victim of too many mods screwing with my tech tree? The KE-S210 Compact Survey Unit is in the Scanning Tech node (300 sci cost) and the KE-S110 Medium Survey Unit is in the Electronics Tech node (also 300 sci cost). I would have thought that one of the scanners would be available around the same tech level that the extractor can be researched, even if it's not a good scanner.

Just a quick note: Your 1.5 version of the mod on GitHub is not a zip file, it's each mod file individually. Your install directions are no longer accurate to this way of packaging the mod and will likely confuse people when they cannot find the "InFlightFlagChanger" folder.

With USI addons like MKS/OKS, most of the normal EL parts get hidden because the USI mods replace things like the orbital workshop, dock, launchpads etc. The documentation on those mods should state what parts are hidden as well as defining the new resource chain required to create ships in-situ. Using an older version of all those mods will make it more difficult to get the exact info though, because both MKS and EL have changed slightly since 1.0.5.

Thank you very much @MaxRebo! (Love the band, btw. Glad you guys made it off the sail barge) I just might have time to test your unofficial build later this evening.

Have you read much of this forum? I just scrolled through the last few pages worth of posts and found this: Sounds like a similar problem to the one Zwa mentioned and what you said was happening to you as well, and the posts after the above quoted one discuss the issue and possible workarounds or reasons why that happens. Edit: And also, there's a fix coming when Diazo can find enough time to add it in, as shown by the post above mine.

Sure thing. Thanks for having a look!

Thank you for having a look, that is mighty awesome of you.

RemoteTech does not allow antenna to be turned on if a probe has no connection, the XF Config allows antenna to be activated/deactivated manually without a connection so you don't get screwed over by forgetting to activate them before losing a connection, however ALL action groups are still disabled without a connection (no matter what is being activated or deactivated). With Action Groups Extended I like to set up two action groups for Antenna, one to activate and another to deactivate(for aero-braking and whatnot). I usually bury the antenna inside the ship with part clipping, so it's more difficult to manually activate them in flight. If part clipping actually occluded the antenna and stopped them from getting ripped off by aero forces, this wouldn't be a problem and the antenna could stay activated. I'd rather be able to toggle the antenna on/off with AGE at any time, without worrying about connection status and without having to turn the bypass option on every time I'm coming out of an aerobrake or landing on a foreign body. Because AGE already has a bypass remote tech option, I thought the easiest solution to this issue would be just to have that as a toggleable option that remains active/inactive through scene changes (currently requires re-activation every time I want to reactivate antenna with the action groups set to do so).The only problem with this option is that it would make ALL action groups ignore remote tech connection requirements rather than just antenna. I'm not sure a more elegant solution falls under the purview of your mod though, I'll probably have to ask the XF config guys if they can make their config allow antenna activation/deactivation through action groups. TL;DR problem: action groups can't be activated unless the temporary bypass remote tech option is enabled (with or without XF config) possible solution: make the bypass remote tech option a toggle that remains on until disabled.

I agree that this could use a bit more organization in where the different experiments are listed. I would say that EVA Reports should be one row across, Mystery Goo as another, etc so you can see where you have/have not done certain experiments on each given body without mousing through a semi-random list of experiments to see which ones are all the same science part. I can't seem to find any listing for Atmospheric Pressure scans in space High or Low(which can be done now) and KSC is now apparently 9 different biomes for surface tests.

Reduce the altitude and/or pressure at which the chutes deploy so that you don't have as long to float downwards. Don't be afraid to use drogue chutes and then cut them off to freefall to a lower altitude.

Ah, I'll look into that. Might have to run some tests to see what velocities will actually destroy things now. Thanks for reminding me about a feature I probably should have known about, had I been paying attention.

StageRecovery DOES detect when KSP auto-deletes objects due to atmospheric entry and recovers those objects if they are capable of landing and don't burn up in atmosphere. I think the burning up calculations for StageRecovery are still at 1.0 or 1.0.1 sensitivity, because I drop things that trajectories says burn up but if I follow the objects myself, they never burn up. I even modify the atmospheric pressure for parachutes so they don't deploy until dropped stages reach safe velocities (provided they don't hit a mountain). StageRecovery can only do so much though, and I can deal with some things being lost due to aggressive reentry speeds.

I will test a fairing-missile probe right now and see how accurately I can land it without ejecting the fairing... be right back with results. Vehicle: Attempt #1 Long, flat trajectory with the missile pointed prograde through the atmosphere. Result Passed over KSC at 31.8 km. Image is darker than I wanted, the impact point is just off the coast of the next continent. It seems that long atmospheric flights tend to have the most inaccurate predictions, but this is true for all vessel types. The longer and flatter your trajectory, the more mistakes in the prediction and the less accurate it is. Attempt #2 More aggressive, steeper trajectory. Result Passed over KSC at 5.6 km, impacted about 11.5 km from the VAB (where my flag is). I forgot to get a screenshot before I attempted to refocus the worldmap and lost the impact point. TL;DR - Yes, it works with fairing and heat shields. The more aerodynamic the vessel, the more inaccurate the prediction (it seems). It may just be worth it to make a test landing and see how far off your vessel is from the prediction, then correct for it. Generally speaking, aim short.

AFAIK parts on rails do not experience drag in atmosphere, but KSP does auto-delete objects that reach a certain altitude in atmosphere. I recall that altitude being somewhere around 20-40 Km in previous versions of KSP, not sure if that is still the case or what the specific altitude is.