John Dowson

Sorry, you don't need to edit the ini for this. Just assign your throttle direct to FSUIPC calibration and select a throttle axis, and with your throttle at 4% set the lower limit, and at 74% set the upper limit in the throttle calibration page..

But I thought your issue was when calling any lua script (e.g. your simple example) on a button press? If you were doing that on repeat, that would certainly be problematic as the lua is compiled before being executed and then ran, and the repeat would kill the running thread and start this again... Best to use event.button directly for such luas, rather than by direct FSUIPC asignments. Anyway, sorry for the delay in this - I've been busy working on the lvar WASM module. I can take a look at this over the weekend if its an issue, but I think i need more details on what you are actually trying to achieve. John

Maybe try logging the value of next_waypt_info after reading it to see what it contains, and/or having a final 'else' to set to "UNKNOWN" .

Sure - use the attached key file. Just drop it into your FSUIPC7 installation folder. It is valid for 5 days: FSUIPC7.key Hmm. It may be possible by assigning direct to FSUIPC and calibrating, and then manually editing the ini to change the calibration entry to decrease the throttle's value range. You would want to set the range in the calibration entry so that the value sent when at 74% physical position is the full throttle value. However, when you pass the 74%, larger values will then be sent...presumably these will be ignored (and not produce an error) but give it a go. Also, please see the User Guide for details on calibration, although you won't find details on how to do what you want to achieve. Try setting it up and if you have any issues, post your FSUIPC7.ini file here and I'll take a look (but only after you have at least assigned and cailbrated!). John

No problem. You could try looking at the MobiFlight WASM module, and adding the MobiFlight events to FSUIPC. They may have some events/controls for the functions you require (especially for the A320). Also, check out the FBW A320 mod if you haven't done so already. For information on MobiFlight WASM module and events, see: and The lvar-access (and hvar) WASM module for FSUIPC7 is progressing well, but it will be another few weeks before I can get a beta version of this out to test. John

I took a look at the code for this as well, and its just a direct copy from the simvar to the offset, as Pete says. So if its empty, we are getting an empty value/string through from SimConnect for that simvar. The code in FSUIPC6 and FSUIPC7 is the same for this offset. Try logging the offset in both FSUIPC6 and FSUIPC7 and compare the output.

There's an online converter for that: https://clideo.com/merge-wav, and also quire a few freeware programs (ask google!).

Of your throttle is jumping straight to full throttle with any movement, you need to fix the registry entry for that device. Please see that FAQ article I referenced. Remember to back up your registry first! Before you do that, you can try with other controls (but I think you will find the same result). You are currently using Throttle Set, try also with Axis Throttle Set. Note that you are using a profile (called 737 Axic) for your PMDG 737, but you don't have any axis for that profile. You should make the axis for that profile specific. To do this, open the axis assignments dialog (with the PMDG 737 loaded) and check the profile box, and select to import your general axis). A few other minor points from your ini: - you should change AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your ini. This will prevent problems in the future if your device ids change (even though you currently only have one device) - Change your profile string 1=PMDG 737-800NGXu PMDG House (N738PM | 2019) to something like 1=PMDG 737-800NGXu That profile will then be used with any variant of the PMDG 737-800NGXu. You can even use 1=PMDG 737 to use with all PMDG 737s. John

Ah, so it was broken in the Custom mod and is now fixed. Ok.

So its an issue with the Custom mod that should be reported to FBW.

Please don't embed your comments in a quoted message. It make your comment very difficult to read. I think you should at least try and read the provided user manuals - they will be under your Documents folder in an FSUIPC6 sub-folder. Your FSUIPC6.log and FSUIPC6.ini files will be located in your installation folder, i.e. where you chose to install FSUIPC6. If you don't know where that is, please see the included Installation and Registration guide. To disable controllers completely in P3D, go to menu Options->General, and under Other Controls you will see a checkbox for Enable Controller(s) - make sure that is un-checked. This is usually due to the axis being identified as a digital on/off axis in the registry. Please see the following FAQ entry: John

See section Automatic running of Macros or Lua plugins in the Advanced User Guide. John

First, you posted in the Announcements sub-forum, where it explicitly states NOT for support requests. I have moved your post for you this time, byt please take care to post in the correct forum for future requests. What does this mean? You have to assign the throttle yourself, it does not do this automatically. What have you tried? Ok, but best to disable controllers completely in P3D, as it has a tendency to automatically re-assign on occasion. What doesn't work? What controls have you tried? Are you sending to FSUIPC for calibration and calibrated, or are you sending to FS as a normal axis? What version of FSUIPC and P3D are you using? As a minimum, I need to see your FSUIPC log and ini files, and need to know what you have tried. There have also been many posts on assigning the throttles in the PMDG aircraft (although difficult to find, admitadly!) - you should at least try searching these forums first (as well as the PMDG ones) to see if you can find any help there.

As stated in the provided README.txt, you need to uninstall (if installed) and re-install the VC++ 2015-2019 redistributables:

Buttons & switches with ids 0-31 (i.e. the first 32) will be recognised directly by FSUIPC. For the remaining, you need to use a lua script yo be able to use them. See and the following also applies to the Bravo. If not using the Alpha, you can ignore the that script.

Presuming you mean when assigned to an axis? There is no 'slope' functionality as such for the flaps axis, but you could experiment by using the axis scaling facility, although you will loose the full range of your axis. See the Advanced User Guide:

Many of the G1000 controls are not currently working in the stock aircraft. Its a know issue but I doubt it will be addressed by Asobo. However, there are working controls for the G1000 by using the MobiFlight WASM module, and event files to expose the MobiFlight events for use within FSUIPC. Fur further info, see and John

Then you can (probably) just use the freeware version - no need to buy a license. I understand that perfectly well. I expect the vast majority don't know how to program in lua, but I'm also pretty sure that many do use lua scripts (especially with the increasing popularity of the Honeycomb Alpha & Bravo). And - I expect that most people using FSUIPC are running the freeware version, to support 3rd party add-ons such as SmartCars. No license/purchase of FSUIPC required. I support the freeware/unregistered version the same as the registered version - FSUIPC can be considered as a 'toolbox', providing facilities for the user to create utilities as required. You cannot expect us to create these - we provide the tools for our users to do so, and also support our users in doing so - there are many other experienced lua/fsuipc programmers that help out, and many have written bespoke lua scripts for other users. John

This is just not something that should be part of the core FSUIPC, it is something that the lua add-on facility was invented for. Well, from my perspective, you are! I do not have time to write bespoke lua scripts for all my customers. I can help with this, but users are expected to try and do this themselves. There are also quite a few experienced lua programmers who also help out a lot, and even provide bespoke lua scripts. If you ask nicely, someone might help you. I'm just far too busy at the moment (and for the foreseeable future) to start writing bespoke lua scripts upon request. John

No. FSUIPC provides the facilities to pause, and the information you need to determine when to pause. It is up to you to write such a utility (e.g. in lua) to send the pause when you want to. So this is something that you should do in a lua plug-in. If you then want to share with others, you can add it to the user contributions section. John

Yes.

I think, but am not sure, that the MobiFlight module gets the events through via SimConnect. For events that are handled in the gauge key event handler, it seems that you need to match the string name when you register the simconnect event to that used in the WASM module, e.g. hr = SimConnect_MapClientEventToSimEvent(hSimConnect, EVENT_MFD_MODE_1, "#0x11000"); So the event string (in the event file) you need to use would be "#0x11000". However, you cannot use this with FSUIPC as the custom event strings must contain a period (.), e.g. MobiFlight.AS1000_PFD_VOL_1_INC, so not sure at the moment if this is possible. Maybe its possible to use something like "MyWASMNAME.#0x11000", where MyWASMNAME is taken from the WASM manifest (maybe the "creator" attribute?)... Anyway, I'm looking into this at the moment. I will be providing a WASM module to handle lvars (and also hvars, but later) thats integrated into FSUIPC and allows you to specify which lvars you want to use (via files) and then be able to use these (get/set) in FSUIPC as before, but also with an additional control that allows you to set any lvar. John

Hi Jimmy, Did you check that WideServer was actually running in FSUIPC7? Note that is is not auto-started by FSUIPC7 until you have loaded an aircraft. You can start it earlier manually from the WideFS menu. If thats not the issue, could you also attach your FSUIPC7.log and WideServer.log files from the PC running MSFS and FSUIPC7, as well as your WideClient.ini file. John

If you want P3D to start your program, you can use P3D's EXE.xml file (see the P3D documentation). Alternatively, if your program needs FSUIPC, then it may be better to start your program from FSUIPC using FSUIPC's [Programs] section. See the Advanced User Guide, section Programs: facilities to load and run additional programs. John

No, nothing like this is planned. However, if SmartCars is calculating this using information from FSUIPC, then it should be possible to do this yourself (either via the SDK or using lua) Really - which version of FSUIPC was this? How can this calculation be picked up from the sim itself? That is correct, as far as I am aware! John