Nunatak Posted June 3, 2019 Share Posted June 3, 2019 Hi, using the Thrustmaster TARGET Software with a script like NOIDs F/A-18 Warthog Profile(https://www.digitalcombatsimulator.c...files/3300626/) is failing when a key with a modifier like RCTRL is sent by the Target Software. For example trimming: MapKeyIO(&Joystick,H1U,R_CTL+USB[0x33],USB[0x60]); // trim usb code ';', view up usb code 'num8' Pressing the Mode 2 pinkie lever and the trim switch down and checking with the Target Event Tester i see the following: Key Press: RCTL Key Press: . Key Release: RCTL Key Release: . so the script seems to work, but trying to trim the F/A-18 in DCS does not work. Keyboard assignment of the Trimmer Switch - PULL is assigned to keyboard RCtrl + . If i try to change the keyboard assignment in DCS and press mode 2 + H1D only the RCtrl as the modifier is recognized in DCS but not the „.“ as Key/Button. Sometimes in 1 out 30 tries the „.“ is recognized as well and if I use the trim switch diagonal, so that H1D+H1L is executed the same time either a „.“ or a „,“ is recognized in one out of 3 tries. Seems pretty strange to me, and it’s probably more a problem of DCS not recognizing the key than a fault in your script. Tried for more than 2 hours to search google for modifier related faults in DCS without success. Latest WIN10 Pro 1809 Target Version 3.0.18.328 Firmware 23 on Throttle and 12 on Joystick Latest DCS and also tried 2.5.4.26552 both in german and english version. Any help is appreciated. Link to comment Share on other sites More sharing options...
Svend_Dellepude Posted June 3, 2019 Share Posted June 3, 2019 You need the CHAIN() around your code to make it work. If you have more than one key that needs to be sent, you need the CHAIN() command. Looks like this: MapKeyIO(&Joystick,H1U, CHAIN(R_CTL+USB[0x33],USB[0x60])); A word of advice would be to use dx button for vital things like trimming, weapons and such, to avoid stuck keys and modifiers changing commands with multiple key presses. I only use keys for things like gear, flaps, etc. All combat related commands are directx buttons. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD. Link to comment Share on other sites More sharing options...
Supmua Posted June 3, 2019 Share Posted June 3, 2019 You need the CHAIN() around your code to make it work. If you have more than one key that needs to be sent, you need the CHAIN() command. Looks like this: MapKeyIO(&Joystick,H1U, CHAIN(R_CTL+USB[0x33],USB[0x60])); A word of advice would be to use dx button for vital things like trimming, weapons and such, to avoid stuck keys and modifiers changing commands with multiple key presses. I only use keys for things like gear, flaps, etc. All combat related commands are directx buttons. Agreed. When given a choice, DX input should take priority over keyboard input since it doesn’t register keyboard command that could mess up your gameplay if you are not careful about mapping (such as sending out persistent keyboard commands, etc.) For example, for TM Warthog throttle off position I always use DX command since the physical off position on the throttle corresponds to the switch (29 and 30) being persistently active. If we rely on keyboard input then it would either send one pulse and then become inactive instead of remaining persistently pressed (in pulse mode) or sending out persistent keyboard press (in hold mode) which would force you to readjust the throttle position at the beginning of every mission. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/ Link to comment Share on other sites More sharing options...
Svend_Dellepude Posted June 5, 2019 Share Posted June 5, 2019 There is no real rule. Sometimes keys works better than dx and vice versa. I've been programming since the cougar came and the only thing I'm always careful about is that mission and combat critical keypresses will always get through, no matter what. Besides that i never program all commands on my HOTAS. Better to keep things simple and use the keyboard for non critical stuff. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD. Link to comment Share on other sites More sharing options...
Svend_Dellepude Posted June 5, 2019 Share Posted June 5, 2019 Just to add. there is a file that gives you 120 dx buttons, and it works. get it and all is good. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD. Link to comment Share on other sites More sharing options...
Nunatak Posted June 6, 2019 Author Share Posted June 6, 2019 Thanks a lot for your help. I will try to move some of the failing commands to dx buttons. I have read about different limits of dx buttons. Where can i get that file that allows these 120 buttons? Is is a target script? Link to comment Share on other sites More sharing options...
Svend_Dellepude Posted June 6, 2019 Share Posted June 6, 2019 Here : https://forums.eagle.ru/showpost.php?p=3546557&postcount=24 You just place the file in the same folder as the script and link to the new file in the top of the script. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD. Link to comment Share on other sites More sharing options...
Recommended Posts