Problem subscribing to LVARs

[mmullernl]

Hi all,

I developed some instruments for the NextGen EMB-110 on MSFS2020 and for the autopilot (KMC321 and KAS297), which uses some specific LVARS instead of the MSFS2020 default ones, and I got an issue.
This was working fine then suddenly stop working, any LVAR that I try to subscribe I get nothing. I don't know exactly when it stopped working, but I saw this happening last week for the first time.

This is one example for the selected altitude from the KAS297.

https://github.com/marcelompaz/MsfsGaug ... c.lua#L218

But it is not working for any LVAR that to try to subscribe. Just a remark, I read it as Double because it was the only way that worked (I found a post in this forum about this). But even if I change to "feet", still nothing,
For the "H: events" is still working though. So in short, I can set everything but I cannot see any feedback on the display.

I don't know if is a problem with the aircraft, with MSFS or with AirManager.
The AM version I'm currently using is 4.1.6, MSFS 1.34.16.0 and the NextGen EMB-110 version is 1.6.0. For those 3, the only one I'm sure that was not updated after I used the instruments successfully is the NextGen airplane proper. So I would guess is not a problem with the 3rd party airplane.
I don't remember if any update happened on MSFS or with AirManager before the instruments stopped working.
Is someone aware of any issue of this kind?

Thanks

KR
Marcelo

[mmullernl]

Well, after searching more for similar problems in the forum I found someone complaining of a similar issue on the AM 4.2 Beta Bugs thread. In a first moment I ignored because I was not using 4.2 but then I thought that it could be a similar issue. The solution proposed was to upgrade the MSFS 2020 plugin to version 4.1 (I don't know which version I was using, maybe 4.0) and it worked
So no need to further investigate the problem and if someone else find the same issue (on 4.1 or 4.2) the solution is just to update the MSFS2020 plugin to 4.1 or more recent. Just for curiosity I tested with AM 4.2 and I got the same issue (before the plugin update).