Jump to content

erendrake

Members
  • Content Count

    535
  • Joined

  • Last visited

Community Reputation

205 Excellent

About erendrake

  • Rank
    Junior Rocket Scientist

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you for taking this project over Steven! I miss working on kOS a lot and its great to know it is in good hands.
  2. I Approve of this lock. I am no longer active enough to support the kOS team enough to maintain the OP.
  3. Hey :)

     

    I want to inplement a function into the orbit structure. 

     

    The function input of the function is time in seconds or so. 

    The Output is the trueanomaly at this time. 

     

    I had read that the kspAPI has a function orbit.trueanomalyatut.  i want to use this function to calculate the trueanomaly at a certain time.  I had trieb on my own but it didnt work. 

     

    Can you Held me ?

     

  4. New Release Github : Download Spacedock : Download BREAKING CHANGES As usual, you must recompile any KSM files when using the new version. Vecdraw :SCALE no longer applied to :START. Only applied to :VEC. Varying power consumption might make it so if you have high IPU settings some designs might run out of power when they didn't before. (in most cases it should draw less power for most people). !!!! Default extension of ".ks" is no longer applied to all new filenames created. But it still will be looked for when reading existing files if you leave t
  5. v0.18.2 Github KerbalStuff BREAKING CHANGES As usual, you MUST recompile all KSM files before running them on the new version. Some of the changes have altered how the VM works. Nothing else... we hope. NEW FEATURES Compatibility with KSP version 1.0.5 run once ... syntax to run a script only once per session ( http://ksp-kos.github.io/KOS_DOC/commands/files.html#run-once-program ) Volumes and processors have better integration ( http://ksp-kos.github.io/structures/vessels/volume.html#structure:VOLUME ) Volume titles default to the name tag of th
  6. We appreciate you taking the time to share your craft/script and im sure it will help us improve the steering. I think that Dunbaratu is saying that in your post where you said you were getting "unreasonable behavior" you could have been more clear upfront. When you are operating on such narrow margins with such low control authority i am actually pleased as punch that the new steering got as close as it did. We will be making refinements to it over the next few patches and we hope that you continue to give feedback when you can think of improvements for our little mod.
  7. It would be helpful if you have a script and craft that can only work under the old system for us to test with. This is only the first version of the new system and there is surely work to do to improve it. We are interested in finding out why the new one may not be as good out of the box for some applications and find a way to improve it. All of my tests were very positive in the new system but i almost never fly spaceplanes. I dont think anyone who is active on the dev team is interested in including the old system. It was demonstratively broken in far too many situations.
  8. [h=2]Steering More Much Betterer[/h][h=3]Changes[/h] Changed default MaxStoppingTime to 2 seconds ( was 1 ) [h=3]BUG FIXES[/h] Fixed a issue where the effect of the Kd parameter of PIDLoop was having a reversed effect #1229 Fixes an issue where NO_FLOW resources ( eg SolidFuel ) were not reporting correctly #1231
  9. For your question. I simply have never tried it and we dont test for it. I think that having an advanced kOS part with 2 would be fun and useful. Do we have an open issue in github about it? if not would you mind creating one and we can put it in the roadmap
  10. Github https://github.com/KSP-KOS/KOS/releases/tag/v0.18.0 [h=3]BREAKING CHANGES[/h] As usual, you MUST recompile all KSM files before running them on the new version. Some of the changes have altered how the VM works. New LOADDISTANCE obsoletes the previous way it worked ( http://ksp-kos.github.io/KOS_DOC/structures/misc/loaddistance.html ) Fixed broken spelling of "ACQUIRE" on docking ports. The old spelling of "AQUIRE" won't work anymore. Changed the bound variable "SURFACESPEED" to "GROUNDSPEED" instead, as the meaning of "SURFACESPEED" was confusingly ambiguous. New arg/param matching ch
  11. We on the kOS team work on it exactly for this reason. We want it to be a tool for learning Thank you for your kind words and let us know if there is anything we can do to make it better!
  12. it sounds like you have two installs of kOS. maybe one inside of the other? it would be consistent with these errors
  13. @Kbyte have you turned on your RemoteTech (RT) integration in the config window?
  14. @Kbyte will you share your code? I'm not sure we can help you without it
  15. we have a known issue for the LIST..FROM..IN syntax. https://github.com/KSP-KOS/KOS/issues/620 but i think what you are looking for is "LIST ENGINES IN elist" that will give you the list of engines for the current craft.
×
×
  • Create New...