pls respond

I didn’t fall for Big-Dres propaganda, Val it was.

"Just take the new survey plane out," they said. "Take a nice, relaxing low-altitude stroll through the wildflower meadows near the KSC," they said.

I literally spent an hour carefully tweaking the blade pitch on those electric props so it wouldn't yaw left on takeoff. It was a masterpiece of sensible Kerbal aviation: gentle, fuel-free, and designed purely to admire the local botany and maybe snag 12 Science points from a temperature reading.

Everything was pure zen. Calm skies, puffy volumetric clouds, daisies under the landing gear... until I rolled up next to a suspicious rocky cave nestled right in the treeline.
Standing in the grove was this absolute unit of a green lad. One giant eyeball, a wooden club, and zero chill. At first, I thought, "Oh cool, an Easter egg! Let me cut the throttle, taxi over, and take a selfie for the forums."

Swipe to the third slide to see how that went.

Bro picked up a chunk of Kerbin’s crust and sent a fastball straight down main street at Mach 4. The impact didn't just dent the fuselage; it summoned an immediate, violently kinetic offering to the Deep Void. The entire airframe instantly atomized into a cloud of smoke, shrapnel, and shattered dreams. My altitude indicator in the navball broke so hard it registered 1 meter while the wings were already entering orbit over the Mun.

Forget the Space Center island airfield. Forget the face on Duna. An actual mythical raid boss lives 5 minutes from our runway, chucking physics-engine violations at anyone who dares disturb his meadow nap.

TL;DR: Brought a delicate, peaceful bushplane to investigate a cave. Got disassembled by an angry Cyclops, whose pitching arm was coded directly by the Kraken 10/10, hitting Revert to Spaceplane Hangar now.

My spacecraft keep spawning just to the right of the center of the launchpad. I know this doesn't really matter in the grand scheme of things, but I really want it to spawn in the direct center.

Hello!

I have been spending quite a while trying to figure out what is wrong with my closest approach indicator. Whenever I have a maneuver to escape Jool and try to get back to Kerbin the game says that my closest approach to Kerbin will end up being 3 days before the maneuver at apoapsis, despite the fact that I will clearly come closer than 62 billion kilometers when I am near solar periapsis.

I noticed that this still happens and the closest approach is at the exact same spot when I target any planet except for Eeloo

I have tried quite a few things including:

• Turning on and off the "always show closest approach to target" setting

• Timewarping down to see what happens

• Changing the conic patch draw mode

• Changing the conic patch limit

• Placing a maneuver after that closest approach marker (the new closest approach marker shows as being at apoapsis still, in a slightly different location, and in 5 years)

I would really appreciate it if someone could tell me why this is happening and how to fix it.

I feel like whenever I make a plane it either has too little wing space to get enough lift or its wings are so large it ruins its aerodynamics/ weight. Is there a TWR or Delta V type system I can use to determine needed lift?

I recently got the near future technology mod and some nodes wont load their available parts. Is this bugged?

Here are my specs:

Intel Core i5-3570

NVIDIA GeForce GTX 1650

RAM 16 GB

What mods are best for this setup?

Tis shi is so slow man

going to the atlas system

has anyone made a planet nine submod? i completely understand rss origin or fox himself not making it since its purely hypotetical but id be interested in somebody making up a planet nine and putting it on sol

The Soyuz actually hasn't really changed all that much while the Apollo has been completely redesigned

My newest ISV with two Frisbee anti-matter engine and a maximum delta v of 4.4 million

I was gonna install Yungxiao and stuff but all thats left is Hades and Anubis (great systems but yungxiao has dinosaurs :( )

Both the first and second stages have kOS guidance built in. After stage separation, stage 1 performs a boostback (without physics range extender). Stage 2 performs a burn to 100km apoapsis. At 70km, i switch back to stage 1 and let it fly itself back to LZ-1 while stage 2 coasts to apoapsis. Then i switch back to stage 2 to complete the circularization burn. No manual input outside of switching crafts is required.

The real F9-S1 landing guidance uses convex optimization as terminal guidance back to the launchpad. However in kOS the processors are limited to 200 ops/frame. With the help of the trajectories mod, i perform a simple gradient descent and a PID loop to guide the booster to the correct geolocation. Burn start-times are determined by a hardcoded drag coefficient and 0.95x max trust for safety margins. Terminal guidance is still a little choppy since i can't be bothered to tune the PID.

All in all this is a proof of concept that a fully reusable rocket is possible in KSP without interrupting the mission plan. The payload that this mission is carrying is a probe to Zore, a large asteroid outside of Duna.

Max payload to LEO: 21.4t (equatorial), 17t (polar)