10:47 <GH> [Principia] KSPjohnFX commented on issue #1628: Glad to have provided helpful data. Hope the solution is relatively easy for you. Very handy that Principia makes it's own journals. https://git.io/vbeMP

11:34 <GH> [Principia] pleroy commented on issue #1628: Unfortunately, as we dig deeper into the issue, properly fixing it seems to be horrendously complicated. We are going to give it precedence, because we understand it's a real pain for users, but it's likely to take several weeks. https://git.io/vbeHd

14:40 <GH> [Principia] KSPjohnFX commented on issue #1628: Ouch. Maybe advise users in the meantime to only warp when in flight to stop more reports flooding the forum thread?... https://git.io/vbvOw

15:02 <egg|work|egg> !wpn awang

15:06 <egg|work|egg> !u ⚡

15:06 <Qboid> U+26A1 HIGH VOLTAGE SIGN (⚡)

15:06 <awang> egg|work|egg: Sounds like #1628 is going to be fun

15:06 <Qboid> [#1628] title: Crash during timewarp at space center | Steps to reproduce:... | https://github.com/mockingbirdnest/Principia/issues/1628

15:06 <egg|work|egg> awang: yeah...

15:06 <egg|work|egg> means we have to detect collisions within the integrator

15:06 <awang> "We got "lucky" that the downsampling algorithm was stupidly written recursively"

15:07 <awang> "stupidly"?

15:07 <awang> Heh

15:07 <awang> I was literally just about to say that

15:07 <egg|work|egg> yeah it me

15:07 <awang> "If only KSP detected collisions right"

15:07 <egg|work|egg> I wrote it stupidly recursively

15:07 <awang> What's so stupid about it?

15:07 <egg|work|egg> and somehow bring we need to bring the collision detection up through all the integrators to the game, and tell it to destroy the vessel

15:07 <egg|work|egg> awang: well it overflows the stack

15:08 <egg|work|egg> whereas it could just be a loop

15:08 <egg|work|egg> but then you would fail to downsample, and your save would become insanely big instead of crashing

15:08 <egg|work|egg> and then it would take 15 min to change scenes :-p

15:08 <egg|work|egg> so we need to kill those corrupt vessels

15:09 <awang> Ah

15:09 <awang> So it's either a stack overflow or a giant save

15:09 <egg|work|egg> it's hard to devise a criterion for corruption, but it probably only happens with collision

15:09 <awang> Not a great choice either way

15:09 <egg|work|egg> so collision detection should solve the bug

15:09 <awang> Hey, my game takes 15 minutes to change scenes anyways, so I wouldn't notice anything :P

15:09 <egg|work|egg> (and also solve the bug of collision detection :-p)

15:10 <awang> After that, what parts of KSP would Principia have *not* replaced?

15:10 <egg|work|egg> awang: nah, it would take 15 min but freeze the UI thread for that time so you'd get the whole "not responding" feel

15:10 <egg|work|egg> awang: um, I'd say graphics but we actually have our own rendering code for the trajectories

15:11 <egg|work|egg> awang: but that's point-vessel with planet collision detection, not actual collision of ships

15:11 <awang> Well, the "not responding" thing is what I currently experience, soooo...

15:11 <egg|work|egg> so we still need the physics engine :-p

15:11 <awang> At least until users start demanding you simulate gravity interactions between ships :P

15:11 <awang> Or for particularly large asteroids

15:58 <UmbralRaptor> Eh, there's a line in the FAQ about that.

18:38 <xShadowx> principia hasnt replaced the wheel system part of ksp ;3

19:55 <bees> <awang> Or for particularly large asteroids

19:55 <bees> you probably could simulate it as a point source of gravity when you are nearby

19:56 <bees> lets say, in physics range

19:57 <lamont> you can’t

19:58 <lamont> objects in principia either consistently have gravity everywhere or else they’re gravityless like ships

19:58 <lamont> if you violate that you wind up with weird phantom forces