John Dowson

Could you also show me the JS145.lua file please. Note I am on holiday tomorrow so it will be a few days before I can look into this. John

There are no assignments to any button to turn off the autopilot - unless you are doing this assigned to a keypress. If that is the case, then please let me know which assignment? Could it be that your device ids have changed? Looking at your ini axis assignments, you have aileron and elevator axis assigned to device A, which is your throttle, and throttle to device C, which is your Yoke (B is rudder), so try switching those devices by changing your [Joynames] section to: Let me know how it goes with that change, and any issues please show me your updated .log and .ini files. Note that this will invalidate any assignments recently made to thos devices, so you may wish to remove or update them manually (by changing the joy letters used in the assignments). John

Why did you need to edit the FSUIPC5.ini file? Can you show it (i.e. attach it) to me please so that I can take a look. John

The majority of FSUIPC users are still on Windows 10, as am I, which I still need to support. I will be updating to Windows 11 shortly (this weekend). Windows 11 is still only available to Windows Insiders, as far as I'm aware, although it is now the version installed on new hardware. There should really be no changes needed to FSUIPC to support Windows 11. At least, according to Microsoft. So I am not sure why some users are having issues, unless their hardware doesn't meet the minimum requirements for windows 11. John

Your issue looks very similar to this one: Please follow the advise in that thread, i.e. - first check your version of FSX-SE is up-to-date (via the steam client) - see if there's a SimConnect.dll in the same folder as the FSX.EXE (main program)? If not see if you can find the version 62607 SimConnect.DLL in the WinSXS folders. If you can, copy it to the main FSX folder. If there is one there, try temporarily removing (e.g, rename to SimConnect.dll.unused) and see if it finds the WinSxS folder. Its also strange that the crash is in the ai_player.dll, as in the support request I referenced... Note that the FSUIPC4.ini file you attached is empty! John

Ok, thanks - thats good to know. I will update the README.txt to add this as a solution. Cheers, John

No problem. Glad its now working, but rather strange that the problem just solved itself! May have been the update, or maybe just a reboot was required, which sometimes can help. Regards, John

But shouldn't it point to the FSUIPC7.exe? Its FSUIPC that can only handle DirectInput. Your controller should work fine with the MSFS (default) assignments. You can also change/re-assign there rather than using FSUIPC. Would be interesting to know if you can get it working via FSUIPC though, so try pointing it to FSUIPC7.exe instead (and I think you need the dll in the same folder). If its the program that starts the program it points to (which I think it does), then you should disable auto-start (via a re-install) and start FSUIPC7.exe however required, either before or after MSFS is started. John

There is a possible solution to using XINPUT controllers with DirectInput games, called XInput Plus, but I haven't tried this, so not sure it will work. See the following for details: https://steamcommunity.com/sharedfiles/filedetails/?id=755970152 https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/ Unfortunately seems like the UI is in Japanese....If you try this, please report back if it works! John

Could you please activate logging for Buttons & Keys and Events, and produce a short log file where you load an aircraft, press your keys, then exit, and show me (i.e. attach) your FSUIPC7.log and FSUIPC7.ini files. John

What controller are you using? Your problem sounds like you are using an unsupported XINPUT device, such as the Xbox One or Xbox 360 game controller - from the README.txt (section Functionality to be Added (ToDo list)): If that is not your issue, can you please show me your FSUIPC7.ini and FSUIPC7.log files and I will take a look. John

Oh - and I see that you have installed FSUIPC6 in your Documents folder: I have seen this cause some strange issues, although I don't fully understand why and don't think it is related to your issues. But better if you can re-install into a different, non windows-protected, such as C:\FSUIPC6 (no need to re-register). You will need to copy across your files (FSUIPC6.ini, FSUIPC6.key, any luas, macros or dlls, etc) from the old folder to the new one after re-installation. John

Ok - you didn't update your profile section, but that is not that important. The log you posted shows: 1. When you pressed button 0 on your yoke, this sent the PARKING_BRAKES control, as assigned: However, note that you have set this assignment to repeat - you almost certainly don't want this on Parking Brake control. Button 4 on your yoke is also sending the assigned control: So it looks like the button assignments on your yoke are working. Are the yoke axis working? 2. I don't see any other Button changed messages logged. Did you try any buttons on your other devices? If so, FSUIPC is not seeing these. If you go into the buttons assignment dialog, does this recognse the buttons on those devices? How about the axis assignment dialog? Maybe you can show me your FSUIPC6.JoyScan.csv file. What changed during this period? I see that you have also assigned your axis with 'Direct to FSUIPC Calibration'. Lots of folks have issues assigning this way with PMDG aircraft due to priority levels - it is usually better to assign to the FS control instead. You could also try switching your devices USB ports (and maybe change from USB3 to USB2 id that is relevant and possible). It may also be worth trying to initially configure with a stock aircraft as well, just to check if you can assign your devices in a nin add-on a/c. John P.S. Also try rebooting first, if not done already!

Also, check your USB power management settings - make sure they are not set to power off....

There is a strange error relating to your JetMAX 737 TQ, but it was still acquired for use: Your controllers are also ON in P3D (and you are using RawInput): If you don't have any assignments in P3D, best to turn of controllers there, and also use the default DirectInput. You should also switch to using JoyLetters, so please set the AutoAssignLetters ini parameter to Yes. Your profile section should also be changed from: to This will then match all the different versions of the 737, so that you don't have to add them again if you change liveries. Please make the above changes. Also, disable all logging except for Buttons & Keys and Events. Then try again - load an aircraft and press one if your assigned buttons on each device, then exit and show me your updated FSUIPC6.ini and FSUIPC6.log files. John

FSUIPC7 should be started via the EXE.xml, not from the .bat script. The lines that start from the .bat script were the initial method of starting FSUIPC&, before the EXE.xml file was working in MSFS. The problem is that the AFCBridge installer corrupts the EXE.xml file. Please do the following: - Remove (or rename) your EXE.xml file. - re-run the FSUIPC7 installer. This will first uninstall and then re-install FSUIPC7 with a correct EXE.xml file - open the EXE.xml file in an editor, and add back-in the Launch.Addon section. You should end up with a EXE.xml file looking something like this (although the path to your FSUIPC7.exe will probably be different): Note that the FSUIPC7 section is added without any spaces or line-breaks. This isn't an issue. John

I will also move this topic to the FSUIPC7/MSFS support forum, where it belongs. If you search that sub-forum, you will also find many posts on a similar topic which may help you.... John

Most (if not all) functions of the FBW A320 autopilot can be activated by using lvars, hvars or calculator code. Alternatively, you can use the MobiFlight preset module and the provided MF/FBW event files. You can use this resource to see what lvars/hvars/calculator code the MF presets use, and then use FSUIPC7's lvar/hvar facilities to set-up the assignments. If you are unfamiliar with lvars/hvars, it may be easier to install the MobiFlight WASM module and use the MF events. Event files for the MF events are provided under your FSUIPC7 installation folder. Please see the FSUIPC7 Advanced User guide for details. Btw, please give your posts an appropriate title, NOT your username. I will update for you. John

Not sure why you would want to do this, but you can use the right-hans side of the axis assignments dialog to trigger button controls when the axis passes through a particular range (either entering or exiting). You could assign to the controls (or lvars, hvars, lua, etc) to flip the engine start switches there. John

I don't think the freezing can be related to FSUIPC... Did you try uninstalling (or just renaming the FSUIPC6.dll) to see if the problem goes away? If not, please try that. If the problem persists (i.e is only present when FSUIPC6 is installed/running), please show me your FSUIPC6.log and InstallFSUIPC6.log files. John P.S. You also created another topic/support request for the same issue - I have closed/locked that one.

Topic closed as duplicate of this one: Please do not raise multiple support requests for the same issue. John

FSUIPC will only recognise HID joystick type devices. Best to just download and try it. I can provide you with a trial (time-limited) license if you would like to see if recognised and assignable - let me know. John

No - that just means that controllers are set to off in P3D, as they should be if assigning in FSUIPC. John

Can you show me your FSUIPC6.log file please, from when this occurs. Maybe a good idea to open the console window when doing this so that you can see what, if anything, is logged when this happens, and I will need the timestamps (the first number in each log file line) of when this occurs. Try without any logging activated initially - maybe add axis logging later so that you can see when they stop responding. I think you mean 6.1.5! John

Just tried on the Bravo and I can see the issue. Strange. I ended up with the following flaps detents set: FlapStarts=-16384,-14384,-9485,-2213,4213,12213 FlapEnds=-14384,-9485,-2213,4213,11213,16384