Problems getting Warthog HOTAS to work in DCS with TARGET profile loaded

[Bahger]

I am tearing out what's left of my hair over this and would appreciate some advice.

 

It often takes more than three attempts, sometimes including a reboot and/or much switching my TM HOTAS devices on and off, to get the joystick recognised once I'm in the cockpit. I load the profile into TARGET, that goes fine and in the sim's control interface I load to right profiles into the Virtual Device and keyboard columns. The problem is that after most attempts, the joystick input is dead and I have to get out of the sim, stop the TARGET profile, and start the whole process again. Eventually it works.

 

I have disabled "Allow the Computer to Turn off This Device" in all Windows 10-connected USB devices. I know I have to do this after every update. As I said, I often disconnect and then reconnect all three TM devices before activating the TARGET profile, which creates the Virtual Device.

 

I could just make my own profile for the separate devices in the sim's Control interface but I really like this user-made TARGET profile, some scripting aspects of which cannot be replicated within DCS.

 

Can anybody give me some tips and tricks that might help me out here? Many thanks.

[mosqui]

I am tearing out what's left of my hair over this and would appreciate some advice.

 

It often takes more than three attempts, sometimes including a reboot and/or much switching my TM HOTAS devices on and off, to get the joystick recognised once I'm in the cockpit. I load the profile into TARGET, that goes fine and in the sim's control interface I load to right profiles into the Virtual Device and keyboard columns. The problem is that after most attempts, the joystick input is dead and I have to get out of the sim, stop the TARGET profile, and start the whole process again. Eventually it works.

 

I have disabled "Allow the Computer to Turn off This Device" in all Windows 10-connected USB devices. I know I have to do this after every update. As I said, I often disconnect and then reconnect all three TM devices before activating the TARGET profile, which creates the Virtual Device.

 

I could just make my own profile for the separate devices in the sim's Control interface but I really like this user-made TARGET profile, some scripting aspects of which cannot be replicated within DCS.

 

Can anybody give me some tips and tricks that might help me out here? Many thanks.

Do you need target really ?

My advise is do not use target and plug it direct .Windows 10 and dcs world setting Hotas perfect and no problem

[Bahger]

Do you need target really ?

My advise is do not use target and plug it direct .Windows 10 and dcs world setting Hotas perfect and no problem

 

Yes, I am on the verge of doing that; I suppose I could simply recreate almost all of the TARGET profile’s assignments (but not the scripting) directly into the DCS profile input and save it. What’s confusing about this situation is that sometimes it works exactly as it should and sometimes it doesn’t.

[Pac-Man]

I am tearing out what's left of my hair over this and would appreciate some advice.

 

It often takes more than three attempts, sometimes including a reboot and/or much switching my TM HOTAS devices on and off, to get the joystick recognised once I'm in the cockpit. I load the profile into TARGET, that goes fine and in the sim's control interface I load to right profiles into the Virtual Device and keyboard columns. The problem is that after most attempts, the joystick input is dead and I have to get out of the sim, stop the TARGET profile, and start the whole process again. Eventually it works.

 

I have disabled "Allow the Computer to Turn off This Device" in all Windows 10-connected USB devices. I know I have to do this after every update. As I said, I often disconnect and then reconnect all three TM devices before activating the TARGET profile, which creates the Virtual Device.

 

I could just make my own profile for the separate devices in the sim's Control interface but I really like this user-made TARGET profile, some scripting aspects of which cannot be replicated within DCS.

 

Can anybody give me some tips and tricks that might help me out here? Many thanks.

 

So, first, I used to use TARGET as well. Honestly, it's a pain in the rear. It hasn't been updated in a long time.

Every time, you unplug your devices your are changing their location in the registry which can honestly be less effective depending on who you talk to.

 

I use keybinding software as well as DCS by default doesn't allow for many of the functions that TARGET provides. I recommend the following:

 

The only thing this software doesn't do as of yet, is allow for single key toggling.

i.e. one button that will do something different each time you press it.

Press button 1 = air to ground mode

Press button 1 = air to ground mode

Press button 1 = Nav Mode

Press button 1 = air to ground mode

You get the idea..

 

However, it has a couple other much more useful functions. I highly recommend it over the DCS input for the Thrustmaster at least.

[Bahger]

This is very interesting, many thanks.