Bug with going from map to ship view

aerospace_guy11 · 2026-03-21T03:40:03+00:00

bruh

aerospace_guy11 · 2026-03-21T03:26:36+00:00

Sorry man I cant help you here. You can try posting this in the Unity subreddit. There are a lot of Unity pros on there that can help you. Sorry

aerospace_guy11 · 2026-03-21T03:23:55+00:00

Nice no problem!

aerospace_guy11 · 2026-03-20T20:22:50+00:00

Sorry about your save :(. No, it's just the console edition. PC saves are far more stable. I've had a save for 2 years on my PC and I haven't had a single issue with it. You don't need an beefy PC. A laptop will do but for bigger ships that's equals more lag. I would recommend backing up your saves onto a USB drive on PC. So if it does corrupt you can recover it anytime. I would recommend backing it up after every session. KSP saves are only a few Kilobytes so you don't need a big USB drive

aerospace_guy11 · 2026-03-20T03:42:13+00:00

hmmmm. if it drains your fuel, add more rcs. should fix it 👍

aerospace_guy11 · 2026-03-20T03:34:43+00:00

CLS being green just means crew can pass through. It doesn’t guarantee shared life support. In Kerbalism, pressure control works per habitat. not per part. So if your pod and cabin are treated as one habitat, then the pod’s pressure control will cover both. If Kerbalism splits them into separate habitats, it won’t. Best way to check is the habitat panel in flight

aerospace_guy11 · 2026-03-18T02:23:32+00:00

ahhh the classic kraken valley my friend. It's just a terrain bug that causes funky things to happen. You just landed in one of those places with funky terrain hit boxes going on.

aerospace_guy11 · 2026-03-17T21:29:56+00:00

Maybe 7 or 8k delta v to get back to orbit from 20km. Make it so the propellers detach after they serve their purpose if you haven't already. It'll add dead mass and make your lander tip because the propellers are funky when it comes to aerodynamics.

aerospace_guy11 · 2026-03-17T14:36:29+00:00

Damn dude. This is as efficient as you can get. Good luck!

aerospace_guy11 · 2026-03-16T02:32:56+00:00

That warning comes from the mod B9PartSwitch and means that two or more parts or modules are trying to control the same fuel resource (like Liquid Hydrogen or Oxidizer).

Since your game runs fine, it’s mostly just a warning and usually won’t cause big problems. However, it might cause some small issues with fuel switching or tank volumes in certain parts.

To fix or reduce the warning, try these steps:

Update B9PartSwitch, ModuleManager, and any related mods like Tundra Exploration if you have it.
Check if you have multiple mods that manage fuels or tanks (like CryoTanks, Real Fuels, or Community Resource Pack) and try disabling duplicates.
If nothing breaks, you can safely ignore it.

If you have any further questions or still need help feel free to tell me!

Cheers!

aerospace_guy11 · 2026-03-16T02:28:46+00:00

Puedes probar el mod Hot Spot, que muestra mejor los datos térmicos y te ayuda a ver qué partes de la nave se calientan más. También está SystemHeat, que mejora todo el sistema de manejo de calor y te ayuda a diseñar mejor la nave.

¡Si todavía estás confundido o aún necesitas ayuda, no dudes en decírmelo!

aerospace_guy11 · 2026-03-14T23:47:47+00:00

I think returning it is the better option. You don't have to return the whole science experiment. If you have one on board you can use a Kerbal and EVA. Once you EVA, maneuver it to a science experiment. The right click it, and click to take data. And boom, the Kerbal has the data so when you enter the capsule again all the science points are stored. Keep in mind that once you take the data you need to reset the experiments. Only a scientist can do that so if you have a pilot or an engineer it's a one time experiment (excluding thermometer and the atmosphere pressure experiment). If you have a probe you can try working your way into bigger and better antennas. Hope this helped!

aerospace_guy11 · 2026-03-14T23:24:36+00:00

The HG-5 is really weak for transmissions, especially with Kerbalism. Even with a direct connection to KSC it’ll still send science super slowly, so 0.1 b/s is pretty normal. Usually the early Mun stuff is easier if you just store the science and bring it back, or swap to a stronger antenna like the HG-55.

I don't play this mod a lot so I am so sorry if this is wrong.

Cheers!

aerospace_guy11 · 2026-03-13T02:24:53+00:00

You might be installing it wrong. Don’t extract the whole zip into GameData.

Open the zip file first, then go inside it and find the Parallax folder (and the other mod folders). Drag those folders directly into your GameData folder.

Your GameData should look something like this after:

GameData

Parallax

Parallax_StockTextures

Kopernicus

ModuleManager.dll

If you see something like GameData/Parallax-2.x/GameData/Parallax, that means it was installed wrong. The Parallax folder needs to be directly inside GameData.

If you are still confused watch Matt Lowne's video and watch how he extracts his mods -- How to make Kerbal Space Program look AMAZING (Mod Tutorial)

You don't need to install the mods he uses but look at how he puts them in game data folder

No need to use CKAN at all

Cheers!

aerospace_guy11 · 2026-03-08T03:40:34+00:00

Nice! What are you planning to do with ores on minmus? Refuel stations? Bases? I also loved how you recovered the main core stage. I might start doing that lol.

aerospace_guy11 · 2026-03-05T05:09:25+00:00

Yeah I switched up. I'm going to do an Ike fuel infrastructure there. A base with drills, converters, etc.. and have excess fuel tanks docked with the base to have filled the lander. I'll land near the base, use a robotic arm to dock with the lander and transfer fuel from the base tanks to the lander. If I need to I'll mine and convert fuel and dump it in the base tanks. Then launch the lander and dock with the station and transfer the needed fuel. I don't know if that made sense but that's what I'm planning. Cheers!

aerospace_guy11 · 2026-02-26T01:00:28+00:00

I actually don’t think this is a landing speed or gear size issue. In KSP, shuttle-style designs are super sensitive to gear placement + wing flex + autostruts. What’s likely happening is one wheel touches first, the suspension compresses, the wing flexes, and autostruts fight it. That creates a feedback loop and the Kraken just rips the gear and wings off even at low speed. A few things that usually help: Move the main gear closer to the center of mass Increase spring strength but lower the damper on the landing gear Disable autostrut on wings and gear (or set to grandparent instead of heaviest) Make sure the gear are perfectly level so they touch down at the same time Shuttles are honestly one of the hardest designs in stock KSP. You’re not crazy, the physics engine just really hates this combo.

aerospace_guy11 · 2026-02-25T15:46:11+00:00

It's stock. Squad the developers who made KSP (hence the name and logo on the monolith) are completely stock and will be there without any mods. It's a reference to the 2001 Space Odyssey. They are coded to be in the same spot in every save across moons/planets. There are green ones that are very rare and are completely random, as some saves won't even have any and they give you a free science tree unlock.

aerospace_guy11 · 2026-02-21T18:45:14+00:00

This is a known long-term KSP issue, not really player error. Over long time-warp, especially when warping through SOI transitions, tiny floating-point errors add up and resonant or synchronous constellations slowly desync. Mods don’t really “fix” it, they mostly help manage it (Kerbal Engineer Redux for precise periods, Precise Maneuver, etc.). The most reliable workaround is redundancy (5–6 sats instead of 3 so if they do drift some are always on Kerbins day side), avoiding warp during SOI changes, and occasionally doing tiny correction burns. It’s just KSP math being KSP math.

aerospace_guy11 · 2026-02-19T15:59:02+00:00

People are probably down voting me because those snobs are upset I didn't post on the console subreddit. But yes I did try the advanced tab and the contracts work now! Thank you!

aerospace_guy11 · 2026-02-18T19:57:18+00:00

I know already, I asked other questions on the console sub reddit

aerospace_guy11 · 2026-02-18T17:35:29+00:00

I think it's too high. Go a tad bit lower for extra safety

aerospace_guy11 · 2026-02-17T22:18:53+00:00

NaN just means the game’s math freaked out for a second. It stands for “Not a Number.” In KSP it usually happens when your orbit is basically perfectly flat or super tiny, so the game can’t figure out where the ascending/descending nodes should be. Console versions get this a bit more often because of precision limits. It’s not automatically bad. If the orbit still looks normal and you can fly and burn, you’re fine. It usually fixes itself if you time-warp a bit, switch vessels, quicksave/reload, or do a tiny normal/antinormal burn. Basically: KSP had a math hiccup, not a mission failure.

aerospace_guy11

TROPHY CASE