Djeez

It works great. I see Lvars discovered in the log window but my event handlers on subscribed Lvars are not called, so no flickering anymore. Thanks for the fix! -Emile.

Hi John. Thanks for the reply. I installed the version as you indicated (showing 7.3.18b in the About box). Unfortunately, the problem is still there. Just before the "Lvars received: ..." line appears in the log, I see that the Lvars I subscribed to get a callback with parameter 0 and soon thereafter a callback with parameter 1, effectively making the LED's flicker for a moment. It is not critical, just annoying (every time it happens I have this little fear that my custom hardware fails...) so I can wait for a final version that fixes this. If you would like me to test a beta release I am very happy to do so. -Emile.

In my Lua scripts I use event.Lvar() calls to subscribe to Lvar changes to activate/deactive a corresponding LED. It seems as if an automatic Lvar rescan triggers the events: For every Lvar that was 1, I see two events: the Lvar being 0 and immediately thereafter the Lvar being 1 again. As a consequence, I see all LED's that are ON in my cockpit flicker whenever the number of Lvars changes. From the log file I can see this coincides with the change in number of LVars. 10220203 Lvars received: 4494 L:vars & 0 H:vars now available This flickering did not happen before 7.3.17.

For your information: I use the AXIS_STEERING_SET event (67466) for the nose steering (tiller). It takes 1 parameter in the range [-16383..16383]. Emile.

I can confirm that. Thanks to both of you. -Emile.

Sorry about not being clear. The Rotor brake controls do work. My intention is to light up LEDs when the A/P, A/T, or FMC button light up and for that I need to either inspect the offsets, or the LVars. What I see (as Hermann posted) is that the value is always 0, regardless of the state in the virtual cockpit on screen. This is for both the offset as well as the LVar, for all three (A/P, A/T, FMC). -Emile.

Indeed, these offsets do not work as expected, and neither do the corresponding LVar's, such as L:switch_3391_73X. It seems something is wrong at the PMDG side when exposing these states. -Emile.

This works great and is a very nice feature to have. I assume the myOffsets.txt is read during the FSUIPC startup? For development it would be convenient to have a reload myOffsets menu item in the FSUIPC7 interface just as there is one for the WASM reload. -Emile.

What you could do is provide an offset in which I can write in how many batteries I am interested. Since I know which plane is loaded, I set the number of batteries accordingly and it would be my responsibility to set the correct number. The default being 0 so that the bitwise offset is not populated when not requested. This is quite a hack and I can understand you are not fond of such a solution but honestly I don't think we can expect a solution from the SDK team at Asobo in short term. -Emile.

Thanks John. Getting errors on non-existent batteries and no way of knowing the number of batteries seems like a bad interface design on MSFS part. I appreciate you looking into this. Did you report this to the SDK team and would it help if I (also) report this? -Emile.

These is an offset for the Master Battery (0x3102) but MSFS2020 supports multiple batteries, such as in the default C172 (standby battery) or SR22 (master battery 2). When inspecting the log when toggling the switches I see (0x000102c1), Param= 2 (0x00000002) TOGGLE_MASTER_BATTERY (note the parameter 2) I could use the ipc.control with parameter 2 in my Lua script but I also need to know the state of the switch. The MSFS2020 SDK documentation shows that the SimVar needs an index so presumably this means that read and write access to all batteries is possible. My request is to make these settings available as offsets, or one offset with multiple independent bits set for every battery. Thanks! -Emile van Gerwen.

Thanks for thinking with me. My work-around is to call the control twice, once with parameter 1 and once with parameter 5. This looks weird but it does not seem to have any negative effect. Emile.

Hi, I can increase/decrease the barometric pressure in my Lua scripts by using controls 65883 and 65884 with parameter 1. However, in aircraft with a G1000, this control requires a parameter value 5. Is there a generic way to use these controls? If not, I can use either 1 or 5 as parameter but then I need to know if a G1000 is present in the plane. Is there a way to find that out? Thanks, -Emile.

It works for me in 7.0.8. Make sure you have the most recent version of FSUIPC because I remember there was a problem with earlier versions and ensure you write in BCD. -Emile.

Hi, I can confirm that the following offsets work correctly in FSUIPC 7.0.7, MSFS 1.14.5.0: 0x0BEC gear center position 0x0BF0 gear right position 0x0BF4 gear left position 0x0B46 transponder mode 0x0354 transponder code 0x034C ADF frequency main 0x0356 ADF frequency extension 0x311E NAV1 standby frequency 0x0350 NAV1 active frequency 0x3120 NAV2 standby frequency 0x0352 NAV2 active frequency 0x3122 radio audio, although the documentation in offsetStatus-v016.odt is a bit confusing. The Offset Status pdf is accurate. Furthermore, there is a noticable delay between in-game toggle and this offset change (about 0.75 seconds which is noticable when you click a button and the light does not come on immediately) -Emile.