jrbudda

Members
  • Content Count

    87
  • Joined

  • Last visited

Community Reputation

167 Excellent

About jrbudda

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

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

  1. Id appreciate if you could file a github issue to better track this issue.
  2. KSP 1.7.0 is out. There are no conflicts with the existing KER. You can safely ignore any version warning. The new version will be out shortly and on CKAN whenever CKAN updates.
  3. Yup Just tested it. If you actually launch the monoprop ship there's nothing stopping you from just sitting there and burning all the monoprop with the first stage. It does prioritize the fuel tank in the same stage first, but you'd have to manually monitor the level and stage at the right moment for the stock dV values to be correct. KER and vanilla may differ, but both are right depending on your stage timing.
  4. I'm preeeeettty sure monoprop doesn't obey crossfeed rules on parts
  5. I finally got some time to look into this. What it comes down to is bad wording on my part. In the code, and the description, I called those 3 readouts time-til/separation at/rel speed at 'closest approach', but decided to label them time/sep/speed at 'Encounter'. This was misleading. The readouts expose the data available when you hover over the approach markers. When you have a SOI transition, there are no approach markers (on the first orbit patch anyway) so no data. I'm renaming those 3 readouts to 'At Approach' instead of 'Encounter' to better clarify. Providing data about the next 'Encounter' (meaning SOI transition) would have to be a different readout. In the future I will look into extending the 'closest approach' readouts to look into the next orbit patch and pull the periapse and report that, but for now it'll remain N/A if there's a SOI transition.
  6. Deleting the CKAN directory and restarting it seems to have fixed it.
  7. Does KER not show up under 'Compatible' in CKAN for anyone else? The .version file is correct, not sure why it shows under 'incompatible' with 1.6.xxx for me
  8. 1.6 is out, but so am I for the next week. Any updates from me will have to wait til after christmas. I verified that the existing release of KER loads fine, with the expected version warning. The dV readings in the VAB match, which is nice to see. Please post any oddities or discrepancies you find with 1.6 and I will take a look at them next week. Cheers and Happy Holidays
  9. There are no plans to remove anything from KER. Even from a technical standpoint the dV calculations are part of the KER Vessel Simulator which calculates much much more than just dV. Mass, thrust, RCS dV, all that good stuff comes out of the simulator. If at some point in the future the stock calculations (which I am very curious to get a look at) cover 100% of KER calculations then I will remove the simulator for performance purposes and populate the readouts with stock values.
  10. ya no prob, i'll add it to the list. can you give me a good way to reproduce this? I'm relying entirely on the game to tell me about encounters so maybe the map is looking at different code than I am.
  11. Yea I saw the post on reddit. Any idea how to actually get the planet's tilt to properly do that calculation? I imagine some other things in KER are broken by this. A) ok. I will fix. B) Customize how? order? show/hide? Different data?