John Dowson

@pointy56 and other users who are using the 6.2.2-beta version. I am going to release 6.2.2 soon with this fix, but I am going to release with the default value for the new AIAboveGroundLimit ini parameter set to 100, so as to not affect current functionality. Therefore if you need this to be 0, make sure you have this set in your ini file. John

Many presets for MSFS2020 aircraft won't work for the same aircraft in MSFS2024, and unfortunately there is no current way to know if they work or not except by testing. In MSFS2024, many functions have switched to use Input Events, or B vars, which are equivalent and can be used in preset calc code in MSFS2024 whereas it couldn't in MSFS2020. Note that there are some MF presets that are specifically labeled for MSFS2024 aircraft, but there is no general mechanism yet to know if a preset is for MSFS2020, MSFS2024 or both. There have been some discussions on the MF forums on how to handle this, but i don't think anything has been decided yet. Once something has been implemented, I will updated FSUIPC7 to handle this - hopefully by only loading the presets flagged as working for the version being used. Yes. There are two ways of doing this. You need to determine the parameter values for the input event (you can use FSUIPC's Input Event logging for this), and you can then assign directly to the input event by checking the relevant checkbox and selecting the Input Event in the drop-down. Alternatively, you could define a preset to trigger the B-var. The following article shows how you can discover B-vars: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2024-model-behavior-dialog/ That article also shows you how to use the b-var in MobiFlight, but for use in FSUIPC7 you would create a preset for the calc code in your myevents.txt file instead of configuring MF. Note that using Input Events directly would be the preferred option. However, not all B-vars are mapped to the Input Event interface, and so if there is a B-var available but no corresponding Input Event you would have to use the b-var via calc. code or a preset. John

Use one of the free file transfer services, such as https://filetransfer.io/. Also include your FSUIPC7.log file.

Also, if assigning in FSUIPC you should remove/delete the assignment in MSFS. If you don't, both the FSUIPC and MSFS assignments will be triggered. You can mix and match assignments between FSUIPC and MSFS if needed, but if assigning in FSUIPC only you should create a new empty profile for your controller in MSFS.

You certainly need 64bit, but I am not sure about the other dlls. I would try without them. The only XInput dll in my FSUIPC7 folder is XInput1_3.dll and it works here with just that.

You don't need to do this - it is FSUIPC;s calibration that sorts this out. It is always better to try assigning using 'Send direct to FSUIPC calibration' first, and then calibrating the axis in the FSUIPC calibration tab. You need to set the min/max values there, to convert the input range of the game controller axis to the full range of the axis event. But you also need to calibrate!

Here you go: FSUIPC6.dll I will update the documentation and release this version om a couple of days. John

Not available at the moment, but I could add it. What about the other ICAO offsets - 0x09T1 (icao_manufacturer) and 0x0B26 (icao_model)? I will add these as well. I am not "winding down development" of FSUIPC6 - I will still update when needed/on user request. I just don't get that many support requests for FSUIPC6 now compared to FSUIPC7, and the sales of FSUIPC6 have decreased drastically since the release of MSFS2020. Almost all development and support is for FSUIPC7 these days. I will post a version here for you to test shortly. Cheers, John

BTW, I downloaded and installed this version: https://community.pcgamingwiki.com/files/file/2265-xinput-plus-v415290/ I will put that link in the README.txt. John

But that won't work - as it says in the README.txt, you need to point it to the flightsimulator.exe. Sorry, this is wrong! It should point to the FSUIPC7.exe, not FlightSimulator.exe, as it says in the README.txt! I should read my own documentation! Sorry about that. Why isn't it working when you point it to FSUIPC7.exe? Can you see and assign the controller buttons/axes? I just tried this and it works well here with little set-up. I just reduced the response on the left trigger, then assigned this to the Throttle axis (with Send direct to FSUIPC calibration) and then calibrated the max/min values (and set Revers) in the FSUIPC Throttle calibration page, and it works as expected om both MSFS windowed and full screen modes. I also enabled DirectInput Output in XInputPlus (DirectInput tab) but I am not sure if this is necessary or not. So, as it points to FSUIPC7.exe and not the FlightSimulator.exe, it should work the same with the MS Store version as the Steam version.

Maybe also try with the dll files - ftom the tutorial:

Did you run XInputPlus with Admin privileges? This is needed. Maybe also try the XInput Plus Loader to see if that works with the MS Store version. I know other FSUIPC users with a Steam install are using XInputPlus, but I have not tried this yet. I will take a look in the next days and report back if it works ok with the Steam version and the XBox game controller. John

Can you show me / attach your FSUIPC7.ini file and an FSUIPC7.log file showing your issue - activate logging for Input Events, Events and Buttons & Switches, and add offset logging for offset 0xA030 (or whatever offset you are using) as U16. What button numbers to you see when you move the rotary clcokwise and anti-clockwise, and do you have 1 or 2 buttons in each direction? Also check that you haven't selected/checked Control to repeat while held. I did notice this in the VRInsight appendix of the Advanced User manual: So maybe its not possible to override the default assignment for that rotary (except via lua), but if you have assigned to this and its sending the events then it should be ok. Your log file should tell me if its working or not.

But that won't work - as it says in the README.txt, you need to point it to the flightsimulator.exe. So you are using an MSFS Store version? When MSFS is running, try opening the task manager, find the FlightSimulator.exe, right click and select Open file location and try pointing XInput Plus to that location. I could do this, but it may take a few days - maybe I will find time at the weekend... John

This is the support forum for FSUIPC, not FCR. Try https://forums.flightsimulator.com/t/flightcontrolreplay-v5-for-msfs/551430 John

What version(s) of FSUIPC are you using? I have added this feature now to FSUIPC7 which will be available in the next release, and is also in the latest beta release of FSUIPC7, available here: I may add this to FSUIPC6 at some point, but probably not worth it at the moment as almost all development is now with FSUIPC7 and I am currently not planning much for FSUIPC6 - although I do need to release 6.2.2 with a minor update (new ini parameter AIAboveGroundLimit). If using FSUIPC7, can you download and install that latest beta. You can then check/test the auto-download, unzip and install when I release that version officially, planned for the 14th Feb. Cheers, John

So this is with the default MSFS assignments? You can try - there is a free/trial license at the top of the FSUIPC7 sub-forum if you would like to try it. I will also move this post to that forum - please use that subforum for all questions/issues with FSUIPC7 / MSFS, not this main forum. Note that there is a known issues with some Xbox gamepads which makes this device rather tricky to set-up with FSUIPC7. This is because the XBox gamepad is an XINPUT device, and so FSUIPC7 will only see this device when it has the focus, and as it is MSFS that normally have the focus, FSUIPC may not see any actions unless it has the focus. Check this - if FSUIPC7 only sees the buttons/axis of the gamepad when it has the focus, you will need additional (free) software to get it working. From the README.txt: John

Well, the NAV1_RADIO_SET control will send the new frequency to the FS, but you need to trigger this and that would normally be done on a rotary button, i.e. when turning the dial. You could have a lua script that knows the current NAV1 frequency (i.e. via an event callback on offset 0x0350), and the lua script would also wait to be triggered using event.param. The rotary buttons can then be assigned to LuaValue to trigger the lua event.param callback function (with the parameter indicating an increment or decrement, or maybe both fast/slow inc/decs if you have fast/slow buttons), and in the event.param handling function/callback, you would take the current NAV1 frequency and then increment/decrement this value before sending to the FS. Note that NAV1_RADIO_SET takes BCD16 format, whereas NAV1_RADIO_SET_HZ takes a Hz value. Probably better to convert the current BCD NAV1 frequency (from offset 0x0350) to HZ before changing and send on using NAV1_RADIO_SET_HZ.

Please use the FSUIPC7 support sub-forum for all issues and questions for FSUIPC7 - I have moved your post. Do you see any values in other lvars? Can you set/change the value of an lvar (via Add-ons->WASM->Set Lvar)? Check to see if the WASM has crashed in MSFS2024. It seems that the WASM crash is more frequent in MSFS2024. if the WASM is crashing and you have not disabled lvar scanning, please do that. If the WASM isn't crashing and the lvar values are being received by FSUIPC, then that must be the value of the lvars. I don't have the FenixQuaerz so cannot check this here, sorry. John

There are the following ATC simvars (see https://docs.flightsimulator.com/flighting/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_RadioNavigation_Variables.htm😞 Any simvar can be added to spare/free FSUIPC offsets using the facility described in the section Adding Simulator variables (simvars) to FSUIPC offsets on page 35 of the Advanced User guide. As you can see, most of those are read-only, although 4 are updateable. John

All of them - as it says in many, many places, you need to install the latest combined VC++ redistributable package for 2015, 2017, 2019 and 2022. And if you haven't done that, then you haven't read the Installation and Registration guide - please do that! From the documentation: Well if it works when you create the key manually, it means that you had previously entered the details incorrectly... John

I assigned a spare rotary for this... First, add the input event to an FSUIPC offset - e.g. add to your FSUIPC7.ini file (were xxx is your profile name): That will add the input event FCC_ALTITUDE_SEL to offset 0xA030 as an unsigned word (2 bytes) - and for your 737Max profile only. Then assign your rotary buttons to inc/dec that offset. I have both fast and slow buttons on my rotary, so these are my assignments: where 175 is my controller/device number, 10 is the slow inc button and 11 the fast, and 9 the slow dec button and 8 the fast. If you only have one button in each direction, just assign to the slow controls (or you can use a lua script to convert to 2 virtual buttons...). Here's how one of those assignments looks in the UI (slow increment)I: Seems to work ok except for a minor wrapping issue when going below 0, but this shouldn't matter... John

Pete retired over 5 years ago. Please follow the instructions provided in my previous comment on this topic... Note this has been reported thousands of times, and it is ALWAYS due to user error not following the instructions... You can also try manually creating the key file (details in the Installation and Registration guide). Does it register if you do this (the registration details will be pre-populated in the UI if you manually create the key file)? If you run FSUIPC7 with the key file present, does it run as a registered version? John

As your issue is with FSUIPC7, you should use the FSUIPC7 support sub-forum. I will move this post. There are no axes controls logged in the log file - please set logging for Axes Controls and attach a log showing your issue. Also, please ALWAYS exit FSUIPC7 before attachubg files. You should also switch to using substrings for your aircraft names, to prevent issues with profiles not loading when using variants. Change to and to etc Do this for all your profiles (i.e. use substrings of the aircraft name). You should get into the habit of editing the aircraft name each time you add one to a profile.

Please show me / attach your ini and log files, the latter showing your issue (i.e. with logging for Axes Controls activated). Note that as a new user, you will have a very low upload limit. Compress the files but if still too large you will need to use a (free) file transfer service.