N8LBV - I just duplicated your setup on the Taranis, and it too gave me the 64% centers in RF, even though it appeared to calibrate fine in Windows. I then went in and assigned 3 position switches to channels 5-8, and 2 pos to higher channels. (I could have used knobs or sliders in place of the 3 pos. switches, as I also tested that). It then worked perfectly fine in Windows AND in Realflight.
It appears that first 8 channels really want to have something controlling them. Skipping plays havoc with the calibrations. I did not evaluate whether the center is critical, or it just needs a high and a low. As I've noted before, you can continue on the TX to assign as many switches to high channels (9 and above) as you want, and they will be recognized by Win and RF as on/off buttons. 3 pos will only have one position seen as being "on".
No harm or foul by setting up more channels and switches than you will really map in the controller setup, and just leave the others unmapped.
I'm kind of done testing on my end. Try populating all 8 lower channels with anything, and see if just making them all have something attached as a control settles things down.
BTW - in OpenTX, the order of the list in Inputs has no bearing on the order of channels assigned in the Mixer. It is just a list. All that matters in the Mixer is that you pick something for a channel to work - either a native control, or something from somewhere on the Input list.
If yours does then begin to play nice, I think we have maybe found it - RF 8 really wants all 8 channels to be controlled, and doesn't deal well if it isn't getting full data from the Windows layer. And likely RF 9, being more recent, has had that problem addressed in it's implementation. I won't hold my breath for a retroactive fix, though.
It appears that first 8 channels really want to have something controlling them. Skipping plays havoc with the calibrations. I did not evaluate whether the center is critical, or it just needs a high and a low. As I've noted before, you can continue on the TX to assign as many switches to high channels (9 and above) as you want, and they will be recognized by Win and RF as on/off buttons. 3 pos will only have one position seen as being "on".
No harm or foul by setting up more channels and switches than you will really map in the controller setup, and just leave the others unmapped.
I'm kind of done testing on my end. Try populating all 8 lower channels with anything, and see if just making them all have something attached as a control settles things down.
BTW - in OpenTX, the order of the list in Inputs has no bearing on the order of channels assigned in the Mixer. It is just a list. All that matters in the Mixer is that you pick something for a channel to work - either a native control, or something from somewhere on the Input list.
If yours does then begin to play nice, I think we have maybe found it - RF 8 really wants all 8 channels to be controlled, and doesn't deal well if it isn't getting full data from the Windows layer. And likely RF 9, being more recent, has had that problem addressed in it's implementation. I won't hold my breath for a retroactive fix, though.