It’s the little things that bug me - like the C172 Clock Backlight. ( especially when I should be able to fix it myself, but can;t figure it out )
C172 Classic – The LCD’s Clock’s backlight.
The backlight stays ON, even when the battery is OFF, and the engine /alternator not running.
(ie Cold and dark – but not completely dark)
It is controlled by the Panel LT rotary control, and ignores that battery is OFF.
(If left for some time, this would flatten the battery . might takes ages, but it has to be wrong).
So where is it going wrong the JS / Css, and what needs to be changed to fix it ?
Its such a minor & unimportant thing that it has to be right on the bottom of the list for Asobo to fix, but it will take a smarter cookie than me to figure it out as a user Mod.
“If you want the job done, and you want it done right – do it yourself”
ie: Ref the C172 Classic
The Reversed Ammeter.
The AP that does not init it’s VS to planes VS
The AP whose “ALT Arm” does NOTHING (no JS code to process this at all )
The AP that uses the Transponder’s Baro reference and not it’s own adjustable one.
The Transponder whose Baro ref gets set by the B key, when it should remain at Std Pressure, and always display FL (not altitude above MSL)
The Dim, incorrectly aimed, & inadequate Landing & Taxi lights.
The “wimpy” twinkling Strobe Lights
The list goes on - All really simple stuff, that should never have got missed during pre-release testing, where it would have been so much easier to correct then, than now after release.
As with most things, far less costly to get it right the first time (when coding & testing), than to have to go back and correct it later.
The GNS530 & GNS430 have been amazingly moded by the GNS5330 Mod ( @ScorpionFilm422 ), and with the above list if “issues” temporily resolved by a Mod, the C172 Classic is an absolute pleasure to fly in MSFS.
Access to the .fsarchive .cfg files (and .xml files) would allow the plane to become near “Perfect”