I can go into the settings in the game and change that axis to the right one (confirming TARGET is passing the right parameter to the game), but once I back out, the axis does not work in flight and when I go back into the settings, the wrong axis is entered in that field again. Not even sure what input3 is or why it's there, but in the xml config when I export it, the yaw parameter is set to 'js1_x', so it's showing right in the SC controls config. For some frickin reason, it wants to set itself to 'Z-Axis (input 3)(input 3)'. But TARGET is up to date and its script runs fine, all buttons and axes seem to be ok. Not sure if I should contact SC/RSI or post somewhere else or if one of you guys may have run into this.

I'm having a bear of a time getting one last axis to map properly and I can't figure out for the life of me what's going on. I have t.16000m hotas setup and it was doing alright but I figured I'd give the 2x joystick setup a try. Sorry to bump such an old thread but I figured I'd rather do that than recreate a similar topic.