Problem with 'Multiple Throttle Synchronisation' interfering

[jp.pilot]

Peter,

I appear to be having a slight issue with the ‘Multiple Throttle Synchronisation' interfering with the elevator trim, and would be very grateful if you could assist me (or anyone else who might know).

I have the following set up on my computer:

CH Yoke (which I assign two buttons for trim, and another to enable ‘Multiple Throttle Synchronisation’), CH Pedals and the Saitek throttle quadrant.

I often enable Multiple Throttle Synchronisation as the accuracy of the potentiometers is not that good on the throttle quadrant, but what I do notice is that I am not able to use my elevator trim (whether on the yoke or keyboard). On the Level-D 767 you see the number jump up (or down depending on trimming up or down) one decimal place and instantly jumps back down. The autopilot is also unable to control pitch. I have tried enabling ‘Discon elev trim for AP’, but that does not make a difference, and within the axis calibration there are values in the elevator axis box. When I disengage ‘Multiple Throttle Synchronisation’, the elevator trim works fine and so does the autopilot and the elevator trim within the calibration shows ‘0’.

This is also the same for the PMDG 747. I will not use ‘Multiple Throttle Synchronisation’ anymore, but if you could like into it I would appreciate it.

If you require any further assistance then I am more than happy to help.

Regards,

JP

[Pete Dowson]

I often enable Multiple Throttle Synchronisation as the accuracy of the potentiometers is not that good on the throttle quadrant, but what I do notice is that I am not able to use my elevator trim (whether on the yoke or keyboard). On the Level-D 767 you see the number jump up (or down depending on trimming up or down) one decimal place and instantly jumps back down. The autopilot is also unable to control pitch.

Strange -- there's really no relationship at all between throttles and elevator, trim or otherwise.

I will not use ‘Multiple Throttle Synchronisation’ anymore, but if you could like into it I would appreciate it. If you require any further assistance then I am more than happy to help.

Yes, please. To start with I need the usual basic information, missing above, such as

* Version of FS?

* Version of FSUIPC?

* If not the latest version (from the downloads announcements above ), please try that first and report back.

* What about default FS aircraft? You only mention two add-ons. If it is okay with the default it is most likely interaction with some non-standard controls in the add-on panels.

I'm afraid after tomorrow (Monday) afternoon I am away for 8 days, then back for only a couple of days before going away again till December 4th, so it may not get attention till then. I would probably then need some logging performed, because it sounds like some of your controls may be interfering with each other. Certainly logging will be necessary if I cannot reproduce it here -- and I cannot even attempt to without knowing what versions of what you are talking about.

Regards,

Pete

[Pete Dowson]

Just to try to speed this up (since I've not much time before December 4th) I re-checked the FSUIPC throttle sync hot key facility as follows:

Latest FSUIPC3 in FS9 and default 737:

--- throttles 1 and 2 assigned via FS controls. Trim keys (NUM 1 and NUM 7) worked fine when throttle sync enabled.

--- throttles 1 and 2 assigned via FSUIPC direct. Trim keys (NUM 1 and NUM 7) worked fine when throttle sync enabled.

Latest FSUIPC4 in FSX and default 737:

--- throttles 1 and 2 assigned via FS controls. Trim keys (NUM 1 and NUM 7) worked fine when throttle sync enabled.

--- throttles 1 and 2 assigned via FSUIPC4 direct. Trim keys (NUM 1 and NUM 7) worked fine when throttle sync enabled.

I also scanned through the code to see if there was any possible contact point between these completely separate aircraft control functions, and there is not.

There were some changes in some of the incremental updates since FSUIPC 3.75 which upset the PMDG aircraft, but those were fixed pretty quickly. The problem with you not reporting which FSUIPC version you are using is that I can only guess. In fact I can't really even guess if you meant FS9 or FSX.

Otherwise I'm afraid it is certainly looking as if you have some control interference or maybe duplication in your setup. You may need to go through a process of elimination. First though do please test using the very latest FSUIPC updates from the Announcements above.

If you want any more help, do please try to remember that I need to know rather more that you told me so far. Logging of Axis and Events might help too. But I may not be able to look at this for a while, as I said.

Regards

Pete

[jp.pilot]

Hello Pete,

Many thanks for getting back to me so quickly. I will do some more testing and try the process of elimination, but unfortunately I have a lot of work to do so won't be able to do that for a few days. I am using FS9, and version 3.766. If I do find the solution I will report here in the forum, in case anyone else has a similar problem. It must be my setup, so sorry I caused all this confusion.

Regards,

JP

[Pete Dowson]

Many thanks for getting back to me so quickly. I will do some more testing and try the process of elimination, but unfortunately I have a lot of work to do so won't be able to do that for a few days. I am using FS9, and version 3.766. If I do find the solution I will report here in the forum, in case anyone else has a similar problem. It must be my setup, so sorry I caused all this confusion.

No confusion, and not a problem. Please do come back if you find anything else. As I said, logging in FSUIPC might help. But I think some process of elimination will be most enlightening. I'm not here again till the 14th in any case, so there's no need to rush anything for my benefit! ;-)

Regards

Pete