Claw

Absolutely, 100% free for you to use. That's gonna be awesome! I saw your other entries and figured you'd get there, given the pace you were putting them out. Pre-Congrats!

@18Watt Hey, this is amazing! So glad you are carrying on this challenge. It was definitely a favorite of mine. Fengist designed the original badges. I think (but can't remember for sure) that the set was incomplete and eventually lost to the sands of the internet. So I used his design as the basis and redid them all, which are the ones currently in use today. Also, I attempted to give definitions to the "stock / stock craft / modded" categories, so I apologize for any ambiguities! I'm also excited to see another Grand Master on the board. I need to go find that entry!

The rule is really about not simply piloting a vehicle in such a way that you bypass much of the challenge/point of doing a terrestrial circumnavigation. With that said, it's hard to know exactly where the line is. Given that it's Gilly, regular contact with the ground, and the speeds you are showing...I would consider it a novel approach to the circumnavigation. So, with the above in mind, I think that it's within the spirit. Also, I'm not sure this approach would be very practical on other bodies, (vs if there was an engine involved, and simply flying/gliding/hovering), so it doesn't seem overly abusive. Definitely cool to see new/novel approaches to a challenge that's been around this long.

I like the open design. Your delivery rocket also looks pretty interesting, especially with the rover sitting on top. ...Gilly ragdoll...the memories! I found on my rover, I ended up disabling the reaction wheel most of the time. I really only kept it on board in case of a crash/flip. Then I would turn it on so I could get back upright. The only place it didn't really work out was on Eevee. I had to beef up the whole design specifically for that mission. I like that we ended up with similar capabilities and overall size, but different looks for our rovers. Kinda cool to see another similar design!

Thanks! I'd be interested in seeing your design as well! I also had a few instances of kerbals running into unpleasant experiences (i.e. turning into spaghetti) if the rover hit the ground too hard. Took some tweaking to find the right height for the seats, but turned out to be a great design in the end.

Nope. But maybe I try to call this other guy (@Vanamonde) and see if he makes it back in time.

Perfectly acceptable. Here was my core design (though it underwent some modifications). There are actually two command seats inside: One for the driver and one for the navigator. Later, I modified it to have command seats in the side pods as well. There were some other...unfortunate incidents...that this rover helped fix. Also note that cores are allowed, it's just that it also needs a kerbal on board.

@minerbat I'm late to the party but yep, that was me. @Thalamask was hot on my heels, but I don't think he completed. I'm not sure if I want to think about or admit to how much time it took. But it's definitely possible (see links to the Grand Elcano mission in my signature, though some of the content is broken due to age). If you have any questions, let me know. Good luck!! Since it's in legacy mode, I guess I can weigh in. The spirit of the challenge was to take a kerbal along with (no drone). And for the player to drive it (not automated). So it wasn't intended that one would simply make a rover, turn on an autopilot, then go to bed. If that makes sense? It's a long, long journey (I know). But that's part of the core of the challenge. Also, there's actually quite a lot to see along the way if you look for it.

A seat would work better than a lander. I would agree with Geonovast in that I doubt Bob would be able to hold on the entire time. It's possible though, so you could always give it a go! What's the worst that could go wrong??

Yes. The parts act like a big tree (as mentioned earlier). If there's a loop, the physics calculations break. Nope. They automatically disconnect with no action needed on your part (which is why I prefer it over the auto-strut, which can sometimes have unintended consequences). Cool. Just wanted to make sure (it's a common thing for people to try and get tripped up on). Glad you're already on top of it! Also, welcome to the forums!

As mentioned, you can't make a "loop" of directly connected parts. Your particular setup is (in my opinion) best fixed by simply using a strut near the bottom of your engine stack. I personally avoid auto-struts for these situations. Just ensure that the decoupler's connection point for the liquid engines is in a good spot for the liquid engines to run (so they aren't wobbly by themselves). Then strut near the bottom of the solid booster. (Pics below) One other thing I see that might be a problem for you. I see some parachutes on your solid boosters which leads me to believe you are planning on separating and recovering them. If you're running without add-ons, you will have a hard time recovering those boosters. The stock game automatically deletes airborne objects below a certain altitude if they are not near your active vessel (the one you are controlling). This is to help reduce the physics burden, but has the side effect of not being able to recover things like boosters with parachutes. If you really want to do this, you either have to stay near the boosters, switch to them and follow them to the ground (which is a problem for your main ship), or use an add-on (there are a couple to chose from).

Stock doesn't have a "dV spent" tracker. The best bet, as suggested, is to know your starting dV and do the math based on what you have left. If it's for efficiency, I assume you're attempting different ascent profiles for launch?

This has been a culprit in the past, especially with laptops. I've also heard it happen with PCs when the fans stop working or the heat sink doesn't have proper thermal putty. (KSP can be rough on processors and graphics cards.) Also, if you updated KSP or your graphics drivers recently, check if KSP is still using the proper video card. Sometimes the nvidia 3D settings lose track. Does this happen with any vessel, or just some particular ones? Also, take a look at the log file and make sure it's not getting spammed with messages. If, for some reason, you have a corrupted ship or part in the save, it can cause excessive log entries which leads to slow performance (because the computer is outputting so much to the log file).

Maybe consider removing that second stage engine and adding just a bit more fuel (to keep the dV about the same). That might also enable you to remove many of the struts, which will slightly improve performance. Additionally, removing an engine could reduce the overall price of the rocket (if you're dealing with funds at all). If it's still a bit flip happy, you could also try putting some fins near the bottom to help improve aerodynamic stability and control (in a manner visually similar to the Saturn V).

You have a lot of mods that I am not familiar with, but something is definitely breaking your camera, and you're getting null reference errors from things affecting the sky (sky color, sun, sun flare, etc). It's unclear from the log what's causing this. The nearest thing to the big list of errors is Hangar Extender, but that may or may not be the core of the issue. Right before the issues appear, it seems your ship undergoes an explosion, then you revert to prelaunch, then you go back to the editor. Is that what happened? ... Does this same camera issue come up if your ship does NOT explode? (i.e. can you revert or leave with no issue, assuming nothing catastrophic?) Unless someone else comes along and knows right off what the issue is, I recommend removing some of your mods (maybe half) and trying the same scenario that causes the problem in order to narrow down the issue. - If the problem still happens, start removing some mods until it stops. - If the problem isn't happening, then start adding some mods until it happens. Once you find the mod, then you can try asking for help in the mod's specific thread. Hopefully someone can come along and give you a more direct "mod x is incompatible with mod y" answer soon. Good luck!