egg changed the topic of #principia to: READ THE FAQ: http://goo.gl/gMZF9H; The current version is Cesàro. We currently target both 1.2.2 and 1.3. <scott_manley> anyone that doubts the wisdom of retrograde bop needs to get the hell out | https://xkcd.com/323/
Hypergolic_Skunk has quit [Quit: Connection closed for inactivity]
<awang>
egg|zzz|egg: I'll just replace the C# parts with the parts I built here
<egg|zzz|egg>
(but we can live without shared_mutex for a while anyway, it's not that critical)
e_14159 has quit [Ping timeout: 183 seconds]
<awang>
LLVM 4.0 also SIGILLs
Rokker has joined #principia
e_14159 has joined #principia
<awang>
Get a compiler crash with Clang 3.7
<egg|zzz|egg>
awang: I don't think it's worth wasting too much time on this; we'll stab those thread_locals by solving 228 (it's long overdue anyway, look at how small the number 228 is)
<awang>
egg|zzz|egg: :(
<awang>
Wish there were a way for me to help with 228
<awang>
I'd love to be able to get back on Principia master
<awang>
How much work do you think remains for 228?
egg|phone|egg has quit [Ping timeout: 186 seconds]
icefire has quit [Read error: -0x1: UNKNOWN ERROR CODE (0001)]
Jesin has quit [Remote host closed the connection]
<GH>
[Principia] pleroy opened pull request #1607: Remove old docker stuff (master...Docker) https://git.io/vd1dP
awang has quit [Read error: -0x1: UNKNOWN ERROR CODE (0001)]
awang has joined #principia
<awang>
egg|zzz|egg: What planning, if any, have you done for #871?
<Qboid>
[#871] title: Support for engines of next stage in manœuvre | So we don't have to activate an engine to plan for it; this is a prerequisite for #870 (since there is no throttling of SRBs, activating means igniting).... | https://github.com/mockingbirdnest/Principia/issues/871
<awang>
I've been feeling like doing something useful, oddly enough, and I thought that I can at least try taking a stab at the UI part of this
<GH>
[Principia] pleroy opened pull request #1608: Undefine the WE_LOVE_228 macro and fix the tests (master...WeDontLove228) https://git.io/vd1AN
<GH>
[Principia] eggrobin commented on issue #1608: Note: this is a first step towards resolving #228, to get sample dense trajectories to investigates potential downsampling methods. https://git.io/vd1xk
<GH>
[Principia] eggrobin commented on issue #1608: Note: this is a first step towards resolving #228, to get sample dense trajectories to investigate potential downsampling methods. https://git.io/vd1xk
icefire has joined #principia
egg|phone|egg has quit [Remote host closed the connection]
NolanSyKinsley has quit [Ping timeout: 186 seconds]
kmath has quit [Remote host closed the connection]
kmath has joined #principia
NolanSyKinsley has joined #principia
Rokker has joined #principia
NolanSyKinsley has quit [Remote host closed the connection]
Hypergolic_Skunk has quit [Quit: Connection closed for inactivity]
Hypergolic_Skunk has joined #principia
uj8efdjkfdshf has joined #principia
egg|zzz|egg is now known as egg|nomz|egg
Jesin has joined #principia
Daz has quit [Read error: Connection reset by peer]
Daz has joined #principia
Wetmelon has joined #principia
<awang>
egg|nomz|egg: So what I was thinking for #871 was adding another button in the flight planner window in addition to "Active Engines", "Active RCS", and "Instant Impulse"
<Qboid>
[#871] title: Support for engines of next stage in manœuvre | So we don't have to activate an engine to plan for it; this is a prerequisite for #870 (since there is no throttling of SRBs, activating means igniting).... | https://github.com/mockingbirdnest/Principia/issues/871
<awang>
That would pop up another window listing the engines on the vessel
<awang>
With buttons for each engine
<awang>
Player would click the buttons corresponding to the engines that should be used for that maneuver
<awang>
And calculations would be performed using those engines
<awang>
How does that sound?
<awang>
Also, lol at UseTheForceLuke()
<egg|nomz|egg>
hmm, not sure, I'd need to think about it
egg|nomz|egg is now known as egg|zzz|egg
<egg|zzz|egg>
awang: I wouldn't do that this release anyway, we're going to have our hands very full with 228 already
<awang>
That's fine, I just want to at least get a proof of concept or something going
<awang>
At least in part so I can familiarize myself with the way Unity GUI works
<awang>
I'm fine with waiting
<egg|zzz|egg>
awang: also if you warp 100 days with WE_LOVE_228 disabled (like it is at master) you get a 800 MB save and it takes 12 min to switch from the tracking station to the space centre :D
<egg|zzz|egg>
(you get a point every 10 s, for 100 days, for every vessel :D)
<egg|zzz|egg>
awang: this is why WE_LOVE_228 :-p
<awang>
Oh. Ouch.
<awang>
What does WE_LOVE_228 do exactly that disabling it creates such chaos?
<egg|zzz|egg>
awang: the plan is to do some fancy downsampling (but smart, so it doesn't trigger the silly plots shown in #228 which you reported too)
<Qboid>
[#228] title: Keep the whole history | For the moment we compute the histories using `sampling_period == 0`, which results in large gaps in the trajectory at high timewarp (rendered as long straight line segments, see below). We should use `sampling_period == 1` instead, and downsample ourselves as needed when rendering.... | https://github.com/mockingbirdnest/Principia/issues/228
<egg|zzz|egg>
awang: 228 puts a point every max(one frame, 10 s)
<egg|zzz|egg>
awang: so in timewarp you can get very sparse points
<egg|zzz|egg>
at timewarp 10'000 you'll get a point every 200 s for instance
<awang>
Ah, and the sparse points means funny lines when interpolating?
<egg|zzz|egg>
if they're too sparse, yes
<awang>
lol, I like the units there
<egg|zzz|egg>
awang: meanwhile a user wants the moon to move faster https://forum.kerbalspaceprogram.com/index.php?/topic/162200-wip122-and-13-principia%E2%80%94version-ces%C3%A0ro-released-2017-09-20%E2%80%94n-body-and-extended-body-gravitation-axial-tilt/&page=33&tab=comments#comment-3195933 :D
<awang>
egg|zzz|egg: I was expecting something sillier :(
<UmbralRaptor>
^
<egg|zzz|egg>
:-p
<egg|zzz|egg>
awang: also I think you can download a patch to revert back to 1.3 from the ksp site?
<egg|zzz|egg>
(I just keep an archive of all the old versions so I don't really know)
<awang>
I think the proper way is to use Steam. They keep old versions or something
<egg|zzz|egg>
awang: I don't use that, and I think I saw a dowload for a patch backwards just on the ksp store
<awang>
idk, I've never used the KSP store
Rokker has quit [Quit: Connection closed for inactivity]
NolanSyKinsley has joined #principia
Jesin has quit [Ping timeout: 183 seconds]
<lamont>
the “beta” versions on steam for KSP let you roll back
Hypergolic_Skunk has quit [Quit: Connection closed for inactivity]