[FSUIPC WASM module + client-side API + lvar/hvar discussion topic]

10 minutes ago, John Dowson said:

If they are grayed-out, this indicates that the WAPI IF is not active, usually because you are in a main menu on MSFS rather than having a plane loaded and 'ready-to-fly'. If you were in this state, try restarting FSUIPC7.

Also, if using beta facilities you should use the latest, which is now 7.1.0.e.

Nothing will work if the WASM menu entries are grayed-out, as the WAPI interface isn't initialised. Anyway, update and try again.
 

John, your the best,

I had the Model Behaviors window open to monitor the Lvar changes.

I have closed that and restarted FSUIPC7 and it works all.

I was indeed on version 7.1.0e, my mistake.

Now everything worked!!!

Thanks

[FSUIPC WASM module + client-side API + lvar/hvar discussion topic]

41 minutes ago, John Dowson said:

Yes, sorry, the lvar functions were removed as they previously weren't available. I've added this back now, and also added the new functions, but I haven't released the updated documentation yet. I will do this in the next beta release, including the installer, either later this evening or tomorrow.

You should still have the FSUIPC Lua Library.pdf in your documents folder, for the ipc.writeXXX functions. Here's the additional documentation:

 

Thanks John,

Tried it but cannot access the Lvars with the FSUIPC7  version 7.1.0d althoug i have the WASM module installed, can access and set Lvars with the testclient and have enabled the WASM module under Add-ons in FSUIPC7.

See that the other options in the WASM submenu  of FSUIPC7 (List Lvars, List Hvars Set Lvar etc) are all grayed out, only disable is available.

Also event.Lvar in my lua script is not triggered when the Lvar value changes, so i think i still have problems accessing Lvars via lua.

 

I used the lua documentation from FSUIPC4 and FSUIPC7 extensively, was only missing Lvar documentation.

Thanks for that.

[FSUIPC WASM module + client-side API + lvar/hvar discussion topic]

3 hours ago, John Dowson said:

No, but its pretty straightforward. Take a look at the Lua library documentation for event.lvar. In your processing function you just need to use one of the ipc.writeXXX functions (where XXX is the type of the lvar, usually a DBL but can also be an int or other type). For the offset, you can use 0x66C0-0x66FF, or 512bytes from 0xA000. So, try for yourself, and post again if you have any issues.

Hi John,

Where can i find this Lua Library ducumentation, the only Lua library documentation i find is the one i got with the registered version of FSUIPC7 but that doesn't mention Lvar support.

[FSUIPC WASM module + client-side API + lvar/hvar discussion topic]

On 4/13/2021 at 1:50 PM, Helibrewer said:

Ah, I see that now, thanks again and thanks for all the work on this. Looking forward to figuring out how to utilize this in lua scripts in the future.

Me too, also make intensive use of Aircraft dependant lua files to setup and handle things.

Eager to see this becoming available.

[Controls for G1000 from "Controls List for MSFS Build 999.txt" not working]

Thanks John,

Had time to try the mobiflight WASM module and it solved my problem.

Thanks for the tip.

I also found a lot of other controls which were listed in the aforementioned document that are not working e.g. zoom and zoom_fine and many others.

I asume this list was not checked to be valid?

 

regards, Leo

[Controls for G1000 from "Controls List for MSFS Build 999.txt" not working]

Hi Pete and John,

 

I can't use my buttons that are used for control of the G1000 which send the controls listed in "Controls List for MSFS Build 999.txt"

Also ZOOM_IN and ZOOM_OUT are not working.

These controls are listed in the "Controls List for MSFS Build 999.txt

the log shows the cotrols beeing send but no action happens

Is this list verified to be working?

Sorry if this support request is transmitted more than once, because i was unable to login first an was not sure if it was send.

Thanks for your beautiful program.

[USER offset Value as Parameter for Control]

Tested it tonight and worked like a charme!!!
My [button] area in the ini is a lot smaller now!

 

Thanks for the tip!

[USER offset Value as Parameter for Control]

Ok understand, thanks again.

Have to dig up my old programming knowledge a little bit because that's long long ago.

But think many examples can be found on Internet.

 

Leo

[USER offset Value as Parameter for Control]

Hi Pete,

 inrementing or decrementing 66C0 between 0 and 7 but only using value 0 and 7? Why not just have t toggline between 0 and 1?

No, i am using all the values for Incrementing and decrementing the Scale of the ND Display as you can see from the linenumbers, I just didn't want to clutter the post with all these lines.

Doesn't loading and executing a Lua plugin cost extra performance? The PMDG 737 eats already a lot of the performance of my system.

 

Anyway thanks for your time, maybe i will start experimenting with Lua.

[USER offset Value as Parameter for Control]

Hi Pete,

Thanks for your wonderfull program.

I have a (maybe dumb) question.

In my FSUIPC.ini make use of the Cyclic Byte Increment and decrement functions to incr/decr. user offset, which i then use as conditions in Button assignments.

But is it not possible to send the Value of this offset directly in FSUIPC.ini as parameter to the control assigned to a button press instead of using it as a condition which would save a lot of lines in my .ini file because i make extensive use of it. Also I don't like using LUA scripts, seems to me that this is at the cost of Performance (one more thing to load and execute).
Fastest way is directly in the button assignment in my humble opinion.

As example:

350=CP(+64,4)(+Y,8)(+Y,16)Y,2,Cx510066C0,x00070001     -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}-
351=CP(+64,4)(+Y,8)(+Y,16)Y,3,Cx610066C0,x00070001     -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}-
352=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,0     -{Custom control: <69993>}-   ;EFIS ND Scale
353=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,2,C70049,0     -{Custom control: <70049>}-
.....
366=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,7     -{Custom control: <69993>}-
367=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,2,C70049,7     -{Custom control: <70049>}-
368=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,0     -{Custom control: <69993>}-
369=B66C0=0 CP(+64,4)(+Y,8)(+Y,16)Y,3,C70049,0     -{Custom control: <70049>}-
.......
382=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,7     -{Custom control: <69993>}-
383=B66C0=7 CP(+64,4)(+Y,8)(+Y,16)Y,3,C70049,7     -{Custom control: <70049>}-

Wouldn't it be nice to replace it with:
350=CP(+64,4)(+Y,8)(+Y,16)Y,2,Cx510066C0,x00070001     -{offset byte cyclic inc, offset 66C0 (Incr=1, Limit=7)}-
351=CP(+64,4)(+Y,8)(+Y,16)Y,3,Cx610066C0,x00070001     -{offset byte cyclic dec, offset 66C0 (Decr=1, Limit=7)}-
352=CP(+64,4)(+Y,8)(+Y,16)Y,2,C69993,<VALUE OF B66C0>     -{Custom control: <69993>}-   ;EFIS ND Scale
353=CP(+64,4)(+Y,8)(+Y,16)Y,3,C69993,<VALUE OF B66C0>     -{Custom control: <69993>}-

Hope you can help me out here.

Thanks anyway for your time and great program!