Jump to content

Recommended Posts

Posted

Hi

 

On my old X-52 pro I use th slider wheel on the throttle for zooming in and out. In the Saitek software I split the slider into 3 bands. Forward band was zoom in and aft band was zoom out and the middle 80% was a deadzone.

 

How can I do the Sam wth the TARGET software?

 

Thanks

Posted (edited)

Hello

In Target Script Editor :

KeyAxis(&Throttle, THR_FC, 'iu', AXMAP2( LIST( 0, 20, 80 ), USB[85], 0, USB[84] ));

KeyAxis(&Throttle, THR_FC, 'ou', AXMAP2( LIST( 0, 20, 80 ), USB[85], 0, USB[84] ));

KeyAxis(&Throttle, THR_FC, 'im', AXMAP2( LIST( 0, 20, 80 ), USB[85], 0, USB[84] ));

 

Zoom in and Out for some layer on the Throttle slider.

LIST( 0, 20, 80 ) : divide the cursor in 3 zones

USB[85], 0, USB[84] ) : assign key for the 3 zones

 

Hope this help you.

Edited by BeR1
Posted

I have to say that so far Saiteks software is much better or at least more user friendly. Used it for 5 years and you pressed a button and told it what key to use or you right clicked it and split into bands for multiple functions etc. There were also separate columns for shifted states.I haven't got a clue what you do with these scripts and I'll need to study that manual Thanks for the reply. I really appreciate it.

Posted
I have to say that so far Saiteks software is much better or at least more user friendly. Used it for 5 years and you pressed a button and told it what key to use or you right clicked it and split into bands for multiple functions etc. There were also separate columns for shifted states.I haven't got a clue what you do with these scripts and I'll need to study that manual Thanks for the reply. I really appreciate it.

 

The reason that the Saitek software is easier is because it doesn't have anything close to the capability of Target's scripting language.

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

You can also just assign it in the Axis Commands, that's how mine is set up. Mine has no jitter on it and it works perfectly.

Capture.JPG.5044b6a5161794d0f719fc2abf2713fe.JPG



Win 10 64 Pro, MSI Z390 I7-9700K @5ghz Kraken Z63, 32Gb Corsair Dominator, MSI RTX-2070, 1TB NVME 2TB SSD's, TM Warthog, Pro Rudders, OpenTrack w/ IR Clip

Posted

Since the slider potentiometer is a bit twitchy I'm using it with a filtering function, to avoid zoom jittering:

 

int AxisFilter(alias f, int v, int i){
   int n = 3;
   int a = 2048+(i*n)/32;
   int b = 65536;
   if (((v-f)>i) |
       ((f-v)>i) ){
       f = f+(v-f)/n;
   }
   return f*a/b;
}

int s_AxisFilter_THR_FC;

int main()
{
   // Stuff

   KeyAxis(&Throttle,THR_FC,0,AXMAP1(256,
       EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(AxisFilter(&s_AxisFilter_THR_FC,Throttle[THR_FC],256)));"),
       EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(AxisFilter(&s_AxisFilter_THR_FC,Throttle[THR_FC],256)));")));
}

Posted
I have to say that so far Saiteks software is much better or at least more user friendly. Used it for 5 years and you pressed a button and told it what key to use or you right clicked it and split into bands for multiple functions etc. There were also separate columns for shifted states.I haven't got a clue what you do with these scripts and I'll need to study that manual Thanks for the reply. I really appreciate it.

 

 

Well, to be fair, you can use the GUI to program the WH. You don't have to right one code of script.. Just point and click.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Posted
Well, to be fair, you can use the GUI to program the WH. You don't have to right one code of script.. Just point and click.

 

The GUI would be fine, if I can work out how to split the increment into 3 bands. On my old X-52 Pro it was split into 3 with 10% 80% and 10% with the 80% being the deadzone. Worked fine for me.

 

Thanks again

Posted
Since the slider potentiometer is a bit twitchy I'm using it with a filtering function, to avoid zoom jittering:

 

int AxisFilter(alias f, int v, int i){
   int n = 3;
   int a = 2048+(i*n)/32;
   int b = 65536;
   if (((v-f)>i) |
       ((f-v)>i) ){
       f = f+(v-f)/n;
   }
   return f*a/b;
}

int s_AxisFilter_THR_FC;

int main()
{
   // Stuff

   KeyAxis(&Throttle,THR_FC,0,AXMAP1(256,
       EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(AxisFilter(&s_AxisFilter_THR_FC,Throttle[THR_FC],256)));"),
       EXEC("TrimDXAxis(DX_THROTTLE_AXIS, SET(AxisFilter(&s_AxisFilter_THR_FC,Throttle[THR_FC],256)));")));
}

 

Not necessary if you can do without the throttle LED backlighting. Turn it off and all jittering will go away. It's a firmware problem that TM has unfortunately never corrected.

DEFENSOR FORTIS

Spoiler

Systems: Falcon NW Talon: Ryzen 9 5950X @4.9GHz, 64GB DDR4, RTX 3090 FE; Falcon NW Mach V: Core i7 3930K @3.2GHz, 32GB DDR3, GTX 1080 FE

Cockpit: MonsterTech MTX F, 42" 4K TV, HP Reverb G2, Oculus Rift S, PointCTRL

Controls: RS F16SGRH CE, RS F18CGRH, VPC T-50CM2, VFX, WarBRD (Grips); VPC T-50CM2, RS FSSB R3L (Bases); Winwing F/A-18C, VPC T-50CM3, VPC T-50CM, TM Warthog, Cougar (Throttles); VPC ACE2 (Rudders)

 

  • Recently Browsing   0 members

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