Bizz Keryear

My was an answer to an kOS noob... the meaning of the (yet?) was that might come or not .. f*** i am too lazy sometimes

sounds a little like

actually editing the safe file from sandbox to career might also work... they are all text files after all.

If I would have ideas about that I wouldn't need help. edit: That sounded way more snooty than I wanted to be ... actually ... I only wanted to say that I right now have no clue what and how to do. Actually my rockets are working, but not that good. And my programming skills ... well ... they usually work (after removing all typos ... lots of typos) but they are far from genius.

Sorry that was a typo.. since I was testing it in ksp directly (not using archive) there was a then in the actual script! As long as you are using a kOS version that is capable of using thrust and steering (my experience was: 0.82 steering working but throttle broken, 0.83 throttle working but steering broken) Put it on the wiki, I want to have it there anyway. I give you an example what it will be like: Site with anything in it (download and included scripts): http://kos.wikia.com/wiki/Example_-_Descend_Lander/Skycrane Example script displayed as it will included/downloaded: http://kos.wikia.com/wiki/Example_-_Descend_Lander/Skycrane/bodystats.txt?action=raw actual wiki page of the script (for editing): http://kos.wikia.com/wiki/Example_-_Descend_Lander/Skycrane/bodystats.txt Need rights? No problem I will give them t you. (wow thats sound desperate) I don't mean that you should drop this thread here. Its better for communication anyway. I also think so, but for now (and also cause this mod exists) he will concentrate on other things. Hopefully bug fixing. Edit: For some reason I still don't understand eta:apoapsis is still broken in the (old) space computer orbit script. while it was working in my test program. clearscreen. set ttime to 10. lock steering to up + R(0,0,180). lock throttle to 1. stage. when eta:apoapsis > 20 then {print "simple eta works".}. when eta:apoapsis > 20 + ttime then {print "plus time works".}. when eta:apoapsis > ( 20 + ttime + ttime ) then {print "brackets work".}. until <liquidfuel> < 200 { if stage:liquidfuel = 0 and stage:solidfuel = 0 { stage. print "stage compair work". }. }. print "full ressource compair work". in this program everything is executed. That also means throttle and steering are working again.

No functions (yet?), but we can call programs with parameters. And lately (dunno if that is a bug or a feature) all variables are global. edit: reading is an art I am failing sometimes. If you use programs with parameters the name of the variables can change. like "run a(x)." and a is: declare parameter xina. //read as x_in_a set y to xina^2. print "x in a is: "+xina+" , and y is: "+y. And now I am sure that the globaliness of variables is a bug.

Sorry for the double post. But I think the topic is so different that it needs a post of its own. got sidetracked before posting Umm is here anyone who can come up with a vessel and a Kerboscript that is capable of testing every command? Something we can use after each update so we can run a quick test on what is broken? It should be a collab project. http://forum.kerbalspaceprogram.com/threads/52004 anyone who is willing to help?

I use this forum cause I think its better than the wikia to communicate. Ok, that will be a collab project in the kos wikia. We are in need of a vessel and a kerboscript. The vessel should be able to keep up with the script but should kept as simple as possible. The script also should kept as simple possible but it should not only contain all commands but as much alternations as possible. It also should give a reliable feedback. hopefully print, log, and switch to will not break. Update: I created a Wikipage.

bugs in ksp / kOS. well if I am serious its not just one. Its Global warming/Climate change, Overpopulation and Sustainable Energy. Also critical but not as much as above Poverty/Distribution of wealth and Education. When fossil energy runs out and we haven't fixed our energy consumption / sources then Overpopulation will be fixed since Climate change and diseases will kill most poor and and or uneducated. (well uneducated means in most cases poor) Well, War ever was and ever will be there as long as we are humans. I think (its sad but true) that is part of our nature. If fossil really is running out ... then there will be war, and the war for the final resources will make look the WWII like a quarrel of kindergartners in a sandbox.

*blushes* Yes, true.Please feel free to correct any bad grammar / typo / spelling you come across. And if its not understandable what I am try to tell or if I use terms or proverbs wrong. You can also edit it, but if you not understand it yourself just add comment or open a thread in the wiki forum.

OK, I have found it. Lock steering works in general, but it seems that using variables in lock steering is broken! So while lock "lock steering to heading 90 by 45." works set pitch to 45. lock steering to heading 90 by pitch. does not. edit : umm ... in 0.82 it still has worked and I belive I got it to in a test program once... but now it don't. edit2: So I mean I also can confirm this for 0.83. edit3: wheelsteering is also broken.

Could you post the code? because in my case lock steering still works. I think it may the same is as with eta: in some cases it works in some not.

sorry, but that got fixed... maybe because it wasn't game breaking. I have some Versions from 0.5 on. I also have 0.8 but not 0.81. 0.81 was too fast replaced with 0.82. They are all on my google drive. See the issues page on the wiki. Edit: I think the code needs a complete overhaul. The eta thing is too wired. But I am too stupid to find out when it works and when not.

Well the funny thing is: I wrote a program with only three commands, and 4 lines. if eta:apopapsis > 10 {print "if ok".}. wait 1. when eta:apopapsis > 10 {print "when ok".}. wait 50. When sitting on ground and entered on the command line both if and when are fired. When sitting on ground and in program only when is fired. When flying both are fired. sorry no screeny of the flying version. But if I use orbit.txt (from space computer) which btw worked perfectly fine 0.7 then I get the unrecognized eta: term. I checked the code over and over again. I can't find an error. On the other hand I just proved that eta:apoapsis works .. on command line or programs...

Also locked variables also get only updated outside from loops when called. When not they stay at the last value. Edit: There is something really wired going on. While a in a program that I wrote eta:apoapsis works perfectly fine. It doesn't work in space computer anymore... in 0.7 it has! A moment I thought it has to do something with single and multiple lines, but that's also not true. stage. wait 10. print "after wait.". if eta:apoapsis > 10 {print "if 1 line ok". }. when eta:apoapsis > 10 then {print "when 1 line ok". }. wait 10. if eta:apoapsis > 10 { print "if multi line ok". }. when eta:apoapsis > 10 then { print "when multi line ok". }. wait 50. All lines were executed.

can't confirm that. Made a program to test the eta: problem in 0.82 and used manual throttle (cause I had known that that was broken) and it had 3 lock steering commands. lock steering to up + R(0,0,180). lock steering to heading 90 by 90. lock steering to heading 90 by 45. That worked like a charm... So not broken for me. Maybe only with mechjeb? edit: -=[ Does Your System Have Bugs? ]=- 4/97 .--. .--. _ ` \ / ` _ `\.===. \.^./ .===./` \/`"`\/ , | | , / `\|`-.-'|/` \ / | \ | \ .--. .--. .-' ,-'`| ; |`'-, '-. _ ` \ / ` _ | | \| | `\.===. \.^./ .===./` | | ;| | \/`"`\/ | \ // | , | | , | `._//' | / `\|`-.-'|/` \ jgs .' `. / | \ | \ _,' `,_ .-' ,-'`| ; |`'-, '-. ` ` | | \| | | | ;| | .--. .--. | \ // | _ ` \ / ` _ | `._//' | `\.===. \.^./ .===./` .' `. \/`"`\/ _,' `,_ , | | , ` ` / `\|`-.-'|/` \ / | \ | \ .-' ,-'`| ; |`'-, '-. | | \| | | | ;| | .--. .--. | \ // | _ ` \ / ` _ | `._//' | `\.===. \.^./ .===./` .' `. \/`"`\/ _,' `,_ , | | , ` ` / `\|`-.-'|/` \ / | \ | \ .-' ,-'`| ; |`'-, '-. | | \| | | | ;| | | \ // | | `._//' | .' `. _,' `,_ ` `

Oh ... I haven't seen that 0.83 is out.. edit found out throttle fixed (at least kevin says that) and eta: still broken.

Meh ... I wish the people would read all sources. See github. eta: is broken as well (in programs at least)

In the wiki http://kos.wikia.com/wiki/Mods I described a way to make all stock drone cores a kOS computer. That would work for radial parts like flight engineer, too Well, since the problems the current version has I have uploaded every version I had to google drive. Link in the wiki http://kos.wikia.com/wiki/Issues

So it might realistic to have that in the big engines. Like mainsail, or skipper. But that would generally not add a challenge. Well beside from that I am sure that a real rocket would have in that case a method to reduce the fuel consumption to a minimum without turning it off completely. We read the same article, yet we came to different conclusions. -------- Well at least it seems to add some new interesting aspects to the game while not really realistic. But on other hand its not my cup of coffee.

Is that realistic? I can't find source that states that liquid engines have limited ignitions. IMHO is it a electric spark that is doing the job. Like in any good old gasoline engine. And that is having a few thousand ignitions ... per second. (rpm/cylinder) So is it based on the real world or just for challenge? --------Edit below:------- From the German and English wikipedia I know now that are two kinds of liquid engines. One can not ignite itself and once it is turned off its over. >wikipedia=> "a pyrotechnic charge can be used, a plasma torch can be used" The other however can be ignited (almost) unlimited subtypes: wikipedia=> "or electric spark plugs may be employed. " wikipedia=> "Some fuel/oxidizer combinations ignite on contact (hypergolic)," wikipedia=> "and non-hypergolic fuels can be "chemically ignited" by priming the fuel lines with hypergolic propellants (popular in Russian engines)." I've just (while writing) realized that might be the one and only that is limited cause the amount of hypergolic propellants is also fairly limited. But I am not sure if its a one time ignition method.

Nice, we also discussed about that, but I think all of us would prefer to have the existing features working as intended before having new features. Having then (new features) are nice, but all for naught if the rest isn't working. Wait.. What? There are reddit challenges for kOS?

I didn't use lock variables for a while now, cause they where broken within loops. Maybe Kevin has worked on that, but since 0.82 (? dunno hadn't tested 0.8 -loops broken- and 0.81 -was too slow or 0.82 was released too fast- so far) Lock throttle and wheelthrottle is broken.

Neat... Feel free to make a wiki page

Oh, man. It works fine as long as you use it on the command line.... but in programs its broken.... and only for when. Its reported on git