Elliptical Orbit

I had the ability to control the throttle with mechjeb enabled on an earlier version of KOS. I take it that this is broke at the moment?

The best results I had was back in 21.1 and using Mechjeb and KOS at the same time. Mechjeb did all the ascent guidance and KOS did all the mechanicals and it worked perfect. I would just setup my plan in to Mechjeb and manually engage the auto pilot, then go start my script in KOS sit back and watch the show. The one thing that I can’t get to work in this newest version is the ability to lock the throttle to positions I want the engines to have with Mechjeb engaged. It seems not to work in this version and I know that in the older version I have for 21.1 Kevin has had this issue before and fixed it. I want to say that those file versions was either 8.x or 9.x. So at the moment I have to engage Mechjeb after my vehicles leave the ground but I still have no throttle control using KOS. Wonder if this can be possibly looked at?

Don’t suppose we could use these really cool venting effects on other engines?

Those items do not ignite the engines. They are only meant to burn off excess hydrogen that has not been ignited internally inside either the combustion chamber or the gas generator. Ariane 5 does a pretty good job at it while the Delta IV does a modest job at best (hence the charred blackness on the sides of the cores that you see after it has lifted off). A nice view of this is on the most recent GPS launch. If you have not checked it out there is a picture on the Spaceflight Now website that is a good example. http://spaceflightnow.com/delta/d365/launch/ But then the amount of hydrogen the RS-68 pumping out is a lot more than the Vulcan, not to mention the SSME had all the gas generator exhaust going through the combustion chamber so all the excess was pretty much burning at engine start.

It already is, just add the module lines to your pods in the part cfg files. MODULE { name = ModuleSAS } MODULE { name = MechJebCore } MODULE { name = TelemachusDataLink } MODULE { name = kOSProcessor }

Wow I have not checked out all the new stuff in a very long time and have been away from KSP. I see things have become a bit more interesting and there is a lot of great work going on. Here is a spot that may help better than Wikipedia stuff that it seems everyone wants to go to for their info. http://heroicrelics.org/info/h-1/h-1-c-d.html Of course the H-1 did not begin life as the H-1. Also there were two types of H-1 on the Saturn 1’s. I will just let you check the site out. If it wasn’t for the government taking down the NTRS site and not placing back all the info that it had, you could find out a lot more.

If you are like me then I tend to change fuel/oxidizer amounts in tanks to more accurate volumes for their sizes (sometimes gallons, other in liters). Not to mention that I will change the burn ratios on engines to match those we use on earth. For that reason even if you were to put amounts for fuel and oxidizer that you think that will be used evenly in an engine, I tend to make my vehicles oxidizer deplete first depending on what I have set for ratios. So you may be reading your liquidfuel amounts with your line of code but running out of oxidizer first which the program never sees if you do not have a line for that as well. Here are a few lines of code I have that works perfect for me that sort of works like an oxidizer gauge. wait until stage:oxidizer < 650. print "Lox 5% Sensor". print "". wait until stage:oxidizer < 390. print "Lox 3% Sensor". print "". wait until stage:oxidizer < 300. lock throttle to 0.

Simple timer code: set t to 15. until t < 7 { print "T - 0:" + t. set t to t - 1. wait 1. }. clearscreen.

This may help some users about using volumes, unless I have missed something that has changed… You have two volumes to work with one is “0â€Â, which is the archive volume. This is the volume you need to be in to save (at least your first) program. And you tend not to use it unless you really want to after your first program. The other is “1†which is what I call the working volume. This is the default volume you are working in when you first start the terminal and it is the volume that I run my programs from. If you wish to program in the terminal then you switch to volume 0 with the switch to volume 0. command. Say the file I wish to create is named ls2. Switch to volume 0 and start with edit ls2. command to label the file and start coding the program. From there you can program your code and save the completed file by pressing F5 when you are done. Your files will be saved in the archive folder on your machines hard drive. Mine happen to be in C:\KSP 21.1 - Loaded\Plugins\PluginData\Archive. Not sure what steam users would be. As long as you have a single file there you can copy, paste and rename as many files in the directory, and they are technically stored on volume 0 for KOS. Once you have a working file then I switch back to volume 1 and load the file from volume 0 that I wish to run. switch to volume 1. Copy ls2 from 0. Run ls2. If you have a file already then all you need to do is copy the file over from volume 0. If I have another file that I have modified then all I do is load that file name since I am usually in volume 1 anyway, then run the program.

Great work with the latest version sir! Back in action again.

Well, don’t get the error on the terminal anymore but it will not execute the command. It will do everything up until that point.

I can confirm that the below line does not function anymore either. Unrecognized term: ‘stage’ error. wait until stage:oxidizer < 200.

Don’t suppose we could get a feature to lock the camera in a stationary position and have it follow an object with out moving with it?

Don’t suppose that we can get this to turn on/off parts of Mechjeb? Right now I got a pretty good ascent script using it to control the mechanical parts and Mechjeb to control guidance, but I have to manually turn on and off the Mechjeb ascent guidance for my vehicle to do what I want it to do. I prefer it more than trying to code that part right now, and it works wonderful. If it was not for that I could send a probe to Duna completely hands off! This mod is the best thing since sliced bread!

Is there a way to get back the ability to have your vessel keep a pro grade orientation rather than swapping ends for a retro grade one while on the coast up to AP during ascent? Or have the ability to toggle what you would like to happen after engine shutdown?