John Dowson

You need to understand how profiles work w.r.t. axes assignments vs button assignments. For button assignments, general assignments are always loaded, even when using a profile, and then the profile-specific button assignments are loaded, replacing any assignments that are in the general profile. For axis assignments, if a profile axes section is present then only the profile axies are loaded. This is why, when you first create an axes profile, it asks if you want to import the general axes section. Once a profile has been selected for the axes for an aircraft, all axis assignments for that aircraft will be profile specific. You cannot add a general axis assignment when an aircraft is loaded that has profile-specific axes assignments. If you want to add a general axis, you would have to load an aircraft that has no profile axis assignments. For buttons, you can select or deselect the profile, depending upon where you want the button assignment to go. There are still many MSFS controls that work only when assigned in MSFS and have no affect when assigned in a simconnect client, such as FSUIPC. This is a known issue, and affects many controls/events, including the view and slew controls. For now, you either have to assign these directly in MSFS, or assign to keypresses in MSFS, and then assign your buttons/POVto those keypresses in FSUIPC. John

Its John. not Pete... As I said, how are you reading these values? Offset 088C is a 2 byte signed integer, and can therefore only hold values from -32768 to +32767. If you are seeing numbers larger than this, you are reading it as an unsigned 2 byte integer which has a range of 0-65535. You can verify this by logging the offset as both an S16 and an U16 using FSUIPC's offset logging.

How are you setting this value? What FS and version of FSUIPC are you using? And how are you reading the value? The maximum value of a 2byte signed integer is 32767 it looks like you are reading it wrong, maybe as an unsigned integer? The maximum value held in this offset should be +16384 (as described in the documentation).

Your log shows that the mouse action failed for those mouse macros: This must either be due to the mouse rectangle being invalid, or a problem with the FSLabs a/c. Can you redo the macros that are failing. Maybe just create a separate new macro file for those that are failing and verify that the rectangle ids are the same. If not, update your existing script with the correct rectangle ids. If the rectangle ids are correct, you need to contact FSLabs support to determine why they are returning an error.

You log file shows that you were not connected to MSFS. You need to have MSFS running and be connected before lua files are auto-ran. You do have a HidDemo.log file, but that must have been generated on a different run. So, please try again and make sure that you have MSFS running and always better to assign/calibrate with an aircraft loaded. Also, try the attached HidDemo.lua. In this script (based on the Alpha script) only buttons 32-64 are made accessible by virtual buttons, and the others (0-31) are still available in the usual manner. This saves some virtual buttons (for other uses) and prevents multiple buttons (teal and virtual) being seen at the same time. On the button assignments panel, when you press the button you will see the joystick letter (C for your throttle) and the button number if < 32. For the buttons > 32 asigned to virtual buttons, you should see a joystick number of 64, and button numbers starting from 0. John hidDemo.lua

The FSUIPC7.ini file is created the first time you run the application, if not already present. You can check the installation location by using the File -> Open Installation Folder... menu option. If you can't see the extensions, then thats due to your windows explorer settings. See the Addemdum in the Installation and Registration guide to fix this (last page).

If the events are being sent then you should be ok. Have you installed the MobiFlight WASM module into your Community folder? That's the module that handles the events on the FS side.

Ok, but it would be useful if you could explain how to help others who may have the same issue. No problem!

Why should it be? That just lust the controls available. Did you add the MobiFlight events by dropping the event files into your FSUIPC7 installation folder? Once you do that, you should see the MobiFlight events at the top of the controls drop-down menu. Currently you can only use the MobiFlight events, not the hvars, as I said.

Sorry, but what does this mean?

FSUIPC only recognises HID joystick type devices. If its another HID type device, you will need to use lua. There is a demo script provided in the lua axamples zip called HidDemo.lua. You can try that - you need to edit it to provide the VID and PID of your arduino, place it in you FSUIPC installation folder and have it auto-started from your ini's [Auto] section.

Just replace your current FSUIPC7.exe withthe new one, and it will pick-up the same FSUIPC7.key file that the previous version used. If you are running it from a different folder, then you need to copy across your FSUIPC7.key and FSUIPC7.ini file (+ any other files you may use) to the new installation folder (i.e. where you run FSUIPC7 from). Its easier just to replace your existing FSUIPC7.exe with the new one downloaded.

No idea what you mean by that, or if its even related to FSUIPC, sorry.

I am working on a WASM module for lvar and hvar access at the moment. I'm hoping to have a beta out in a couple of weeks, but it depends on how much time I have free to work on this. Support is currently taking up a lot of time, which doesn't leave me much time for new development... No idea about mouse macros at the moment. I'm not sure if the facilities are available yet, but I'll start looking at this one the lvar/hvar functionality has been released. John

As I said, you can't use them (i.e. hvars) yet (as far as I am aware). You can use the MobiFlight events though - check them to see if there is anything there that you can use. Installing the MobiFlight WASM is pretty straightforward. You have to download the MobiFlight connector app and install from there. There are instructions somewhere over on the Asobo forums. Once you have installed the WASM module (into your MSFS Community folder), you will need to download the MobiFlight event files and add them to your FSUIPC7 installation folder. Note that there is currently a bug in the released version of FSUIPC7, v7.0.4, where only one event file is recognised. There is a beta version in the thread I posted where this is fixed - you need to download and use that if using more than one event file. John

As I said in my previous post, it seems that the FBW mods are using lvars for this, so you will have to wait for lvar access, which I'm currently working on (when support doesn't get in the way!), John

There are a bunch of hvars exposed by MobiFlight to control the CDU in the A320Neo: "(>H:A320_Neo_CDU_1_BTN_0)", "(>H:A320_Neo_CDU_1_BTN_1)", "(>H:A320_Neo_CDU_1_BTN_2)", "(>H:A320_Neo_CDU_1_BTN_3)", "(>H:A320_Neo_CDU_1_BTN_4)", "(>H:A320_Neo_CDU_1_BTN_5)", "(>H:A320_Neo_CDU_1_BTN_6)", "(>H:A320_Neo_CDU_1_BTN_7)", "(>H:A320_Neo_CDU_1_BTN_8)", "(>H:A320_Neo_CDU_1_BTN_9)", "(>H:A320_Neo_CDU_1_BTN_A)", "(>H:A320_Neo_CDU_1_BTN_B)", "(>H:A320_Neo_CDU_1_BTN_C)", "(>H:A320_Neo_CDU_1_BTN_D)", "(>H:A320_Neo_CDU_1_BTN_E)", "(>H:A320_Neo_CDU_1_BTN_F)", "(>H:A320_Neo_CDU_1_BTN_G)", "(>H:A320_Neo_CDU_1_BTN_H)", "(>H:A320_Neo_CDU_1_BTN_I)", "(>H:A320_Neo_CDU_1_BTN_J)", "(>H:A320_Neo_CDU_1_BTN_K)", "(>H:A320_Neo_CDU_1_BTN_L)", "(>H:A320_Neo_CDU_1_BTN_M)", "(>H:A320_Neo_CDU_1_BTN_N)", "(>H:A320_Neo_CDU_1_BTN_O)", "(>H:A320_Neo_CDU_1_BTN_P)", "(>H:A320_Neo_CDU_1_BTN_Q)", "(>H:A320_Neo_CDU_1_BTN_R)", "(>H:A320_Neo_CDU_1_BTN_S)", "(>H:A320_Neo_CDU_1_BTN_T)", "(>H:A320_Neo_CDU_1_BTN_U)", "(>H:A320_Neo_CDU_1_BTN_V)", "(>H:A320_Neo_CDU_1_BTN_W)", "(>H:A320_Neo_CDU_1_BTN_X)", "(>H:A320_Neo_CDU_1_BTN_Y)", "(>H:A320_Neo_CDU_1_BTN_Z)", "(>H:A320_Neo_CDU_1_BTN_DIR)", "(>H:A320_Neo_CDU_1_BTN_PROG)", "(>H:A320_Neo_CDU_1_BTN_PERF)", "(>H:A320_Neo_CDU_1_BTN_INIT)", "(>H:A320_Neo_CDU_1_BTN_DATA)", "(>H:A320_Neo_CDU_1_BTN_FPLN)", "(>H:A320_Neo_CDU_1_BTN_NAVRAD)", "(>H:A320_Neo_CDU_1_BTN_FUEL)", "(>H:A320_Neo_CDU_1_BTN_SEC)", "(>H:A320_Neo_CDU_1_BTN_ATC)", "(>H:A320_Neo_CDU_1_BTN_MENU)", "(>H:A320_Neo_CDU_1_BTN_AIRPORT)", "(>H:A320_Neo_CDU_1_BTN_UP)", "(>H:A320_Neo_CDU_1_BTN_DOWN)", "(>H:A320_Neo_CDU_1_BTN_PREVPAGE)", "(>H:A320_Neo_CDU_1_BTN_NEXTPAGE)", "(>H:A320_Neo_CDU_1_BTN_L1)", "(>H:A320_Neo_CDU_1_BTN_L2)", "(>H:A320_Neo_CDU_1_BTN_L3)", "(>H:A320_Neo_CDU_1_BTN_L4)", "(>H:A320_Neo_CDU_1_BTN_L5)", "(>H:A320_Neo_CDU_1_BTN_L6)", "(>H:A320_Neo_CDU_1_BTN_R1)", "(>H:A320_Neo_CDU_1_BTN_R2)", "(>H:A320_Neo_CDU_1_BTN_R3)", "(>H:A320_Neo_CDU_1_BTN_R4)", "(>H:A320_Neo_CDU_1_BTN_R5)", "(>H:A320_Neo_CDU_1_BTN_R6)", "(>H:A320_Neo_CDU_1_BTN_PLUSMINUS)", "(>H:A320_Neo_CDU_1_BTN_SP)", "(>H:A320_Neo_CDU_1_BTN_DIV)", "(>H:A320_Neo_CDU_1_BTN_OVFY)", "(>H:A320_Neo_CDU_1_BTN_CLR)", "(>H:A320_Neo_CDU_1_BTN_BRT_S1)", // Experimental brightness increase (INOP) "(>H:A320_Neo_CDU_1_BTN_DIM_S2)", // Experimental brightness decrease (INOP). "(>H:A320_Neo_CDU_1_BTN_DOT)", However, I don't think its possible to use these yet. I am currently working on a WASM module for FSUIPC7 that should be able to handle these (and also lvars), but this is still a few weeks away. John

No mouse macros yet in FSUIPC7. If there are no controls in the dropdown, it means that there aren't any provided by MSFS. You can check to see if MobiFlight provide additional events for this, and if so you can install the MobiFlight WASM module and add the events to FSUIPC using event files. See and

What aircraft are you using? The magnetos seem to behave differently depending upon the aircraft. Did you try activating logging to see what controls are being sent? There are many controls for magnetos (set, off,, right, left, both, etc). Maybe try those to see if any work for the aircraft that you are using. FSUIPC only provides access to these controls that are exposed via SimConnect. If they are not working for a particular aircraft, then you can check the Asobo forums and maybe raise a bug report with Asobo. Some controls are momentary though (i.e. they take affect but then go back to the previous state), but this is also aircraft dependent.

The separate engine autostart controls are FSUIPC-added controls that use various offsets (depending on the aircraft type) to auto-stat the engine. Those offsets, or the controls/events sent when using those offsets, may no be working in the vanilla A320. I'll make a note and look into this at some point, but it may take a few weeks to get around to this. You could try one of the FBW mods to see if its working there. John

If you want to write to an offset, say 0892, then assign to Offset Word Set (0892 is 2 bytes or 1 word) and give the parameter a value of 2 (which is Magneto Left). Sorry, not sure what you mean by this. What controls are you using? Maybe activate logging of events (and open the FSUIPC console), and you can then see what controls (and parameters) are being used when you activate the buttons or the controls in the UI.

Sorry, but that seems to contradict itself! What 'works' if FSUIPC6 is not showing in the Add-ons menu? You can, but I wouldn't install directly there if I were you. You can create a Modules folder and install under that. If you P3D isn't loading the add-ons correctly, it may also be worth just uninstalling and re-installing the P3D client as this only takes a minute or two.

That is strange! You can try manually activating by editing your C:\Users\<username>\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg file. Find the FSUIPC6 entry and change to 'ACTIVE=true'. If that doesn't work, I would re-install: - uninstall FSUIPC6, by using the uninstaller located in the installation folder (or using the windows Apps panel) - run P3D once: just start it and exit - re-install FSUIPC6. This time, select to install in a folder other than your P3D add-ons folder (which is the default location) - run P3D, and this time when it asks you to enable the add-on, select Yes

Sorry, what does this mean? What is 'hook'? If you activate it, don't you see the FSUIPC entry in your add-ons menu? Or are you saying that you can activate FSUIPC, but the next time you start P3D it is again not active? There is no "Modules" folder any more, although you can still install there if you so wish. I see that you installed FSUIPC6 in your P3D add-ons folder. It is better to just use this location for yout add-on.xml file and install FSUIPC6 in a separate location (e.g. C:\FSUIPC6 or C:\P3D Add-ons\FSUIPC6).

Try with the Rotoe Brake control first with the parameters mentioned in that post: There is also a spreedsheet (2nd comment in that link) with more control codes that may be useful.