VentZer0

I still have this weird bug in KSP 0.90 : - having a mobile SAM on ground, in guardmode with engagement range 15km - physics range 50km - flying in aircraft into range of the SAM - first missile gets fired, tracks me, no problems - second missile fires but sticks to the launchplattform while it's motor is running OR launches in slowmotion and explodes after it cleared the launch-ramp and explodes destroying the launchplattform in the process This is happening since the last version I think, for me at least. This problem does not happen when the missiles get fired from a airborne launchplattform only groundbased launchplattforms have this problem.

I would love to see a B9 and/or SP styled Cockpit like the one you already have in here but a bit longer (like Bahamutos MK2 Lightning cockpit) and without any intakes. That'd be awesome ^^

It would also be possible to differenciate between friend and foe on the radar screen, would a bit more code intensive but it would work. And I can override the weaponmanagers targetting.

I think yes. I can check if the craft is on the ground or below a certain altitude ( need to find outif I can check altitude for above ground level instead of above sea level). Please explain your second question, I do not understand what you mean.

I'm not talking about the BD target aquisition, I mean the normal targets you can assign yourself and BD tracks those targets if you fire a missile. I have the code to arm select and fire missiles, but if I cant select a target for a vessel im not controlling then the whole thing doesn't work. And I quite frankly do not like the guard mode at all, it is not really smart. Ah ok so I can check if I have a target, nice ok pursuit radar mode comes next :B Damn, I just checked it, I cant check if a variable exists or not, so I either have to set a target before I can check it or the program encounters an error. I hope they fix this issue, since its not good to have no means of telling if a variable is set or not.

Yep, I believe that is entirely possible. I cant determine if you have targetted something or something is targetting you, so no RWR or pursuit-tracking modes yet. They dont have that ability in kOS yet. I am currently working on an autopilot that will pilot my test drones and later they will even evade missiles and engage you autonomously. Though dogfighting would be impossible I think.

Here's something I made with kOS and had some fun testing it with BDArmory. Yes it's a RADAR screen! It still has a glitch that the script breaks when you hit something, but up until then it works like a charm. Y axis distance X axis degree offset from nose of the radar Numbers on contacts are HEADING (taken out because it's your heading not the targets heading) ALTITUDE (ft) SPEED (m/s)

Thanks man! I appreaciate your help and hope it will get fixed soon Also I would love to see the ability to target a craft using kOS and check if a craft (yours or other) has a target selected, that way I could go further with the RADAR and have some pursuit-tracking modes instead of general scan mode. It would also enable me to have something like a RadarWarningReceiver (RWR tells you if you are locked by an enemy or friendly radar/missile/etc) checking if you are being targetted (very useful for me, I dont know if it could be useful for others). Edit: It would be nice if we could have a check if a variable exists or not like you can do in c++ for example something like this: IF x isNil {SET x TO y.}. I think that might be easier and more elegant to check than to add another suffix. I tried to add a more detailed information to my RADAR, by displaying current target information .. problem is you cant check if you have a target. IF TARGET:NAME IS NOT NIL { display target info code } ELSE { do nothing }. Something like that.

Ok I played around with the WAIT time before the LIST ... command. It seems that this actually has something to do with it, the longer it was the fewer the occurancies of the error. You can see the error at the very end of the video. That is the only error message I get, nothing else just these two lines even when I don't have anything else printed in the terminal window. It is weird. If you can tell me where to find the error log for it I will look there, or how to log the output somewhere.

It is interessting This generates an error. LIST TARGETS IN contacts. FOR contact IN contacts { IF contact:DISTANCE < 90000 AND ABS(contact:BEARING) < 45 { PRINT contact:NAME. }. }. This does not. LIST TARGETS IN contacts. FOR contact IN contacts { PRINT contact:NAME. }. First thing will break up directly after all the debris appears, the other one just goes thru without problem. If I could check if the part actually has a :DISTANCE suffix that would maybe be enough to fix this bug. Moar testing ... LIST TARGETS IN contacts. FOR contact IN contacts { WAIT 0.1. IF contact:DISTANCE > 0 { SET VDIST TO contact:DISTANCE. SET VBEAR TO contact:BEARING. SET VNAME TO contact:NAME. IF contact:DISTANCE < 90000 AND ABS(contact:BEARING) < 45 { IF contact:BEARING < 0 {SET X TO 1 + (24 - ROUND(ABS(contact:BEARING / 45) * 24)).}. IF contact:BEARING > 0 {SET X TO 1 + (24 + ROUND(ABS(contact:BEARING / 45) * 24)).}. IF contact:BEARING = 0 {SET X TO ROUND(contact:DISTANCE / 1000).}. SET Y TO (30 - ROUND(contact:DISTANCE / 3000)). IF NOT (VNAME = "AIM-120 AMRAAM Missile (fired)" OR VNAME = "AIM-9 Sidewinder Missile (fired)" OR VNAME = "AIM-54 Phoenix Missile (fired)") { PRINT " " + ROUND(contact:HEADING) AT(X,Y-1). PRINT "U " + ROUND(contact:ALTITUDE) AT(X,Y). PRINT " " + ROUND(contact:AIRSPEED) AT(X,Y+1). } ELSE { PRINT "." AT(X,Y). }. }. }. }. Doesn't work either, IF contact:DISTANCE > 0 gives an error. I wonder why. Is the distance not a number in this instance or is it too quickly gone. I wonder. It is definitely the :DISTANCE SET counter TO 0. UNTIL counter = 10000 { LIST TARGETS IN contacts. FOR contact IN contacts { PRINT contact:NAME. PRINT contact:DISTANCE. }. SET counter TO counter + 1. WAIT 0.001. }. That gives an error.

Ok I now changed it to this : SET counter TO 0. UNTIL counter = 10000 { CLEARSCREEN. LIST TARGETS IN contacts. FOR contact IN contacts { IF contact:DISTANCE < 90000 AND ABS(contact:BEARING) < 45 { IF contact:BEARING < 0 {SET X TO 1 + (24 - ROUND(ABS(contact:BEARING / 45) * 24)).}. IF contact:BEARING > 0 {SET X TO 1 + (24 + ROUND(ABS(contact:BEARING / 45) * 24)).}. IF contact:BEARING = 0 {SET X TO ROUND(contact:DISTANCE / 1000).}. SET Y TO (30 - ROUND(contact:DISTANCE / 3000)). PRINT "." AT(X,Y). }. }. PRINT "90" AT (0,0). PRINT "-" AT (0,3). PRINT "-" AT (0,7). PRINT "60" AT (0,10). PRINT "-" AT (0,13). PRINT "-" AT (0,17). PRINT "30" AT (0,20). PRINT "-" AT (0,23). PRINT "-" AT (0,27). PRINT "0" AT (0,30). PRINT " | | | | | | | | |" AT (0,31). PRINT " 45 22.5 0 22.5 45" AT (0,32). SET counter TO counter + 1. WAIT 0.01. }. Still the same error occurs. :/ I didnt use VESSEL this time. I also noticed that the impact of the missile causes alot of debris to appear which vanishes shortly after, I guess because of explosive/thermal damage of the explosion (I made the script pit out all the targets as a continously scrolling list. Went like this : SHIP MISSILE (update) SHIP MISSILE (update) SHIP MISSILE(vanishes) (update) SHIP(hit) (update) SHIP DEBRIS SHIP DEBRIS SHIP DEBRIS (update) SHIP(remains) (update) SHIP (update) SHIP (update) etc. It is weird If I do not perform any contact:SOMETHING calls then it works, but it will not give me anything that I can work with.

Ok I just tried it and it didnt work, it gave and error about 'SET VDIST TO VESSEL:DISTANCE.' so it basically threw a tantrum about the first line of code in the FOR loop. I will try a longer wait time in at the start and try again. Yeah VESSEL:LOADED doesnt seem to work at all :/ The error I get is always the first line in the FOR loop. "At test on 1, line 20 SET VDIST TO VESSEL:DISTANCE."

So I made a radar screen, works so far but I have one problem. As you can see I get an error at the end, I dont know why really, maybe because the script runs while the missile is destroyed? Here is the code for the RADAR: SET counter TO 0. UNTIL counter = 10000 { CLEARSCREEN. PRINT "90" AT (0,0). PRINT "-" AT (0,5). PRINT "60" AT (0,10). PRINT "-" AT (0,15). PRINT "30" AT (0,20). PRINT "-" AT (0,25). PRINT "0" AT (0,30). PRINT " | | | | | | | | |" AT (0,31). PRINT " 45 22.5 0 22.5 45" AT (0,32). LIST TARGETS IN radar. FOR VESSEL IN radar { IF VESSEL:DISTANCE < 90000 AND ABS(VESSEL:BEARING) < 45 { IF VESSEL:BEARING < 0 { SET X TO 1 + (24 - ROUND(ABS(VESSEL:BEARING / 45) * 24)). }. IF VESSEL:BEARING > 0 { SET X TO 1 + (24 + ROUND(ABS(VESSEL:BEARING / 45) * 24)). }. IF VESSEL:BEARING = 0 { SET X TO ROUND(VESSEL:DISTANCE / 1000). }. SET Y TO (30 - ROUND(VESSEL:DISTANCE / 3000)). IF NOT (VESSEL:NAME = "AIM-120 AMRAAM Missile (fired)" OR VESSEL:NAME = "AIM-9 Sidewinder Missile (fired)" OR VESSEL:NAME = "AIM-54 Phoenix Missile (fired)") { PRINT " " + CEILING(VESSEL:DISTANCE/1000) AT(X,Y-1). PRINT "U " + CEILING(VESSEL:ALTITUDE/1000) AT(X,Y). PRINT " " + CEILING(VESSEL:AIRSPEED) AT(X,Y+1). } ELSE { PRINT "." AT(X,Y). }. }. }. SET counter TO counter + 1. WAIT 0.1. }.

I am curious how this will turn out. I'd like to suggest in terms of functionality that you also keep people in mind who are more into planes and like to autopilot them. Like me for example Currently I am working on a autopilot in kOS for my drone planes (which are targets for my missile tests) and I have serious issues with steering the plane into turns and have them turn at ~0 vertical speed, ALT hold while turning. I would love if you could implement some smart PID-controller function. That way it would also be very easy to have a SAS alternative tailored to your craft, since SAS and FAR/NEAR do like eachother, planes start to oszillate extremely at some point with FAR or NEAR. With a PID function it that we could tie into the controls this behaviour could be avoided.

I am having a really hard time understanding how one can get information about ship part modules, I am trying to get the different things I can do with a certain part on my craft namely: BDArmory's WeaponManager, the Ship:Part is called 'missileController' but I can't seem to get the actions I can do with this part through right click interactions. I've consulted the manual, but the examples didn't really help me. I get errors that I cant have this or that prefix/suffix for the part... etc. I am really at a loss here Listings are very confusing to say the least IMO.

Yep, I fixed it with a radioisotope generator in my craft, all it does now is that it will restart the terminal. Before it made the whole plane completely unresponsive once the juice ran out.

meh I wasnt aware of this, trigonometry was never my cup of tea, but yeah that should work SET dist TO sqrt((spot1:distance)^2 + (spot2:distance)^2 - 2 * spot1:distance * spot2:distance * cos (spot1_2_angle). SET spot1_2_angle to (spot1:bearing - spot2:bearing). you might need to fiddle around with spot:bearing and a lil IF magic to sum them up correctly, and depending on situation there could arise problems

Exactly using a bit of tangens, but this only works if there is a 90° angle somewhere, I tried to calculate the other sides but had no luck. the information you have in this case is not enough to calculate the triangle entirely.

just have the 2 spots use the function :distance. example: print spot1:distance. print spot1:bearing. print spot2:distance. print spot2:bearing. now you have distance to each and angle between the two. from that you can form a triangle and calculate the rest. btw there are approximations for sinus functions, if the angle IN RADIANS is very small then sin(angle) ~ angle. that is if the angle IN RADIANS is below 1.

Whats the deal with SHIP:HEADING ? I not get any degrees instead I get numbers in the area of X*10^-6 or smaller. SHIP:BEARING gives me degrees however.

Hello, I made a little aeronautic attitude observation system, basically it gives you information about, ASL/AGL/Speed/Machnumber/Roll angle/Pitch/actual flightpath Pitch/Angle of Attack/G-Forces. Right now its all embedded in a UNTIL loop because I use it to visualize flight parameters with the vectordraw function. You can just delete the Loop and the vectordrawing information and just go with the attitude sensoric stuff and use that as seperate program your for example autopilot executes to determine which way the plane is heading rolling or what other flight parameters are. SET counter TO 0. UNTIL counter = 1500 { SET counter TO counter + 1. SET anArrow1 TO VECDRAW(). SET anArrow1:VEC TO SHIP:FACING:FOREVECTOR. SET anArrow1:SHOW TO true. SET anArrow1:START TO V(0,0,0). SET anArrow1:COLOR TO RGB(1,0,0). SET anArrow1:SCALE TO 20. SET anArrow2 TO VECDRAW(). SET anArrow2:VEC TO SHIP:FACING:STARVECTOR. SET anArrow2:SHOW TO true. SET anArrow2:START TO V(0,0,0). SET anArrow2:COLOR TO RGB(0,1,0). SET anArrow2:SCALE TO 10. SET anArrow3 TO VECDRAW(). SET anArrow3:VEC TO SHIP:UP:VECTOR. SET anArrow3:SHOW TO true. SET anArrow3:START TO V(0,0,0). SET anArrow3:COLOR TO RGB(0,0,1). SET anArrow3:SCALE TO 10. SET anArrow4 TO VECDRAW(). SET anArrow4:VEC TO SHIP:FACING:TOPVECTOR. SET anArrow4:SHOW TO true. SET anArrow4:START TO V(0,0,0). SET anArrow4:COLOR TO RGB(1,1,1). SET anArrow4:SCALE TO 10. SET anArrow5 TO VECDRAW(). SET anArrow5:VEC TO SHIP:VELOCITY:SURFACE. SET anArrow5:SHOW TO true. SET anArrow5:START TO V(0,0,0). SET anArrow5:COLOR TO RGB(0,1,1). SET anArrow5:SCALE TO 0.1. SET anArrow6 TO VECDRAW(). SET anArrow6:VEC TO VCRS(-1*SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR). SET anArrow6:SHOW TO true. SET anArrow6:START TO V(0,0,0). SET anArrow6:COLOR TO RGB(1,1,0). SET anArrow6:SCALE TO 10. // IMPORTANT PART, IF DO NOT NEED THE UNTIL LOOP OR VECTORDRAW DELETE EVERYTHING ABOVE SET c1 TO (90 - VANG(VCRS(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR),SHIP:FACING:TOPVECTOR)). // roll SET d1 TO VANG(SHIP:FACING:TOPVECTOR,SHIP:UP:VECTOR). // angle between UP and TOP SET e1 TO VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR). // pitch SET e2 TO VANG(SHIP:VELOCITY:SURFACE,SHIP:UP:VECTOR). // flightpath pitch SET f1 TO VANG(SHIP:FACING:FOREVECTOR,SHIP:VELOCITY:SURFACE). // angle of attack SET g1 TO (SHIP:SENSORS:ACC:MAG / SHIP:SENSORS:GRAV:MAG). // GFORCE IF VANG(SHIP:FACING:TOPVECTOR,SHIP:VELOCITY:SURFACE) < 90 {SET f1 TO -1*f1.}. IF VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR) < 89 { // check nose up IF VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR) < 5 { // check pitch limit up SET c1 TO 0. SET d1 TO 0. // VERTICAL UP } ELSE { IF d1 < 90 { IF c1 <= 1 AND c1 >= -1 { // NOSE UP LEVEL } ELSE { IF c1 > 1 { // left }. IF c1 < -1 { // right }. }. }. IF d1 > 90 { IF c1 <= 1 AND c1 >= -1 { // NOSE UP UPSIDE DOWN } ELSE { IF c1 > 1 { SET c1 TO (180 - c1). // left }. IF c1 < -1 { SET c1 TO -1*(180 + c1). // right }. }. }. }. } ELSE { // nose down IF VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR) > 91 { // check pitch limit down IF VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR) > 175 { SET c1 TO 0. SET d1 TO 0. // VERTICAL DOWN } ELSE { IF d1 < 90 { IF c1 <= 1 AND c1 >= -1 { // NOSE DOWN LEVEL } ELSE { IF c1 > 1 { // left }. IF c1 < -1 { // right }. }. }. IF d1 > 90 { IF c1 <= 1 AND c1 >= -1 { // NOSE DOWN UPSIDE DOWN } ELSE { IF c1 > 1 { SET c1 TO (180 - c1). // left }. IF c1 < -1 { SET c1 TO -1*(180 + c1). // right }. }. }. }. } ELSE { // nose level IF d1 < 90 { IF c1 <= 1 AND c1 >= -1 { // LEVEL } ELSE { IF c1 > 1 { // left }. IF c1 < -1 { // right }. }. }. IF d1 > 90 { IF c1 <= 1 AND c1 >= -1 { // LEVEL UPSIDE DOWN } ELSE { IF c1 > 1 { SET c1 TO (180 - c1). // left }. IF c1 < -1 { SET c1 TO -1*(180 + c1). // right }. }. }. }. }. // YOU CAN DELETE ALL THIS IF YOU DO NOT USE THE UNTIL {} FUNCTION CLEARSCREEN. PRINT "ASL : " + ROUND(SHIP:ALTITUDE). PRINT "AGL : " + ROUND(ALT:RADAR). PRINT "SPEED : " + ROUND(SHIP:VELOCITY:SURFACE:MAG*3.6). PRINT "MACH : " + ROUND(SHIP:VELOCITY:SURFACE:MAG/343,2). PRINT "ROLL : " + ROUND(c1,1). PRINT "PITCH : " + ROUND(90 - e1,1). PRINT "PITCH : " + ROUND(90 - e2,1). PRINT "AOA : " + ROUND(f1,1). PRINT "G-FORCE : " + ROUND(g1,1). wait 0.01. }. This is how it looks in action : http://imgur.com/a/vzY2F#0 sidenote: how do I embed imgur galleries?

Very good, that's what I need. Now I can actually code my atmospheric drone autopilot. My attitude detection system works nicely, eventhough its so simple ... SET counter TO 0. UNTIL counter > 1000 { SET counter TO counter + 1. SET a1 TO VANG(SHIP:FACING:STARVECTOR,SHIP:UP:VECTOR). SET a2 TO VANG(-1*SHIP:FACING:STARVECTOR,SHIP:UP:VECTOR). SET b1 TO VANG(SHIP:FACING:STARVECTOR,SHIP:BODY:POSITION). SET b2 TO VANG(-1*SHIP:FACING:STARVECTOR,SHIP:BODY:POSITION). SET c1 TO VANG(VCRS(SHIP:FACING:FOREVECTOR,SHIP:FACING:STARVECTOR),SHIP:UP:VECTOR). SET d1 TO VANG(SHIP:FACING:FOREVECTOR,SHIP:UP:VECTOR). IF ROUND(d1) = 90 { CLEARSCREEN. PRINT "pitch attitude level". } ELSE { IF ROUND(d1) = 0 { CLEARSCREEN. PRINT "pitch attitude : straight up". } ELSE { IF d1 < 90 { CLEARSCREEN. PRINT "pitch attitude : nose up". }. }. IF ROUND(d1) = 180 { CLEARSCREEN. PRINT "pitch attitude : straight down". } ELSE { IF d1 > 90 { CLEARSCREEN. PRINT "pitch attitude : nose down". }. }. }. IF ROUND(a1) = 90 AND ROUND(a2) = 90 { PRINT "wing attitude level". } ELSE { IF a1 < a2 AND b1 > b2 { IF ROUND(c1) < 90 { PRINT "wing attitude : rolled left". } ELSE { PRINT "wing attitude : overrolled left". }. } ELSE { IF a1 > a2 AND b1 < b2 { IF ROUND(c1) < 90 { PRINT "wing attitude : rolled right". } ELSE { PRINT "wing attitude : overrolled right". }. }. }. }. wait 0.01. }.

I see, so the individual SCS parts act as if they are an independent system? One variable called the same thing running on 2 different SCS parts will not interfere? Good then I should have no problems in theory. In the context of using run/function calls what do you mean with global here, global for the SCS meaning a variable set in the main program and a variableset within the run/function called the same, will override the first one for this SCS part or all of them in universe?

Local to the vessel, I had to crafts using the same programm, executed an volume 1 from each craft and their behavior at points were VERY weird You answered my next question already, there is no way I can have 2 scripts running on the same craft at the same time, right? Or what happens if I have a 'run xyz.' in my program that executes a special portion of code and then what happens when it ends, does it continue with the program it was called from ?

oh YESSSSSSSSSSSSSSSSS *_* btw is there progress on local variables?