Pol is Bugged?

[Draconiator]

I wanted to do a mission to the Joolian system this morning, so I designed an ion probe to head up there. When I got there I first orbited Laythe, flew by Vall on the way to Pol. But when I got there, the game refused to save in orbit, I successfully landed the probe and it failed to save on the surface. Returned to a 10KM orbit ans STILL refused to save. so I exited anyway hoping it somehow would save anyway. When I got back, the probe was WELL out of Pol orbit, and 1/4 of the way to Bop orbit, so I scrubbed that one.

One other time in 0.90, I went up there, only for the game to crash on me when I got there. Weird o_O

[LordFerret]

I wanted to do a mission to the Joolian system this morning, so I designed an ion probe to head up there. When I got there I first orbited Laythe, flew by Vall on the way to Pol. But when I got there, the game refused to save in orbit, I successfully landed the probe and it failed to save on the surface. Returned to a 10KM orbit ans STILL refused to save. so I exited anyway hoping it somehow would save anyway. When I got back, the probe was WELL out of Pol orbit, and 1/4 of the way to Bop orbit, so I scrubbed that one.

One other time in 0.90, I went up there, only for the game to crash on me when I got there. Weird o_O

I have wondered likewise of Moho, where in v0.90 my SCANsat probe disappeared into never-never-land before completing its scans. A few here in the forums had mentioned that orbits about Moho can be 'wonky'. I'll find out soon enough if the same is true in v1.0.2, as I'm preparing another SCANsat mission there soon (right after I'm done with Eve and Gilly). I'll note that when I did a SCANsat mission for Pol in v0.90, I had no problems holding orbits of 250km and 750km the duration of the lo-res and hi-res scanning. The vessel for that mission was, also, an Ion probe.

[NoPanShabuShabu]

That inability to save is the game getting ready to crash. There's nothing buggy about any particular world other than bugs and glitches which could occur anywhere.

[Mr. Scruffy]

Well, that´s an awesome way of getting ready to crash.

"You´ll know when the engines are gonna fail, when the emergency signal wont allow you to activate it anymore, cap!"

[Geschosskopf]

That inability to save is the game getting ready to crash. There's nothing buggy about any particular world other than bugs and glitches which could occur anywhere.

Agreed on the "game about to crash" thing. However, Pol is definitely bugged in other ways. The main problem is that the visible surface mesh and the invisible surface collider do not correspond, and the error in the surface collider is on the high side. Thus, as you're coming down for a landing and every instrument as well as your eyes are telling you you're still like anywhere from a few hundred to 1500m above the ground and thus going rather fast, BOOM!, and the F3 post mortem says you collided with Pol. Or, if you're coming down very slowly and cautiously, you can actually land safely on the invisible collider well above the visible ground. This bug seems concentrated in areas near the taller mountains so it's best to land in the more open regions.

This particular bug isn't unique to Pol. It happens in a couple of isolated spots on Bop and Gilly as well. So, it's a "feature" any small, irregularly shaped bodies. But it's so bad on Pol that I just don't go there unless I absolutely have to, and then I only send probes.

[Sattorin]

The main problem is that the visible surface mesh and the invisible surface collider do not correspond, and the error in the surface collider is on the high side. Thus, as you're coming down for a landing and every instrument as well as your eyes are telling you you're still like anywhere from a few hundred to 1500m above the ground and thus going rather fast, BOOM!

Can confirm, did boom.

[moogoob]

Agreed on the "game about to crash" thing. However, Pol is definitely bugged in other ways. The main problem is that the visible surface mesh and the invisible surface collider do not correspond, and the error in the surface collider is on the high side. Thus, as you're coming down for a landing and every instrument as well as your eyes are telling you you're still like anywhere from a few hundred to 1500m above the ground and thus going rather fast, BOOM!, and the F3 post mortem says you collided with Pol. Or, if you're coming down very slowly and cautiously, you can actually land safely on the invisible collider well above the visible ground. This bug seems concentrated in areas near the taller mountains so it's best to land in the more open regions.

This particular bug isn't unique to Pol. It happens in a couple of isolated spots on Bop and Gilly as well. So, it's a "feature" any small, irregularly shaped bodies. But it's so bad on Pol that I just don't go there unless I absolutely have to, and then I only send probes.

Planning my first post-1.0 Jool mission and was hoping to use Pol as a fuel mining depot (as ore is easier to lift from low-gravity bodies, of course). I'll have to keep this bug in mind.

[LordFerret]

Agreed on the "game about to crash" thing. However, Pol is definitely bugged in other ways. The main problem is that the visible surface mesh and the invisible surface collider do not correspond, and the error in the surface collider is on the high side. Thus, as you're coming down for a landing and every instrument as well as your eyes are telling you you're still like anywhere from a few hundred to 1500m above the ground and thus going rather fast, BOOM!, and the F3 post mortem says you collided with Pol. Or, if you're coming down very slowly and cautiously, you can actually land safely on the invisible collider well above the visible ground. This bug seems concentrated in areas near the taller mountains so it's best to land in the more open regions.

This particular bug isn't unique to Pol. It happens in a couple of isolated spots on Bop and Gilly as well. So, it's a "feature" any small, irregularly shaped bodies. But it's so bad on Pol that I just don't go there unless I absolutely have to, and then I only send probes.

Does this apply to v1.0.2 or previous versions?

[Geschosskopf]

Planning my first post-1.0 Jool mission and was hoping to use Pol as a fuel mining depot (as ore is easier to lift from low-gravity bodies, of course). I'll have to keep this bug in mind.

Vall is actually the best place to mine in the Jool system. It's gravity isn't huge and it's conveniently located next door to and coplane with Laythe, which will surely be the main focus of any Jool expedition. Sure, Vall's got more gravity than Pol but, due to the distance and inclination changes travelling to and from Pol, you actually have more efficiency (and less time wasted) using Vall. Plus, of course, Pol is horribly bugged while Vall has an interesting anomaly to investigate.

Does this apply to v1.0.2 or previous versions?

I can't say from personal experience but I've seen several posts lately talking about Pol's collider bug, so I'm sure it's still there. Nothing in the change log says Pol got any love, either.

[Randazzo]

I can't say from personal experience but I've seen several posts lately talking about Pol's collider bug, so I'm sure it's still there. Nothing in the change log says Pol got any love, either.

Pol murdered Jebediah and Bill at 1500m. Not only that, any contract to be complete in Pol local space never registers as being completed. IE, the Explore Pol contract could not be completed because despite orbiting, collecting science, then landing (after dying) and then returning to Kerbin resulted only in completing the surface objectives. Fly-by Pol missions won't complete either.

[gogozerg]

Last time I left Pol, I had a weird bug. On the map, Pol wasn't on its own orbit!

[Andrewx21]

Pol is home to the craken, what do you expect.....

[Geschosskopf]

Pol is home to the craken, what do you expect.....

The Kraken (aka Cthulhu) actually lives on Bop. Pol is the unholy spawn of the Daemon Sultan Azathoth

[Windspren]

This probably has something to do with when they fixed the flagPOLe bug in 1.0