This post is really a great source of information. I have already tried several of the solutions, and it’s a great learning experience. I think that step by step I’m starting to understand better. Thanks a lot!!!
@davux3 I wanted to look at your fs-gauge-bridge, but what I don’t understand is that you seem to put the wasm module in the “Panel” folder, and not in the “Community” folder? Is there a reason? Can I also put it in the Community folder like the other WASM modules mentioned in this post (example MobiFlight, FSUIPC)
@ImpoliteGem5317 I have successfully used your WASM module and client to experiment with the native A320_Neo. So far the only one that worked! Because of that, it will be a good starting point to look into your code and better understand the internals. I downloaded both the WASM and the client source code, and will have a look at it.
One question I have is why I couldn’t use the H-var “H:A320_Neo_MFD_BTN_CSTR_1”. If I use that, nothing happens. Although, if I push the CSTR button with my mouse, the green light goes on, but not if I use the “Set HVAR” menu in your client. I could successfully set other HVars such as all the buttons of the CDU, so “Set HVAR” is definitely working.
@Umberto67 You gave a good explanation of all the variables. But what I miss is the type “B”. On the native A320_Neo I find for example “B:ELECTRICAL_Battery_1_Toggle” (the BAT1 button on the OVHD). But what is a B-type, and how can we access it? If I want to toggle the BAT1 switch, how do I do that?
Am I correct to conclude that the WASM module is only used for L-Vars and H-Vars? The other types have to be managed directly with SimConnect? With other words, WASM has to be seen as an “add-on” on SimConnect, to allow controlling L-Vars and H-Vars? If I use the FSUIPC client application, it has also an “Execute_Calculator_Code”, which I could successfully use with L and H vars, but can I use that for other types as well? I tried with the B-type in it, but my Battery switch is not toggling.