N4CDLAW

Hm, could have sworn what you say used to be the case for me. Stepped away from KSP for a while and on return now I must hold ctrl as well. Steam or mod thing, maybe? Edit: got curious and looked into it, I need to use ctrl because I'm running a GeForce GPU and its native software co-opts the alt f12 function. In debug (however you get into it, Google if unsure), click 'cheats' on the left. At the top is a slider and a box marked "hack gravity". Check the box and run the slider to the left, you will be in almost zero G and should be able to wiggle the ship hard enough to bounce it off the ground and float off. Play with your ship a while, then when happy, uncheck "hack gravity" the box again to return to normal.

If you want to cheat your way around tipping, as long as you have SOME RCS or reaction wheels you can hack gravity to nil to correct orientation. Ctrl Alt F12 for the debug menu.

I have a refinery in Mun orbit I use to refuel interplanetary missions. Refinery has a 55k equatorial orbit, I think. That altitude is mostly based on now-obsolete rules for how fast you can time warp based on altitude, but it works well enough I still use it. Once I undock, set a maneuver node with rough prograde dV, zoom out to Kerbin system view, advance node orbit so that you're leaving the Mun when Mun is in best position (between Kerbin and sun for inner planets, opposite side of Kerbin for outer), then tweak position on that orbit to start burn from to adjust departure trajectory. Tweak dV variables and exact burn time to get planetary intercept. I've done this for every planetary body in the game. I have done this from Minmus orbit and the orbital period was just too great to nail launch windows. Inclination didn't help, either. Mun orbit is perfect, haven't noticed any problems even with narrow launch windows (looking at you, Moho). Hope this helps.

I thought so. Been a while, but it definitely is an anomaly that registers via Kerbnet. Course, now that I think about it, the comm dishes on Kerbin show up too but I've never gotten an achievement for that either... now I'm 2nd guessing.

Having an issue and cannot find anyone else with the same problem. I started a large career game a while back with a goal to fully explore the Kerbal system. All surface anomalies explored, all biomes and artifacts mined for full science. The problem is that I'm having recurring issues getting the game to recognize that I've gotten close enough to an anomaly for the achievement to pop. I planted a flag on top of a Moho Monolith and never got the achievement notice. Now I've just had the same problem exploring the Mohole: circumnavigated the rim, then saved and jumped in: achievement never popped up to the second I smashed into the bottom of the hole. This has happened before on other bodies but I'm sometimes unsure if the achievement is triggering and I'm just missing it. Been watching the screen carefully as I explore Moho and convinced it's just not happening. Theories I think I've ruled out: I am using the Bon Voyage rover mod to explore the surface. It's basically a rover autopilot that will move across the surface while you're off doing something else. I discovered some time ago that you must cross a certain threshold in order for the game to recognize the achievement, so if you just Bon Voyage to the anomaly it will not trigger until you drive away and return across the threshold. I address this by manually driving in from about 3 km out and have had this work, but repeated attempts to drive 3k away and return have been unsuccessful at times. I have wondered if physics warping while manually driving my rover will allow the craft to skip past this threshold and not trigger the achievement. Not certain, but it seems like I've had this happen in the past and solved it by driving in real time. Haven't used any warping within 3k of the anomaly and it's still not popping. Potential factors: I am running V1.7.2 because that was current when I started this career. Don't want updates to break my ships, especially the ones I spent forever designing and testing to explore Eve. Possibly something more recent had addressed a cause of my issue? Other mods besides Bon Voyage wouldn't seem a factor to me, but are: Kerbal Alarm Clock, Kerbal Engineer, For Science, Hyperedit, Transfer Window Planner, USI Life Support, EVE, Precise Maneuver, and Trajectories. The only non-stock parts on the rover in question are from Bon Voyage and USI LS. Thoughts? The lack of achievements isn't breaking the game, but it's annoying because the whole point of the career is to thoroughly explore, so it'd be nice if the game recognized it. I plant flags at every discovery to track my progress, but and still annoyed driving around for hours of real time trying to get achievements to pop with no dice. Thanks for reading and any assistance.

The Trajectories mod does this, though it's not that mod's primary purpose.

Wish I had screenshots (didn't take them at all locations, lost those being a little hasty with a Windows reinstall), but most ambitious (successful) mission was to plant a flag on every body in the game and return the Kerbals safely. Currently working on another repeat of that task with USI life support active. If all goes well I may try again in a no save/no revert game. Eve itself was the lion's share of that mission. Walked around grinning for the rest of the day after successfully re orbiting Eve. Also needed a Moho rescue mission and Tylo was dicey enough I'm not sure I could take the same ships and repeat the accomplishment.

Yup. Got a piece of paper taped to the monitor so I don't forget. Backspace: 1) toggle ISP engines 2) toggle TWR engines 3) toggle all engines 4) deploy comms and/or ladders 5) Kerbnet 6) Activate life support (for USI LS mod) 7) Mission specific 1 8) Mission specific 2 9) toggle thermal radiators 0) toggle solar panels

I usually name with <destination> <role> and go from there with a series of applicable suffixes. Manned crafts may be Orbiter, Transport (Kerbal capacity), Refinery, Launcher (usually cargo of some sort), Miner, Rover, Explorer (full sci array), Lander, Hopper (lander designed for multiple landings on same low-gravity body), SSTO, etc. Probes are usually 1 way named for their destination and Comsat (signal relays), Survey, or Surface Probe. Suffixes I may add are (LR) Long Range, or an extended dV version of another ship, (NS) for non-solar electrical generation, (At) for having components requiring an atmosphere to work, (Vac) for landers designed for vacuum worlds, or (LFO) for liquid fuel only: no need for oxidizer. I also have some ships that include the word Double or Triple to denote multiple probes built into a single launcher. Usually a surface probe with detachable Survey or Comsats. So I end up with crafts like my "Explorer Lander (NS)(ISRU)" that can gather sci data from every moon of Jool, "Ike Survey Comsat", and "Pol Refinery (NS)"

Crud, that's what I missed. Electric charge I have, and there was still an issue with the first rover I sent since that craft had good comms, but the test craft I rebuilt from the ground up for troubleshooting has no comms and adding a dish fixed the problem. Thanks for your input, folks.

Nope, I was hyperediting above the surface to test 'chutes as well.

Would like to run an issue by the forum because I'm scratching my head trying to figure out what I'm missing. I am attempting to build a large rover I can land on Eve to support crewed missions there, but I'm getting no response out of my rover wheels once I land test rovers. I have a lighter rover that functions fine. Problem Rover Older design that works fine. Essentially, I'm building a large rover which originally had 2 pair of RoveMax XL3s. Rover drove fine on Kerbin, so I hyperedited it onto the surface of Eve and have no indication that the wheels are even registering my keystrokes. Here's the problems I've noticed: No directional keys seem to have any effect, though I can apply and remove the brakes with effect on downhill rolling. With wheel menu open, 'Motor' readout always reads 0 regardless of directional keystrokes, whereas on Kerbin this is not the case. Vernor RCS engines didn't seem to activate, having no visible plume during attempted use. Unsure if that's a factor of Eve's atmosphere, never noticed it before. Things I've done to troubleshoot: Tried with another lighter rover design I've used before built on 3 sets of TR-2L Ruggedized wheels. Works fine. Tried hacking gravity on Kerbin to see if wheels just aren't strong enough. I can break the wheels but cannot replicate the problem on Kerbin. Tried hacking gravity on Eve to no effect, even when floating away the wheels didn't appear to turn. Tried increasing to 6 pair of XL3 wheels to no effect on Kerbin or Eve. Tried replacing with 6 pair of TR-2L wheels just to see if I could see the wheel turn animation (since the XL3s don't ever do that), and they visually turn on Kerbin but won't move on Eve. Tried hyperediting back to Kerbin in case hyperediting was breaking the wheels, but rover worked fine as soon as I returned to Kerbin. Ensured wheels were powered and brakes off during every attempt. Anyone have any ideas? Thanks in advance.

I am wondering if a mod exists or could exist that would let me experiment with redesigning the career mode tech tree. I've seen the mods that redesign it, but I'd like to play around with different ways to progress through the tech.

A recent tourist wanted to pay me to make him pass out from a high G adventure. His name was Barfrid.

I used to use Minmus for my refueling needs, with the refinery and fuel storage in orbit and the miner and ore storage on a lander. It worked and was the most resource efficient option. However, in more recent games I've switched to the Mun for a few reasons: 1) Much easier to hit transfer windows from Mun orbit when doing interplanetary missions after refueling. This was my main reason to switch. 2) Less in-game time for when said transfer window sorta snuck up on me. 3) Mun generally has better ore concentrations, so less in-game time mining. 4) Started using a fuel depot in low Kerbin orbit when getting into reusable space planes, The mining lander I'd designed had a hard time achieving a 100k orbit over Kerbin when I chose to deliver ore from Minmus to the fuel depot there, it just didn't have the delta-V. Worked fine from the Mun, though. 5) Routine landings on the Mun prepared my "flying insticts" for interplanetary visits better than Minmus. I'd gotten to accustom to Minmus' "barely there" gravity and low delta-V landings and was getting into trouble during other landings when I stopped paying attention. Either way works, but in the end, Minmus was better because it saved resources; but those resources were free anyway, so... I prefer the Mun.