John Dowson

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

I am looking into providing an WASM module to handle lvars at the moment. I will also add access to the h variables, but at a later stage. John

Sure, You just can't run them both at the same time.

As I say EVERY TIME, if you have an issue and you are using a mod, you should also try the vanilla version. And whenever you report an issue, you should always specify if its with a mod version or the vanilla. And, of course, if something is working in the vanilla A320Neo but not the mod version, then you need to report to the mod developers. John

Hi Fragtality, which version of FSUIPC and which Flight Sim are you using? Focus handling is different in FSUIPC7 to other versions, as FSUIPC7 is a stand-alone application, so I need to know this before I can take a look. If you can let me know, I will look into this and report back. However, I'm pretty busy at the moment, so it will take me a few days to get around to this.... John

Vanilla A320Neo or a mod version? What has changed since you reported this as working?

Does this wheel use an axis or buttons? If the latter, it could be that the button number are outside of the 0-31 range. If thats the case, you would need to use a lua script (e.g. the hidDemoi.lua script provided in the example lua files). This is quite a way away. I am looking into adding lvars first. Once that is done, I'll see if mouse macros are possible. MobiFlight has a bunch of controls/events for the G3000. Try installing the mobiflighrt WASM module and the MobiFlight/FSUIPC7 event files. See

Is that for all versions, i.e. the vanilla and the mods? There has been no change with this in the latest release (v7.0.4). There has been no MSFS update either, so I'm not sure what could have caused this...

It should be possible to do that in FSUIPC, so should also be possible in Linda. First, you need to add the events to FSUIPC7 using event files. Then, you need to determine what control number FSUIPC7 has assigned to the events. You can do this either by temporarily assigning the event to a button, activate event logging and then press the button to see what event number is logged. You can also work it out by the the number of evt files you have and the index number - the control number will be: 32768 + (256*fileIndex) + controlIndex where fileIndex is the order the file is loaded (starting with 0) and controlIndex is the index number of the event in the file. If you are only using one event file, this is then just: 32768 + controlIndex John