tkb

I'm getting a strange error when trying to load up KSP. The screen hangs on WarpPlugin/Spaces/sci/model and here is the last bit in the log... [EXC 21:22:21.184] FileLoadException: The assembly name is invalid. System.Reflection.AssemblyName..ctor (System.String assemblyName) ModuleManager.MMPatchLoader.PrePatchInit () ModuleManager.MMPatchLoader.StartLoad (Boolean blocking) ModuleManager.MMPatchLoader.StartLoad () LoadingScreen+.MoveNext () [LOG 21:22:24.619] [iR GUI] destroy **EDIT** Nevermind, I did a stupid.

Thanks. I may have in fact used your method, I did come up with one that worked. But, the one I used ended up having to wait a VERY long time in some lat/long combinations.

I'm dense and am not quite sure I'm following your solution as every time I try I can't get it to work out. I've ended up working out a method that takes the given lat/long, then just does stepping burns based on that to slowly bring the satellite and the location closer together. I've also thought about launching, achieving KSO, burning out to double my orbital period, performing the inclination change, then recircularizing.

Yep! Again, I really appreciate the help in figuring it out. If you'd be willing to continue the help, I'm working on another issue now. I'm working on adding polar insertion into my spreadsheet. I've got the first part down, I think. I can get it to tell me based on from what latitude I burn from to the equator, it tells me the longitude I'll arrive at. I know with these values I can then figure out when in the future I'll arrive at the correct lat/long to burn for a polar orbit that passes directly over KSC at the same time my KEO satellite does (Don't worry, I'll give them 50 meters or so of altitude difference so there's no sad engineers on the ground!). I figure for now that passing over it heading north or south is really inconsequential, but I'm having problems putting the equation together.

My original question has been answered, but if anyone wants a spreadsheet that they can input their orbital values into to move into a kind of precise KSO/KEO orbit, the link is: SPREADHSEET I haven't bothered making it super precise so that you can enter your current altitude, so it works best if you start from a parking orbit with an eccentricity close to 0. If anyone has any suggestions or notices something wrong, please let me know!

Ah, it was absolutely luck that it ended up in the correct position! I ended up making corrections to a spreadsheet I made for KEO/KSO launches and tested it with varying parking orbits and I'm putting satellites within a degree of KSC, so it's great. I know it may be more complicated, but it makes me feel like I'm doing it the way a mission planner on earth would do it. Anyway, thanks again!

Thanks for the answer. I'd just like to make sure I smell what you're stepping in and not getting lucky. Let's say I'm in a parking orbit with a SMA of 2633.09 km. That should give me an orbital period of 14285.41 seconds. I would want to burn to raise my apoapsis to ~2868.75km, giving me a SMA of 3050.92 km, and increasing my orbital period to 17817.24 seconds. So I'd take the difference of 3531.83 seconds, divide by 21600, then multiply by 360 to get the degrees? That results in 58.86 degrees, which I'd then wait one full orbit and circularize at periapsis to give myself an orbital period of 6 hours? Based on the above, I decided to try to half it so I could burn at the next apoapsis, and it put me about right above KSC (I burnt at ~104 degrees west). Now to figure out the timing for a bi-elliptic transfer.

My original question is below, but if anyone wants a spreadsheet that they can input their orbital values into to move into a precise KSO/KEO orbit, the link is: SPREADHSEET I haven't bothered making it super precise so that you can enter your current altitude, so it works best if you start from a parking orbit with an eccentricity close to 0. If anyone has any suggestions or notices something wrong, please let me know! Hello! I apologize for such a simple question but I can't seem to find an answer in the normal wiki spots. Currently in my games, to put a satellite into KEO/KSO I just park them above or below the correct altitude and wait for the target to pass under to correct the orbital period to 6 hours. I got to thinking that there must be a way to predetermine when to make a burn so that you arrive at periapsis or apoapsis above your target and make it a bit more scientific. If some of you wizards of maths could help me I'd very much appreciate it. I'd ultimately like to put 3 satellites each into inclinations graduating by 45 degrees, for a total of 24 if my math is right. Each satellite in the same inclination would be separated by 2 hours, and all inclinations would intersect above a common point (KSO for the first satellite), with a satellite passing over that intersection point every 15 minutes. I plan to have the apoapsis and periapsis values different for satellites orbiting in prograde and retrograde to prevent collisions, but will enjoy the problem of fine tuning that dance when I encounter it. I did search the forums, but didn't find an answer so assumed if it's there to find I'm suffering from a case of missing keys.