egg changed the topic of #principia to: Logs: https://esper.irclog.whitequark.org/principia | <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…
_whitelogger has joined #principia
paculino has joined #principia
_whitelogger has joined #principia
paculino has quit [Ping timeout: 207 seconds]
_whitelogger has joined #principia
_whitelogger has joined #principia
_whitelogger has joined #principia
_whitelogger has joined #principia
<queqiao->
⟨qazerowl⟩ Stock KSP, the planets will just phase through each other. Principia, an error message pops up that tells you your planets are not stable and the game will refuse to let time continue. So in other words, solar systems that haven't been tested/tweaked for principia are almost guaranteed to brick your save at some point.
<queqiao->
⟨clayel⟩ wow, i feel like this release is going to have the most user-facing features in quite a long time
<queqiao->
⟨Damien⟩ that first one sounds good if it means what I think it means (being able to view trajectories of a target vessel while landed or prelaunch
<queqiao->
⟨Damien⟩ * prelaunch)
<queqiao->
⟨Damien⟩ that'll make launch to intercept way easier
<queqiao->
⟨clayel⟩ all of them are super useful honestly (except for the nan one, thats just backend)
<queqiao->
not drawing the prediction past the collision is really good for removing clutter from the map view
paculino has joined #principia
<queqiao->
⟨sambug2000⟩ I've just started up my first RP-1 playthrough (have only done roughly a dozen launches so far) and I was wondering if you Principia people recommend using Principia for a first-timer like me. I'm using the Cape btw.
<raptop>
Something something lunar missions will always require an off-planet intercept
<queqiao->
⟨sambug2000⟩ I'm reading the Principia concepts page and the tutorial of how to do a Mun transfer (which yes, I know doesn't apply to RP-1, but still) and it seems super complicated but I figure, would I rather spend my time learning the "wrong" orbital dynamics of base RP-1 and then switch over to Principia and unlearn that and relearn this, or just start from the beginning with Principia
<queqiao->
⟨ezsnack⟩ Patched conics is incomplete more than wrong. Most concepts still apply
<queqiao->
⟨razgriz16⟩ Once you learn how to use the UI, and what different reference frames are, Principia is really no harder than normal RP-1. Some things are easier IMO
<queqiao->
⟨sambug2000⟩ Also I have to ask, since I keep seeing it mentioned in here and on the Principia page...
<queqiao->
what _is_ a conic
<queqiao->
⟨sambug2000⟩ and what are "patched" conics
<raptop>
conic as in a conic section (circle/ellipse/parabola/hyperbola). Blame the ancient greeks
<raptop>
The "patching" is from "patching together" different ones for approximating your trajectory in different SOIs (Spheres Of Influence) as a series of keplerian orbits
<queqiao->
⟨sambug2000⟩ oooooo slices of a cone, yeah that makes sense
<raptop>
okay, yes, technically
<queqiao->
⟨sambug2000⟩ Well, I'm convinced, I'll install Principia onto my existing RP-1 save 🫡
<queqiao->
⟨sambug2000⟩ How do I do that btw? Do I follow the installing page on the Principia wiki, do I use CKAN? Or is there some special way I'm supposed to install it since I'm using RP-1?
<queqiao->
⟨razgriz16⟩ Follow the Principia wiki
<queqiao->
⟨sambug2000⟩ Alright, just unzip the archive and copy the "Principia" folder into the "GameData" folder for KSP?
<raptop>
Yes, the manual install approach. Note that you may need additional libraries are the like (see the troubleshooting section)
<queqiao->
⟨sambug2000⟩ Thanks! Got it installed and working with no issues!
<queqiao->
⟨mmeridian⟩ it's great. Just set your max persistent debris to 0 in settings to save a few frames
<queqiao->
⟨Al₂Me₆⟩ Perhaps you should, but I don't envy upgrading the entire project to use the new features.
<queqiao->
⟨egg⟩ That does not need to be done all at once. Plenty of our C++ needs modernization too. But upgrading the language version seems like a good idea.
<queqiao->
⟨Al₂Me₆⟩ I would personally just put "<LangVersion>latest</LangVersion>" and be done with it.
<queqiao->
⟨sichelgaita⟩ What does "don't work" (in the description of PR #4076) mean? Using these features fails at compile-time? At run-time? How do we make sure that we don't use them (and don't have mysterious failures if we execute them on an uncommon code path)?
<queqiao->
⟨Al₂Me₆⟩ All the cases that I am aware of generate compile errors (either feature not supported on target runtime or missing annotation type from the standard library). I'm not aware of anything that will cause a runtime error to occur.