TQS Target enable not working

[peter]

Hello,

I know, wrong forum but I didn't seem to be getting any exposure in the input device forum.  Thank you.

Just upgraded my warthog to TQS and AVA base for stick.  Everything works as should except for one thing.  The RDR/CURSOR ENABLE button on the middle of the hat does not "ENABLE" the target in the F-16 like it should.  It is mapped correctly, stock DCS mapping and I have verified that the button is actually alive via TM settings.  Even the keyboard action of "ENTER" in DCS doesn't work.  Therefore I am unable to lock up a radar target for AIM120 use. Any thoughts?  Am I missing something stupid like, Turn The Radar ON?  I don't ever remember doing that but when in Dogfight mode, I see NO RDR at the top of the HUD.

 

Thank you

[rob10]

As I said in the other subforum where you posted this, ADD A TRACKFILE.  That will narrow down what you could be doing wrong.  Currently it's a complete guessing game.

[peter]

So, take a guess. I don't think a track file of the published training mission will help to isolate the issue with ONE button.  All I wanted to do was to verify the integrity of new hardware. If I plug the warthog throttle back in it works fine.  Thank you.  Does anyone else have some helpful information?

[rob10]

21 minutes ago, peter said:

So, take a guess. I don't think a track file of the published training mission will help to isolate the issue with ONE button.  All I wanted to do was to verify the integrity of new hardware. If I plug the warthog throttle back in it works fine.  Thank you.  Does anyone else have some helpful information?

Why are people SOOOOO resistant to posting a track?  It's the easiest thing you can do and often shows some simple step that's not mentioned in the written description that is causing the issue and saves so much time guessing what's actually going on for people trying to help.

In your original post you mentioned both the button and the keybind not working which suggested a procedural error (in fact you even said "Am I missing something stupid?").  A track would help diagnose what you missed or help ruling out a procedural error.

Now mentioned if you plug (presumably the old hardware) back in it works fine.  Which suggests a possible hardware issue.

Good luck figuring it out.

Edited yesterday at 03:12 AM by rob10

[MAXsenna]

So, take a guess. I don't think a track file of the published training mission will help to isolate the issue with ONE button.  All I wanted to do was to verify the integrity of new hardware. If I plug the warthog throttle back in it works fine.  Thank you.  Does anyone else have some helpful information?

To save a track. Press Esc, then quit the mission and click the button that says "Save Track". I completely agree with Rob, why not post a track. Apart from that. Press TMS upon your stick to lock a target, like I wrote in the other forum.

Sent from my SM-A536B using Tapatalk

[peter]

Track posted.

enable track.miz

[peter]

Here is a track file.  Tried enabling virtual buttons and not enabling virtual buttons.  Tried running with LED scripts and without, tried 120B's and 120C's.  Thank you.

enabletrack.trk

[MAXsenna]

27 minutes ago, peter said:

Here is a track file.  Tried enabling virtual buttons and not enabling virtual buttons.  Tried running with LED scripts and without, tried 120B's and 120C's.  Thank you.

enabletrack.trk 6.9 MB · 0 downloads

No need for all these posts at the various forums. Can't have a look at the track right now. But I did have the same issue until I learned to do it the correct way. When I got my original TM Cougar, I was confused. I also thought pressing that button on the TQS would lock the target. As it turns out you have to press the TMS up button on the grip on the stick, (as long as its correctly bound), to lock the target. Not on the throttle. Have you actually tried that? Just mentioned it like four times now. 

Cheers!