Important Information regarding version 2.0.1129.0 of GIT

admin_pps

Hi,

Whilst producing support for the A2A C172 Trainer I have come across a number of bugs hence the regular updates this week. However one major issue was uncovered, that being that simconnect data was frozen in time (or blocked) whilst a bespoke event operated. What this meant was that simconnect variables used within a bespoke event would not indicate the correct state after an appropriate event was called. E.g. the AUTOPILOT_OFF event would not update the AUTOPILOT_MASTER variable.

This issue was obviously unacceptable because the bespoke events would not operate in a logical manner (it certainly had me scratching my head for a long time until I realised what was happening). This issue would also cause the confusion of having a perfectly workable bespoke event in Detective which would then not work when assigned to Goflight hardware (Detective did not run the blocking code).

I have fixed the problem, but you need to be aware that any bespoke events that you have created that reference simconnect variables may no longer work as expected (the variable will change state and not stay fixed).

If you still do not see simconnect variable changes in Bespoke Events then add a small Sleep task which will allow sufficient time for the data to be received and processed before checking or using a simconnect variable.

Any problems, please don't hesitate to raise the question here.

Best wishes

Steve