Gen. Jack D. Ripper

  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About Gen. Jack D. Ripper

  • Rank
    Bottle Rocketeer

Recent Profile Visitors

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

  1. Gen. Jack D. Ripper

    [1.4.x] Precise Maneuver editor *Looking for translators*

    Oddly enough, it *has* been updated on github: Please, Morse, don't let this one die. This is the One Maneuver Node Editor To Rule Them All.
  2. The most recent ModuleManager will take precedence.
  3. Gen. Jack D. Ripper

    KJR Replacement?

    This mod still seems to work, and will automagically autostrut everything.
  4. Gen. Jack D. Ripper

    IS 1.3 Ever going to work on a MAC?

    I had the same issues after the High Sierra upgrade on my MacBook Air (late 2013). What solved it for me was running KSP in a window rather than fullscreen. For some reason, KSP running fullscreen will lock up within a few minutes; in a window, I've never suffered such a lockup.
  5. Gen. Jack D. Ripper

    [1.4.x] Precise Maneuver editor *Looking for translators*

    This document shows the hotkeys; 'P' will show or hide the maneuver editor. Clicking on the toolbar button will let you show and hide different parts of the interface. Otherwise, here's how to use it... Look at the picture in Victor3's post, just above, because it's showing just about everything the maneuver editor has. At the top (left arrow, Node 1, etc.): If you have multiple nodes set, the buttons on this row will let you select which node you're editing. Time: Pretty self-explanatory. The 'Alarm' button is (I think - I've never used it) a way to pull up the Kerbal Alarm Clock window, if you use that mod. New Preset, Save, etc.: This row will let you save maneuver data you've entered (see below) as presets. Say that you're in a nice 100km orbit, and you've just plotted a perfect Mun intercept: you can save it, so in your next launch, you can pull up the preset instead of fiddling with re-entering the maneuver. Increment: 0.01, 0.01, 1, etc.: The button pushed on this row affects the increment (or decrement) of the + and - buttons in the next few lines, as well as the orbit inclination tools. If 0.01 is selected, clicking the + next to Prograde will add 0.01 to Prograde, and clicking the - will subtract 0.01 from it; so on and so forth. This is useful for making very fine maneuvers - like when you're trying to plot an intercept of a Joolian moon from low Kerbin orbit. UT: This line lets you very precisely control the time of a maneuver. You can type a number into the UT box: it's the number of game-time seconds since your saved game's very first moment. You probably won't want to worry about the actual number, though, most of the time. The + and - will increment and decrement the number by whatever increment you have selected (see above). If 100 is the selected increment, + will move the node 100 seconds ahead in time. The x10 button multiplies the increment by 10 - for those cases when 100 second jumps just aren't enough. (Perhaps you're plotting a node that you'll execute in a few years of game time.) A circle with a -, a circle with a +, AP, PE, etc.: This row lets you snap a node to certain important points in an orbit. The circles with - and + let you move the node backwards or forwards in time one orbit at a time - that is, clicking the circle with the + will set the node at this particular point in the orbit, but ahead in time one orbital period. AP snaps the node to the apoapsis - the highest point in the orbit. PE snaps the node to the periapsis - the lowest point in the orbit. If you have a target selected, the AN and DN buttons will snap the node to the orbit's ascending or descending node - which is mostly useful when trying to match a target's orbit inclination. The fields and buttons of the next three rows (Prograde, Normal, and Radial) all work the same way: after the label, there's a field, in which you can type a number, followed by a +, a -, and a 0. The numbers are changes in velocity, and the + and - buttons adjust those numbers according to the increment selected above. The 0 buttons simply reset their respective fields to 0. If you're wondering: 'prograde' means 'in the direction of orbit'; 'normal', for simplicity's sake, means 'towards north'; 'radial', again, simplifying a little, means 'away from the ground'. The Orbit Tools: The buttons with the arrows curling up and down will change the orbit inclination without changing the orbital altitude. This is, again, very helpful when used on a node that's snapped to the AN or DN. The button with a circle and a little R will circularize an orbit at the node's altitude. The two buttons to the right of that will copy or paste maneuver data, respectively. The Maneuver Gizmo is below that. I turn it off. Otherwise, it works like the maneuver gizmo in the stock game. Below that, there's some more orbital information. At this point in your KSP career, the ones you should worry about are mostly Apoapsis, Periapsis, and Incl. (Inclination). Below that is the Conics Draw Mode section. This controls how the orbit paths are drawn in the Map view. I suggest playing around with them. 'More patches' and 'Fewer patches' basically control how far out the flight path is calculated, in the event that your flight path passes by several different planets. Hope this helps a little. To answer your other question, about raising your AP and PE: first raise your AP out of the atmosphere, and then burn *at* the AP to raise your PE. (Or drop a node at the AP, then click the Circularize button, and execute the burn it gives you.)
  6. Gen. Jack D. Ripper

    [1.4.x] Precise Maneuver editor *Looking for translators*

    Would it be possible for the AN/DN buttons to snap a node to the current planet's equatorial AN/DN if no object is targeted?
  7. Gen. Jack D. Ripper

    [1.4.x] Precise Maneuver editor *Looking for translators*

    And my vote. This is by far the best of the maneuver editors, and a +/- orbit button is the *one* useful tool it lacks.
  8. I just want to say 'thank you' for the most recent update. The precise countdown time is perfect - it just looks *right* in that corner of the screen. Now I don't need KER to report the exact time.
  9. Would it be possible to make it possible to configure the time-to-burn increments? One of the things I'd like to use this for is knowing when to slow down or stop time-warping. The current increments just aren't very useful for that: two or three dots that take a long time to go by, and then the rest flash by. Actually, if I had my *real* wish, it'd be for the option to display time-to-burn in the same d/h/m/s format as the time-to-impact display - it would be (in my view) the most intuitive, broadly useful, and stock-alike way of displaying that information.
  10. I'm really sorry to see Custom Clusters go. It was (and will remain, as long as it works) one of the most massively useful - not to mention, elegantly done - mods I have. It's how stock should've been. If you ever have the time, I really hope you can bring it back somehow.
  11. This is magnificent. The new burn timer works perfectly - and not only that, but looks like it really belongs where it is. There are two suggestions I'd make now. First: the dots are really small. Might it be possible to print them in bold text - or otherwise, something to make them just ever so slightly easier to spot (and count) against a non-black background? Second: as far as counting goes, it might be nice if the dots were red within 3 seconds and yellow within 30 seconds or maybe 1 minute - something to quickly differentiate 'time warp', 'probably time to return to normal speed', and 'finger over max throttle'. In other words, the timer works wonderfully - already in the 'how did I ever play without this?' category - but, it would be helpful if it conveyed the information it does a little more quickly. Thank you for this. I'm in the 'learning to pilot without MechJeb' phase, and this has made one part of that much, much more intuitive.
  12. The impact, half the point of KSP is flying based on somewhat-educated guesses, rather than the finely-computed physics of real spaceflight, and part of the learning curve is figuring out that leaving a good margin for error is the difference between 'landing' and 'splattering'. I've found it useful, anyway, and your user warning was enough to tell me not to substitute its calculations for common sense. Thus, one could just append ' (Est. Half-Burn in T- XmYs)' to the time-to-node string, perhaps with a config option to disable it, and that would be that. The promise need be nothing more than 'this will give you the time to node - (estimated burn time/2), which some find helpful for making relatively short burns'. To wit, 'It comes with some caveats, but hopefully it should be helpful for guessing when to begin burns. No more trying to do division in your head while also trying to make sure your craft is ready to start a burn.' That's how I'd handle it, anyway. At any rate, thank you ten thousand times for *not* cluttering up the interface. It's simple and entirely unobtrusive; it looks and works as if it were stock, and really ought to be.
  13. Would it be possible to give a nice time-to-burn-start option? Yes, I can divide the estimated burn time by two in my head and compare that to the time-to-node, but I'm also lazy and prefer the computer to do that kind of work for me.
  14. One suggestion: Could a second bottom node be added, in order to support LV-N clusters?