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

[John Dowson]

Also, change this:

Quote

[Profile.Helicopter]
1=Bell 407 Blue-Gray
2=Bell 407 Black-Orange
3=Bell 407

to this:

Quote

[Profile.Helicopter]
1=Bell 407

(the first two entries are redundant)

That will match all Bell 407 variants. When you create or add an aircraft to a profile, the full name if the aircraft is used. You should always then edit/shorten the aircraft name in your [Profile.xxx] section to a substring to match all variants. This saves you having to add the aircraft to the profile when you use a different variant or livery.

 

[peloto]

2 hours ago, John Dowson said:

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.

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

Ah ok, done.

I have been testing with the default 407, in FS20-24, in FS24 I am in the beta, I stabilise the helicopter trimming it in the air then I go to Drone mode and all is well, less when I press the right trigger (that is binded to the collective in FSUIPC7) to up the Drone and then released, and then the collective is full to down and helicopter goes to down. Yes I have removed the left and right triggers only, the only what I use in FSUIPC7 by the moment, if not other assigns automatic added by FSUIPC7?, the others assignments are the same, it flights well so, maybe I have some props assignments?, and that interferes?, I have to check tomorrow.

FSUIPC7.log FSUIPC7.ini

[peloto]

4 hours ago, John Dowson said:

Also, change this:

to this:

(the first two entries are redundant)

That will match all Bell 407 variants. When you create or add an aircraft to a profile, the full name if the aircraft is used. You should always then edit/shorten the aircraft name in your [Profile.xxx] section to a substring to match all variants. This saves you having to add the aircraft to the profile when you use a different variant or livery.

 

Ah, ok, really thanks, great, I was thinking in that some times if it would be possible to do that and not each colour, I will do it. I didn´t watch the second page in my former response with this reply till now.

[John Dowson]

The script is working but only for airplane axes controls - offset 0x310A does not currently disable any of the helicopter specific axes. I will look into updating this to handle the helicopter-specific axes as well.

Also, offset 0x310A resets itself after 10 seconds, so the script will need updating to handle this as well.

 

[John Dowson]

Does the Axis Collective Set axis work for you with the Bell then?
Tried it here and that axis doesn't work - I have to use the throttle axis.

Can you try this attached version please: FSUIPC7.exe

That disables most of the helicopter axes via offset 0x310A, but I am not sure about the collective as the calibration for this is mapped to prop pitch which isn't suppressed by that offset, and I cannot test here as that axis isn't working in the Bell for me anyway.

Here is an updated lua script which keeps updating offset 0x310A until drone mode has exited: disableInDrone.lua

John

 

[John Dowson]

17 minutes ago, John Dowson said:

Does the Axis Collective Set axis work for you with the Bell then?
Tried it here and that axis doesn't work - I have to use the throttle axis.

It does work, but not if calibrated (in prop pitch calibration panel).

Try the attached please: FSUIPC7.exe

[peloto]

5 hours ago, John Dowson said:

It does work, but not if calibrated (in prop pitch calibration panel).

Try the attached please: FSUIPC7.exe

Great, with this FSUIPC7.exe the disableInDrone.lua works, I don´t know if the former disableInDrone.lua attached also, and with the original FSUIPC7.exe not. Maybe the only minor problem when you are not trimmed or with the collective-throttle position with buttons etc., and you have pressed the trigger, you need maintain the position in the trigger one second or so, because FSUIPC7 disabling its control in that axis is not instantaneous, and that is not a problem really, and maybe better done so to not consume too much resources?.

 

Yes "Axis Collective Set" works for me in the 407, only I need to have in FSUIPC7 in the axis calibration tab and then in the page of the Prop pitch calibration, in "axis not processed", do nothing there.

 

An all work in both FS20/24.

[John Dowson]

11 hours ago, peloto said:

I don´t know if the former disableInDrone.lua attached also, and with the original FSUIPC7.exe not.

The previous disableInDrone.lua only disabled for 10 seconds, and in the previous FSUIPC7.exe all main flight axes (including the helicopter specific ones) were disabled except for the collective.

11 hours ago, peloto said:

Maybe the only minor problem when you are not trimmed or with the collective-throttle position with buttons etc., and you have pressed the trigger, you need maintain the position in the trigger one second or so, because FSUIPC7 disabling its control in that axis is not instantaneous, and that is not a problem really, and maybe better done so to not consume too much resources?

There is always some latency with these type of things (nothing to do with  resources) and it won't be instantaneous - nothing is! However a second seems way to high and it should be a couple of hundred ms at the max. Appropriate logging would give more exact times, from FSUIPC's point-of-view (i.e. it only knows, for example, that drone mode is activated once it receives an update of the CAMERA STATE simvar which is going to take time getting from the FS to FSUIPC).

12 hours ago, peloto said:

Yes "Axis Collective Set" works for me in the 407, only I need to have in FSUIPC7 in the axis calibration tab and then in the page of the Prop pitch calibration, in "axis not processed", do nothing there.

As I said it does work when not calibrated. You can calibrate this in the prop pitch panel (on page 2 of the calibration screens, not the separate ones in page 5) but if you do this it stops working, As I said previously, you can post-calibrate (i.e. calibrate when assigned with 'Send to FS as normal axis') most axes for most aircraft, but this can cause issues with sine due to priority levels. If this is the case, you cannot calibrate in FSUIPC's calibration tabs and would have to use the scaling functionality (or lua) instead.

John

[peloto]

Really thanks. Yes, and sure the culprit in not being more fast detecting the CAMERA STATE, is from MSFS´s Simvars times, and there isn´t nothing to do there.

 

Excellent support

 

Enjoying more MSFS with FSUIPC7, thanks!