I have created a basic autopilot with funky trees for use in some of my crafts. If you wonder how the autopilot system works, you have to understand these basic flight data functions.
.
There is a flight data function named RollAngle (in degrees). You may notice how this is used in the roll indicator of the gauge. If an aircraft roll right, the indicator “needle” may roll right. Configure this into the ailerons and you will have a system where if the aircraft rolls, then the the ailerons automatically cause the aircraft to roll in the opposite direction. When the aircraft rolls in the other direction, the ailerons automatically act again to roll the aircraft in he opposite direction and the system flip flops and you get an aircraft that stabilizes it’s roll angle by itself. Note that the same can be applied to other flight data functions PitchAngle for the pitch angle and Heading for the heading (both also in degrees).
.
I’ll give out a function from a code from one of my crafts:
(RollAngle / 4) + (10 * Roll)
Let’s see how this works:

• The RollAngle function is what we already described before. However, do note that ailerons with this function may vibrate if you did not reduce the amount, hence why this function is divided by 4. Any more than 4 and the RollAngle function becomes less powerful and may affect how the aircraft stabilizes it’s roll angle by itself.
• The Roll input counters the RollAngle function and will allow the aircraft to roll until a specific degree, provided that it has a given amount enough to counter the power of the RollAngle function (in this case, said Roll input is multiplied by 10).
• The brackets are essential, because it prioritizes counting in the brackets first before counting the others (remember PEMDAS).

That is all I have got for you. Good luck. :)

@Mekomara
no prob, happy to help.

@ZeroWithSlashedO ah i had a smooth brain moment and totally forget sp uses m/s. My bad, it works now. Thanks for help again ^^

@Mekomara
are you below that speed? Reminder that SP uses metric as raw data. Speed is actually in m/s. If you're using km/h, go to calculator and divide the number by 3.6.

@ZeroWithSlashedO I managed to do the stall thingy, seems like it has some problems.

(GearDown ? 0 : IAS<300) & (APUAct | (MainElectricityAct & SystemElectricityAct))

Beacon lights up as soon as i retract landing gears. Am i missing something?

Also checked the camera, however seems like the code it uses is not much different from what i use at the moment. But thank you anyways!

• Check out this
• First of all, collect data. Get to know your aircraft first and how much speed does it starts to stall. Then get a beacon light or a text.
  
  
  
  • If you get a beacon light, use this: GearDown ? 0 : (IAS<(whatever speed it was)). Haven't actually tested it yet, but I'm sure it'll work.
  
  
  • If you get a text, type this: {GearDown ? "(put fcs ready or smth you want here)" : (IAS<again, whatever speed it was> ? "STALL" : "(smth you want here)}. Again, haven't actually tested it, but it revolves around speed.
  
  
• Damage part indicator is possible, but it is way beyond my reach.
• Again possible, but beyond my reach.
• Currently unable. The only way for a parking brake is to just hold down the brake until the day you die or restart the sandbox.
• Autopilots are pretty hard to do. The only thing I could think off is the PitchRate/40, and trim up input. While yes, it is possible with gyro, but gyro doesn't let you turn. Well, at least that's my impression after using it for once and never again.

you can do basic autopilot with trim up and a gyro