raptop changed the topic of #principia to: READ THE FAQ: http://goo.gl/gMZF9H; The current version is Gateaux. We currently target 1.8.1, 1.9.1, and 1.10.1. <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
egg|cell|egg has quit [Ping timeout: 189 seconds]
Blu3wolf has joined #principia
Blu3wolf has quit [Quit: Konversation terminated!]
UmbralRaptop has quit [Remote host closed the connection]
raptop has quit [Ping timeout: 198 seconds]
raptop has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
UmbralRaptop has joined #principia
raptop has quit [Read error: Connection reset by peer]
<discord-> F​alcon. — Any idea as to why mid course corrections between the earth and moon dont go as planned? I did the burn where the node was telling me to point for the specified amount of time, and it didnt bring my close approach to the moon where the plan said it would be
<discord-> F​alcon. — do i have a reference frame wrong? or is this an issue?
raptop has joined #principia
<discord-> s​cimas. — How did you execute the manoeuvre?
<discord-> s​cimas. — If you executed by following the manoeuvre marker, then it should have been correct. Unless there was a change in your ship's expected state (mass, position, velocity, engine thrust) since you created the flight plan.
<discord-> s​cimas. — If you didn't follow the marker and instead manually executed the node, then yes, it is possible that you planned the manoeuvre in one reference frame but executed in another. In the screenshot you do have the manoeuvre in ECI but the plotting frame is MCI.
<discord-> s​cimas. — Also, if you are playing RO/RP-1 then engine spool up time can be an issue, Principia cannot account for delayed starts of engines.
<discord-> l​pg. — could have been boiloff, could have been attitude changes, could have been that you didn't take spool-up time into account, ...
<discord-> l​pg. — (or ullage)
<discord-> F​alcon. — correct, i used ECI because i was still burning/maneuvering in the earths SOI not the moons, at least that is how i have always done it before, maneuvering in the suns SOI to reach mars for example
<discord-> F​alcon. — So i did that maneuver i showed above about 5 hrs after the TLI injection, which I had 2 fuel cells running, that was it though, so minimal change in mass for that large of a difference between the intended orbit and the actual orbit
<discord-> F​alcon. — also, would the spool up time change the final orbit that drastically? I know the RL10 has a pretty lengthy spool up time of sorts
<discord-> l​pg. — it certainly would if it means you end up burning at full throttle 2 seconds less
<discord-> F​alcon. — I have run into this issue in the past as well with other none cryogenic missions
<discord-> l​pg. — Souds like one mistake you definitely made was not hitting the Rebase button a few minutes before the burn to make sure it's still good
<discord-> l​pg. — Sounds like one mistake you definitely made was not hitting the Rebase button a few minutes before the burn to make sure it's still good (edited)
<discord-> F​alcon. — I dont even know what the rebase button does, was recently added iirc
<discord-> l​pg. — it refreshes the planned trajectory according to the vessel's current situation
<discord-> l​pg. — (though I'm not certain whether it refreshes absolutely all relevant parameters, e.g. mass)
<discord-> s​cimas. — It does, as far as I'm aware.
<discord-> F​alcon. — Will do that the next time i have KSP open then for that mission, why was the rebase button added btw? Since i dont recall the issue im bringing up being a thing before
<discord-> l​pg. — if you've never taken spool-up time into account, you've been ludicrously lucky not to have problems before
<discord-> l​pg. — I think the main use case for Rebasing is seeing what effect attitude changes have had on your trajectory
<discord-> s​cimas. — It has always been an issue. Rebase is one of the most important QOL additions to Principia. Imagine creating a flight plan with 10 manoeuvres. You execute the first one (but you can never execute it perfectly) and now the rest of the plan is almost useless. So you would need to delete the whole thing and replan the 9 manoeuvres. Rebase does all of that for you in a single click.
<discord-> l​pg. — that too
<discord-> S​umguy. — how do you take spool-up into account?
<discord-> S​umguy. — how do you even know how much spool-up there is? I haven't seen stats anywhere in-game.
egg|cell|egg has joined #principia
<discord-> l​pg. — trial and error, and start burning a bit earlier than scheduled
<discord-> l​pg. — or, simpler but less accurate, just don't rely on the End time and eyeball the time to stop burning
<discord-> l​pg. — (or cheat and hack engines not to have any spool-up time)
<discord-> F​alcon. — So this is how i usually do my maneuvers and then further ones after that, and deal with spool up. For spool up i usually click the kill rotation button right before cutoff if i know i am not close or i shutdown earlier for example, and then use RCS to match the planned orbit as close as i can. And as for more maneuvers after that? I usually plan the whole mission out, usually no more than 3 man
<discord-> F​alcon. — probably inefficient, but i feel like rebasing would still require new fiddling with the maneuver anyways which negates most of the long work i did beforehand
<discord-> F​alcon. — or does rebasing set the delta V requirements to be different whilst keeping the originally plotted orbit?
<discord-> l​pg. — it does not
Mike` has quit [Ping timeout: 194 seconds]
<discord-> s​cimas. — You still do need to fiddle with the manoeuvres after rebasing, but it cuts down that work by a LOT compared to creating them from scratch.
Mike` has joined #principia
Mike` has quit [Ping timeout: 189 seconds]
Mike` has joined #principia
raptop has quit [Ping timeout: 189 seconds]
Blu3wolf has joined #principia
egg|cell|egg has quit [Ping timeout: 198 seconds]
egg|cell|egg has joined #principia
egg|laptop|egg has joined #principia
sdrodge_ has quit [Ping timeout: 198 seconds]
Blu3wolf has quit [Quit: Konversation terminated!]
Jesin has quit [Ping timeout: 189 seconds]
Jesin has joined #principia
raptop has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
<discord-> H​aukifile. — I'm getting issues with Principia, KSP.log shows:
<discord-> H​aukifile. — `[ERR 21:11:40.886] Failed to load assembly H:\pelit\KSPRO181-new\GameData\Principia\x64\principia.dll:
<discord-> H​aukifile. — System.BadImageFormatException: Format of the executable (.exe) or library (.dll) is invalid.`
<discord-> H​aukifile. — I'm getting issues with Principia, KSP.log shows:
<discord-> H​aukifile. — `[ERR 21:11:40.886] Failed to load assembly H:\pelit\KSPRO181-new\GameData\Principia\x64\principia.dll:
<discord-> H​aukifile. — System.BadImageFormatException: Format of the executable (.exe) or library (.dll) is invalid.`
<discord-> H​aukifile. — Similar errors with libprotobuf.dll & serialization.dll (edited)
<discord-> H​aukifile. — and libglog.dll
egg|laptop|egg has joined #principia
egg|laptop|egg has quit [Remote host closed the connection]
egg|cell|egg has quit [Ping timeout: 204 seconds]
egg|cell|egg has joined #principia
UmbralRaptor has joined #principia
raptop has quit [Read error: Connection reset by peer]
raptop has joined #principia
UmbralRaptop has quit [Ping timeout: 204 seconds]
egg|laptop|egg has joined #principia
Blu3wolf has joined #principia