Jools moon Pol broken?

[Bunny Commander]

I went to land on Pol and 3 times Ive tried to land and when i get close to land my ship just explodes. I havent touched the ground and im going less than 20 m/s.

Is anyone else having this problem?

[astropapi1]

Less than 20 m/s? xD

Try going under 5 m/s at least.

[Aphox]

im going less than 20 m/s.

Uhh, yeah, anything over around 5m/s is pretty excessive speed when it comes to landing spacecraft that are carrying immense amounts of highly flammable chemicals. I've had parts destroyed going slower than that. Try slowing down a bit. Come back and let us know if it keeps happening, though.

For reference, 20m/s is around 45mph or 72km/h. You say you're going less than that, but that's just a comparison. Smashing into a moon at 45mph is bound to cause some problems

Edited September 28, 2013 by Aphox

[Keldor]

Note the part about "haven't touched the ground yet".

I had a problem with a kerbal randomly popping while jetpacking around on Pol. He was about 30 feet up in the air at the time.

[Galacticruler]

Note the part about "haven't touched the ground yet".

I had a problem with a kerbal randomly popping while jetpacking around on Pol. He was about 30 feet up in the air at the time.

Don't tease the Kraken, it hates it.

A Kraken attack can attract a Space-Rhinoceros.

[Kasuha]

I visited Bop today and its real surface is significant distance above its map surface. After I landed and then zoomed out at maximum, I could watch how the whole moon inflates/deflates as I step over the resolution limit showing me map surface or real surface.

http://imgur.com/a/klktD#1

Maybe Pol has similar problem?

[lajoswinkler]

Interesting, I've had some problems with Gilly recently. Every time I'd enter its sphere of influence and switched to live mode, framerate would drop below 1.

It was not until I've dipped below 20km or so before it went back to normal again.

Every now and then people have weird problems with small moons. I wonder why.

Bop indeed has problems with surface height. Even if you land on the lowest region, you're still kilometres above the zero height, which is not how height should be calculated.

Zero height on a planet without oceans would be the point where the whole planet is molten and it settles in a sphere, that is, the average height.

Edited September 28, 2013 by lajoswinkler

[Captain Sierra]

Interesting, I've had some problems with Gilly recently. Every time I'd enter its sphere of influence and switched to live mode, framerate would drop below 1.

It was not until I've dipped below 20km or so before it went back to normal again.

Every now and then people have weird problems with small moons. I wonder why.

Bop indeed has problems with surface height. Even if you land on the lowest region, you're still kilometres above the zero height, which is not how height should be calculated.

Zero height on a planet without oceans would be the point where the whole planet is molten and it settles in a sphere, that is, the average height.

Not technically correct. the zero height is the lowest point on the planet, assuming it has no oceans. Your solution would make the plains of minmus be negative altitude.

[lajoswinkler]

Not technically correct. the zero height is the lowest point on the planet, assuming it has no oceans. Your solution would make the plains of minmus be negative altitude.

Well that would be called geological depressions, wouldn't they? I honestly don't know anymore, my geography was a long time ago.

[Fooblack]

For a pilot landing on the ground of a world, the only number they want to know is exactly how far away the landing gear is vertically from the closest bit of dirt, whether it matches the geologically correct altitude reading or not. The in game altimeter currently isn't reliable for that because it's designed mainly to be useful for flying and orbiting. We need a laser rangefinder part or something. For example have it switched on when fine-control mode is activated. In this way it would also be a benefit in docking.

[-Velocity-]

YES! I was just landing on Pol the other day, and high above the surface, while travelling slowly, my lander's cabin randomly exploded. I checked the flight log, it said that the cabin collided with the surface of Pol- and yet, I was 1000 meters above the surface!

So yes, there are some bugs. Anyway, I landed three other times, no issues, it was just one time that this happened. Just use quicksave a lot, and also, just make occasional backups of your entire career folder. The save system of KSP is bull$@##, what with all the Kraken bugs that like to randomly destroy my spacecraft, we REQUIRE the ability to make multiple, NAMED SAVE FILES for the LOVE OF GOD. There's a reason most games use autosave, quicksave, AND named saves.

Edited September 29, 2013 by |Velocity|

[-Velocity-]

For a pilot landing on the ground of a world, the only number they want to know is exactly how far away the landing gear is vertically from the closest bit of dirt, whether it matches the geologically correct altitude reading or not. The in game altimeter currently isn't reliable for that because it's designed mainly to be useful for flying and orbiting. We need a laser rangefinder part or something. For example have it switched on when fine-control mode is activated. In this way it would also be a benefit in docking.

The lander cabins have a radar altimeter inside them. When I'm feeling adventurous, I land a lander entirely from within the cockpit using the vertical velocity indicators, ball, and radar altimeter.

But yea, we need it available in the flight UI too.

[Bunny Commander]

Okay I guess i was just unlucky. too bad its not liek i spent my entire day trying to get there or anything xD.