In Xbox gamepads, RT or LT triggers for throttle, collective or brakes etc., they have only erroneously half path movement.

[peloto]

In Xbox gamepads, if I select the RT or LT triggers for throttle, collective or brakes, they have only erroneously half movement, not like other Flight Simulators. I press-release the left/right trigger, and e.g. collective and only moves from middle to full, never back again totally, so you have always half applied throttle or collective or brakes.

 

The problem is that both triggers are the same axis, there are other flight o racer simulators that they have not problem with this and triggers for a full movement despite being both triggers the same axis.

Can I configuring FSUIPC7 solve this?

 

I have this thread in MSFS forum searching help: https://forums.flightsimulator.com/t/xbox-gamepads-rt-lt-not-working-properly/666892

[John Dowson]

1 hour ago, peloto said:

In Xbox gamepads, if I select the RT or LT triggers for throttle, collective or brakes, they have only erroneously half movement, not like other Flight Simulators. I press-release the left/right trigger, and e.g. collective and only moves from middle to full, never back again totally, so you have always half applied throttle or collective or brakes.

The problem is that both triggers are the same axis, there are other flight o racer simulators that they have not problem with this and triggers for a full movement despite being both triggers the same axis.

So this is with the default MSFS assignments?

1 hour ago, peloto said:

Can I configuring FSUIPC7 solve this?

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:

Quote

XINPUT devices, such as the XBox One and XBox 360 controllers do not work natively with FSUIPC7.
If you want to use FSUIPC7 with such devices, you will need to install and configure a conversion utility called XInput Plus.
Please see the following tutorial:
    https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/
It has been reported that the UI for this utility is also now available in English.
Also note that you need to point this utility to the FSUIPC7.exe, not the MSFS.exe.
 

John

[peloto]

@John Dowson Really thanks.

 

Yes with the default MSFS assignments. Thanks for the help, lets go to test with Xinput Plus also. Regards.

[peloto]

There is no way, despite I select XInput Plus to FSUIPC7.exe  I don´t find the way in both programs, maybe I do something wrong or I don´t do what I have to do and I miss some step, despite XInput Plus have apparently the solution with their settings selecting in its options "Half+" or "Half-" regarding its manual and what I understand, and XInput sounds when FSUIPC7 starts, like it had the link and the modofied assignement done from XInput Plus,
 

Quote

 

You can now re-assign the controls/axis as you see fit. For instance, if your game is expecting the LT/RT (left trigger/right trigger) to map to the Z Axis/Z rotation, then you would use the drop down box and select this.

Notice the drop down box to the right of “LT/RT”. In the picture, it’s currently blank. If you click on this box, you will see the following options.

Invert – Inverts the axis. If, for instance, you’re playing your game and your car is accelerating when it should be standing still, and coming to a halt when you put the trigger down, you need to invert the axis.

Half (+) – See below.

Half (-) – This option needs a little explanation. In DirectInput, an analogue axis has a range of digital values from -10000 to +10000. The problem is that some games expect the rest/no input position to be at -10000 and some expect it to be at 0. If you were using a joystick, for example, the rest position would be at 0, while fully pulled back might be -10000 and fully pushed forward might be +10000.

In Xinput Plus, if you have neither Half (+) nor Half (-) selected, the analogue triggers input will be at -10000 at rest, going to +10000 when fully depressed. If you select Half (+), the analogue triggers will have a value of 0 at rest, going to +10000 when fully depressed. Selecting Half (-) will mean the analogue triggers will have a value of 0 at rest, going to -10000 when fully depressed.

Where might you need these settings? If your car starts to accelerate away before you touch your controller, but doesn’t go to full throttle until you press the trigger down all the way, then you may need the Half (+) or Half (-) options. Likewise, if the deadzone on the trigger (that is, the amount you have to push it to register any input) seems too high, you might need to use these options too.

 

neither I can´t point XInput Plus directly to FS20 Flightsimulator.exe like this user, for some file rights and blocked by Microsoft or something so and regarded only to the MS Store versions, not Steam versions of MSFS..., maybe my next MSFS version is Steam and for more reasons regarding MS Store and Xbox App issues I have had,

https://www.flightsim.com/forums/topic/57714-xinput-plus-not-working-with-fs2020

 

If someone know more and can help, really thanks, or if someone can test XInput Plus in a MSFS Steam version maybe would help.

[John Dowson]

10 hours ago, peloto said:

There is no way, despite I select XInput Plus to FSUIPC7.exe

But that won't work - as it says in the README.txt, you need to point it to the flightsimulator.exe.

10 hours ago, peloto said:

neither I can´t point XInput Plus directly to FS20 Flightsimulator.exe like this user, for some file rights and blocked by Microsoft or something so and regarded only to the MS Store versions, not Steam versions of MSFS

So you are using an MSFS Store version?

10 hours ago, peloto said:

If someone know more and can help,

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.

10 hours ago, peloto said:

if someone can test XInput Plus in a MSFS Steam version maybe would help.

I could do this, but it may take a few days - maybe I will find time at the weekend...

John

[peloto]

Really thanks @John Dowson, yes when you can, thanks for the help.

And yes, I can´t select that FlightSimulator.exe of my MS Store version with XInput Plus, XInput Plus tells me always that I don´t have the permission to open the Flightsimulator.exe file, the other MSFS .exe gamelaunchhelper.exe that is just next to the Flightsimulator.exe file, and it can launch MSFS also, I can yes select it with XInput, but nothing happens regarding the Xbox Gamepad axis.

Reading people I understand that they are saying that it is only related to the Windows-Xbox-MS Store versions (named UWP games?), and that not happens in the Steam version Flightsimulator.exe file?

Quote

 

Dolemoo

Posted June 27, 2023

 UWP games have different permissions and security settings than Win32 games, which are games downloaded from Steam or other sources. Therefore, you may not be able to access the Flightsimulator.exe file or apply the Xinput Plus settings to it. When you use a tool like UWPHook to add your UWP games to Steam and use the Steam controller rebinding feature. This may allow you to use your Xinput controller with FSUIPC7 without having to run FS2020 in windowed mode.

 

Quote

 

edgermiles

Posted July 8, 2023

if your game's were downloaded from steam then you also get an .exe file which you can easily store into your system, but it seems UWP games don't gave that advantages.

 

Thanks!

[John Dowson]

1 hour ago, peloto said:

And yes, I can´t select that FlightSimulator.exe of my MS Store version with XInput Plus, XInput Plus tells me always that I don´t have the permission to open the Flightsimulator.exe file

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

 

[John Dowson]

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

Quote

If you can’t seem to get Xinput Plus to work with your game, try going to the “Setting” tab, then selecting “DLL Files”, as per the picture below.

 

 

[John Dowson]

4 hours ago, John Dowson said:

14 hours ago, peloto said:

There is no way, despite I select XInput Plus to FSUIPC7.exe

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.

 

[John Dowson]

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

[peloto]

@John Dowson Haha no problem at all, haha.

 

I had only the DLL 1_3 checked and 64bit, not all, I have to test with all checked also then, or one by one, thanks.

 

Ok, really thanks for all the help, I have to test again all that this night.

 

What I tested was if Half+ or Half- in Xinput settings and pointed to FSUIPC7 then and saved Xinput config in FSUIPC7, and in FSUIPC7 I didn’t touch nothing because I didn´t find to do that what I am seeking in the options, that is to have a full movement in the triggers axis, and I didn´t watched nothing happening in MSFS neither after doing all that, and after that FSUIPC7 starts correct with the sound that Xinput adds its settings to FSUIPC7, to inform you that it is working with the program selected and the Xinput settings in FSUIPC7, but I don´t watch nothing that now the Xbox gamepad triggers have full movement, either in FSUIPC7 or MSFS, all is the same, and the curves in MSFS when I move the triggers they move the same and only half movement.

 

I think I had selected also "Send direct to FSUIPC calibration" in one of the multiple tries testing, I am novice using FSUIPC7, but sure it is functioning well in that way, though I can´t make the triggers with full movement for throttle etc., they move only to the middle to the top and back to the middle, only half movement, both triggers. Thank thanks.

[John Dowson]

11 minutes ago, peloto said:

What I tested was if Half+ or Half- in Xinput settings

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.
 

15 minutes ago, peloto said:

I think I had selected also "Send direct to FSUIPC calibration" in one of the multiple tries testing,

But you also need to calibrate!

[John Dowson]

17 minutes ago, peloto said:

I had only the DLL 1_3 checked and 64bit, not all, I have to test with all checked also then, or one by one, thanks.

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.

[John Dowson]

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.

[peloto]

@John Dowson Ok ok, great, thanks, lets go to test with all that.

[peloto]

Solved, yes and I can set the right trigger for throttles and left for right-left brakes, and full movements, though for brakes left-trigger I need to have pressed to release brakes, and I can´t reverse that because then it messes with the right trigger and reverse the throttle, then the right trigger released would be full throttle, because they are the same axis I think.

 

And also enabled DirectInput Output in XInputPlus (DirectInput tab), it is necessary yes, tested without it, if not FSUIPC7 doesn´t do that beep sound that XInput Plus adds to the program.

 

What I miss in the drop-down in the Axes Assignments tab, and I think it is very important, is the option for the collective axis, sometimes I fly a lot helicopters, collective axis that is bound also to throttle axis in MSFS, and you can fly the helicopters with the throttle axis assigned like FSUIPC7 does, but I think the collective axis and the throttle axis act different in the behaviour of the helicopter, and better for helicopters the collective axis, more smooth-precise-controllable the helicopter, through a test I did many months ago, I experienced that, maybe I am wrong?

 

Really thanks, a needed purchase for sure to solve this problem with the triggers that I have since the launch of MSFS and they didn´t solve never, and FS24 is the same. Thanks.

 

After test, now I go to fly with my new throttles!

[peloto]

Another thing is that with the helicopter (other aircrafts the same surely), when I am flying stabilised (or not) trimmed e.g., and I go to drone mode and I press the right trigger to go up with the drone, the FSUIPC7 throttle still work with that trigger and the collective-throttle is moved while in Drone Mode still and that is a "disaster" haha, and with MSFS that doesn´t happen, and in Drone mode the right trigger stop functioning like collective-throttle and it is not moved, only with the Drone mode assignments, maybe there is a solution-option already in settings?

[John Dowson]

10 hours ago, peloto said:

can set the right trigger for throttles and left for right-left brakes, and full movements, though for brakes left-trigger I need to have pressed to release brakes, and I can´t reverse that because then it messes with the right trigger and reverse the throttle, then the right trigger released would be full throttle, because they are the same axis I think.

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.

10 hours ago, peloto said:

What I miss in the drop-down in the Axes Assignments tab, and I think it is very important, is the option for the collective axis, sometimes I fly a lot helicopters, collective axis that is bound also to throttle axis in MSFS, and you can fly the helicopters with the throttle axis assigned like FSUIPC7 does, but I think the collective axis and the throttle axis act different in the behaviour of the helicopter, and better for helicopters the collective axis, more smooth-precise-controllable the helicopter, through a test I did many months ago, I experienced that, maybe I am wrong?

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).

6 hours ago, peloto said:

Another thing is that with the helicopter (other aircrafts the same surely), when I am flying stabilised (or not) trimmed e.g., and I go to drone mode and I press the right trigger to go up with the drone, the FSUIPC7 throttle still work with that trigger and the collective-throttle is moved while in Drone Mode still and that is a "disaster" haha, and with MSFS that doesn´t happen, and in Drone mode the right trigger stop functioning like collective-throttle and it is not moved, only with the Drone mode assignments, maybe there is a solution-option already in settings?

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

 

[peloto]

@John Dowson 

Yep, mine both triggers axis are different also Z-R in FSUIPC7, though regarding its Microsoft driver apparently since a pair of years they did it like one axis, against two like the previous Xbox gamepad drivers and apparently there began all my problems with the RL-RT triggers axis and only half path, and in the gamepad Windows calibration in "Devices and Printers page" in control panel, it is represented in only one axis called Z, and I think for that if I check the Rev box in FSUIPC7 in only one trigger axis is a mess, and in the other trigger axis the Rev box is checked automatically also, and I can´t change only separately the reverse in one of the triggers isolated, in both triggers the Rev box checked or not, weird or it is because they are the same axis?

Great to be able to assign the "Axis Collective Set" and in a new FSUIPC7 profile for helicopters and check 'Send to FS as normal control', buuut haha I can´t reverse the axis in the "calibration tab", and I need to reverse it, because unpressed the trigger is full collective an pressed release the collective, and if I leave the Gamepad in the desk without touching it the trigger is unpressed and then the collective, and if I am in the ground I need to have pressed the trigger and the gamepad in the hand to maintain the Helicopter quiet. Is there a reverse option for that trigger axis in the setting 'Send to FS as normal control'?

 

4 hours ago, John Dowson said:

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!).

 

Really thanks, that would solve the problem, yes, and to other users like these, that I found googleing for info

Yes ofc!, when you have the time, something for dummies like a check box haha, would be ideal.

 

Regards

[John Dowson]

13 minutes ago, peloto said:

if I check the Rev box in FSUIPC7 in only one trigger axis is a mess, and in the other trigger axis the Rev box is checked automatically also, and I can´t change only separately the reverse in one of the triggers isolated, in both triggers the Rev box checked or not, weird or it is because they are the same axis?

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.

16 minutes ago, peloto said:

Great to be able to assign the "Axis Collective Set" and in a new FSUIPC7 profile for helicopters and check 'Send to FS as normal control', buuut haha I can´t reverse the axis in the "calibration tab"

16 minutes ago, peloto said:

Is there a reverse option for that trigger axis in the setting 'Send to FS as normal control'?

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.

22 minutes ago, peloto said:

Great to be able to assign the "Axis Collective Set" and in a new FSUIPC7 profile for helicopters and check 'Send to FS as normal control', buuut haha I can´t reverse the axis in the "calibration tab", and I need to reverse it, because unpressed the trigger is full collective an pressed release the collective, and if I leave the Gamepad in the desk without touching it the trigger is unpressed and then the collective, and if I am in the ground I need to have pressed the trigger and the gamepad in the hand to maintain the Helicopter quiet. Is there a reverse option for that trigger axis in the setting 'Send to FS as normal control'?

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.

34 minutes ago, peloto said:

Really thanks, that would solve the problem, yes, and to other users like these, that I found googleing for info

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).

 

[peloto]

@John Dowson All solved. I was ticking for reverse the left/right brakes the wrong box haha.

 

Regarding reversing the collective axis solved also, not ticking the reverse box in throttle, it does still nothing, but adding *-1 to the end of that related axis like you told other user, I copy-paste all the string:

1=BR,256,F,67492,0,0,0,*-1    -{ TO SIM: AXIS_COLLECTIVE_SET }-

 

 

Yes, it is not the same those topics haha, but they are similar haha, asking for FSUIPC7 to do nothing with controls some times, when or in Drone mode or Camera-Photo Modes? in FS20-FS24, would be great.

FSUIPC7.iniFSUIPC7.ini

Regards!

Excellent support

 

[John Dowson]

5 minutes ago, peloto said:

@John Dowson All solved. I was ticking for reverse the left/right brakes the wrong box haha.

Ah, ok.

6 minutes ago, peloto said:

Regarding reversing the collective axis solved also, not ticking the reverse box in throttle, it does still nothing

Ah, sorry - it is not mapped to throttle, but to prop-pitch. It is the specific helicopter throttlr axes that are mapped to throttle calibration. From the changes.txt file (or FSUIPC history document) for 7.4.1:

Quote

  - allow the following helicopter axes to be calibrated using FSUIPC's calibration facilities:
        AXIS_CYCLIC_LATERAL_SET -> calibrate as Aileron
        AXIS_CYCLIC_LONGITUDINAL_SET  -> calibrate as Elevator
        AXIS_COLLECTIVE_SET -> calibrate as Prop-pitch
        AXIS_HELICOPTER_THROTTLE_SET -> calibrate as Throttle
        HELICOPTER_THROTTLE_SET -> calibrate as Throttle
        AXIS_HELICOPTER_THROTTLE1_SET -> calibrate as Throttle1
        HELICOPTER_THROTTLE1_SET -> calibrate as Throttle1
        AXIS_HELICOPTER_THROTTLE2_SET -> calibrate as Throttle2
        HELICOPTER_THROTTLE2_SET -> calibrate as Throttle2

I should really add that information to the calibration section of the user guide (not that many people actually consult the documentation...!).

12 minutes ago, peloto said:

but adding *-1 to the end of that related axis like you told other user,

Well, I also mentioned this method several times above...

13 minutes ago, peloto said:

Yes, it is not the same those topics haha, but they are similar haha, asking for FSUIPC7 to do nothing with controls some times, when or in Drone mode or Camera-Photo Modes? in FS20-FS24, would be great.

I will send you a lua to try for this functionality later today (hopefully) or over the weekend.

Cheers,

John

[John Dowson]

22 hours ago, John Dowson said:

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).

Please try this lua script: disableInDrone.lua

Save that to your FSUIPC7 installation folder. You then need to auto-start this lua plugin - you can do this by adding the following to your FSUIPC7.ini file:

Quote

[Auto]
1=Lua disableInDrone

John

[peloto]

@John Dowson Really thanks, but the lua for me does nothing in drone mode in FS22-24, maybe I am doing something bad?, I attach the .ini

 

And the Prop-pitch in the calibrate page for axis_collective_set either, if I set that calibration the collective is like freeze.

 

Not a problem, I am enjoying already the new axis, even the F-18 with FSUIPC7 has a full throttle path afterburners included, before I had to press a button for that, happy.

 

Regards

FSUIPC7.ini

[John Dowson]

36 minutes ago, peloto said:

 Really thanks, but the lua for me does nothing in drone mode in FS22-24, maybe I am doing something bad?, I attach the .ini

Please also attach your FSUIPC7.log file - that is file that tells me what is happening, To diagnose any issue, I need to see both your ini and log files from the same session, and always only attached AFTER FSUIPC has exited.

36 minutes ago, peloto said:

And the Prop-pitch in the calibrate page for axis_collective_set either, if I set that calibration the collective is like freeze.

Did you remove any assignments in MSFS? What aircraft/helicopter are you using?