TM:Warthog Coolie Hat issue

[Baggy MacDouche]

I've had my WH for a little over a month now and I've been finding that many times when I want to select one of the MFCDs to SOI using the Coolie Hat Long press, it will just keep cycling modes instead of making it SOI. It's like it isn't giving the hat a chance to give the long command. Overall, it just seems overly sensitive and I find I have to hold the hat direction very carefully or it won't let me make SOI.

[Runibl]

I have experienced the same thing, but luckily only twice so far, so i haven't given it much thought.

Can be annoying when it happens though, and makes it very difficult to make a page the SOI.

[ivanwfr]

Same here and I just went through the intensive testing I intended to do about this:

 

First, I made sure TARGET's Device Analyzer reports everything's fine with CS POV when mapped to DXHAT.

 

Then I played with MFCD SOI and functions cycling. After some serious testing and tracing with a script that reported each and every activation event... my conclusion is that it's all my fault!

 

In fact, every time it happened was when I pushed the hat in one of the UPRIGHT, DOWNRIGHT, DOWNLEFT or UPLEFT corners. More to the point for this SOI glitch to the Up or Down left corners. There always was an extra (short!) event instead of the single long-left-press!

 

Too bad we have the POV assigned to this hat because corners are not only wasted here but they are even a problem.

 

From what I've experimented so far, Micro Switch and H4-CMS on the Joystick are not able to get into those corners and would be perfectly adapted to China Hat functions. (Their pushed state seems to be an alternative.)

 

To completely cover the matter, I can say that H2-TMS and H3-DMS are not POV but they can fire 2 closed switch-events at the same time when they are pushed in a corner.

 

Conclusion, either we have to carefully avoid pushing CS in a corner or find a way to discard those events with some TARGET code...

[Baggy MacDouche]

Yup, came to the same conclusion. My initial approach was to see if you could double up commands for coolie hat L/R with the corners as well, but of course it won't let you. :p

 

I try to avoid using T.A.R.G.E.T. at all costs(it scares me :)). I've thought about moving it to another hat like the mic switch hat, which I find I have better control of directions. The purest in me would rather stick to the default layout though.

 

Let me know if you do find a way, T.A.R.G.E.T. or not, to essentially turn it into a 4-way hat.

[ivanwfr]

TARGET solution in this thread attached archive.

 

The idea is to ignore any other CS input as long as there is already one in progress. I think the code segment below from the end of th/th_MO.tmc is readable enough.

 

The whole script files entry point is in DCSW_PNP_main.tmc, which you have to feed TARGET Script Editor with. It is a "Combined" mapping that mimics Joystick and Throttle PLug and Play functions for DCS A-10C as soon as you import the profile/Combined_ivanwfr.lua that goes with it.

 

The idea is to use that as an entry point for more personal tuning.

 

TARGET DXInput China Hat mapping has the exact same issue as the TARGET-less input.

   // DXHAT POV mapping (...which has a corner issue for SOI)
   //  CSU_MO        = DXHATUP;
   //  CSR_MO        = DXHATRIGHT;
   //  CSD_MO        = DXHATDOWN;
   //  CSL_MO        = DXHATLEFT;

 

This "filtered" solution seems to work pretty well:

   // ...alternate keyboard mapping [uHJH] [uRDL] ... single key (press and hold)
   CSU_MO        = EXEC("if(!Throttle[CSR] & !Throttle[CSL]) ActKey(KEYON+ USB_U);");
   CSR_MO        = EXEC("if(!Throttle[CSU] & !Throttle[CSD]) ActKey(KEYON+ USB_K);");
   CSD_MO        = EXEC("if(!Throttle[CSR] & !Throttle[CSL]) ActKey(KEYON+ USB_J);");
   CSL_MO        = EXEC("if(!Throttle[CSU] & !Throttle[CSD]) ActKey(KEYON+ USB_H);");

   // ...(release pressed key)
   MapKeyR(&Throttle, CSU, EXEC("ActKey( USB_U );"));
   MapKeyR(&Throttle, CSR, EXEC("ActKey( USB_K );"));
   MapKeyR(&Throttle, CSD, EXEC("ActKey( USB_J );"));
   MapKeyR(&Throttle, CSL, EXEC("ActKey( USB_H );"));

 

[edit]

...answers to a bunch of questions that may come to mind here ;) TARGET - Advanced programming

Edited May 22, 2011 by ivanwfr
added link

[raelias]

Sorry to revive this post, but i've been having the same issue and I did not understand the fix, can anyone walk me through it step by step? thanks a lot

[PhoenixRising]

I realize this is an old thread, but I was having this problem and stumbled upon this thread. I don't like using TARGET for DCS, but I was having terrible issues with the A-10 not marking targets, and with the coolie hat not doing what I expected it to do. After spending my Saturday morning messing around with TARGET, I found some code that seems to have fixed those problems. This is just the coolie hat. You need to do this for all of the four way switches. If anyone has a better solution, I am all ears. I have only done a couple of flights with it, but I didn't have any of the previous issues I was experiencing from accidently pressing the corners of the four-way switches.

 

MapKey(&Throttle, CSU, EXEC("if(!Throttle[CSR] & !Throttle[CSL]) ActKey(KEYON+DOWN+DX19);"));
MapKeyR(&Throttle, CSU, EXEC("ActKey(KEYON+UP+DX19);"));
MapKey(&Throttle, CSL, EXEC("if(!Throttle[CSU] & !Throttle[CSD]) ActKey(KEYON+DOWN+DX21);"));
MapKeyR(&Throttle, CSL, EXEC("ActKey(KEYON+UP+DX21);"));
MapKey(&Throttle, CSD, EXEC("if(!Throttle[CSR] & !Throttle[CSL]) ActKey(KEYON+DOWN+DX20);"));
MapKeyR(&Throttle, CSD, EXEC("ActKey(KEYON+UP+DX20);"));
MapKey(&Throttle, CSR, EXEC("if(!Throttle[CSU] & !Throttle[CSD]) ActKey(KEYON+DOWN+DX22);"));
MapKeyR(&Throttle, CSR, EXEC("ActKey(KEYON+UP+DX22);"));