As I understand it the script isn’t all of the binds. If you don’t explicitly bind a button TARGET will do it for you anyway. To actually get a null result the button must be explicitly bound to 0, a.k.a. the null output. A comment “handled by key file” suggests that the explicit bind was omitted from the script and the key file relies on this secondary behavior.
The other possibility is that particular TARGET script is excluding the joystick but puts the comments in the script for the joystick anyway as a reminder.
So if I understand correctly, its safer to bind in TARGET. The TM script manual is very basic. I wish there was something more comprehensive out there. There is scripting in some of the profiles that is not really covered that well in the manual, and TM’s support kind of sucks.
Prior to the issue, I was aware of the sorting issue. But I didn’t think it applied to rudder pedals as it has not buttons. I guess it does…Something good to know.
Thanks for you thoughts on the matter.