Does Comanche 2020 support multiple joysticks, or setting the joystick among all available on your system. Most new games do, so I assume the answer is yes.
When you compile and run a TARGET profile or script (be it in the GUI, or the Script editor), TARGET disables your existing controllers (the T16000M should disappear from the game controller list) and creates a new virtual controller called "Thrustmaster Combined". Did you see this and tell Comanche to use that controller?
If you don't see it in Comanche, close the game, make sure the TARGET profile is running, then re-run the game. Most new games will rescan the game controller list when there is a change, but some games do not, so they only know of the controllers that exist when the game is run. With those games, if you run the TARGET profile after the game is running, it may not see the change. Or, you may find that the game can see the new controller and save it as the controller to use, but maybe when you re-run the game while Thrustmaster Combined is missing, if it doesn't see the controller you previously configured, it may default to a different controller.
A few other comments about how TARGE works...
Both the TARGET GUI and the TARGET Script editor eventually compile a TARGET Script and run it. This script is the script you would see in the TARGET Script editor if using that program. In the case of the GUI, when you run the script, it generates and exports a TARGET Script and then runs a separate window which is the compiler which compiles and runs the script. That window in the GUI does exactly what the TARGET Script Editor does to run script as well.
The file you load in the TARGET GUI is a .fcf file. This file stores info that the TARGET GUI needs but not the TARGET Script Editor. The TARGET Script Editor cannot read the .fcf file. Instead, the GUI must create a .tmc file and pass it to the compiler window. In the TARGET GUI, there is a button you can click that will export the .tmc file, which is a good way to see how your configuration in the GUI can be done in the TARGET Script Editor. Or you can use that file as a starting point to add more advanced features which are not easy or possible to add using the TARGET GUI.
The file you load in the TARGET Script Editor is a .tmc and .ttm file. The .tmc file is the main file (you only have to load the .tmc file), and it references the .ttm file for additional information. In fact, in the Script Editor, when you load a .tmc file, since it references the .ttm file, the Editor will automatically load the .ttm file for you when you compile a script. Additionally, you will see it load some additional .tmh files (target.tmh, sys.tmh, hid.tmh and defines.tmh). These .tmh files are system files used by TARGET and you would not normally edit them. Meaning you should not edit them unless you really know what you are doing.
The above is just an overview of some basic concepts that help understand what is going on. For a tutorial, it is best to follow the Thrustmaster TARGET documentation carefully and come back here with questions. The documentation is pretty thorough, but yes, it may not explain a lot about the background details like I have explained above. So don't hesitate to ask specific questions.
