S4qFBxkFFg

Somehow, I've lost the icon for VOID, or the mod isn't running. I tried running with only the mods automatically installed by CKAN when selecting VOID, but it still isn't showing. The logs are here: https://drive.google.com/drive/folders/1vqrA8CiBbAGKT-CerIOXISyHH48mVC-N?usp=sharing , I think that link should work for anyone. Using the Steam Linux game, both DLCs installed.

This is weird, if I attach the smaller LES to a rocket, when it launches, the rocket stays stationary, the LES starts overheating and blows up, then the rocket launches "normally". If I stage the LES, it flies away (as I think it should), and it also appears to act correctly if the abort command is used.

Yes, just tried a similar flight to the video, there is now no sign of the weird behaviour I described.

If you go to 1:40, it starts shortly after that and lasts until about 2:35 https://drive.google.com/file/d/1fWL2GFnNII4uLkNy9_XlFRDZ9H1sfGJj/view?usp=sharing

Hi, I have an issue when both Scatterer and EVE are installed, I get flickering dark/light areas at the edges of Kerbin, like so: While playing, they are a lot more obvious than the screenshot as the flickering area stretches over most of the space/planet edge, they start appearing approximately after climbing above 120km, but not when high enough for the clouds to change to the distant versions seen from high altitude. If only EVE, or only Scatterer, are installed, this doesn't happen, the settings for both these mods are defaults, and my installed mods are: Log file: https://drive.google.com/file/d/1MywcreV304L9dYeCjL5TCSPnnAv6Vm26/view?usp=sharing

Hello, I have the following minor issue: When I hold down the CTRL key (in an attempt to select more than one mod), I get the following error and CKAN crashes: I tried to copy the text, but there isn't a right-click option to do so. The crash happens before clicking any mods, as soon as CTRL is held. Linux, CKAN v1.30.4

I did: they replied saying it's Xsolla (who handle payments) who need to fix something here. I'm going to leave it for now; if I have to spend time and effort getting a company to take my money, it's probably a bad idea.

Is anyone else having trouble buying from the new store? I was going to buy one or both of the DLCs, but every time I tried it failed with a message saying "Your payment has been cancelled". Looking at the above comments, I think I'll just wait until there's a sale if KSP2 comes out...

Hopper 4a There are still some scientific objectives we can meet without using our higher performing vehicles (mainly gathering data close to KSC) and our crew could always use more flight time - therefore, with inspiration from some older designs, we are again planning suborbital flights. This rocket will be filling in some of the blanks in our materials investigations - in this case, in the upper (above ~18000m) atmosphere. With thrust and fuel reduced to about 60% of maximum, Val will be taking the rocket almost straight up and down - this is about as routine as it gets. MISSION REPORT Crew: Valentina Kerman Result: Success Status: Recovered Details: Uneventful - but that’s what we expected, the materials samples have been safely recovered to the lab, and the rocket is being refuelled. These are starting to look too small for the pad. Target altitude achieved. Not too close, not too far.

Circlet 1a In many respects, this may be the most significant mission we ever fly - the single greatest challenge in our space program is delivering payloads to Kerbin orbit - if we master this, we can place personnel and hardware anywhere in the system, with enough launches. While the previous vehicle design (used for the abort test) was considered suitable for an orbital mission, some changes have been made to enable tests to be carried out on some newly available vehicle components. We have tried to incorporate this testing into the recovery of the first booster stage - throwing away so much hardware is to be avoided, if at all possible. In all, we have contracts to test three different systems - launch clamps, booster, and drogue chute. The flight profile will be: 1. Launch using solid boosters (adjusted to have approximately equal burn durations), after clearing pad, pull back approximately 10° to begin turn eastwards. 2. Jettison first stage, with its parachutes armed - the drogue should deploy immediately, slowing the empty stage, before the main chutes deploy once a descent has commenced, hoped to be to a safe splashdown. 3. Start main engine in stage 2 - continue pulling back into the turn while gaining speed, throttling down to maintain a net acceleration of approximately 1.5G. 4. Jettison escape tower in upper atmosphere. 5. Cut throttle when apoapsis is comfortably out of atmosphere. 6. Exit atmosphere. 7. Begin circularisation by exhausting stage 2’s fuel. 8. Jettison stage 2, continue circularisation using stage 3 engine. 9. Once stable orbit has been achieved, perform observations and experiments. 10. Monitor life-support and electric charge depletion to determine a safe mission duration. 11. Deorbit, targeting the sea off KSC 12. Jettison stage 3. 13. Using reaction wheels, maintain a retrograde attitude during descent. 14. Arm parachute once in lower atmosphere and subsonic. 15. Jettison heat shield after parachute deployment. 16. Splash down and await recovery. Jeb and Val agreed to a coin toss for this mission - Jeb being the victor. MISSION REPORT Crew: Jebediah Kerman Result: Success Status: Recovered Details: This really could not have gone any better - Jeb and the vehicle performed excellently during the entire flight, all mission objectives were achieved, and we can now get “halfway to anywhere” (i.e. LKO) with our rockets. From Jeb’s point of view, everything was routine up until the circularisation burn and with the long burn using the vacuum-optimised stage 3 engine, “routine” became “relaxing”. Without the urgency of a sub-orbital flight, there was plenty of time to devote to scientific experiments and reports - several EVA reports were made during the mission. At an approximate altitude of 85km and just over half an hour into the mission, Jeb overflew KSC and used the opportunity to transmit data using the communication equipment installed in the capsule - while useful, this was expensive in terms of electric charge, which would have been the limiting factor determining mission duration - we need to think about installing solar cells in future vehicles. It was decided to end the mission before another overflight of KSC, and a deorbit burn was made targeting the ocean off our coast. While the energies involved were greater than previous missions, the heat shield again was more than adequate, and a safe splashdown was achieved. Jeb was particularly proud of getting so close to KSC, although the trajectory prediction software has to take most of the credit. The capsule and scientific equipment did float rather lower in the water than we would like, so flotation devices can expect to make an appearance in future missions where a water landing is planned. While most of the team were concentrating on Jeb getting to orbit, the recovery contractors got some practice by retrieving stage 1 - the parachutes worked well, and it only needs some drying out before we can refill the boosters and light them again - more money saved!. For our next mission, tentative plans have been made to fly a two kerbal (scientist and pilot) capsule, equipped with solar panels, radar, and extended stores. We may attempt a launch into a significantly inclined orbit - something not yet attempted either. Launch will be just before sunrise - this should ensure Jeb can land during the day if we need to end the mission in its early stages. Ascending smoothly on the stage 2 liquid-fuelled engine. Coasting, escape tower jettisoned and firing. Circularisation, just after stage 2 burnout. Instruments deployed - in a stable orbit! At this point, Jeb is just sitting back and enjoying the view. KSC through the capsule camera. Burning for deorbit. All propulsive stages gone, preparing for re-entry. Trajectory looking good. This is one of the trickiest parts - keeping the heatshield oriented correctly. Within 5km ! That's not good - some sort of buoyancy aid should be added to our capsules. This is what happened to stage 1. Nice and slow... We can certainly use these again.

Am I missing something or do the "Vintage Propelator Heavy" and "Vintage Propelator Super Sport" have the exact same stats?

Before I ask for support, I want to make sure I'm using this mod correctly - if someone could tell me my assumptions are right, that would be appreciated. I'm trying to use parachutes to recover the first stage of a rocket, and have added a drogue chute and a main chute (separate parts) to the booster. Both chutes stage when the booster decouples - this deploys the drogue, and arms the main chute (main is set to "Must go down to deploy", drogue is not). When the booster starts descending, the main chute SHOULD deploy as well? This should work whether or not the booster has a probe core, I assume? edit: OK, I found the problem - the parachute isn't deploying because realchutes thinks it's in a fairing, although it's just attached to the side of the booster - the problem only occurs when using realchute parts, not the stock parts with realchute options. In case it's useful, log attached here: https://drive.google.com/open?id=1gxjklVT9eb8pW9Mr4vtlppaPbFyHOyPR -

Apologies if this has been answered before, but is there any way to disable TweakScale in all cases except for those mods that provide their own configs? I can see the option to restrict it to Infernal Robotics only, but what I'm looking for is a way to restrict it to something like "Everything NOT in GameData/TweakScale". edit: am I better just deleting all the configs in the TweakScale folder to do this?

Orbiter 1 - Abort Test There was never much of a plan about what to do if something disastrous happened during a rocket ascent - other than “decouple capsule, deploy parachutes, and hope for the best”. Now that a spacecraft suitable for orbiting Kerbin has been designed, attention has also been paid to an abort system that will pull the crewed section away from tumbling/exploding/diving rockets. This test will consist of a full abort from the launch pad - simulations indicate that as long as the SAS remains operative, the launch escape rockets will be able to pull the capsule to a sufficient height/distance for the parachutes to safely deploy. The abort command also activates all decouplers, shuts down all engines, and arms the parachute - the less a pilot has to remember, the better. We have an active contract to test a decoupler at the pad, which fits well with this test - it will merely be jettisoned from the rocket’s base before the abort test is conducted. MISSION REPORT Crew: Valentina Kerman Result: Success Status: Recovered Details: Short and sweet - the launch escape system performed effectively, propelling the capsule and science package several hundred metres up and in the direction of the runway; the parachutes then took over to deliver the vehicle safely to ground. The decoupler test also went without any problems. The next flight will be historic - our first attempt to reach a stable orbit around Kerbin. Looking closely, the detached decoupler/shroud can be seen under the rocket's base. Val isn't fazed by 5G. This is just before jettisoning the launch escape rocket. The tranquil part of the descent. This is another one of those missions where recovery is easy.

Swift 1a There are many reasons for not relying exclusively on vertically launched rocket vehicles - recovery to the launch site is difficult, and lots of expensive hardware ends up being discarded. Also, rockets are virtually useless for extended atmospheric missions. Therefore, after some hangar upgrades, the spaceplane team has commenced work on a light survey/research aircraft - designated Swift 1. Simulations suggest its handling is generally docile, although shedding speed on approach is annoyingly difficult. A brake chute is virtually mandatory if we want to avoid runway overruns. Another issue is the engine placement - on top, out of a lack of other suitable positions (one of the reasons a v-tail configuration was chosen). Scientific equipment carried includes the SC-9001 mini lab, two mystery goo canisters, thermometers, and barometers. Other than testing the general handling of this aircraft, the objectives are to survey three locations near the space centre, and test the Mk1 cockpit in flight. New recruit Megrys Kerman will be piloting the Swift on its first flight. MISSION REPORT Crew: Megrys Kerman Result: Success Status: Recovered Details: “A pleasure to fly”, said Meg after climbing out of the aircraft. The Swift 1 was perfectly suited to the survey mission, managing to fly the route planned, visiting all three survey areas, without causing any problems. As expected, the landing speed is still higher than ideal, but Megrys was up to the task (she stated during the debriefing that the SAS was more of an irritation than assistance - the aircraft’s aerodynamic balancing was sufficient to ensure stable flight). One other finding was that roll authority could be usefully increased - e.g. by moving the ailerons outboard; this would allow adding flaps to their current location, which should improve take off and landing performance. Pre-flight checks are nearly complete. Meg turns towards waypoint 2. KSC is barely visible above the port wing. This is OK, as long as you know where the mountains are. After gaining altitude over land, Meg turns to head for home. KSC is visible again (in the left side of the HUD). Straightening up for final approach. Meg actually popped the chute while still airborne - it worked, this time. After a successful landing, it's time to vacate the runway. Mission complete! - the ground crew are on their way.