• Content Count

  • Joined

  • Last visited

Everything posted by FloppyRocket

  1. Your side boosters were deleted as sub-orbital debris. Only craft that you're flying are persistent.
  2. Is it normal that I cannot restore a previous save during the Munar 1 mission? This image is from right after I crashed again, but even before crashing, I could not go back to a previous save. I keep crashing on launching from the Mun, and can't restore from my in-orbit quick save. I can save the game as much as I like, but there is no load button. I"m pretty sure I was able to save and restore during some of the other Making History missions. But not this one. I am puzzled. Thanks for any clues.
  3. Specifically, place a fuel duct between the side of the tank and the inside floor of the SM25. That will connect the fuel flow to the engine.
  4. Is there any conflict between having ForScience and [x] Science! both installed and active at the same time?
  5. In my limited experience, automatic fuel flow for asparagus staging can be a real beast to set up, because it only works if you DON'T use symmetry when you originally added the tanks and engines. The fuel duct parts are a reliable means around this problem.
  6. @GRS, no updates from me, the remainder of this challenge is beyond the combination of my skills and how much time / effort I'm willing to invest in it.
  7. The game does its best to tell you what it thinks you want to know. It isn't always right.
  8. I never claimed it was efficient ("typical" was the word I used), and I also said said that there are infinite possibilities. I wasn't the one asking the question on this thread, just trying to be helpful. Needless badgering is one of the reasons that people avoid posting on the forums.
  9. Just getting above 70 km isn't sufficient information - how fast do you want to be going when you reach 70km? The rule of thumb is that you need 3400 m/s to get into low Kerbin orbit (80 km). A typical launch might use 2400 m/s to get an Ap of 80km, then a 1000 m/s circularization burn. There are an infinite number of variations possible.
  10. Do any of your probe cores have a built-in antenna? If not, did you add any antennas?
  11. @Xt007, you quoted my message, but didn't add any reply. Notepad++ here also. I don't use it as an IDE, but it is a very good code editor.
  12. I haven't been actively investigating this. Early on I tried some simple experiments to duplicate the issue from the original topic (i.e. sudden shifts away from the intended pitch curve), but I wasn't able to observe any abrupt departures from the planned pitch. The only curious thing I observed was that the rocket I designed also had pitch control saturation, but I chalked that up to the pitch curve being aerodynamically difficult for my specific rocket design to fly. I have seen PID integral windup before professionally. It was not a happy experience.
  13. The thing you don't need is the 3400 m/s that got you into Kerbin orbit. You dispel the equivalent energy in the atmosphere when you re-enter.
  14. Note that the delta-v numbers in the chart are all vacuum delta-v, not the atmospheric delta-v you'll see by default in the VAB. You'll need to adjust the setting in the VAB's DV menu so that is shows vacuum delta-v as you design your rocket.
  15. You're going to intercept the Sun any time you leave the Kerbin SOI. No plan is needed.
  16. @GRS No questions from me, I'm just not working on this project at the moment. I'm writing a kOS autopilot script for sending unmanned probes to Minmus.
  17. Topic: How to traverse the list of orbit patches in a maneuver, without just using a huge set of if-statements. I did a few searches and couldn't find this topic, sorry if it is a duplicate. I'm trying to write a kOS script (based on the "cheerskevin" youtube series) that will auto-launch from Kerbin to a hoverslam landing on Minmus. This is his video series that uses a ternary search to find the time when the current trajectory will have the minimum distance to the Mun. I'm expanding the script so it can auto-land on Minmus instead. Obviously, the Mun occasionally gets in the way, so the trajectory planner has to cope with the maneuver having multiple orbit patches. Sometimes these Mun encounters provide a nice gravity assist, so that's handy. But my code has a problem. Is there a way to artfully traverse the list of patches within a maneuver node, so that I can find the right patch on which to base the "proximity to Minmus" calculations? I tried this sort of program flow (just pseudocode) if maneuver:orbit:hasNextPatch { set orb to orbit:nextPatch } ...within a loop, trying to find a patch that applies to Minmus, or stop when it finds that hasNextPatch is false,. But the assignment of "set orb to ..." doesn't seem to work. I got an infinite loop with every patch belonging to Kerbin. Update: Aha. I think I found the problem - I was stupidly using the variable 'obt" for my local orbit, but "obt" is a reserved keyword for "orbit". That might have been monkeying up the works. This seems to get the job done: // note: 'm' is the current maneuver node set orb to m:orbit. // traverse the list of patches until not orb:hasnextpatch { print "Body:" + orb:body. print "ecc :" + orb:eccentricity. print "Per :" + orb:periapsis. set orb to orb:nextpatch. } print "Final patch: Body " + orb:body. I'll leave this post here in case others find it useful. The basic task is to traverse all the patches from a single maneuver that causes a trajectory that starts in the Kerbin SOI, flies into the Mun SOI, then back into the Kerbin SOI, then into the Minmus SOI. That's four patches, all triggered by one Maneuver. - Tom
  18. Thanks for the suggestion. I've gone idle on this project, as I'm at a low of enthusiasm for the amount of effort required for the Eve and Jool missions.
  19. Thanks, that's what I was missing. Thanks, that's what I was missing. I am able to view the video from May 21 now.
  20. I'm just seeing "An error occurred" when I try to play the video.
  21. Re: "disabling the reaction wheels': Maybe set the Wheel Authority to zero? And then add some RCS thrusters to get pointing control for the circularization burn.