SGT Coyle

I must say your comparisons don't delve to deep into detail. I half tempted to report this as advertising. But, I'd like to know what makes the electronics of SLAW better than TPR?

In DCS mapping screen, it should be joy_RX and joy_RY. I always have to manually select the axis from the drop down menu mapping page.

Not only do you have settings for all Modules, but there's also a "General" category. I tend to erase all mappings in this category after every update. If you use TARGET with your TM devices, they'll be combined into a "Thrustmaster Combined" column. This presents it's own set of challenges when mapping and saving bindings. If your mapping a Direct-X button, it goes in the "Thrustmaster Combined" column. If your mapping a key stroke, it goes in the "Keyboard" column regardless of the device your using.

That's gospel brother. Don't be afraid to try TARGET Script Editor. It beats the hell out of the GUI and there's so much more you can do with the Stick and Throttle.

there's always small claims court.

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.

Did you look at ViaComPro? It works. It's worth the some odd dollar. Everything is already mapped for you. It takes a bit of getting used to but it works in the end. https://www.vaicompro.com/ https://forums.eagle.ru/showthread.php?t=198297

dburne Thanks for the instruction.

I would love to see direct import of TARGET Script Mapping. Example would be: MapKey(&Joystick, TG1, Macro Name I use for the button); (I normally use the Trigger_First_Detent as a macro here) or MapKey(&Throttle, LTB, Change_to_Pilot_Pit); (witch is a macro I use for switching seats in the F14) In this case you would have two variables that are in a predictable format. The actual button name (TG1, S2, H2U...) that can point to a specific text field to be filled, and a variable location that already has text to put in the proper field(Trigger, Weapon_Release, Flaps_Down...). I hope that makes sense. Regardless of what you decide. This is a great tool. I'm having much fun making my profiles. I look forward to further developments.

So I've got mine set to operate the Gear Up, Gear Down, Hook Up, Hook Down, and the Nose Strut Kneel (a.k.a. Launch Bar Extend). Works like a freaking charm. It makes me feel so authentic.

Can you expound on that? How do you remove the driver correctly? When I update I always do a clean install.

Put this little didy in your TARGET Script and you too can have a gear handle on the little grey lever. KeyAxis(&Throttle, THR_FC, [color=#ffffff]0[/color], AXMAP2( LIST(0,30,70,100), Gear_up, 0, Gear_Down)); But, asking Heatblur to go to the trouble to assign an axis to a binary switch, that is not something I can get behind.

What's stopping you? It's either up or down. If it's not down then up. If it's not up it's down. There is no halfway. That would be like being a little bit pregnant.

Awesome! Just tried it and wow.

Excelent, thank you. How about an F18 Grip version?

Are there instructions on how to use this?

I have no idea. I would think that most if not all folks in here are using the Script Editor, not the GUI. But, you might have a corrupted install. Maybe uninstall/reinstall GUI and try again.

Did you use Windows to calibrate? If not DON'T. Never heard of it solving problems. Probably remove devices (Throttle and Stick) and reinstall from scratch. Remember to reboot after software/driver install. Good luck.

YFKM!! That's awesome! LMAO! I'm trying that right now!

ataribaby, Didn't mean to imply any malfeasance. Just letting you know. I really didn't have any concerns, but can't be to careful. Thanks for the effort. I look forward to trying this.

slickdevel, In that thread I failed to mention that you can map any controller button to a ui layer binding. You don't need to use TARGET.

Probably not. I'd think they'd make an announcement if it were. Probably just busy with real world stuff.

dmonds, Great find. I've used KeyAxis for this sort of thing, but forgot about IOUMD feature it offers. Thanks for that. My question was more fore a way to have a traditional axis behavior assigned to say Flaps axis, and via flags or function call, change that traditional axis to the KeyAxis functionality. This is an example (non functional) of a .tmc that Drakos helped me out with for the F14. There are probably many things wrong with it at this stage, but I thought it might illustrate the problem. There are 2 modes of the script: Mode1 = Pilot settings Mode 2= RIO settings Modes are switched via the Left Throttle Button. In the Pilot settings I want to have the landing gear, hook and kneel operations on the Friction Lever as KeyAxis, and also the Flap axis that is not available via keyboard binding (there is Flap_UP and Flap_Down, but those aren't working as axis control, just full up and full down). So my desire is to move from KeyAxis to MapAxis control on the fly. ...And of course I'd like to do the same sort of thing for the RIO settings. I hope that makes sense. Any help or insights would be appreciated.

What about "UI Layer" in game control settings? There are bindings for scroll up and down.

Give it time...