John Dowson

Ok, but could you elaborate please? O would be interested to know the cause of this issue. Thanks, John

Yes - you can pass the value as a parameter to the axis control/event.

That was what I was asking you...aren't they the same? I would have thought that P3D populates the ATC MODEL simvar from the atc_model entry in the aircraft.cfg. So they are the same and there is no point adding atc_model. In MSFS I thought (but didn't check) that icao_type_designator would be distinct from ATC MODEL, and so added it, but it also may be the same as ATC MODEL...but I thought that would maybe match icao_model... I will re-check this in MSFS/FSUIPC7, but still don;t think its worth adding this in FSUIPC6 unless it is actually distinct from offset 0x3500,

But isn't that also stored in the ATC MODEL simvar held in offset 0x3500?

I should have checked before adding.... The ICAO information doesn't seem to be available in the aircraft.cfg files in P3D. I've checked several aircraft and can't see any ICAO entries anywhere (in MSFS they are in the [General] section). So it won't be possible to add this - I will remove. John

I will check this. If FSUIPC sees them as two distinct axis, then the calibration for each should be separate, regardless of how they are seen in windows game controllers - although that also surprises me. Could you show me / attach your current FSUIPC7.ini file so I can check your current assignments. You should be able to calibrate that control, including reverse, in the Throttle calibration tab. Try that first. Otherwise you can reverse any axis by adding a scaling factor of -1 to the axes assignment entry in your FSUIPC7.ini file. There is a section entitled Additional parameters to scale input axis values on page 42 of the Advanced User guide on how to do this. By default, anything calibrated in FSUIPC's calibration tab also affects axes assigned with 'Send to FS as normal control', it just happens in a different order. When assign with 'Send direct to FSUIPC calibration', the axes values are calibrated before being sent to the FS. When assigned with 'Send to FS as normal control', the uncalibrated value is sent to the FS, the FS then sends back the event with the value, which FSUIPC then masks (i.e. blocks), calibrates the value with that event and re-sends it. Its rather technical, but its easier to first always try with 'Send direct to FSUIPC calibration' if the axis is available there and also calibrate. If not, or if this causes any issues/doesn't work, switch to using 'Send to FS as normal control'. And when using this method, you can try calibration but if that causes issues then remove/reset the calibration and use axis scaling if you need to reverse. The specific helicopter axes are mapped to the equivalent aircraft calibration panels, so you should be able to calibrate "Axis Collective Set" in the Throttle calibration panel. Try that - if you can't calibrate there, then you can reverse via axis scaling. Those are slightly different. The first is for button/key assignments, which can easily be handled via offset conditions (although that is an old post and the Camera State offset wasn't available then and so wasn't mentioned explicitly). The second was to disable flight controls when AP is active, which is possible via the solution provided, In fact, that second post provides another solution for your issue. You could have a lua script running that monitors the camera state offset, and when that changes to 4 it can update offset 0x310A to disable the flight control axes, and when changed away from 4 to reset. Should be a pretty simple script - I can provide you one to try if you like (over the weekend).

Upload limits are restricted for new uses - your limit will increase the more you post. You can compress the file, but if still to large you will have to use one of the (free) file transfer services, such as https://filetransfer.io/. Sorry, but I have no idea what that is - are you actually using the WebSocketServer? Does the FBW Remote Tool use the WebSocketServer? This is confusing...the myOffsets.txt file is for adding simvars to offsets, not lvars. And I have no idea what the "legacy LVAR Interface" is. As this is from the "FBW Remote Tool ", you should contact them to see what this means and what you need to do to correct this. Please post/update here if/when you have further information. John

Are you sure? Mine are two distinct axes - X and R. If they are distinct axes, you can assign and calibrate distinctly, including reverse. You can also reverse without calibrating, by adding a scaling factor of -1 to the assignment in your in - see the Advanced User guide for details. (Note you need to click Rescan to pick up a second axis after the first has been assigned). If they are both are on the same axes, then I can only assume that one trigger controls the +ve values and the other the -ve. If thats the case, then you can assign your trigger (either one!) to both controls (or all three -throttle, left brake and right brake) and then calibrate the throttle on the left trigger for one set of values and for left/right brake on the right trigger for the other ser of values. You can assign to Axis Collective Set, but only when assigning with 'Send to FS as normal control'. You should also be able to calibrate this axes in FSUIPC when assigned like this, if needed, although calibrating when assign with 'Send to FS as normal control' can sometimes cause issues (but usually not). Hmm, yes - I can see that would be an issue.... FSUIPC knows nothing about the modes. However, it does hold the camera state in offset 0x026D, which will be 4 when in Drone Mode. You can configure button and key assignments to be dependent on offsets, so they can trigger one action when an offset holds one value and another (ir none at all) when it holds a different value. So this would work for button/key assignments, but unfortunately this is not possible with axes assignments. Se the Advanced User manual, section Adding offset conditions, on how to use this functionality. So, the only way you could currently handle this with FSUIPC would to use a lua script instead. The way this works is that you configure your trigger to write its axis value to an FSUIPC offset. You then have a lua script running that picks up changes to this offset, and when it gets a new value it can then calibrate it and decide what to do with it, i.e. send it on to the FS if in normal mode, or ignore (or send a different control) if in drone mode. I will have a think to see if I could add something simple to handle this - maybe another ini parameter that, when set, would instruct FSUIPC to not send on axes controls if in Drone mode. This would be pretty blunt though and suppress all axes, although I could maybe allow a parameter to specify the axes letters to ignore. I will take a look when time permits, but it may take me a while to get around to this (I am pretty busy at the moment!). John

@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