adammada

>Regarding Max Q... could we have a meter or variable to show the dynamic pressure on the craft... Good idea!

Yes. Please include how to best enter it into MechJeb node editor. Or some other plugin node editor?

I just tried this Kerbin->Eve->Moho transfer. I started with 200666 m orbit. Then i entered into mechjeb node those values: Prograde Delta-V = 1050.30975 m/s Radial Delta-V = -0.00000 m/s Orbit Normal Delta-V = 424.66546 m/s Time of lanuch was within minute from predicted: Year 5, Day 223 20:25:29.912 (just to be on correct angle). Sadly, closest encouter with EVE was aroun 42 000 000 m. Any prograde/normal burn changes were only getting it worse. So i tried to move burn forward and backward by whole orbit period. (39m54s), and ended about 10 hours earlier, because this was giving me closer PE. I also reduced normal burn (about 100 m/s), and ended with about 5 000 000 km Eve periapsis. I lanunched and used mechjeb "fine approach" to get me closer to eve ( about 10 m/s used). Then i waited until entering Eve SOI, sadly i was going wrong way around. I needed about 90 m/s radial burn just to go by other side. Then i was keep raising Eve PE by adding (about -130 m/s at the end) radial burn, until it gave me Moho SOI. So, thoughts: 1. Something was wrong with time of launch, was bit (10 or more hours) too late. 2. Its really, really hard to set launch excactly to get one burn. I know that i should set correct Eve PE before entering its SOI, because this would take much less fuel, but: a) Warp changes PE on changing SOI Its harder to set correct burn angle, to change just PE, not inclination when not in SOI c) it has to be really carefull But it worked! P.S. When i set SMA to 700 (i usually start from 100 km orbit, not 200km), it gave me totally different solution: year of launch: 3 around 1400 delta-v just by changing Kerbin start orbit.

If you want to set ceiling, it should be to the edge of atmoshpere, so 70km. Because why 40, not 30, not 50... And i must say, that it will seriously make it harder, because spaceplane ( you will need to rename chalenge, because with ceiling set to not reach space, it will not be spaceplane challengee ) has just tendency to reach suborbital speeds. I was practically forcing it to not have AP higher than 70 km, and lost .

No, i'm not in orbit, because PE is below 70 000. How i got there? 7 air intakes + one jet engine + low throttle setting (MechJeb AutoThrottle to prevent flameout can do it automatically) = some thrust practically to the 70 000 meters. Completly no cheating. Any additional thrust above 70 000 (RCS or Ion) probably would give me orbit. But since jet is only option, i cant. Mabe if i could rise AP high enough to reach Mun? .

Right no i have over 3 hours of flight, 72% fuel left, for sure went around kerbin over 5 times.

> No altitude limit except the functional limits of air-breathing engines So i can go suborbital? (AP over 70 km)

So infinity glide counts? FTL egg for example?

Bug reports: - point legend goes under other elements - can't resize window ( plot should be scallable ) - optimal results from status box should be default values for "compute departure burn". Or somehow add button there to do it. ( Intel Pentiun G850 processor - 2 cores, windows 7 64 bit ) - when i runned KSP TOL first time, windows firewall spammed me with warnings about making connections (ctfxlauncher process i think) i clicked to allow them. Then it started counting, but only around 50% of cpu usage. When it got to particles it started to jump to higher values like 90%. And it was done. - second time i runned it i didin't got those firewall warnings. So now if i will not do anyting while starting, it just counts like in previous time (50%). - but if i click "Ok" in "attemping to start parraller worksers" i get error from screenshot:

Bug (or just to complicated to users...)? I'm looking for Kerbin -> Eve launch window (going to Eve, so aerobreaking) http://alexmoon.github.io/ksp/ (100 km orbit start, no orbit end, ballistic) : Departure Year 1, day 147 at 6:43:12 Arrival Year 1, day 196 at 22:43:12 Time of flight 49 days 16:00:00 Phase angle -36.35° Ejection angle 150° to retrograde Ejection inclination -1.07° Ejection delta-v 1,074 m/s Transfer periapsis 8,879 Mm Transfer apoapsis 13,339 Mm Transfer inclination 0.12° Transfer angle 238° Insertion inclination N/A Insertion delta-v N/A Total delta-v 1,074 m/s KSPTOT: http://imgur.com/a/HS2k0 Questions: - why there is different optimal time selected on plot and different displayed in status box? - why i cant copy text to clipboard from status box? Result: when I entered correct arrival time in "Compute Burn Box" ( 196 at 22:43:12 ), it computed correct departure time, and gave me ~1000 delta-V departure burn. But i could get it on porkchop. (but i set in options 100 points per axis). But by itself it gives very not-optimal results.

Does this "fly-by" assistance takes into account possibility of first waiting few orbits, then getting to destination (like Kerbin->Eve->3 orbits around Kerbol-> Moho) ? Also, could you somehow add posibility for searching "all planets flyby" path, just like here: http://forum.kerbalspaceprogram.com/showthread.php/37974-Optimal-gravity-assisted-grand-tour-%28AKA-Voyager-like-mission%29-challenge I understand that this could take really long, but it is one time to find for everybody, so i think that many users could spare their computer CPU to find it. So it should be splittable to many parts, so many users can count different parts.

In another try i decided to go straight to Moho, when he is in ecliptic (co i would have two eve-orbit intersects). 1500 m/s delta-v. It was successfull, but i couldng get to Eve, cause its orbit is inclined. After inclination change to cross Eve orbit in one place, i still couldnt hit it, event with 10 orbits. Time for more scientific approach i think.

Another try. I looked at this page: http://alexmoon.github.io/ksp/ And found good delta-v window from Eve to Moho at 187 day. So i looked when i could go from Kerbin to Eve, to get there at 187 day. And it was: Kerbin -> Eve Departure Year 1, day 128 at 13:59:54 Arrival Year 1, day 187 at 10:09:03 Time of flight 58 days 20:09:09 Phase angle -74.43° Ejection angle 85° to retrograde Ejection inclination -12.33° Ejection delta-v 1,329 m/s Transfer periapsis 9,226 Mm Transfer apoapsis 13,713 Mm Transfer inclination 1.82° Transfer angle 250° Insertion inclination N/A Insertion delta-v N/A Total delta-v 1,329 m/s Eve->Moho Departure Year 1, day 186 at 1:47:08 Arrival Year 1, day 206 at 7:37:17 Time of flight 20 days 5:50:09 Phase angle -171.51° Ejection angle 141° to retrograde Ejection delta-v 1,578 m/s Transfer periapsis 5,577 Mm Transfer apoapsis 9,625 Mm Transfer angle 133° Plane change time Year 1, day 192 at 17:19:42 Angle to intercept 100.99° Plane change angle 0.02° Plane change delta-v 3 m/s Insertion inclination N/A Insertion delta-v N/A Total delta-v 1,581 m/s So i went to Eve, then straight from Eve to Moho (and because of gravity assist i used less about 800 m/s, so even counting non optimal Kerbin-Eve transfer it was profit). Now i ended on big-inclination orbit, which crosses Eve orbit and 700 delta-v left. Can't see good options to get back to Eve, even after few full oribits. I think that next time i will try to intercept Moho when i can do it without inclination change. Current score: 20 points (Eve + Moho, less than year of flight).

No mods required. About 7500 delta-V.

Yes. I tried to go from Kerbin to EVE on first transfer window (day 138), then from EVE tried to flyby to Moho, but no luck. This gives me 10 points .

Goal of this challenge is to discover best path for flyby mission of Kerbol System. Rules: 1. You have to use ship provided in this post. 2. You can only use fly-help mods like Kerbal Alarm Clock, Protractor, MechJeb etc. You can strap them to provided ship. 3. No cheats. 4. You have to launch your ship before 10-th year (time displayed in Tracking Center). 5. There is hard limit of 30 years of flight time. What happens later is not taken into score. Score: - 10 points for flyby of planet (means entering its SOI), excluding Kerbin. Moons are ignored. Counts only once for planet. - 20 points bonus for flyby of all planets - 20 points for ending in Kerbol escape trajectory - -1 point for every full year of flight (counts mission time) - In case of draw, who has more remaining fuel - wins. Because goal of this challenge is to provide best mission plan, you are required to document your fligh, so others can recreate it. Craft: http://kerbalspaceprogram.com/voyagerchallengecraft/ TIP: Read here metaphor's advices: http://forum.kerbalspaceprogram.com/showthread.php/37340-One-Engine-to-Rule-Them-All!?p=476805&viewfull=1#post476805 http://forum.kerbalspaceprogram.com/showthread.php/37340-One-Engine-to-Rule-Them-All%21?p=476018&viewfull=1#post476018

Can it be used to plan gravitty-assisted voyager like missions? Like Kerbin -> Eve -> Duna etc flybys?

@metaphor - how, how did you managet to do it all? Did you use some external tool ? How you planned that? I want to do something similar, but dont know how, when, what order, etc.

I managed to: Orbit: 1 Mun: 2 Kerbin Escape: 3 (used Mun grativy assist) 6 * 2 = 12 But i think that it would be doable to get Mun and Minmus SOI, just need to time launch correctly.

What mass?

Full album:http://imgur.com/a/hcH2D I used project similar to metaphor, just different first stage. And no parachute . Ship mass: 12.42t Part count: 20. Used mods: MechJeb.

I used scenario module so it was started only when scenario was started, it was OnLoad (if i remeber correctly). I think that you could set it when somebody selects mission, and revert when deselects. Or something similar.

Yes. I used similar approach for setting part count. And somwher in "on unload" i was setting it back for 999. You would have to remember starting values and set them back when needed.

As i understand, your plugin uses now own formula for part costs. Could you then display true part costs in editor? It could be done like that: foreach (AvailablePart ap in PartLoader.fetch.loadedPartsList) { ap.cost = getPartCost(ap); // I think its cost, but maybe money or something in here }

0.20.2 I had "Close" button when i finished first mission (Sputnki I), landed on ground. Now with sputnik II and splashdown, i didn't had "CLOSE" button. So its not always, i will post if i ever see it again.