John Dowson

This one: offsetStatus-v0.21.ods Try reading the manuals. For general lua information, use google. To find out how lua plugins work with FSUIPC, read the FSUIPC Lua Plug-Ins.pdf document. This also contains an overview of the provided examples. Then, for specific on the FSUIPC lua library, take a look at the FSUIPC Lua Library.pdf document. Also check-out the User Contributions and FAQ sub-forums on this support site.

As the message you quoted says, the spreadsheet comes in the zip file that you downloaded. The example lua programs can be found in your FSUIPC7 Documents folder, bundled together in a zip file called Example LUA plugins.zip. Of course all lua scripts are exited when you exit the Sim. FSUIPC7 also exits when the sim exits, if it is started by MSFS, and all programs started by FSUIPC7 will also exit. Why would you want to run anything when MSFS is exiting? Once the sim is exiting, there is nothing that can be done except shut-down gracefully.

It will - I will post a new one next week.

Yes, v7.2.0 is no longer in beta - it is now the latest and only supported version.

First, the format is incorrect - The offset cannot be both a signed word (SW) and an unsigned byte (UB). PLEASE see the documentation in the Advanced User guide for the format. I am not going to explain this yet again.... Second, you have added the lvar in general section (i.e. not profile specific) so it will try and get that lvar for every aircraft. It certainly won't exist for every aircraft, so you will get an error if the lvar cannot be found. Try listing the available lvars for your loaded aircraft using the Add-ons->WASM->List Lvars menu option.

For lvars, you can use the new lvars-to-offsets facility, available by editing the FSUIPC7.ini. See the Advanced User Guide for details and an example.

Yes, many. See the offset document spreadsheet - this gives the simvar names (where relevant) for the offset address. For reading/writing to these offsets via lua. check out the lua examples provided.

Spaces are optional in xml files, although help readability. The Logitech MSFS plugin has the same issue. There is an example of an EXE.xml for this in this support request: You just need multiple <Launch.Addon>...</Launch.Addon> sections, one for each application that you wish to launch. And make sure they are both within a <SimBase.Document> section.

I think it does, but I'm not sure if thats in the stable version yet. This video explains how to set up the throttles using the FlyPad/EFB, atarting at th1 10L20 maek:

You can read simulator variables that are held in offsets, using the lua ipc.readXXX functions. If the simvar is not yet held in an offset, you can request it to be added. John

Yes, thats the easiest way. Best to do this without FSUIPC running. That will only remove axis assignments for the currently loaded aircraft, so will only affect one profile (the one currently loaded). Yes, but the axis/button assignments are not updated then - they are updated when you close the FSUIPC window (click 'Ok').

First, you posted in the FAQ sub-form, where it states NOT for support requests. I have moved your post for you. Could you attach you FSUIPC6.ini please so that I can see your assignments. Also, activate logging for Axes Controls, and generate a short(ish) log with your a/c loaded and move your assigned elevator axis through its full range, and also move the axis assigned to the tiller through its full range. Close down P3D and attach the FSUIPC6.log file generated. Thanks. Also, which version of ProSim are you using? I don't use ProSim but Pete does, so he may be able to assist further if you let us known the ProSim version.

Only lvars can be accessed via offsets. I wasn't planning on adding hvars to offsets - there is no point really as they don't have a value (so could only be used for activating). I am planning to add an FSUIPC control to activate hvars, which would allow you to assign hvar activation to buttons and switches. But, for the time being, you will have to use either a macro file or lua to achieve this.

It hasn't been fixed yet. There are still issues with basic text display, let alone menus. The SimConnect_Text function is currently documented as: The SimConnect_Text function is not currently available for use. !

I don't think so if its a know issue with the switch. If there is a control (or controls) that is sent with a parameter that you can use to differentiate the OFF position, you could write a lua script to intercept this control (using event.control) and then maintain your own user offset with the correct value, and configure MobiFlight to use this offset instead.

I don't see much point in this, sorry. Yes, I think so. And I don't see this as an issue.

The FSUIPC WebSocket server provides a websocket interface to the FSUIPC offsets. You can't, as far as I am aware, retrieve anything else.

Btw, also check that you have controllers disabled in FSX....

Hmm, strange. Can you show me your latest FSUIPC4.ini and FAUIPC4.log files please.

FSUIPC populates these offsets with the data received from the PMDG SDK. If the value is not correct, you need to raise a support request with PMDG. However, before you do this, best to verify what these offsets actually hold via FSUIPC (not MobiFlight). To do this, use the offset logging facility for offsets 6430 and 6431, both as U8, and check what is logged for the different button positions. Also maybe log offsets 6436 and 6437.

To list the lvars, make sure you have the FSUIPC WASM module enabled, then just use the Add-ons -> WASM -> List Lvars... menu option to see all lvars and their values. Note that more lvars are available the longer the aircraft is loaded - you can issue a Reload command (again, from the WASM menu) to rescan and reload all lvars. [NB. There is also an ini parameter to the WASM called LvarScanDelay which you can increase to delay the lvar scanning - see the Advanced user manual for details on this). For the description of the lvars, you need to check the documentation for the a/c you are using.... However, there doesn't seem to be much of this available, especially for the stock aircraft. However, its usually pretty obvious what they are from the name. Note also that not all lvars are writeable - some are read-only. There is no way (that I know of) to determine if an lvar is updatable - you just have to try. I will also be releasing FSUIPC7 v7.2.0 later today (this has been available as a beta release for a while now). This has an additional facility to populate free user offsets with lvars for both read and write (where applicable). You may want to download and use this, once I've released. John

You could disconnect your device and just remove the registry entries for that device anyway, reboot and re-connect to get them added again. Take a backup of your registry first, and then save the following text in a .reg file (e.g. removeVPCStick.reg) and then execute by double-clicking: Windows Registry Editor Version 5.00 [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_3344&PID_4130] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_3344&PID_4130] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_3344&PID_4130] [-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_3344&PID_4130] As I said, I'm not sure if this is the issue or will help, but worth a try. Otherwise, just continue to use device 1, thats not really an issue.

Not unless provided by the aircraft, i.e. this data is available for the PMDG airliners via the PMDG SDK (for FSX and P3D). There is no provision in the SimConnect API for such data, so I don't think this info is currently available for any MSFS a/c.

No problem, updated again!

Ah, ok. I don't know why this is and cannot really look into it as I don't have such a device. Could it be that it has multiple registry entries (just a thought)? Anyway, if it works with device 1, just use that.