John Dowson

All you need in the executable, however other files should be installed. The looks like the installer is crashing due to a corrupt EXE.xml file. You need to delete this file (or rename) and then re-run the installer. Depending upon whether you have an MS Store or Steam install, this file will be in the following location: Steam: <user>\AppData\Roaming\Microsoft Flight Simulator MS Store: <user>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

Or maybe its better to use the same offset, and replace the simvar used - I don't think this would be a problem....

That offset is just showing the value of the TURB ENG IGNITION SWITCH variable, and at index 1. I've just checked the latest MSFS documentation, and it seems that this is no longer indexed and is a boolean, so just 0 and 1 (i.e. off/on - but I still don't understand why you just see 1!). However, there is also a new EX1 simvar for this: TURB ENG IGNITION SWITCH EX1 Position of the Ignition Switch. Similar to SIMVAR_TURB_ENG_IGNITION_SWITCH but differentiates between ON and AUTO. (Enum) UNITS_ENUM TYPE_ENUM Is this what you need? I could add that to a different offset for you to try if that helps - let me know.

Your EXE.xml (not sim.xml) is fine. Your problem is most probably that highlighted in the README.txt, which also tells you how to resolve:

It is and always has been the case that all programs that are communicating with the FS have to be ran at the same level as the FS.

Thanks. I think its only a few people who seem to be having an issue with the Bravo on the buttons > 32.....

Ok. but this is the second report I have no heard of this. There are many other Bravo users using the lua script - is this actually working for anybody? How about the 128 button beta release? As the script has been downloaded and presumably used many times, I thought that this issue was specific to a user - or two, but could be mistaken. Not having the Bravo, it is difficult to check - but I have the Alpha and that works fine (either using the lua script or the 128 beta release). Yes. And this is also the reason why many folks switched to using FSUIPC for controlling the Alpha/Bravo, to get around this.

There is currently an issue where the installer will crash after installing the FSUIPC7.exe. This is due to a corrupt EXE.xml file. To fix this, you should remove (or rename) your current EXE.xml before running the installer. Depending upon whether you have an MS Store or Steam install, this file will be in the following location: Steam: <user>\AppData\Roaming\Microsoft Flight Simulator MS Store: <user>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Note also that the current official release is v7.0.8, so downlload that if you haven't already. To use with these devices, uoi could try the 7.1.0a beta release which has direct support for up to 128 buttons. See: Alternatively, there are lua scripts available for the Alpha and Bravo to handle the buttons with numbers > 31:

You could try scaling the input axis values instead - see page 38 of the Advanced User Guide. Basically assign to the THROTTLE 1_AXIS_SET_EX1 control, then edit the ini to add the following to your the axis assignment: ,*0.5, +8182 That should then scale from (-16384, 16384) to (0, 16384). I am also going to look into providing support for the _EX1 controls via direct to FSUIPC calibration. I will look into adding a new ini parameter that will switch the throttle calibration controls to use the _EX1 versions.

Sorry - I uploaded to one of the download sites but the upload to the 2nd site failed and I hadn't noticed. Thats been corrected now. Thanks for letting me know, John

Try re-installing (or installing) the VC++ redistributables. First, uninstall any of the 2015, 2017 and 2019 VC++ redistributables from the Windows App management panel, and then re-installed the combined redistributable packages (both the x86 and x64 ones) from here: https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads

ah, I must have mixed-up your old/new files, sorry - nothing strange. And, as I couldn't reproduce your issue, and now neither can you, I'll consider this closed.

Alternatively, if most of your assignments are to the initial letters, you can change your [JoyNames] section to the following: and then map any assignments as follows: G -> B H -> C K -> E L -> J M -> D P ->B (or C)

It probably has a button number > 31. You don't say which version of FSUIPC you are using, but if its FSUIPC6 or FSUIPC7, I have just released a beta version with support for up to 128 buttons: please see Otherwise, you would need to use a lua script to map those buttons to virtual buttons. You can use the example HiDDemo.lua provided for this, or, probably better, adapt one of the Aha or Bravo lua scripts for your device (by changing the Vendor and Producr ids), which are available from the User Contributions section.

It won't - I just mentioned this as it is a general control to insert a pause, but it will not 'break' or prevent further assignments being executed. Sorry if that confused you.

You can assign an axis to these controls using 'Send to FS as normal axis'. If you do this, also check and remove any calibration as well. Yes, its a know issue with some add-ons. For throttle configuration in the CRJ with FSUIPC, please see this post:

Sending direct to FSUIPC calibration and calibrating can cause issues with some complex add-ons due to the priority levels of the axis controls seen by the sim. Try 'Send to FS as normal Axis' instead and remove any calibration.

You need to add the MF events to FSUIPC using event files (*.evt). Please see these threads:

As well as what Pete has said, there is a 'Pause Control' that you can use to insert a break in multiple assignments or macros (but not in compound assignments) Its FSUIPC added control 'Pause (ms)', number 1152:

The FS doesn't need to be he active window to receive button presses, although it needs to be the active window to receive key presses. Are you sure you had something assigned to the button press? You can always activate logging for Events and Buttons & Keys yo see what events, if any, are being sent when you press a button or key.

I've far too much to do and no time to start looking at c#. I can rebuild the API as a dll at some point though, and export the public functions of the WASMIF class. Not sure when I'll get time for this at the moment, but I'll let you know when its done.

Sorry, what do you mean? There is no 7.1.0, only 7.1.0a. Are you sure it was FSUIPC7 that crashed, and not MSFS. Do you have an FSUIPC7.log file for the crash, and a windows event? No it doesn't! If it says that, that is the version you are running.... I don't know what you are doing, but sounds like you did not install the v7.1.0a version correctly. You should use the downloaded FSUIPC7.exe to replace your previous FSUIPC7.exe (or just rename the existing one first). I think you should re-install the full version again (v7.0.8), then re-download the 7.1.0a version and use that to replace the installed FSUIPC7.exe. If you then have any issues, show me your install log as well as your EXE.xml file. You can do this by not selecting to 'Auto-Connect to FS'. But then you need to manually connect. If that is a feature request, I can put it on the list and look into it at some point. However, there is a lot to do at the moment and I it will be a long time (> 1 year) before I will get a chance to look into this. I thought the recommended way to start Linda was via lua and ipcReady.... However, it should start with a run command if you want to do it that way. But there is no point in just telling me these things, I need to see your logsd and ini files if you want me to look into anything. Sorry, what does this mean? The [LuaFiles] section is auto-generated by FSUIPC and just lists the lua files found in your installation folder, for assignment purposes. I'm not sure what you are asking, but if it is related to Linda then you should ask on the Linda support forums. I don't use Linda. John

Presume you mean 66748 to 66800.... There have been many reports on many of these events not working (both in the FSUIPC as well as the Asobo forums). However, there are MobiFlght events for the G1000 which are working, so you should try with them (you will need to install the MF WASM module - there are various posts on this here, on Asobo forums and on MF).

No, that won't be an issue. If a button isn't assign, it just means that FSUIPC will not do anything when you press the button (except maybe log). That shouldn't be happening. Can you explain what you were doing when this occurred? You could activate logging for axis events, and the next timne it happens, show me your FSUIPC log fie, as well as your ini. Note also that your FSUIPC version is out of dat - the latest version is 6.0.13, so please update. There is also a beta version available, v6.0.14, which has support for yp to 128 buttons, and as the bravo has button numbers > 31 you may want to try this version that should allow you to assign all the butons. Its avaiilable here:

Yes, looks like your GUIDs have changed at some point. You can remove the following entries: Leaving just the following for your [JoyNames] section: You will also need to check for references for those devices in your profile files and update. Change the following joy letter references (in the [axis] and [buttons] sections: B -> G (or H( C -> H (or G) K -> E L -> J M -> D P -> G or G (?)