Deutherius

Granted. It's a lot slower than using an axe. It also hurts like hell. I wish to have a space suit.

Not exactly about KSP, but it applies here as well: "Anything with a big enough engine will fly - no matter how badly."

...a headache? (Like the one I have trying to figure this out)

You get a copilot to sine with you. What babe do you remind me of?

Neighbors

Yeah, no, sorry. Goldenpeach?

I positively guarantee - zenith truss has, verily, exploded. retjhjgv

Granted. One idiot didn't know it cannot be detonated and managed to detonate it. And of course, you were standing right next to the bomb when it happened. I wish for peace on Earth.

guss what 0

The pic in OP is from my submission to the Chunkin' Challenge, so I tried a few things. I think I got something. You can work out the distance from the f3 menu, but it's horribly inconsistent. The launcher is bolted in place, so moving shouldn't be much of an issue. It wobbles a bit, but doesn't bend or go anywhere. Launch procedure used was just: full throttle, stage and switch to the now accelerating payload. Payload always exploded on impact, no bouncing was recorded. Conclusion - At first I thought the F3 menu divided the distance based on how many times your craft has "divided" (be it by decouplers or explosions) - That would explain the inconsistency on payload impact (based on the angle when hitting the ground - sometimes exploding all at once, sometimes hurling parts a little further). However, using a payload consisting of 1 part gave me the same funky results (and I've tried multiple times) - the launcher itself was still complete, nothing fell off or exploded there. Anyway, based on my tests and my launcher design, the gound distance covered seems to be divided either by 2 (in one case), or by 4 (in a majority of cases). I wouldn't trust either. Other than that, I have absolutely no idea what is going on.

That sounds like a challenge But honestly, I would just follow Slashy's advice - even if you do attempt to complete the contract, just wait until you have the funds and tech. The deadline is well over 14 years - you can easily max the tech tree in just a weeks of in-game time and the travel time shouldn't be more than 2 years. The target orbit is also very eccentric, so you can send your probe to target Ap, reverse the orbit and from there it's just a few m/s of deltaV to complete the contract. Good luck!

The real question is, can you really get those speeds just by using rover wheels and/or Gilly's gravity? I haven't done any calculations, but something tells me you'd need a seriously high and seriously smooth mountain... The highest elevation difference I was able to find on Gilly is about 3 km, but the slope is pretty damn bumpy.

0 because I do

You can edit your original post (make sure to "go advanced") and set the prefix to "answered"

Well then... Since going for distance is obviously meaningless, lets go for altitude. Same device, same division, different angle.

Alright, I have a quick submission for the "air" cannon division. Just one thing I don't understand - how can the ground distance covered be so small? The payload was obviously delivered over 1.8 km away.

0 because balance

...or not. 0

Granted. Squadcast was not cancelled, but it was announced KSP is stopping development. (And licencing prevents anyone from continuing independently) I wish to visit ISS.

Presume our posts were errorneous. We can ignore them. But then the number sequence would look like: Arugela: -2 Arugela: -3 Arugela: -4 ...which is against the rules. You gotta let others add/subtract before adding/subtracting again It should therefore still be at either -2 or 0. Or whatever, it's just a game

(I lold) Most years, vandals just zone back cunning quarks. kgfwehgn

I'm sorry, but even if Dman's post didn't count, you can't keep subtracting by yourself It's either -2 or 0

0, lets keep it nice and balanced

-1, tower clear

That felt more satisfying than it probably should have. Cue instant replay: 1, Prepare to release launch clamps!