Kainne

I tried my hand at recreating the NASA shuttle in RSS. http://http://imgur.com/a/6zDdk

Kevin, I was wondering how you structured the longitude coordinate system. My observations have shown that the coordinates change value seemingly at random. I'm sure there is an order I'm not perceiving, or perhaps the program is conflicting with some of the mods I have, but if you could set me straight that would be awesome. Right now I've got mechjeb and kethane, both showing me coordinates that agree with one another, and KOS seems to deviate by either 360, or 180 from these standard points. However, occasionally KOS will jump to a different variation of the angle it's measuring, and I haven't figured why. If you could shed some light on this puzzle, it would be much appreciated. I think this mod is great and I would love to use it to coordinate reentry programs with ground coordinates. Edit: I tried making a program that compensated for variation in the numerical angle designation but kept the true angle the same and it caused ksp to crash lol. here's the program: clearscreen. set k to -245.58. set i to -65.58. set p to 6.28*( (altitude+600000)^3/(3.5316*10^12) )^0.5. set x to 0.5. set y to 0.482. set a to (x*p)/60. set b to (a*p)/360. set d to x*(p+b)/60. set tVal to 0. lock throttle to tVal. if apoapsis > 105000 { wait until (longitude > i and longitude < i+1) or (longitude > i+360 and longitude < i+361). if longitude > i and longitude < i+1 { wait until longitude > i and longitude < i+1. lock steering to retrograde. print "go for altitude change.". until periapsis < 96000 { wait until longitude > i+d and longitude < (i+d)+1. if longitude > i+d { set tVal to 1. }. if periapsis < 97000 { set tVal to 0. print "altitude change complete.". }. }. }. if longitude > i+360 and i+361 { wait until longitude > i+360 and longitude < i+361. lock steering to retrograde. print "go for altitude change.". until periapsis < 96000 { wait until longitude > (i+360)+d and longitude < (i+361)+d. if longitude > (i+360) { set tVal to 1. }. if periapsis < 97000 { set tVal to 0. print "altitude change complete.". }. }. }. }. set x to y. print "coasting to deorbit coordinates.". wait until (longitude > k and longitude < k+1) or (longitude > k+360 and longitude < k+361). if longitude > k and longitude < k+1 { wait until longitude > k and longitude < k+1. lock steering to retrograde. clearscreen. print "go for deorbit burn.". until periapsis < 1 { if longitude > k+d and periapsis > 1 { set tVal to 1. clearscreen. print "initiating deorbit burn.". }. }. }. if longitude > k+360 and longitude < k+361 { wait until longitude > k+360 and longitude < k+361. lock steering to retrograde. clearscreen. print "go for deorbit burn.". until periapsis < 1 { if longitude > (k+360)+d and periapsis > 1 { set tVal to 1. clearscreen. print "initiating deorbit burn.". }. }. }. if periapsis < 1 { set tVal to 0. lock steering to prograde + R(0,5,0). print "deorbit burn complete.". }. As you can see, it relies on longitude for it's calculations, but I can't get it to work with KSP's wonky longitude system. Any help would be much appreciated.

I've been working on a reentry program for my shuttle and come to find out that the longitude coordinates don't make sense. I can do one orbit, and they kind of correspond to the coordinates displayed by MechJeb or the Kethane grid, but recently discovered that it jumps from -74 degrees to 298 degrees, and then counts up into the 400s where it jumps back down to something else. Since I'm trying to coordinate a reentry program based on ground coordinates, it would be nice to have them stay the same throughout a flight. I don't mean to be overly critical, I just wanted to see if there was anything I had missed, or if this is a feature that has yet to be fully developed. I can't tell you how much I love this mod. It has enabled me to create programs that get asymmetrical shuttles into orbit and (occasionally) get shuttles back to the runway with extreme accuracy.