erendrake

Keep talking Onak, ill rope you into the project and get you to implement it

@Mihara I am the current kOS maintainer. I would be interested in working with you on getting kOS working with RPM. Im not quite ready to start yet but after our next release i think it would be a fun project! We currently have two windows, the terminal and a code editor that is invoked with a terminal command. If you would like to help us out let us know.

Its never too early to talk about sweet features. It would be nice to have a few views, a terminal, a file manager/runner and the editor. You would switch between with IVA buttons maybe? as for listening to other buttons in the cockpit. One thing at a time

I have thought about it a lot. it would be a pretty cool experience! its not on the roadmap yet but it should be

you cant get to all tweakables right now. However, you can set the thrustlimit on engines

I imagine we will release it when it is ready

For all of you who are commenting on current bugs. Thank you! We have been working on these bugs and others and hope to have another version out soon to take care of them. your anecdotes are helping me track down the root causes. Just FYI if you want to help me out a bit more we could talk about these on the Github issue tracker. That way i dont forget an issue in the shuffle on the forums here.

Shoot, i had multi quoted some people days ago and didnt notice they were still selected

Are you using RemoteTech? If so would you try turning off integration in the kOS config file and tell us if that is still an issue? im trying to narrow down the source of the trouble

This is a bug that we have known about for some time. The reason it isnt documented is that past me would be pissed that the bug is still around we dont use engine torque to determine LOCK steering. We had most of a solution https://github.com/erendrake/KOS/pull/48 but that has clearly not finished development. Sorry for the trouble

Many of the "Actions" are named pretty simply. In this case abort is... ABORT

I think an abort sequence is a great use for kOS, and there is nothing wrong with a short script if it adds value

Which version are you running and where did you get it? you should try the new pre-release from github https://github.com/KSP-KOS/KOS/releases/tag/v12.2P1 if you dont want to use a pre-release we should have a new full release with the editor in the next few days.

Good Show Chap! That was a fun video to watch. Thank you for sharing!

I'll be there. PMed

We have been having this conversation over on github. looks like we will have quite a few people in the mix.

One of the reasons i recommend a PID is that there are so many resources out there to help understand how it works and how to tune it. I suggest watching a few videos online.

You could also use a PID controller with your setpoint being your altitude and your output as the throttle. Then when you are trying to gain speed by thrusting away from "UP" you can still maintain the right altitude.

Those are the structure definitions, once you have an engine or body or whatever structure this will help you figure out what your available suffixes are. If you get your engines into an array and iterate over them like this: LIST ENGINES IN foo. FOR engine IN foo { PRINT "Name: " + engine:NAME + " Thrust: " + engine:THRUST. }

Was there an update somewhere that added these values, and I just don't have it? MAXTHRUST is an alias for the max thrust of the currently active engines. It is a pretty simple query to the vessel that doesnt take into account available fuel or anything complicated. if you want to get more sophisticated information about engines you need to get the engines into an array and then iterate over them. We i wouldnt mind helping you figure that out if you tell us more about what you are trying to do.

I have been thinking about this but i havent put hands to keyboard on it. I am out this weekend but after that might be a good time to tackle it.

Welcome, I hope i can answer your question. I assume you are talking about Jet engines? Their thrust does vary on atmospheric density and speed. These are part of the eval for "THRUST" aka current thrust. Because we dont expose either the atrmocurve or velocitycurve and KSP doesnt use them for the "MAXTHRUST" calculation you would have to look at "THRUST" with throttle at 1. If you post a sample of your code we should be able to help more. I havent seen an issue like yours before. Around the first of the year.

Yes, they are detailed in the flight docs http://ksp-kos.github.io/KOS_DOC/summary_topics/ship_control/ under Raw Control

Calm yourself. What mod ships with 2.4.4?

Just FYI mods will very often remove links to dlls that dont include source. I am only saying something to keep it from being taken down I will say that the new FX module makes for a lot of crappy looking code