John Dowson

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.

Yes, I know, but this topic is for your ACARS not connecting. You already raised a topic for WideFS not connecting, so use that for the WideFS connection issue.

Yes, I know, but this topic is for your ACARS not connecting. You already raised a topic for WideFS not connecting, so use that for the WideFS connection issue.

I guess it makes sense that the WHOLE / FRACT events control the standby, as there are no stnby equivalents...sorry about that. To set the active frequency directly, you would need to use the NAV1_RADIO_SET control, or write the new frequency (in BCD format) to offset 0x0350.

As I said, please check what it is assigned to. For ALT select in the 737max, you need to use the input event FCC_ALTITUDE_SEL. Have you tried assigning to this, as advised? Well, I think the strange thing is that the other encoders actually work! The default assignments will be to the standard FS controls - these do not work for many aircraft functions in MSFS2020, and even less in MSFS2024. The encoders that are working must be because the aircraft is using the standard controls for those functions, but not for the Altitude select, where it is using that input event.

Have you configured FSUIPC to handle your VRInsight MCP? Can FSUIPC see the (rotary) buttons of the alt select knob in the buttons assignment panel? And if so, what is this assigned to? To control the altitude selection in the 737max in MSFS2024 you need to use the input event FCC_ALTITUDE_SEL, which takes the altitude as a parameter. To use this, add this input event to a spare/free FSUIPC offset and assign to one of the offset increment/decrement controls.

Not via FSUIPC. Only one of those ini parameters will be read. Normally you would write the file to a networked drive if you wanted it to be accessed from multiple PCs. If you wanted it copied to multiple locations, you could maybe trigger a lua script after the file was generated which could call the OS to copy the file.

Of course there are events for active frequencies, e.g. 65707 COM_RADIO_SET 65708 NAV1_RADIO_SET 65636 COM_RADIO_WHOLE_DEC 65637 COM_RADIO_WHOLE_INC 65638 COM_RADIO_FRACT_DEC 65639 COM_RADIO_FRACT_INC 65640 NAV1_RADIO_WHOLE_DEC 65641 NAV1_RADIO_WHOLE_INC 65642 NAV1_RADIO_FRACT_DEC 65643 NAV1_RADIO_FRACT_INC 66434 COM_RADIO_FRACT_DEC_CARRY 66435 COM_RADIO_FRACT_INC_CARRY 66445 NAV1_RADIO_FRACT_DEC_CARRY 66446 NAV1_RADIO_FRACT_INC_CARRY 67361 COM1_RADIO_HZ_SET 68064 COM1_8333HZ_MODE_TOGGLE 68065 COM1_8333HZ_MODE_SET etc Basically you have all the same events on active frequencies as with standby.

WideFS only supports FSUIPC client programs. I think the only way to move MSFS pop-ups to a networked PC would be to use something like WideView. There may be other solutions - probably better to ask on the Asobo forums.

Isn't the error obvious? BCD for 109.20 would be 0x0920 (leading 1 omitted). You are converting the value to hex, not BCD.

This really depends on the function/control. Generally you would use logging - set logging for Events (Log -> Events) and open the logging console (Log -> Open Console). If you see lots of events logged when not doing anything (many MSFS aircraft continually emit certain events) then you should use the DontLogThese ini parameter to stop such events being logged (see Advanced User guide). Then click the button/switch/etc in the VC and see if anything is logged, and if so you can use that. You can also log Input Events with a corresponding ini parameter of DontLogTheseIE. If standard (or known custom) controls are not used, then you can try inspecting the model behavior to see how how button/switch is implemented - see the following on how to do this: MSFS2020: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ MSFS2024: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2024-model-behavior-dialog/ What aircraft/avionics system? There are many presets for this, e.g. for the G1000 in MSFS2020: AS1000_MFD_RANGE_DEC and AS1000_MFD_RANGE_INC for the G1000 in MSFS2024: MFD RANGE ZOOM - Dec and MFD RANGE ZOOM - Inc for the ATR: MSATR MFD CPT RANGE INC + and MSATR MFD CPT RANGE DEC - etc So it really depend on the aircraft / avionics system being used.

Calibrating when assigned with 'Send to FS as normal axis' can be problematic, and this depends on the aircraft. When assigned this way, the uncalibrated values are sent to the sim. and then the value is calibrated once it is received back with the event, and it is masked (i.e. original value blocked) and then calibrate value is then sent. This can cause issues with some aircraft due to priority levels. And it is not clear to me when any MSFS calibration is applied - if this is on the initial value sent, or on the 2nd calibrated value sent. Basically if calibrating when assigned with 'Send to FS as normal axis' causes issues, you will not be able to use FSUIPC's calibration facilities. If you wanted to calibrate such an axis, you can write the axis value to an FSUIPC offset and read that value and perform any calibration needed in a lua script and then send the event on from the lua script with the calibrated value. You could possible try changing the event priority values to see if this helps, but I wouldn't recommend this. John