Jump to content

Recommended Posts

Posted

How do the keybindings work on the radar switch ? the trigger has 3 detents - does that mean four positions ? neutral, detent zero, detent one, detent two ?

 

I'm designing a radar stick and need to know how to work out the switching on the trigger - I won't be using a hat switch or joystick buttons.

---------------------------------------------------------

PC specs:- Intel 386DX, 2mb memory, onboard graphics, 14" 640x480 monitor

Modules owned:- Bachem Natter, Cessna 150, Project Pluto, Sopwith Snipe

Posted (edited)

The Trigger works like a typical 2 stage trigger, like the one on the Warthog HOTAS stick for example and has a neutral position (T0) and 2 detents (T1, TV).

 

In the Viggen the trigger is used for nav fixes as following:

1st detent (T1): initiates nav fix

2nd detent (TV): executes nav fix

To abort a nav fix that you already have initiated by pressing the 1st detent (T1) you will have to release the trigger (T0) instead of pressing the 2nd detent (TV).

Edited by QuiGon

Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit

DCS Panavia Tornado (IDS) really needs to be a thing!

Tornado3 small.jpg

Posted

Ok thanks guys. It's clear now.

---------------------------------------------------------

PC specs:- Intel 386DX, 2mb memory, onboard graphics, 14" 640x480 monitor

Modules owned:- Bachem Natter, Cessna 150, Project Pluto, Sopwith Snipe

  • 3 weeks later...
Posted

If you don't have a two stage trigger to use, I bound T0, T1, Tv to buttons on my HOTAS and basically think of it as "T1 to enter the mode, Tv to lock, and T0 to cancel"

---

AJS37 Viggen, F-16C Viper, Adobe Premier.

X56 HOTAS, Ryzen 7, GTX 2070S

youtube.com/leadnapgaming

  • 1 month later...
Posted

For the enthusiastic users of TARGET, a function to spit the two stage trigger.

One issue I've always had was how to reliably split the two stage trigger when using TARGET. The problem is that physical trigger is made up of to switches actuated by a cam. Unfortunately when trigger 2 is actuated, trigger 1 is also actuated. That makes doing things like the radar stick tricky to map.

 

 

I have finally split the triggers.

 

 

Put this in a .tmc script

 

//Trigger
MapKey(&JoystickF18,TG1, EXEC("Trigger();"));//    Split Trigger Function Call TG1
MapKeyR(&JoystickF18,TG1, CHAIN(
                               EXEC("ActKey(DX24);"),
                               EXEC("ActKey(DX25);"),
                               EXEC("ActKey(PULSE + KEYON + DX23);")
                                   )
                                       );// Simple CHAIN to Release TG1 & TG2

MapKey(&JoystickF18,TG2, EXEC("Trigger2();"));//    Split Trigger Function Call TG2
MapKeyR(&JoystickF18,TG2, CHAIN(
                               EXEC("ActKey(DX24);"),
                               EXEC("ActKey(DX25);"),
                               EXEC("ActKey(PULSE + KEYON + DX23);")
                                   )
                                       );// Simple CHAIN to Release TG1 & TG2  

and this in a .tmh file. Name it whatever you want and "include" it in you script.

//*************************************************************************************************
//*******___ Viggen ___**********
// Trigger Split for Viggen Radar Fix

int    Trigger1()    {
   if(JoystickF18[TG1])
   ActKey(KEYON + DX24);
   }
   
int Trigger2()    {
   if(JoystickF18[TG2])
   ActKey(DX24);
   ActKey(KEYON + DX25);    
    }

Make sure to map radar stick controls in DCS.

 

 

  • T0 to DX23
  • T1 to DX24
  • T2 to DX25

This has worked a hoot for me.

Night Ops in the Harrier

IYAOYAS


 
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...