17:06 <_whitenotifier-cd19> [Principia] vladtcvs commented on issue #2324: Suggestion: don't remove the last manœuvre node from the navball - https://git.io/JenyB

17:08 <_whitenotifier-cd19> [Principia] vladtcvs commented on issue #2324: Suggestion: don't remove the last manœuvre node from the navball - https://git.io/JenyE

17:12 <_whitenotifier-cd19> [Principia] vladtcvs opened issue #2346: Increase pilots experience when flying to lagrangian points - https://git.io/Jenyo

17:22 <_whitenotifier-cd19> [Principia] vladtcvs edited issue #2346: Increase pilots experience when flying to lagrange points - https://git.io/Jenyo

18:10 <discord-> G​regrox. — broke: declination and right ascension

18:10 <discord-> G​regrox. — woke: altitude and azimuth

18:10 <discord-> G​regrox. —

18:10 <discord-> G​regrox. — *this message brought to you by John Dobson*

19:14 <discord-> K​obymaru. — loving the new Orbit analysis tool, you guys! finally some non-wobbly mechjeb orbit parameters

19:17 <discord-> S​umguy. — purple noodle gang rise up

19:25 <discord-> K​enira. — looking forward to launching a new comsat constellation once i make the jump from RT to RA. no longer guessing orbital periods for sats! being able to sync constellations up!

21:23 <_whitenotifier-cd19> [Principia] pleroy labeled issue #2346: Increase pilots experience when flying to lagrange points - https://git.io/Jenyo

21:23 <_whitenotifier-cd19> [Principia] pleroy closed issue #2346: Increase pilots experience when flying to lagrange points - https://git.io/Jenyo

21:23 <_whitenotifier-cd19> [Principia] pleroy commented on issue #2346: Increase pilots experience when flying to lagrange points - https://git.io/JenQN

22:47 <discord-> E​strelaGaliza. — i guess RT is Remotetech. What is RA? Does it replaces RT?

22:48 <discord-> c​apkirk123. — RA is real antennas. It replaces remote tech with a more flexible and realistic (and less laggy) alternative

22:49 <discord-> E​strelaGaliza. — but then probably will lose Flight computer right?

22:49 <discord-> c​apkirk123. — Yes

22:49 <discord-> l​pg. — you also "lose" signal delay

22:50 <discord-> E​strelaGaliza. — dont kill my immersion! xD

22:53 <discord-> n​eph. — https://github.com/KSP-RO/RP-0/wiki/Recommended-Extra-Mods#communications

22:58 <discord-> E​strelaGaliza. — thanks, i wasnt able to found the mod. I will take a look

23:28 <discord-> e​gg. — WIP documentation https://github.com/mockingbirdnest/Principia/wiki/Orbit-analysis

23:29 <discord-> e​gg. — with pretty pictures! https://camo.githubusercontent.com/f2b00e35a7283be75a8ebe5281b99aa12cf2a140/68747470733a2f2f692e696d6775722e636f6d2f3939746e53724d2e706e67

23:29 <discord-> e​gg. — with pretty pictures! https://camo.githubusercontent.com/f2b00e35a7283be75a8ebe5281b99aa12cf2a140/68747470733a2f2f692e696d6775722e636f6d2f3939746e53724d2e706e67

23:29 <discord-> e​gg. — https://camo.githubusercontent.com/80e721584b2e01acb3ef3b05206e2039cce8d24c/68747470733a2f2f692e696d6775722e636f6d2f616c696f5730542e706e67 (edited)

23:31 <discord-> K​enira. — apologies if it's there and i just didn't see it, but apoapsis and periapsis would also be helpful to see in the orbit window. otherwise i still had mechjeb's orbit info open just for that, even if it wasn't quite right

23:32 <discord-> e​gg. — @Kenira yes, but the problem is this will not at all behave the way you would expect

23:33 <discord-> e​gg. — which is why I did not provide it

23:33 <discord-> K​enira. — ah. how so?

23:33 <discord-> e​gg. — The mean elements are just "quantities that remain constant"; they lose their geometric meaning to a large extent

23:34 <discord-> e​gg. — so the apoapsis is not the sum of the minimal distance from the centre and the maximal distance from the centre

23:34 <discord-> e​gg. — so the semimajor axis is not the sum of the minimal distance from the centre and the maximal distance from the centre (edited)

23:35 <discord-> e​gg. — it just is "a quantity that is characteristic of the orbital energy and remains mostly constant, and is kind of the same thing as the semimajor axis in the geometric sense, most of the time"

23:35 <discord-> e​gg. — in particular, for low eccentricity orbits, the apoapsis and periapsis will be ninety degrees away along the orbit

23:36 <discord-> e​gg. — this is obviously not an ellipse

23:36 <discord-> e​gg. — so performing arithmetic based on assuming an ellipse will just result in nonsense

23:37 <discord-> K​enira. — ah

23:37 <discord-> e​gg. — The better question would be "what do you want the apoapsis and periapsis for", rather than "can we have it"

23:37 <discord-> e​gg. — because, much like you get three different periods, there are many ways of getting something that corresponds to that, depending on the question that you are trying to answer

23:37 <discord-> K​enira. — basically what i'd like is having a display for the next apoapsis and next periapsis height, as you can see in map view. so i don't have to go to map view and check it whenever i want to look them up

23:38 <discord-> e​gg. — but only the *next* ones?

23:38 <discord-> e​gg. — or *any* over the mission duration

23:38 <discord-> e​gg. — what if you bump into the ground 3 revolutions down the line, surely that's not great

23:38 <discord-> K​enira. — personally, i am usually only interested in the next single one

23:38 <discord-> e​gg. — and again, why do you want those numbers

23:38 <discord-> e​gg. — what do you do with them

23:38 <discord-> K​enira. — and i keep checking that in map view

23:38 <discord-> e​gg. — what question does this number answer

23:39 <discord-> K​enira. — but i certainly can see how this is not as simple of a thing to solve as i first thought

23:39 <discord-> K​enira. — and what i want the numbers for may not be what everyone wants

23:39 <discord-> e​gg. — I still don't even know what you want the numbers for to start with :-p

23:43 <discord-> K​enira. — well any time i am doing a maneuver basically, be it to capture into an orbit or adjust my orbit. the main things to look at are what are the periapsis and apoapsis, for me at least, and i find myself constantly checking what map view tells me for those (or i just go with what MJ / KER tell me when it's close enough, like in LEO)

23:44 <discord-> n​eph. — I wonder if it'd be possible to plug the new Principia values into contracts as far as completion goes

23:45 <discord-> e​gg. — @Kenira you answered *when* you want those numbers, not what you do with the information

23:45 <discord-> e​gg. — how are these numbers useful

23:46 <discord-> e​gg. — @neph I don't think that makes sense

23:46 <discord-> K​enira. — point, but also i am going to bed now because it's almost 2AM for me, i'll get back to you tomorrow when i am no longer too tired to word

23:47 <discord-> e​gg. — @neph this making no sense is why @Sir Mortimer and I need to poke at https://github.com/Kerbalism/Kerbalism/wiki/Dev-~-Satellite-Contracts; orbit contracts are largely broken by design when perturbations come into play

23:47 <discord-> l​pg. — I want to know how close to the atmo I'm going to get in my flyby. I want to know how high I'll be before I start falling down during ascent. etc.

23:49 <discord-> e​gg. — @lpg OK, so for that sort of thing an "upcoming events" window showing the two upcoming apsides and nodes would make some sense

23:49 <discord-> e​gg. — note that this is would be a completely separate thing from the orbit analysis window, which analyses the current orbit over the long term

23:50 <discord-> l​pg. — certainly. I'm largely happy with mechjeb's display; a more accurate one would be nice, but hardly necessary

23:51 <discord-> e​gg. — (the long term and the next apsis are the same thing in stock, obviously, because conics don't move on their own; but lots of things dissociate because of Principia)

23:51 <discord-> l​pg. — As kenira said, this is info we already get in map view; having it without having to switch is what this feature request boils down to

23:51 <discord-> e​gg. — yeah, that makes sense

23:52 <discord-> e​gg. — Remind me to file a GitHub issue for that tomorrow

23:52 <discord-> l​pg. — (though if I could have just one witch, it'd be for the right-clicked, "pinned" info in map view to stay pinned instead of quasi-randomly switching to a different info bit)

23:52 <discord-> e​gg. — yeah, establishing identity is hard

23:53 <discord-> l​pg. — (though if I could have just one wish, it'd be for the right-clicked, "pinned" info in map view to stay pinned instead of quasi-randomly switching to a different info bit) (edited)

23:53 <discord-> e​gg. — Also, have three witches rather than just the one https://internetshakespeare.uvic.ca/doc/Mac_F1/index.html