edit buttons in Thrustmaster T.A.R.G.E.T then lost all buttons in DCS

[bin801]

I try to make those 3-positon switchs on warthog work as 3 buttons, and succeed and I didn't touch any other buttons.

 

and start DCS by clicking "fly now" through TARGET.

 

In DCS, I tested the 3-positon switch, they work as 3position,as what I need.

But question is:

when I try to set all the other buttons those I never edit, using the usual way in DCS, I found DCS dose Not identify all the other buttons.

Click "add" , press buttons on controllers, buttons did not show up in setting.

what should I do?

 

later, I try to synchronize button name in "windows control panel" with "direct X gmae buttons" in TARGET parameters setting" virtual game/keyboard/mouse/, except those 3-position switches I successfully set as I need. And then I save event.

after I finish synchroniz those buttons on "direct X game buttons" 32keys in virtual game/keyboard/mouse, I start synchronize names of right hand stick buttons, till that moment, I found there are only 32 direct X game buttons for both stick and throttle in "virtual kdyboard ....." I overwrote many buttons on throttle, and then I realize.

 

what should I do? how to let all buttons and switches be identify in DCS control setting.

 

thank you

due to my language problem, even I read manual but failed to find any information about the problem I met.

please illuminate me, Appreciate!

[cichlidfan]

My first recommendation is to not spread similar questions into multiple threads.

 

what should I do? how to let all buttons and switches be identify in DCS control setting.

 

The answer to this is to not use Target or program more buttons without DX assignments.

[bin801]

My first recommendation is to not spread similar questions into multiple threads.

 

 

 

The answer to this is to not use Target or program more buttons without DX assignments.

 

I know, but I found here is more suitable for my question after I'v post my question at other place, and there is no delet founction in this forum.

and I'm new at here, thanks.

who can delet that thread,please delet it.

[bin801]

I want to use TARGET has only one reason, because, in my mind,that is the only way to make those 3-positon switches work as 3-postion switches.

Are there only 32 DX game buttons for both throttle and stick controller?

if yes, that means 1/3 TM warthog buttons will be wasted.

 

did I make any mistake? or misunderstand about TARGET?( I'm new at TARGET) should I synchroniz buttons' names to "DC game buttons" in "virtual game/keyboard/mouse" in paremeter setting section?

 

is there other way to use TARGET but without waste any buttons on warthog or cougar? and of course, be recognized by DCS?

Appreciate

[tintifaxl]

You need to assign each button and switch either a keyboard keypress or a dx button in TARGET. Then you could assign the dx buttons in DCS.

 

When I used TARGET I would first assign keypresses to every command I needed in the sim (in DCS nearly all useful commands have keypresses already assigned). Then I defined the commands in TARGET with name from the sim and keypress. e.g. Toggle Gear=G. Then I assigned the commands to the buttons and switches. A lot of work.

 

Maybe it would be easier to not use the off position of the 3-way switches. I don't use TARGET anymore, because on my setup I had randomly hanging modifier keys like CTL or SHFT and had to restart TARGET to get rid of them.

 

Only the A-10C does support the 3-way switches in DCS atm, so for every other plane I do the following:

 

I assign the paddle of the joystick as a modifier in DCS, and then I map the modifier + up position to the command for the middle position.

 

e.g. the FW-190 has a 3 position flaps switch, so I map "flaps up" to FLAPU, "landing flaps" to FLAPD and "takeoff flaps" to FLAPU + S4.

[bin801]

You need to assign each button and switch either a keyboard keypress or a dx button in TARGET. Then you could assign the dx buttons in DCS.

 

When I used TARGET I would first assign keypresses to every command I needed in the sim (in DCS nearly all useful commands have keypresses already assigned). Then I defined the commands in TARGET with name from the sim and keypress. e.g. Toggle Gear=G. Then I assigned the commands to the buttons and switches. A lot of work.

 

Maybe it would be easier to not use the off position of the 3-way switches. I don't use TARGET anymore, because on my setup I had randomly hanging modifier keys like CTL or SHFT and had to restart TARGET to get rid of them.

 

Only the A-10C does support the 3-way switches in DCS atm, so for every other plane I do the following:

 

I assign the paddle of the joystick as a modifier in DCS, and then I map the modifier + up position to the command for the middle position.

 

e.g. the FW-190 has a 3 position flaps switch, so I map "flaps up" to FLAPU, "landing flaps" to FLAPD and "takeoff flaps" to FLAPU + S4.

 

Thank you so much, suddenlly I understand, please tell me I'm right or not.

Those DirectX game buttons do not correstpond to real buttons on throttle and stick.

In TARGET, I should assign all buttons to simulats keyboard keys, following the default key combine set in game, such as DCS option control section.

Those DirectX game buttons in TARGET will be used only when a game dosen't allow player assign keyboard to that function or wasn't defaultly assigned by game maker.

 

am i right?

so A detail TARGET PROFILE can be used only for one aircraft in DCS, because once I start DCS throught TARGET "fly now", those real buttons on controller will not be regarded as buttions anymore, if I didn't assign them to any key command, DCS can not detect them anymore. Those assigned buttons are keyboard command, those did assigned buttions are nothing, just blank.

thank you so much

[bin801]

I wanna say, if TARGET software let player assign part of buttons and switches, while leave the others still as buttons, programming for us will be much much more easier.

Maybe they can creat a check box, in parameters gui, named "work as usual founction" and checked in default.

When player do want to change a button, uncheck.

Then player can even edit a single button and start profile use.

 

but now I need print all key assignment list in game and do alot to assign all key commands to fulfil all those functions that can originally done by buttons by default. Maybe just for one single needed button.

Edited January 16, 2015 by bin801

[Iku_CC]

This si good tutorial...I started with this and it helped...

 

http://forums.eagle.ru/showthread.php?t=81222

[Socket7]

T.A.R.G.E.T. is one of those programs you have to learn pretty thoroughly before you'll be able to use it effectively. Here's the problem, DirectX only supports so many buttons on any particular USB device such as a joystick throttle, or pedals.

 

The reason the Thrustmaster Warthog has 2 USB connections is because of this button limitation. By splitting the unit into two devices, you stay within the number of allowable buttons in DirectX.

 

 

When you use TARGET, it combines both the joystick and the throttle into one virtual device, and now you are over your button limit, so buttons stop working (The ones on the base of the throttle come to mind as ones that stop working).

 

In addition to this, when TARGET has turned the virtual controller on, DCS will no longer have an automatic default binding that just works for it.

 

So If you want to use TARGET, you're going to be spending a lot of time programming buttons in it, so the buttons that no longer function as Directx buttons send keystrokes instead.

 

In addition to that, you'll have to program DCS to properly use all the DirectX buttons that the combined virtual warthog joystick does have.

 

It's... a lot of time consuming, but not hard work. The benefit doesn't outweigh the work required for me personally, I just don't use TARGET.

Edited January 16, 2015 by Socket7

[nervousenergy]

I know providing Warthog-aware LUA files for every aircraft would be a pain and not something most devs would be willing to spend the effort on, but would it be practical for ED to simply create an assignable action for a button being OFF? Then it wouldn't be hardware specific, and any device that had an ON/OFF switch could natively support two actions.

 

That would solve the issue without having to learn LUA programming or use TARGET for the Hog, and it would work for many other peripherals as well.

[bin801]

This si good tutorial...I started with this and it helped...

 

http://forums.eagle.ru/showthread.php?t=81222

 

Thank you

I will go and learn from the link!

[bin801]

T.A.R.G.E.T. is one of those programs you have to learn pretty thoroughly before you'll be able to use it effectively. Here's the problem, DirectX only supports so many buttons on any particular USB device such as a joystick throttle, or pedals.

 

The reason the Thrustmaster Warthog has 2 USB connections is because of this button limitation. By splitting the unit into two devices, you stay within the number of allowable buttons in DirectX.

 

 

When you use TARGET, it combines both the joystick and the throttle into one virtual device, and now you are over your button limit, so buttons stop working (The ones on the base of the throttle come to mind as ones that stop working).

 

In addition to this, when TARGET has turned the virtual controller on, DCS will no longer have an automatic default binding that just works for it.

 

So If you want to use TARGET, you're going to be spending a lot of time programming buttons in it, so the buttons that no longer function as Directx buttons send keystrokes instead.

 

In addition to that, you'll have to program DCS to properly use all the DirectX buttons that the combined virtual warthog joystick does have.

 

It's... a lot of time consuming, but not hard work. The benefit doesn't outweigh the work required for me personally, I just don't use TARGET.

Thanks

you are right, it is time comcuming, but not hard work, true. After I understand the way TARGET think, step by step, it has became very handy to me, just in past two days.

With TARGET, I'v already assigned DCS functions to every button and every switch position on cougar and for LN's Mig21 and Huey, alot fun.

I am almost totally hand free from keyboard for usual flight.

I'll try to understand TARGET more in future.

Only drawback is I need open Target and open DCS , switch from DCS window to TARGET window, time and time again. I use one whole night for one aircraft setting. But after I finished one profile and adjusted it to ideal state, I felt so good.

Edited January 17, 2015 by bin801