Target Device Analyzer: no Thrustmaster combined when script is running

[Lange_666]

Target Device Analyzer:

When no script is running i have bot the stick and the throttle as separate devices in the Target Device Analyzer.

However, seeing some pictures where the Thrustmaster combined shows in the (when a script is running) Target Device Analyzer, i wonder what setting needs to be set to get that combined device in the Target Device Analyzer, i don't have that (i do have other devices in there like the MFG rudders)?

[sedenion]

You do not need specific setting, indeed while script is running the Device Analyzer should show you the virtual device with the two physical devices on the left frame. However, Device Analyzer is not realy reactive, and may even cause some trouble if you let it run while you start or stop a script. Before your start or stop a script it is better to close the Device Analyzer and open it again once the script is running or stopped.

Edited October 1, 2021 by sedenion

[Lange_666]

Well, it never showed the combined device in any way (and still doesn't whatever i try). Thought this was normal behavior when a couple of days ago i saw a screenshot with the combined device showing on the analyzer. I then had something like... WTF...

[_Hoss]

If you are running Target GUI or TARGET Script Editor with the green arrow checked, so it's a red square it's in "Combined" mode.  Looking at Device Analyzer to determine if it's there can be confusing.  Where you need to look is start TARGET, and go into DCS and see if the "Joystick", "Throttle" and COMBINED are showing on the settings page as controllers.  Never use the Joystick/Throttle columns for commands, always put everything in Combined, unless you have another controller like I do... BlackHog Explorer.  You need to clear out those columns before you go in and start assigning DX keystrokes, that's step number one (having a clean sheet before you start).  Or you will have multiple devices throwing out the same commands from different buttons, and you will see what "Hosed UP' looks like when you try to use it. 

Hoss

[Lange_666]

@352nd_Hoss: Thx for the input but that is not what i'm after. I have the TM Combined within DCS (i write and run my own scripts). Both stick and throttle show up as separate devices in the Analyzer (and in DCS) when not running a script but both vanish in the Analyzer when a script is run and are not replaced with a combined device. In DCS it does but not in the Analyzer.

The things is that i never saw that combined device come up in the "Target" Device Analyzer  and thought it was normal until i saw a picture here in the forum where it showed up as a combined device  in the Target Device Analyzer. I have never seen the combined device show up in the Analyzer so i wondered why.

Edited October 1, 2021 by Lange_666

[_Hoss]

Did you emulate them into one device in the Device manager?

 

[Lange_666]

Not sure what you mean by emulate here. At least i didn't emulate them into one device manually. That goes automatically once a script runs.

Once a script runs it shows up as Thrustmaster Combined in DCS (if no script runs it are 2 separate devices). Other games are the same.

If no script runs, it shows as 2 separate devices in TARGET Device Analyzer, if a script runs both separate devices vanishes in they but are not replaced by the virtual combined device. I was just wondering why not...

In Windows Device manager, once a script runs a Thrustmaster Devices shows up containing 3 entry's:

 

 

Once i stop a script, the above disappears again.

This is what i believe is normal behaviour. The only thing that it doesn't do is show up in the TARGET Device Analyzer as a combined device. For the rest everything works just fine.

Edited October 2, 2021 by Lange_666

[sedenion]

This is the normal behavior, you should theoretically see the virtual device in the Device Analyzer. Try to uninstall and reinstall with latest driver and software versions, and verify your devices have the latest firmware (but avoid flashing for nothing)... Maybe there is somewhere a variable, register value or something like this that is not correctly populated or a mismatch between software version, drivers and/or firmware version.

Edited October 2, 2021 by sedenion