Jump to content

MrSystems

Members
  • Content Count

    64
  • Joined

  • Last visited

Community Reputation

54 Excellent

About MrSystems

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good advice above ^. And if you're concerned about not finding enough in time (because they're too rare or whatever), you can launch multiple craft that all meet the criteria. Each telescope only finds objects relatively nearby, but you can for instance have 4 Sentinels 1/4 of an orbit apart (use the same flight plan but launch 1/4 of a Kerbin year apart) to 4-tuple your chances.
  2. Once you're settled in to a circular orbit at the correct altitude, you can enter into an elliptical orbit, having its periapsis at the altitude and latitude needed for the survey, with a period such that you'll be in the correct spot next orbit. Say for example the measurement needs to happen at 100°W longitude, 20°S latitude. You notice this orbit that you're crossing 20°S latitude at 0° longitude. So you know Kerbin needs to rotate 100° in the time it takes you to complete some whole number of orbits. As the commenters above said, Kerbin rotates at 1°/min, so you need to complete
  3. The easy (and fuel-inefficient) way that @king of nowhere was talking about: Get to circular Kerbin orbit. Click Minmus and Set Target. Look for the AN / DN (Ascending/Descending Node) markers on your current orbit, and set a Antinormal/Normal maneuver node there such that the AN/DN readout shows 0.0°. It should be about ±230 m/s dV, depending on the height of your orbit and how close to equatorial it is. Burn that node. You're now in the same orbital plane as Minmus. Aim ahead of the planet and set a node (about 920-925 m/s dV) the same way you would do for the M
  4. I wrote some code in kOS a while back to do the flying to orbit, so I have a consistent basis for experimentation as to how to get to orbit cheapest. You could do some experimentation yourself in MechJeb. I have three different rocket profiles: Boosters + LFE at liftoff, separate trans-orbital stage Boosters + LFE at liftoff, no separate trans-orbital stage Boosters only at liftoff, LFE stage, trans-orbital stage Of those, for most rockets #1 is least expensive. #2 is good for a bulky, draggy payload where much thrust is necessary to gain the first 20km altitude (but
  5. Here's another possibility: try rotating the Bobcat 90°. It has some pretty intense thrust vectoring, but only along one axis. Right now it's vectoring on the North-South axis, and it might help to have it on the East-West axis instead. (You could also, instead of rotating it, try turning the Gimbal setting down a bit and see if that helps.) A third option is to install Kerbal Joint Reinforcement.
  6. Thanks for that idea! I couldn't find any mods that do it for a KSP version newer than 0.25, but I did find this thread that has the config needed to add it to a part myself. The only question is, what part should I add it to? The klaw? I'll have to think about it.
  7. My method relies on some readouts from Kerbal Engineer. Among other information, it can give the time to impact, the current acceleration of your craft, the surface gravity of the body, and display a red circle where your craft will impact the surface. From a circular orbit, I decelerate about 1/4 of the way around the body so that the red impact circle is just past my intended landing point. I check my craft's acceleration (for this example let's say it's 10.0 m/s²) and the body's delta-v from surface to low orbit listed on the Subway Map (for this example, we'll use the Mun's val
  8. Limited to 0, though? And the science in the stock game is infinite thanks to contracts and the Mobile Processing Lab. In fact, with the MPL (or a bunch of them on separate craft, rather) you could unlock the entire tech tree without ever leaving Kerbin's SOI.
  9. This is an interesting challenge. I play nearly this way anyway, as I find it a pain to leave Kerbin's SOI without parts from late in the tech tree. Using data from the Wiki, and ignoring any science gained from recovered ships, contracts, Achievements, anomalies, and KSC "mini-biomes", I calculate there are 21,937 science points to be earned doing stock experiments at Kerbin, Mun, and Minmus. 18,468 are needed to unlock the tech tree, Thus, completing this challenge efficiently is a matter of ignoring the most obnoxious 3,469 points. 1,161 points come from being landed or flying at
  10. Usually the first Kerbol SOI craft I launch in a new game are relays 1/3 of an orbit ahead of and behind Kerbin, at Kerbin's approximate SMA. You can fit them with Infrared Telescopes to scan for asteroids while you're at it.
  11. I just intercepted my first comet, with a craft fitted with all the stock and DMagic Orbital science parts that can do science on asteroids. Not a single one of them would do science on the comet. I get that DMagic might not have been updated yet, but I was surprised that none of the stock science parts were comet-aware. Aside sending a crewed vessel to take a surface sample, is there any way to get science from a comet?
  12. It might be your save--pressure limits are an option that defaults to off. Open your save with a text editor, and look about 200 lines in, under AdvancedParams. Here's how one of mine looks: AdvancedParams { EnableKerbalExperience = True ImmediateLevelUp = True AllowNegativeCurrency = False PressurePartLimits = False <!-- from this line --> GPartLimits = False GKerbalLimits = False <!-- to this line --> KerbalGToleranceMult = 1 ResourceTransferObeyCrossfeed = False ActionGroupsAlways = True BuildingImpactDamageMult = 0.05 Pa
  13. I was also having an issue with my solar panels not charging. Even the stock OX-STAT, when manually pointed directly at Kerbol in the stock solar system, did not charge. Installing Kopernicus 1.7.3, released yesterday, did not fix the issue. In the file Kopernicus\Config\SolarPanels.cfg is the following note: // This will replace all instances of ModuleDeployableSolarPanel with the Kopernicus version // that has proper support for multiple lightsources // // If you want to keep your ModuleDeployableSolarPanel, add "useKopernicusSolarPanels = false" to the MODULE node
  14. The Training mission Asteroid Redirect Part 1 provides assistance with some of these concepts.
×
×
  • Create New...