Jump to content


  • Posts

  • Joined

  • Last visited


461 Excellent


Profile Information

  • About me
    Spam in a Can
  • Location
    USA, Florida, Space Coast

Recent Profile Visitors

5,846 profile views
  1. I think we're already collaborating pretty well. If you like the FP interface, you can have it call K2D2 behind the scenes to execute nodes for you, and if you prefer the K2D2 interface it can call FP for you, so you really only need one or the other on your screen at any time.
  2. Release 0.10.6Updated for compatibility with latest K2D2 version Download on SpaceDock
  3. You probably set the altitude you want to finish at to be lower. Go to the config settings for Lift (gear icon) and set the altitude to finish at to be something higher that's outside the atmo for Kerbin.
  4. I think that @cfloutier has a bunch of plans for future K2D2 improvements, but right now he's pretty busy with an overhaul of the UI. One of the things that he and I have talked about a little is improvement in the landing autopilot. My thought is to have FP offer a deorbit burn node that would put you on a collision course to a waypoint or lat/lon surface coordinates, and then for K2D2 to do something with the waypoint or lat/lon to try to bring the landing down more precisely to those coordinates. I don't know if cfloutier might have any thoughts on how to handle staging on the way down. My approach has personally been along these lines. If I've got a transfer stage with some fuel in it and would like to spare the fuel cost on my descent and landing stage then I may do the deorbit burn with that stage to get my craft headed toward the surface, then stage and turn things over to K2D2 for the remainder. One problem I would see is that the K2D2 landing autopilot is probably making calculations for when to turn the engine on and how long to burn based on the TWR of the current engine. If you start down with one engine, then jettison that once it's done, you would at best need K2D2 to recalculate for the performance of the new engine - and you could very easily get into a situation where you've not got enough time left to land safely with the second engine. So, it's not that easy of a problem, and the much easier thing is to make sure you're on your descent and landing engine well before you're close to the surface so that K2D2 can do its thing based on that engine. Similarly, for ascent (lift), staging can be tricky if what you want is to insert a delay between stages. Here, I think the problem is that there is both a time component (how long a delay you want), as well as the many variables of design. It would be a very tall order to ask K2D2 to assess your particular rocket design and make some choices based on that. As for using the lift curve, I'd need a bit more info to offer any advice. I've found it easy to use, but then I've been using it for a long time. If it's not doing what you're expecting then it may be that you're not fully understanding how to use it - which is something that I think can be helped.
  5. Release 1.2.1Added check to prevent the mod UI from being toggleable while the game's UI is hidden (F2). This should help to prevent situations where the mod's UI is inadvertently raised while the game's UI is hidden which can result in the mod's UI only being visible when the game's UI is hidden and vice versa.Download on SpaceDock
  6. I've confirmed that this state can be entered. One way I've found to enter it is to hide the UI via F2, and then launch MNC via the hotkey (Alt+N). That will quickly get you into a state where toggling the UI's visibility has MNC up when it shouldn't be and not when it should. I'm looking into this, and will also be looking for why switching between Flight View and Map View with the UI hidden has this effect. Hopefully, I can run this down soon and get a new version posted where it doesn't do this.
  7. Update to version 0.4.0 Added capability to switch between Open and Closed part variants in the VAB. This update impacts the FPS-60, FPS-400, and FPS-2000, eliminating three parts from the part picker and instead delivering the capability to choose from Open (has no top truss structure or top attachment node) or Closed (has a top truss structure with a top attachment node) in the VAB. Selecting the Open variant will be lower mass. For backward compatibility, the old parts are all still in the asset bundle (so sadly it isn't any lighter), however, they are hidden in the parts picker. This means that any craft previously built with the now deprecated variants will still load and work as they have, but any new craft built will only have the new parts. https://github.com/schlosrat/TNO/releases/tag/0.4.0 https://spacedock.info/mod/3471/The Nuclear Option
  8. Thanks, this does help me understand the issue better. When you’re looking for a way to plan a Gilly to Eve trajectory the tab you need is indeed the Moon tab, and the maneuver is Moon Return. Of course going the other way it’s not this tab and you’re just planning a simple Hohmann transfer. Right now the Moon Return maneuver is giving poor results for Gilly to Eve, but that is the one intended for this purpose. It sounds to me like you’re finding this arrangement of maneuvers and tabs counterintuitive, and if you are then others may be as well, but this arrangement is by design. When you go from Eve to Gilly, you’re starting in an orbit about Eve and going to another object also orbiting Eve. Consequently the tools you need are basically the same as you need if you want a Hohmann transfer to rendezvous with another ship also orbiting Eve. When you go from Gilly to Eve, OTOH, your starting orbit is not about the same body that your target is orbiting, thus the math is a little different. There is still a hohmann transfer involved, but you need to escape Gilly’s SOI first, and to do so in such a way that your excess velocity puts you on a Hohmann transfer to Eve. Tab availability is situational. If you have two ships both orbiting the same body and one targets the other you’ll get the Target Relative Maneuvers tab for Vessels. This should work at any body including moons. If you target a celestial body that’s orbiting the same body you are then you’ll get theTRM tab for Celestials. If you’re orbiting a planet and target another planet you’ll get the Planet tab which gives you interplanetary transfers. You don’t get this at a moon, which may be frustrating or confusing, but again this is because the interplanetary transfer tools are not designed to get you out of a moons SOi, and then out of a planets SOI after that to put you on a transfer to your destination. Your use case of moon to moon transfer (at Kerbin or Jool) is a good one. I’ll explore if interplanetary transfer code can be used for this since the situation is analogous
  9. In the (very brief) testing I've done, the only moons where I've seen this problem are Minmus and Gilly. In every other case, I get pretty good results, although with Bop and Pol the returns to Jool are not nearly at the requested 100km Pe and instead at a few thousand Km Pe. Not really a bad result when we're talking about Jool - I mean, do you really want to be swinging around within 100km of its "surface"? I had thought I'd find the same problem at Bop and or Pol given their very small size, but apparently not - though my testing was hardly exhaustive. I do wish I had a good theory for why this happens in some cases and not in others...
  10. OK, I'm home now and I've been able to do some simple testing at Gilly, perhaps this is the problem you've encountered... In a 15.7km x 15.7km circular orbit at 0 inclination at Gilly, I used the Moon Tab to get a Return From Moon trajectory with no target selected. As with performing a Moon Return at Minmus, the result is a good burn vector at a very silly time. By a "good burn vector", I mean the Prograde, Normal, and Radial components are good - but as with returns from Minmus the node time is just plane wacky as you can see below. The resulting trajectory, while not headed all the way back to Kerbin (it's only a 221 m/s maneuver), is definitely leaving both Gilly's and Eve's SOI. In fact, if you turn the camera so you can see where Eve is in relation to all this, you'll clearly see the node time is just wacky. For a good Moon Return, or for that matter any transfer from a higher orbit to a lower orbit, we need to burn in a direction that will decrease the orbital energy so that the Pe will drop. In other words, we need to take off in more or less the opposite direction of the moon's orbital velocity about its parent. Fooling about with Maneuver Node Controller, I was able to get a not too terrible result with only modification to the time of the node. Here, the node time has been pushed out by about 2:10 - which is a lot for this orbit and results in a Gilly ejection that is headed in about the opposite direction of Gilly's motion as shown below. This problem has been reported before (by me and by others) and is being tracked on GitHub with this issue: https://github.com/schlosrat/FlightPlan/issues/49 The good news is that there is a relatively simple (albeit tedious) workaround, and also that I am aware of this and working on it. Not fantastic news, I'll grant you - but not bad news either. I am also working on this one! In fact, with this one, I feel closer to a solution than I do with the Moon Return problem, but we'll see.
  11. Are you saying that you’re orbiting Gilly and you don’t have a Moon tab with a Moon Return maneuver or that the Moon Return maneuver isn’t giving a good Pe at Eve in this case but is sending you out of Eves SOI? Any time you’re orbiting a moon there should be a Moon tab. You would not need to target Eve or anything really to be able to use it, though it does recommend that you be in a low inclination/low eccentricity orbit for best results. I’ll test the Gilly to Eve return when I get back to my PC, but it may help if you can describe more about your situation and the options you’re getting in FP
  12. Release 0.10.5Corrected issue where in some cases the Next Window time for a transfer window would be computed incorrectly and count up rather than down.Download on SpaceDock
  13. Well, that's odd. I verified it in 0.10.4 with Node Manager 0.7.3. In fact, I just reverified it in a debug build - so I've verified that the bug is possible in both the release and debug versions of FP 0.10.4 Since I'm able to reproduce it I should be able to get to the bottom of it. In my test case, I'm at UT 1y, 3d, 1:22:03 and flipping back and forth between Duna (which seems to work) and Dres (which is showing the bug). At Duna, I see this Relative Inclination: 0.06 Phase Angle to Target: 134.531 (counting down) Transfer Window Phase Angle: 44.361 Transfer Time: 302d 0:13:23 Synodic Period: 2y 57d 2:04:17 Next Window: 227d 4:51:33 (counting down) At Dres, I see this Relative Inclination: 5.00 Phase Angle to Target: 8.414 (counting down) Transfer Window Phase Angle: 82.056 Transfer Time: 1y 177d 0:55:54 Synodic Period: 1y 101d 5:22:42 Next Window: 107d 5:22:42 (counting up) The difference here is that in one case (Duna) Phase Angle to Target > Transfer Window Phase Angle, and in the other (Dres), it's not. It's also not for Moho or Eve at this UT, but those have Phase Angle counting up - which Dres does not. For any case where the target is in an inferior orbit, you can expect that the Phase Angle to Target counts up, and vice versa. All of this points to a bug in my logic where I was checking to see if Phase Angle to Target > Transfer Window Phase Angle when I should have been checking to see if the target is in an inferior or superior orbit relative to the starting planet. I've fixed this in 0.10.5 and verified it with all the stock planets. I should have a release out for you shortly.
  14. That is sooo weird! I tested with Moho, Eve, Duna, and Jool before releasing 0.10.2 and they all work fine (still do, too). I tested again with Dres and by Jove you're right - it is indeed counting up for the window. I'll look into this and sort it out. Thanks for bringing it to my attention.
  15. Release 0.10.4Multiple fixes/improvements to Resonant Orbit Maneuvers TabFixed handling of Synchronous Alt, Semi Synchronous Alt, and SOI Alt to display altitude instead of radius from the center of the body being orbited.Fixed Diving prohibition to account for atmosphere depth. You are now (correctly) prevented from setting up a diving resonant orbit around a body with an atmosphere where the Pe would be inside the atmosphere - which, I think we can all agree, would be bad.Updated FixPe and FixAp Maneuver buttons to allow for "after a fixed time" burn time option and also force a better default ("at Ap" for FixPe, and "at Pe" for FixAp)Download on SpaceDock
  • Create New...