Thanks for your answer. But honestly...... the problem with the altitude selector ......  that's not very consumer friendly: 1. I still don't understand why with the Bravo Throttle Autopilot NAV/HDG/SPEED/VS selectors work but the ALTITUDE selector not. 2. Why there isn't an easy to understand description in the documents how to implement the scripts with Axes and Ohs or with FSUIPC. 3. I remember some years ago there was a discussion about the small altitude font in the PFD and the desire to make it a bit bigger.  So one can read it in an easier way when trying to see PFD altitude and FCP altitude selector at the same time. It would be so much easier if the font is about 50% bigger. But the developer had no interest in changing that font......why ??  I really don't know! 4. Maybe an easy dirty solution: why don't you make a clickspots at the upper left edge of the PFD frame to decrease and a similar clickspot at the right edge to increase altitude.

Thanks for the utility, I had discovered it already and I have made sure on a windows box that the lights of my bravo indeed work, they do on windows. But no way to make them work in Steam atm, the christmas tree sees the bravo (it populates the leds list) but changing the lights commands don't do anything.    PS: is your login linked to the simware bought by aerosoft? I used to buy my sims from Simware 30 years ago ;)

Ich vermute, Andreas mein Autofeather. Aber Autofeather bringt den Flieger im Anflug nicht vom Kurs ab,

Nein, das habe ich nicht, die Verständnisfrage, die mich beschäftigt hatte und mir hinreichend beantwortet wurde, bezog sich auf Anflüge von kleinen Flugplätzen, die mir keine Frequenzen zur Peilung rückmelden.   Weiterhin habe ich mich auch nie richtig mit den Bordmitteln der Cessna ( GNS 430/530 ) beschäftigt. Hier insbesondere die Direkt Eingabe in Verbindung mit dem GPS + OBS Mode.    Gelernt und verstanden habe ich, daß das VAG die Funktion aufnimmt, wenn am GNS die Funktion GPS + OBS aktiviert wird.   Das war der Schlüssel zum Erfolg meiner Verständnisfrage zum Anfliegen kleiner Sportplätze.   Bislang waren meine gesicherte Anflüge mit VOR Frequenz erfolgreich   Lernkurve hier: Das Manual des GNS 530 bebilbert in das Deutsche  übersetzt.     Ja, das setzt es natürlich vorraus .      Und das unterschreibe ich auch

OK, thank you, I’ll check with rain. 

Hallo allerseits,   ich schick Euch morgen ein Script zu. Ich hoffe, es löst die Probleme 🙂   Andreas

That's how it works in the real plane.

Die Frage ist eher, wie, warum, wer es einschaltet. Die KA hat kein Autothrottle. Da hilft nur permanentes Überwachen und dagegenhalten. 🙂  

First of all, sorry I do not have screenshots since I create this post some hours after my last flight.   I made now 5 flights with it and altough many things did improve with the aircraft, things are still not up to standards. Im limitting myself only to autoflight and flight controls but there are more (like fsx like textures in the cockpit, etc).   1.) Takeoff does not feel correct all the times. Even tho I did set the trim correctly according to the efb, the nose tends to shoot up (or even autorotate) without flex settings. With Flex it does seem a bit better. 2.) Direct To does not calculate the best intercept path but does so from the current position. Therefore the airplane does overshoot and flies a 30 degree intercept towards the line drawn from the executed position. Vatsim controllers are not amused.. 3.) FMA != what the airplane does. I had the issue in v1 already, that sometimes the ILS seems to be active on the FMA and autopilot is in approach mode, it tends to deviate drastically from the actual beam. By deviating I mean it might be following a path which is 5 degree left or right of the beam leading to you missing the runway by miles. Happened once - in eddf 07R-Z. 4.) Transition from FMS to ILS which should occur automatically has as of 5 flights worked once - in all other cases I had to manually set it to the correct source. Not sure if that is the correct behavior 5.) Pitch control feels rubberbandish on approach. I dont have that weird feeling with the md80, the 320 (I know not the best comparison) and not with the HS cl650 in xplane. 6.) Fadec engines still overshoot the N1 limit in some cases but it tends to be better than v1. 7.) When you manage to get into overspeed and select a lower altitude, reduce the target speed and select speed mode the aircraft pitches down to around 7 degrees and completely ignores the speed you have set. Adding spoliers just makes it dive even more. I would expect it to slow to the target speed instead of YOLO'ing to its doom at 360 KIAS. 8.) Holds... While they are a major improvement since the first version the airplane still tends to perform kind of weird rectangular shapes sometimes. Nothing too bad but still something I noticed.   As of now every single flight something went wrong in one way or the other. Which is a little bit frustrating given the exceptionally long wait for an update to fix the issues which are here since the inital version.    Generally it is an improvement and its nice that AS finally starts to support their aircraft - which is a step in the right direction - but in comparison to your competition this aircraft still needs some work to be flyable.

It is working. Only shows rain - not clouds. Try it in a situation with rain. It is NOT a proper WXR radar.