piper99

Hi Pete, Thanks for your very detailed answer. The joystick is disabled in FS, so axis assignment in FS shouldn't have any effect, should they? I am afraid this is not the reason. Joystick is disabled and calibration is ok (sensitivity max, null zone min). That is likely to be the case, indeed. I tried with the following aircrafts: Aussim Warrior, PMDG 737, PMDG 747. The first two won't work with "send to FS". The 747 works with any method. (I asked PMDG why their 737 could behave differently than the 747 but they don't answer) I did read that part of the manual. However because I don't know about the internals of FS nor about how panels integrate with FS and FSUIPC, I can't cleary understand what is the effect of "send direct FSUIPC" vs. "send to FS". Anyway I think I can now better guess what could be happening: with "send direct to FSUIPC", aircraft panels cannot access the axis before FSUIPC calibration, which is where the flaps detents are created. So with "send to FS", some aircraft panels may intercept the axis before FSUIPC gets a chance to create the flap detents. Would that be correct? Cheers, Christophe.

Hi, In trying to assign an axis to control the flaps (including flaps detents) I noticed it didn't work with some my add-on aircrafts (the flap lever is jumping all over the place). However when I changed the default "send to FS as normal axis" to "send direct to FSUIPC calibration", it all works fine! I am happy but I am curious to know why using "send direct to FSUIPC calibration" makes it work. Unfortunately the manual does not tell much about the difference between "send direct to FSUIPC" and "send to FS". Cheers, Christophe. PS: if it matters, I use FS2004, FSUIPC 3.65, Joystick disabled in FS, flaps axis assigned and calibrated in FSUIPC, aircraft specific.