raptop changed the topic of #principia to: READ THE FAQ: http://goo.gl/gMZF9H; The current version is Fréchet. We currently target 1.5.1, 1.6.1, and 1.7.x. <scott_manley> anyone that doubts the wisdom of retrograde bop needs to get the hell out | https://xkcd.com/323/ | <egg> calculating the influence of lamont on Pluto is a bit silly… | <egg> also 4e16 m * 2^-52 is uncomfortably large
<discord-> e​gg. — really Frobenius was surprisingly close to the right thing, except we were thinking that we were doing something completely different
<discord-> e​gg. — the main difference being the force application strategy (see my long comment and those graphs, with the difference between 500 rpm reentries (lol) and 24 rpm)
<discord-> D​amien. — here's that recording, gonna install the new version now
<discord-> D​amien. — it's not just a graphical bug because the 'in shadow' and batter% on the kerbalism window changes
<discord-> D​amien. — it's not just a graphical bug because the 'in shadow' and battery% on the kerbalism window changes (edited)
<discord-> D​amien. — and only happens at a specific timewarp level
<discord-> l​pg. — oh that could just be kerbalism being kerbalism
<discord-> D​amien. — yeah it could be anything
<discord-> D​amien. — just a curiosity for now
<discord-> l​pg. — at 10,000+, it goes into 'analytics' mode
<discord-> l​pg. — it averages out sub exposure over a full orbit
<discord-> D​amien. — no look at the icon for the craft itself
<discord-> l​pg. — it averages out sun exposure over a full orbit (edited)
<discord-> D​amien. — I'm in orbit with one craft, there's a lander on the body below
<discord-> D​amien. — the icon for the lander is spinning round in a small circle apparently leaving the ground, as I move around it in timewarp
<discord-> D​amien. — it's really weird
<discord-> e​gg. — let’s ignore that weirdness for now
<discord-> e​gg. — it is too mad for this time of the night
<discord-> D​amien. — lol no doubt, I should have been in bed ages ago
<discord-> l​pg. — I _have_ seen lander icons behaving that way in the past.
<discord-> D​amien. — yeah but has the movement of the icon had a corresponding effect on its ability to generate power and whether it's considered to be in shadow?
<discord-> l​pg. — never noticed the 'as if on an elliptic orbit' pattern, though
<discord-> D​amien. — but yeah, too mad for tonight
<discord-> l​pg. — (i.e. the way it speeds up & down)
<discord-> D​amien. — it's moving relative to my orbit
<discord-> D​amien. — really freaky
<discord-> D​amien. — ok so I've installed the new test version which I'll test on some descents tomorrow
<discord-> D​amien. — I quickly tested to see if I still have ghosts haunting my lander and I do
<discord-> D​amien. — in complete shadow, it at one point in its magic loop it gets sunlight. I think it's clipping inside the body and seeing the sun
<discord-> D​amien. — that's guesswork though
<discord-> D​amien. — yeah it's definitely clipping inside the mun
<discord-> D​amien. — anyway, bedtime
<discord-> D​amien. — o/
<discord-> P​roton-M blok DM-SL. — How come the orbital path isn't showing up when I focus?
<discord-> P​roton-M blok DM-SL. — I am on Frenet
<discord-> e​gg. — because that is not a thing it does
<discord-> e​gg. — we show the trajectory of the active vessel, and that of the target if there is one
<discord-> e​gg. — we don’t show other trajectories
<discord-> P​roton-M blok DM-SL. — o h
<discord-> _​felixu_. — Can we make a channel called #principiaporn or #principiamissionreports? I really love just browsing n-body trajectories
<discord-> A​cer_Saccharum. — here's a funky n-body trajectory for you
<_whitenotifier-d13c> [Principia] eggrobin commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf06h
<_whitenotifier-d13c> [Principia] eggrobin edited a comment on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf06h
<discord-> _​felixu_. — Oooh I remember seeing this ages ago. I love it
<discord-> A​cer_Saccharum. — what if I told you you could perturb it like this:
<discord-> A​cer_Saccharum. — http://tuvalu.santafe.edu/~moore/rot8x.loop.gif
<discord-> e​gg. — I think those are unstable equilibria though right?
<discord-> A​cer_Saccharum. — the first one is surprisingly stable
<discord-> A​cer_Saccharum. — I'm not sure about the second one though
<discord-> A​cer_Saccharum. — https://burtleburtle.net/bob/physics/eight.html
<discord-> A​cer_Saccharum. — yeah I did a little project for an introductory numerical methods class about the figure eight, so in my search for the initial conditions I found a bunch of pages like the ones you and I linked
<discord-> A​cer_Saccharum. — would sure make a fun configuration for three far-out asteroids in a planet pack
<discord-> e​gg. — why three far-out asteroids when you could be on one of the three bodies :D
<discord-> A​cer_Saccharum. — I mean you're already throwing plausibility out the window
<discord-> A​cer_Saccharum. — so you might as well go for it
<discord-> A​cer_Saccharum. — I have the initial conditions, but I'm not exactly what needs to change to put them into orbit around a star besides making them rotate slowly
<discord-> A​cer_Saccharum. — maybe all you need to do is give them a tiny bit of angular momentum though
<discord-> A​cer_Saccharum. — the tidal effects would be massive for objects large enough to be gravitationally rounded
Webchat242 has joined #principia
Webchat242 has quit [Client Quit]
<discord-> M​yshiko. — Testing latest build today in the late evething / night
egg|laptop|egg_ has quit [Remote host closed the connection]
<_whitenotifier-d13c> [Principia] lpgagnon commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf0XZ
Mike` has quit [Ping timeout: 190 seconds]
Mike` has joined #principia
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Ping timeout: 190 seconds]
<discord-> P​rofiremu23. — How to a manuver planning with Principia while i see the approch (Venus)
<discord-> M​yshiko. — @Profiremu23 could you please clarify your question? (Screenshot?)
<discord-> P​rofiremu23. — Like this?
<discord-> P​rofiremu23. — MechJeb gives me a manuver in 800 days, but i want to do i correct burn in 50 days
<discord-> P​rofiremu23. — I dont know about Principia manuver planning
<discord-> P​rofiremu23. — cuz MechJeb don'est work
<discord-> P​rofiremu23. — Hallo?
<discord-> M​yshiko. — You do want to create a flight plan, add a maneuver node to it and see how trajectory evolves
<discord-> M​yshiko. — You do want to create a flight plan, add a maneuver node to it and see how trajectory evolves as you change the burn parameters and timings. (edited)
<discord-> P​rofiremu23. — I see
<discord-> M​yshiko. — Try also different plotting parameters, not only VCI to understand how trajectories (actual and planned) behaves from different “points of view” (aka coordinate systems)
<discord-> M​yshiko. — MechJeb can usually only give very approximate suggestion.
<discord-> P​rofiremu23. — i see
<discord-> P​rofiremu23. — So i decided i using Principia manuver planner
<discord-> M​yshiko. — Good.
<discord-> M​yshiko. — It’s rather accurate.
<discord-> P​rofiremu23. — Least can tell the flyby alt
<discord-> P​rofiremu23. — First step: go to orbit around Earth
<discord-> P​rofiremu23. — Second step: plan Venus encounter with Principia manuver planner
<discord-> P​rofiremu23. — Third step: ???
<discord-> M​yshiko. — Burn!
<discord-> P​rofiremu23. — Fourth step: Jackpoint!
<discord-> M​yshiko. — Make sure you checked the “show nav something”, this will add a manever node to navball
<discord-> M​yshiko. — Forth step - repeat again with correction plan.
<discord-> P​rofiremu23. — yep
<discord-> M​yshiko. — While burning I recommend watching how trajectory evolves real-time to be ready to cut the engines
<discord-> P​rofiremu23. — I doing that
<discord-> P​rofiremu23. — Step five: my staging decides to die
<discord-> P​rofiremu23. — my spacebar don't work if i try to stage
<discord-> M​yshiko. — Signal loss or avionics don’t work that far
raptop has quit [Ping timeout: 190 seconds]
egg|laptop|egg has joined #principia
<discord-> e​gg. — Hm, has anyone seen neph?
<discord-> e​gg. — he had a repro for the original « spin » aspect of 2519 so it would be nice if we could check that that one is fixed
<discord-> s​iimav. — He left our community
<discord-> P​rofiremu23. — noooooooo
<discord-> e​gg. — @Sir Mortimer also I guess if you want to try using the API you can also use the latest test build linked in 2519, it is built after we implemented the API
<_whitenotifier-d13c> [Principia] eggrobin commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf0NX
<_whitenotifier-d13c> [Principia] eggrobin edited a comment on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf06h
<_whitenotifier-d13c> [Principia] eggrobin edited a comment on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf0NX
<discord-> S​tonesmile. — I experienced something similar to neph's reentry spinup where my sounding rocket spun up to 3k rad/s; that is completely gone with the new test build
<discord-> e​gg. — Ah, good to know
<_whitenotifier-d13c> [Principia] eggrobin commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/Jf0NS
<discord-> D​eparted. — Are these RSS Delta-V Maps not accurate for principia? For a low lunar orbit I'll need alot more than 680 m/s delta v. More in the ballpark of double that.
<discord-> s​iimav. — 680 m/s isn't even accurate for patched conics
<discord-> s​iimav. — more like 750-850
<discord-> B​utcher. — I mean, depends on your intercept, but I'd go for more like 8-900 to be safe.
<_whitenotifier-d13c> [Principia] eggrobin labeled pull request #2573: Pass the iterator traits as a template parameter to Forkable and ForkableIterator - https://git.io/Jf039
<discord-> D​eparted. — So 680 is the lowest possible?
<discord-> B​utcher. — Yes.
<discord-> S​tonesmile. — well, tecnically you could do something fancy like https://en.wikipedia.org/wiki/Low-energy_transfer
<discord-> S​tonesmile. — well, technically you could do something fancy like https://en.wikipedia.org/wiki/Low-energy_transfer (edited)
<discord-> D​eparted. — But principia doesnt add delta v requirement?
<discord-> S​tonesmile. — delta v pops out of the math, however the math for patched conics and principia/IRL are different
<_whitenotifier-d13c> [Principia] pleroy closed pull request #2573: Pass the iterator traits as a template parameter to Forkable and ForkableIterator - https://git.io/Jf039
<_whitenotifier-d13c> [Principia] pleroy pushed 4 commits to master [+0/-0/±12] https://git.io/Jf0AL
<_whitenotifier-d13c> [Principia] pleroy f002533 - Change Forkable to pass Traits explicitly.
<_whitenotifier-d13c> [Principia] pleroy d0aed6a - Adjust DiscreteTrajectory.
<_whitenotifier-d13c> [Principia] pleroy b3feef8 - Comments.
<_whitenotifier-d13c> [Principia] pleroy 8006b18 - Merge pull request #2573 from pleroy/2570b Pass the iterator traits as a template parameter to Forkable and ForkableIterator
<discord-> D​eparted. — thanks for the help. I'll try again with more delta v
Hypergolic_Skunk_ has joined #principia
egg|cell|egg has quit [Ping timeout: 190 seconds]
egg|cell|egg has joined #principia
egg|cell|egg has quit [Ping timeout: 189 seconds]
egg|cell|egg has joined #principia
egg|cell|egg has quit [Read error: Connection reset by peer]
egg|cell|egg has joined #principia
egg|cell|egg has quit [Ping timeout: 189 seconds]
egg|cell|egg has joined #principia
egg|cell|egg has quit [Read error: Connection reset by peer]
<_whitenotifier-d13c> [Principia] pleroy opened pull request #2576: Change Forkable to distinguish two kinds of iterators - https://git.io/Jf0hN
<_whitenotifier-d13c> [Principia] pleroy synchronize pull request #2576: Change Forkable to distinguish two kinds of iterators - https://git.io/Jf0hN
<_whitenotifier-d13c> [Principia] Pending. Build queued… - 
<_whitenotifier-d13c> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4299/
<_whitenotifier-d13c> [Principia] Failure. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4299/
raptop has joined #principia
Hypergolic_Skunk_ has quit [Quit: Connection closed for inactivity]
<discord-> F​alcon. — @egg how would you go about recording a large event of gravity assists, well in Principia?
<discord-> F​alcon. — im doing a MESSENGER like mission and would like to document it
<_whitenotifier-d13c> [Principia] pleroy synchronize pull request #2576: Change Forkable to distinguish two kinds of iterators - https://git.io/Jf0hN
<_whitenotifier-d13c> [Principia] Pending. Build queued… - 
<_whitenotifier-d13c> [Principia] Pending. Building… - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4300/
egg|cell|egg has joined #principia
<_whitenotifier-d13c> [Principia] Success. Build finished. - http://casanova.westeurope.cloudapp.azure.com:8080/job/Principia/4300/
<discord-> D​amien. — Are you timewarping between and doing the entire mission in one go or taking breaks to do other things?
<discord-> F​alcon. — taking breaks and doing other things
<discord-> F​alcon. — if it will take me 5 years, i will be doing a lot between
<discord-> P​rofiremu23. — That is a accident
<discord-> P​rofiremu23. — Two Venus flybys in a year
<discord-> D​amien. — Ok, maybe a series of videos of each flight plan?
<discord-> P​rofiremu23. — No
<discord-> D​amien. — Unless you're planning it all in one go
<discord-> P​rofiremu23. — Just for flybys
<discord-> F​alcon. — he is talking to me Profire
<discord-> P​rofiremu23. — not orbiters
<discord-> P​rofiremu23. — Sorry
<discord-> F​alcon. — and i will just have to remember i guess to do a video
egg|cell|egg has quit [Ping timeout: 190 seconds]
<_whitenotifier-d13c> [Principia] pleroy closed pull request #2576: Change Forkable to distinguish two kinds of iterators - https://git.io/Jf0hN
<_whitenotifier-d13c> [Principia] pleroy closed issue #2570: DiscreteTrajectory should use a vector, not a map - https://git.io/JfRtJ
<_whitenotifier-d13c> [Principia] pleroy closed issue #2552: Implement a quadrature and use it in the PID - https://git.io/Jfst6
<_whitenotifier-d13c> [Principia] pleroy labeled issue #2552: Implement a quadrature and use it in the PID - https://git.io/Jfst6
<_whitenotifier-d13c> [Principia] pleroy labeled issue #2570: DiscreteTrajectory should use a vector, not a map - https://git.io/JfRtJ
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
raptop has quit [Ping timeout: 189 seconds]
<discord-> T​ransparent_Elemental. — is there a way to check what inclination will be at a certain point in my planned trajectory?
<discord-> T​ransparent_Elemental. — for example I'm plotting a maneuver to the moon and i need specifically 48 degrees moon orbit or higher, can i check what would it be after a current maneuver *before* doing it?
<discord-> D​amien. — view the frame in moon centred inertial and it should show you your equatorial an/dn
<discord-> D​amien. — view the flight in moon centred inertial frame and it should show you your equatorial an/dn (edited)
<discord-> D​amien. — view the flight plan in moon centred inertial frame and it should show you your equatorial an/dn (edited)
<discord-> T​ransparent_Elemental. — the nodes are there, but they do not show any inclination related info, only the speed
raptop has joined #principia
<discord-> D​amien. — hmm, not sure then
<discord-> e​gg. — yes because instantaneous inclination is not a thing that is very meaningful with arbitrary trajectories
<discord-> e​gg. — @Transparent_Elemental if you want the mean inclination of a vaguely Keplerian orbit, use the orbit analyser
UmbralRaptop has quit [Remote host closed the connection]
<discord-> D​amien. — can't do that if he's not there yet though
UmbralRaptop has joined #principia
<discord-> e​gg. — yeah, we should provide the analysis in the flight planner.
<discord-> e​gg. — I mentioned that here https://github.com/mockingbirdnest/Principia/issues/2517#issuecomment-608569038 but it looks like I never opened a dedicated issue
<discord-> T​ransparent_Elemental. — my eye served me great though and i didn't expect to enter an 87 degree orbit
<discord-> B​utcher. — @egg does the 2574 fix versión for 1.9.1 also work for 1.8.1?
<discord-> l​pg. — yes
egg|laptop|egg has quit [Remote host closed the connection]
<discord-> B​utcher. — Bueno.
egg|laptop|egg has joined #principia
<_whitenotifier-d13c> [Principia] nepphhh commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/JfEY3
<discord-> l​amont. — @egg does this discussion sound correct:
<discord-> l​amont. — " inertially fixed [...does] not works if the navball’s reference frame is different than the node’s reference frame, which is sometimes used when planning complex trajectories."
<discord-> e​gg. — what?!
<discord-> l​amont. — yeah
<discord-> e​gg. — inertially fixed means inertially fixed
<discord-> l​amont. — lol
<discord-> e​gg. — it *is* true that it will use more Δv, that much the user understood
<discord-> l​amont. — yeah i was just typing that out as a question.... get out of my mind.
<discord-> e​gg. — (because if you burn in a fixed direction, as the trajectory curves, some of the energy expended does not go towards increasing your kinetic energy but instead towards slightly bending the trajectory)
<discord-> l​amont. — yeah linear tangent steering
<discord-> l​amont. — i just know that control theory tells me you're right
<discord-> e​gg. — we are not smart though, we cannot into control theory
<discord-> e​gg. — we just follow the Frenet frame
<discord-> e​gg. — (because « what is forward » depends on the chosen reference frame)
<discord-> e​gg. — > inertially fixed [...does] not works if the navball’s reference frame is different than the node’s reference frame
<discord-> e​gg. — If that actually does not work (as in, the marker points in the wrong direction), it is a Principia bug and should be reported
<discord-> e​gg. — if it results, via sybilline interactions, in misinterpretation by MechJeb that is a different problem
<discord-> e​gg. — if it results, via sibylline interactions, in misinterpretation by MechJeb that is a different problem (edited)
<discord-> S​tandecco. — I never understood what happens when your plotting frame is different than your maneuver frame, on a related note
<discord-> e​gg. — OK so the manoeuvre frame defines "what is ~~prograde~~ tangent" "what is ~~radial~~normal" "what is __bi__normal"
<discord-> e​gg. — the plotting frame just changes what you see
<discord-> e​gg. — so, say you are in circular LEO, and your manoeuvre frame is ECI, burning +tangent means prograde/along track
<discord-> e​gg. — which, if your *plotting frame* is ECI, is forward along the plotted trajectory
<discord-> e​gg. — if your plotting frame is SCI, the burn direction is unrelated to what you are seeing, because "forward" at the time of the burn is then primarily dictated by the motion of the Earth
<discord-> D​amien. — I remember when I was recreating molniya, I was manually adjusting the orbit (not planning a maneuver) by performing pro/retro burns in ECI maneuver frame but with ECSF plotting
<discord-> S​tandecco. — are there cases when I'd want my plotting frame to be different than my maneuver frame or vice versa?
<discord-> S​tandecco. — in practice, I mean
<discord-> e​gg. — yes, because for a flight plan with more than one manoeuvre, you will want to look at your trajectory from multiple plotting frame
<discord-> e​gg. — well, for any nontrivial trajectory even
<discord-> e​gg. — the plotting frame is "how you look at it", and you may want to look at it in multiple ways
<discord-> e​gg. — the manoeuvre frame determines what it is; that does not change if you look at it differently
<discord-> e​gg. — say you are injecting into a TLI to impact
<discord-> e​gg. — from a parking LEO
<discord-> e​gg. — you are in LEO, you want to burn forward along that orbit, so the manoeuvre frame is ECI
<discord-> l​amont. — alright so in theory now MJ will execute principia burn nodes
<discord-> e​gg. — but you will want to look at the trajectory:
<discord-> e​gg. — — in MCSA to see the general outline of the transfer ;
<discord-> e​gg. — — in MCI to see the approach to impact ;
<discord-> e​gg. — — in MCMF to see where on the surface you land
<discord-> l​amont. — (not super duper well, but hopefully better than eyeballing it? IDK, i haven't actually even tested the code yet, so its all a bit yolo)
<discord-> e​gg. — > its all a bit yolo
<discord-> e​gg. — DO-178B MechJeb when
<discord-> e​gg. — oh there is a DO-178C now
<discord-> e​gg. — @lamont aside from the slewing issue, that even works with non-inertially-fixed burns, right?
<discord-> e​gg. — @lamont perhaps we should just set the marker to the initial orientation of the burn, and make it follow the Frenet frame only past ignition
<discord-> e​gg. — I think that would solve the issue that they would have in the steered case
<discord-> l​amont. — yeah, if you don't do inertially fixed it'll just stutter-warp for the last 10 minutes up to the node
<discord-> e​gg. — ah, right, as the node reorients it will dance to follow it?
<discord-> l​amont. — it'll "work" but just be annoying
<discord-> l​amont. — yeah
<discord-> e​gg. — OK so it sounds like the correct solution here is to have the marker inertially fixed to its initial orientation until ignition
<discord-> l​amont. — and MJ will warp... see its offf... stop warp... reorient... warp... see its off...
<discord-> e​gg. — showing the initial orientation is probably more friendly even to manual burners
<discord-> l​amont. — probably?
<discord-> e​gg. — (you can orient yourself correctly immediately, instead of having a perfectly useless attitude for the burn 30 min from now)
<discord-> l​amont. — that makes sense to me
<discord-> e​gg. — OK I will open an issue then
<discord-> e​gg. — that ought to be a relatively simple fix, but I forget what the code is like in that area
<discord-> e​gg. — @lamont I wonder how all that interacts with our persistent rotation
<discord-> e​gg. — but I suppose if you do sufficiently good attitude keeping you leave it close enough to nonrotating that you do not care
<_whitenotifier-d13c> [Principia] eggrobin opened issue #2577: The manœuvre node marker should show the ignition orientation for guided burns - https://git.io/JfEOB
<_whitenotifier-d13c> [Principia] eggrobin edited issue #2577: The manœuvre node marker should show the ignition orientation prior to ignition for guided burns - https://git.io/JfEOB
<discord-> B​utcher. — > showing the initial orientation is probably more friendly even to manual burners
<discord-> B​utcher. — @egg yes please
<discord-> e​gg. — haha
<discord-> e​gg. — @lamont is there some magical sarbian CI from which I can yoink a build of that pull request to try it out? (especially if I am to eggsperiment with the new marker behaviour)
<discord-> D​amien. — imagine not being a manual burner
<discord-> l​amont. — it kills any angular momentum down to some very small number before enabling warp to the node
<discord-> D​amien. — although if MJ handled burns I may be tempted
<discord-> l​amont. — roll is typically very zero'd
<discord-> e​gg. — thanks
<discord-> l​amont. — it was designed to work with persistent rotation since a long time ago
<discord-> e​gg. — > Took 9 sec
<discord-> e​gg. — wow, the luxury
<discord-> B​utcher. — It's a pain not being able to orient ahead of time easily.
<discord-> e​gg. — @lamont compare
<discord-> l​amont. — you know i should probably use reflection to see if Principia or PR were loaded and only do that angular momentum check then, and rely on magical stock warp killing angular velocity to zero other times, that'd reduce a lot of stock players whining
<discord-> B​utcher. — > imagine not being a manual burner
<discord-> B​utcher. — @Damien I'm a kos burner.
<discord-> D​amien. — bigbrain right here
<discord-> D​amien. — I don't have the attention span to learn kOS
<discord-> e​gg. — (the Jenkins Windows CI is a bit faster, but it still takes about 20 min to build and run the tests)
<discord-> l​amont. — 1h 2mins is amateur
<discord-> D​RVeyl. — What are stock folks whining about? That MJ manually kills rotation instead of relying on "abusing" warp killing it?
<discord-> e​gg. — apparently
<discord-> B​utcher. — @egg incidentally I've had odd results doing burns where the manoeuvre frame is changed. E.g. a course correction in mci frame was wrong, but it was fine in eci.
<discord-> e​gg. — OK, so perhaps there is something to that comment
<discord-> S​tandecco. — I'd love to use kOS, but it's impossible to use on a 4k screen
<discord-> e​gg. — in which case, plz2filebugreport thx
<discord-> l​amont. — @DRVeyl people make gigantic wiggle-rockets that never settle down
<discord-> B​utcher. — @Standecco why?
<discord-> B​utcher. — @egg yeah I need to verify what occurs.
<discord-> l​amont. — (i think that was due to stacked up serialized builds, normally its only a bit over 2h)
<discord-> B​utcher. — @Standecco you can just turn the font size up, I've used it at 4k.
<discord-> e​gg. — well, yes, it is amateur build times, I am not at work here :-p
<discord-> S​tandecco. — @Butcher I usually play at 150% UI scale, but kOS doesn't seem to be scaling, or if it's scaling, it doesn't do it enough
<discord-> S​tandecco. — I think I have turned the font size up previously, but it didn't help much
<discord-> D​amien. — I know another mod that doesn't play nice with UIScale
<discord-> B​utcher. — Kos doesn't do ui scale I think, but you can set the size.
<discord-> D​amien. — looking at you Egg 😛
<discord-> S​tandecco. — everything is still quite small
<discord-> e​gg. — @Damien what? our UI scales now
<discord-> S​tandecco. — can confirm
<discord-> e​gg. — pleroy did a massive refactoring to allow that
<discord-> D​amien. — it was a while ago so if it's changed then nice
<discord-> B​utcher. — Turn it up more.
<discord-> S​tandecco. — @Butcher where do you set the font size? Maybe I didn't do it in the end, but I doubt it
<discord-> B​utcher. — Font size 16 is OK for me at 4k.
<discord-> D​amien. — I'll retract my semi-serious complaint
<discord-> B​utcher. — @Standecco either in the kos terminal by clicking the +
<discord-> D​amien. — I played on my TV for a while last year sometime
<discord-> B​utcher. — Or you can set the default in settings.
<discord-> S​tandecco. — @Butcher ok, looks like kOS wasn't saving my default but changing the font in the actual terminal worked
<discord-> B​utcher. — Read only config file?
<discord-> B​utcher. — Earlier versions didn't have proper font scaling either.
<discord-> B​utcher. — I don't recall a when it came in.
<discord-> S​tandecco. — no, maybe it requires a restart? The actual xml file looks good
<discord-> e​gg. — @lamont just tried it on a plane change (so binormal guided, here inertially-fixed flat-out does not work), it executes quite nicely considering that it is open-loop
<discord-> e​gg. — Got into an orbit which appears to very slightly resonate with the Mun’s
<discord-> l​amont. — noice
<_whitenotifier-d13c> [Principia] scimas commented on issue #2519: Spin-up on reentry under physics warp with FAR - https://git.io/JfEsL