Erratic LED lights when trying to program MCP Pro

Slayer

I'm working on a profile for the Milviz 737-200, the problem I'm having is that when I set the light display data for a LED it seems to be hit and miss. I can use my function sometimes 4 times perfectly then either the light will stay on or not turn on when it should. It seems like sometimes GIT is missing the LVAR data and just showing it's last state. I've got the sliders in the program settings at their defaults , is there any kind of tweak I con do here to make it more responsive to changes in LVAR data?

Edit: button presses etc are detected ok, and reflect properly in the sim, just the LED lights on my MCPPro don't always behave

admin_pps

Hi,

When programming the device, this behaviour is normal. To reduce the amount of code that is executed the Goflight devices are only updated when data has changed.

A change is detected when the current data structure from simconnect contains differences from the previous data structure received. This happens many times a second so whilst you are programming the device, the chance to update the Goflight devices has been and gone.

You can force a change and thus a Goflight device update by making the variable change its value e.g. by turning something on and then off in the cockpit that would change the lvar or restarting GIT.

The other issue may be a too high polling interval in detective. In a recent release a slider has been added under the detective console which allows the sample rate to be adjusted. A too high sample rate can result in an lvar that is altered from say 0 to 1 and then back to 0 before its resampled and thus no change is detected.

Under normal use when flying the above issues do not exist.

Best wishes

Steve