Quick question about using TARGET with the Warthog?

I've got my Warthog up and running. Haven't messed with any configuration settings since it's pretty much set up out of the box for A10C. My question is that if I load up a configuration file or create one myself for something like FC2 or anything, run that file in TARGET, map axis accordingly from within the respective SIM, will the default configuration for DCS A10C still exist since I loaded up a completely new profile to the HOTAS? Is there a default mappings for the stick I can load up so I can get the stick back to the config it was originally out of the box for DCS A10C?

Thanks for any help.

That's the very reason I haven't touched TARGET yet. I'm assuming that if TARGET isn't running at the moment, everything works per defaults with DCS: A-10C, but I'm waiting for someone else to test it. :)

I know with my old Saitek if I didn't specifically load some profile it would work like default, so hoping it's the same here.

I've played with the software, but haven't gone as far as running a config file or loading it into the stick. Really just familiarizing myself with the software. The reason I ask this is that currently I'm using my TM Elites for rudders connected to my Cougar (works nicely if you only have gameport rudders for use in A10C) and I'd really like to use the Warthog with FC2 instead of my cougar. Currently I'm just moving the hardware around on my desk depending on what sim I'm going to fly.

I noticed that there are stock files in TARGET currently, such as a files for BS, IL2, FC2-F15, etc.. but no stock file ( or I guess .TMC) for DCS A10 ( makes sense since the mappings aren't finalized yet).

DCS: A-10C has built in mappings. The game ships with lua files you load from within the game to map the HOTAS controls to the controller. There's not really a need to run TARGET if all you're playing is A-10C so no need for a TARGET profile for the game. :)

I've said this a bunch of times, but clearly it bears repeating....

Notwithstanding anything TM may come up with regarding firmware updates....nothing you do...nothing....is saved to the stick or throttle.

You don't "download" a program to them...or flash them...or however you want to think about it like other sticks. They don't have the ability to take a program.

When you're using TARGET to execute a profile, a Windows service runs in the background and acts as an interpreter. Your code/profile/script tells that interpreter how to work.

Anytime you don't actively have a script running, the two units are ordinary directx joysticks.

Thus...to get it "back to default"...after running a TARGET profile...you do nothing more than click 'stop' in target.

Sweet! Thanks for the confirmation!

NP.

Just to put it another way...it's not that the TMWH is preprogrammed for DCS A10 (It most assuredly is not)...DCS A-10 is preprogrammed to understand the TM Warthog.

What happens is when you plug the sticks in, Windows sees them as something like "Throttle - HOTAS Warthog" and "Joystick - HOTAS Warthog". They act like generic sticks - the buttons generate DX Button events, as do the switches. Most switches are set as 1 DX button and are either on or off (such as EAC for example) In windows you'd see a DX button (like...25 or something I don't know) lit up with the EAC in ARM, and unlit with EAC off. Some things (flaps lever, engine oper switches) have 2 dx buttons associated with them as they're 3-way controls - either both dx buttons are off, or one or the other is on.

If you have the game controllers open when you launch a TARGET profile, you'll see the two Warthog entries (and, if you've included them) Cougar, MFD, T16000.M disappear and will all be replaced by a single "Thrustmaster Combined" entry. At that point, the Windows service is acting as an interpreter.

When you're done with the profiled game, you just click 'stop' in TARGET (no need to even close it..just stop the script/profile) and your devices return to the control panel applet and work as they otherwise would have.

You don't need TARGET for A-10C because DCS A-10C has code included that understands the joystick/throttle - HOTAS Warthog game controllers.

Thanks for the explanation. Very much appreciated. Now I understand the convenience of the quick fly functionality from within target.

Hmm.. how do you get a lua file you can use in LockOn FC2 then to map buttons? Or does TARGET just make it into a single controller so you can use the throttle for example but have to manually map each control?

Fc2 wouldn't have a lua file for the warthog like Dcs does. The warthThog is a replica of the actual stick and throttle so the mappings would make sense to match the actual plane. Fc2 has multiple aircraft with different hotas' that aren't = to the hogs hotas. You have to emulate your prefered mappings to your liking with target by running it in the background. Sort of like CCP for the cougar does when you hit the big green button. Target is an emulator. If I understand it correctly.

FC2 does have the same lua files as DCS. Seems though that TARGET simply replicates the Keyboard commands and maps them to the stick controls, so you just don't map anything special in the Joystick column and you essentially fly via keyboard using a stick. :)

So start TARGET, Run Configuration and leave it running, then start FC2 and enjoy.

I just got mine the other day and have only tried it in A10C while using TARGET. Is that a mistake? it seemed to have destroyed all my stock keyboard commands and binded joystick commands in the keyboard area. Is this because I have TARGET running in the background and should not even open it?

Don't need TARGET for DCS: A-10C since the default configs for the stick that ship with DCS already are configured for the TM Warthog controller. Just leave it off while runing DCS: A-10C

For other games though you'll want it running.

I just got mine the other day and have only tried it in A10C while using TARGET. Is that a mistake? it seemed to have destroyed all my stock keyboard commands and binded joystick commands in the keyboard area. Is this because I have TARGET running in the background and should not even open it?

If TARGET has control of your Warthog, you cannot 'minimize' the TARGET window (you can bring other things on top of it, but you can't click the button to shrink it down). If you can click the [_] button and have TARGET drop down to the task bar, it has absolutely no control over your Warthog. It's the same as not running (or never having installed) TARGET. TARGET is only active when the window is "stuck" open with a configuration running.

hmmm. I just booted up my pc, launched beta 3, without TARGET, and not all of the keybinds seem to be correct. For instance, my trim hat is mapped to view slewing. TMS, DMS, and CMS, hats have no mapping to them. Do I goof something bigtime or miss a step?

Make sure you've loaded the DCS defaults by following the procedure in this thread:

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

The most important part is clicking in the Throttle column to load the Throttle profile and in the Joystick column to load the Joystick profile.

I think since you ran Dcs with target running you remapped the stick and need to reset the warthog to defaults by erasing a few files. There was a post explaining how to reset the stick for those who ran target while running Dcs. You didn't write over anything but those new user made files that were created need to be erased.

You need to load the .lua's for both joystick and throttle from the Options screen. You just click on a joystick configurable and then click Load. Load the Warthog Joystick.lua. Do the same for the throttle.

You will still have to hold down the Ctrl key for trim. Of course you can change that in the Options screen. You might also want to assign wheel brakes (w) to the stick paddle switch.

The most important part is clicking in the Throttle column to load the Throttle profile and in the Joystick column to load the Joystick profile.

Ahhh i had forgotten to do the load part. Everything looks good except my trim is mapped to my view. I guess ill just map that manually. thanks guys!

Ahhh i had forgotten to do the load part. Everything looks good except my trim is mapped to my view. I guess ill just map that manually. thanks guys!

Actually that trim mapping is not a mistake because that's how it works on a real plane. It's mentioned in DCS manual.

Actually that trim mapping is not a mistake because that's how it works on a real plane. It's mentioned in DCS manual.

Do you mean that to trim in the real plane they have to hold down LCtrl then use the trim hat? Or that by default in the real plane then they move the trim hat it turns their head? :smilewink::joystick:

I think it's more likely they defaulted to making it the view hat so that Game mode players wouldn't be sliding all over the place by default while the Sim players would know enough to remap it. Didn't see anything in the manual talking about having to do anything extra to use the trim hat in real life though.

Do you mean that to trim in the real plane they have to hold down LCtrl then use the trim hat? Or that by default in the real plane then they move the trim hat it turns their head? :smilewink::joystick:

 

I think it's more likely they defaulted to making it the view hat so that Game mode players wouldn't be sliding all over the place by default while the Sim players would know enough to remap it. Didn't see anything in the manual talking about having to do anything extra to use the trim hat in real life though.

I mean that "view hat" is actually a "trim hat". It's called "view hat" merely because we need this function since we're not in the cockpit(unless you have sth like trackIR).

Sorry I missed some details on previous posts. I thought they map trim to "trim switch" by default but seems to be the other way around. I didn't have a-10c beta yet.

Ahh sure. It's labeled correctly on the Thrustmaster Warthog controller which is nice.

Last question I think about TARGET. If i switch the afterburner thing so it wont move the full motion, do I have to specify that in TARGET someplace so it recalibrates? a10c only goes to about 40%rpm like that.

OK, if you're doing it in TARGET, that's pretty easy. If you're doing it with A10C (without using target) I'd have to play with it to come up with the answer.

But in TARGET...

Open your profile. Go to the 2nd page (configure axes mapping).

Click the green arrow by THRRIGHT (bottom left of screen)

Change the pulldown to JCURVE if it isn't already

Clear the reverse & relative boxes (if not already clear)

Change the 'control position' slider to '81'

Change the 'value of axis' slider to '96'

Repeat for THRLEFT (exact same settings)

T