After working perfectly for the last six months or so, suddenly all of my C gauges are incrementing by 10's!Does anyone have any idea why? Nothing changed from this morning to this evening, but they are all FUBARed... :(Default gauges are working just fine, but Airspeed bug, heading, course, altitude set, etc. are all screwed up...

Show us a pic of your problem.Cees

could it be FSUIPC ? that fix control acceleration thing ? :)

After spending until 3am this morning moving gauges one by one into the panel folder of the a/c (which was complicated by so many shared variables!), I finally narrowed it down to one, rather complex gauge. It was the Engine_Electrical gauge which had somehow become corrupted by one bit or so during the final compile yesterday morning.It was a STRANGE problem introduced, because it affected the MODEL as well! Exit 2's animation was disabled, in addition to the increment problem... ???Ah well, all's well now. Thanks for the suggestions!

Call trigger_key_event so often?

>Call trigger_key_event so often?I've never discovered exactly what the problem was. Simply recompiling the same code cleared up whatever it was that had become corrupted. I've probably compiled that one gauge a thousand times over the last eight months and never had any problems.That's precisely how I knew that it was simply a case of "compiler corruption," although I don't which bit got twiddled... :)