I was able to overcome this problem, although I’m not 100% positive my issue was exactly the same as everyone else.
I’m using XOutput to map my TB VelocityOne yoke and pedals into 3 virtual controllers. They do show up as 3 distinct controllers in MSFS. I’ve got them named V1 yoke, V1 throttle and V1 pedals.
As long as I activate them in XOutput after MSFS is already up and I bring them up in the same order each time, they are recognized properly in the MSFS controller list.
My issue stemmed from the fact that I was assigning commands from each of them into a single profile. This caused inputs from any one of the three controllers to be recognized as input, resulting in things like the rudder pedals controlling the throttle and such.
The solution was to create a separate profile for each controller and only map commands within that profile to a single controller. So for example, I have a profile for the yoke, another for the throttle quadrant and a third for the pedals.
Someone here may have tried to tell me this once, but it never clicked as to what they were saying. With each controller using its own profile, I’m no longer having conflicts across controllers and I’ve been able to get everything working as desired except for the elevator trim wheel and the Status Information Panel (SIP). I mapped a switch on the yoke for trim and didn’t pay that much attention to the SIP anyway.
I’m over the moon about this. I’m finished with Xbox and committed to running solely on GeForce Now from now on. It’s $200/yr for the Ultimate service and I’m running everything at Ultra levels and getting over 90 FPS.