John Dowson

Ah, ok, thanks. I'll also test with this later.

Can you please show us your FSUIPC logs, as before, but using that FSUIPC6.dll please.

That looks fine. How are you starting MSFS? How are you starting FSUIPC7? If you are using the desktop link created by the FSUIPC7 installer, that should start MSFS for you, and MSFS should start FSUIPC7 automatically via the EXE.xml file. So, initially just try starting both MSFS and FSUIPC using the MSFS desktop link created by the installer. If that doesn't show the splash screen, start MSFS and then start FSUIPC7, then let me know what happens. You can also also try starting FSUIPC7 manually by double-clicking the FSUIPC7.exe in Windows Explorer, and starting MSFS how you used to, to see if that starts FSUIPC7. If FSUIPC7 doesn't start automatically with MSFS either using the newly created desktop icon or by starting MSFS as you used to, please show me this file: C:\Users\jfsny\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml

Sorry, don't know what you mean by hidden "Icon". Its available from the main window menu if/when you open the main window (Alt-f).

Please show me your InstallFSUIPC7.log file, which should be in your FSUIPC7 installation folder. If its not there, then the installer may have crashed - when you installed to you finish the installation process and register? Also, please let me know your installation type - Steam or MS Store?

Did you try with the replacement dll I provided?

@David Flynn You seem to have gone quiet on this topic. If I don't hear anything in the next few days, I'll scrap these changes and consider this closed.

@pilotjohn Not sure whats going on with those simvars and controls, but testing in the King Air I only see a value of 0 or 1 for both the TURB ENG IGNITION SWITCH and the EX1 equivalent. Setting it to 2 (when 0) does nothing, however setting it to 2 when its 1 seems to turn the ignition switch off... Anyway, I've made a few changes in the attached version v7.0.9a if you would like to try. Changes are: - offsets 0x208C, 0x218C, 0x228C & 0x238C were previously using (for write) the KEY_TURBINE_IGNITION_SWITCH_TOGGLE control with a parameter for the engine number. I've changed these to use the individual KEY_TURBINE_IGNITION_SWITCH_SET1/2/3/4 controls with the parameter thats written to the offsert - I have added 4 new one byte offsets at 0x02C0, 0x02C1, 0x02C2, 0x02C3 for the TURB ENG IGNITION SWITCH EX1:1/2/3/4 simvars. Writing to these offsets also triggers the KEY_TURBINE_IGNITION_SWITCH_SET1/2/3/4 controls. Can you try this and let me know how this works for you. Which a/c are you using, and dies it actually have an off/on/auto setting for these switches? FSUIPC7.exe

Yes - select Close Console from the Log menu. The state will be remembered, so if you close FSUIPC7 with the console window open, it will start with it open the next time you run it.

Hi Chris, I believe the friction tables were a hack in FSUIPC4 and earlier. Now we no longer hack like this and rely on SimConnect, I don't think there is any access to the friction tables in FSUIPC5 and later, sorry. John

There is a link on the SimMarket sales page to download - it has been reported that a single click doesn't work with some browsers, so if thats the case right-click and select 'Save as....'. You can also download are products from www.fsuipc.com.

That works due to this in your ini: ShortAircraftNameOk=Substring

Could you also check the event viewer and show me the contents when you get a CTD. I'm also a bit confused as to when the crash is occurring - is it always during a flight and after you have edited a profile? And is it any change to the profile or just when you add a new aircraft to a profile? And have you noticed this with any other aircraft or profiles other than your PMDG ones?

No point in doing this each time this occurs - they show nothing. I will look and see if I can reproduce when I get time, but this will be low priority. As you are using an add-on aircraft, especially PMDG, I first need to see if I can reproduce with a default aircraft. However, you shouldn't need to be continually assigning new repaints of the same aircraft to a profile. Edit your ini and give a shorter/substring name for the aircraft in the profile, one that matches the aircraft with different liveries, i.e. change this: to this: and to etc

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