USB HID device with hardware id "VID_044F&PID_0400" cannot be found USB HID device with hardware id "VID_044F&PID_b352" cannot be found USB HID device with hardware id "VID_044F&PID_b351" cannot be found USB HID device with hardware id "VID_044F&PID_0403" cannot be found ![]() USB HID device with hardware id "VID_044F&PID_0402" cannot be found USB HID device with hardware id "VID_044F&PID_0404" cannot be found Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" ![]() ![]() *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Running script: E:\Utilities\TARGET\TriggerFix.tmc What I have works well enough for now I think.Īnyway, still curious why TARGET doesn't behave. Toggle doesn't sound practical for fast combat situations, can lead to more mistakes. There I just unmap Spacebar and DCS reads the trigger as normal, VA doesn't interfere with that and those planes never had double input because of the way the "hold to release" is coded for them in DCS. For FC3 planes, those need hold for all weapon release anyway. There isn't a problem with CCRP since the full fidelity planes I own have a bomb drop button which is separate from the trigger. Press a button once to hold the virtual trigger down, press again to release. In your case for exemple doing CCRP isn't really possible anymore. I don't know why your stick isn't recognised when you run a script, could you share your script so we can check it please.ĭepending on the aircraft and even the ordinance you want to deliver you might need some different pusle duration. I will test more but I guess in the end I have to change some bindings, or simply not run the script on some aircraft.Īnother friend recommended I use AHK as well but I didn't want to keep installing and trying new software yet. However, I am getting some weird and unpredictable results with other aircraft. Throttle shows fine in both left and right panels.Īnt0ine, I do use VoiceAttack so I quickly set that up and it seems to work! Thanks and much easier than TARGET. In the device analyzer, I can see the joystick is there but no button presses or axis movements are recorded. The script finds the Joystick and compiles fine, virtual devices created correctly and real ones disabled. Guys thanks for your help but I think the issues is different. I did the same as I did in Target with AutoHotKey, remapped to keyboard however, we can't remap to Joystick/Vjoy afaik, not easily at least. Do you have it? IIRC the free version is limited to 20 commands but that is enough to do what we want. In Joy2Key I can't find a way to do a macro. Also if you want to use my code you must use the Target Script Editor.Įdit : Do you use AutoHotKey by chance? I'm trying to find an easier solution, that would not require you to reconfigure your whole hotas for all your module just to fix your trigger issue.Įdit : I tried Joystick Gremlin but it will save how many time the button have been pressed and will loop the macro. Note that the default Target configuration isn't complete, you'll have to remap all axes and buttons manually, and due to Target virtual device limitation you'll have to remap a few buttons to keyboard. I'd appreciate some help, bear in mind I'm a complete noob at this:helpsmilie: As far as I can tell the script compiled fine and the virtual controllers have been created correctly. Even on the left panel, the physical panel, the stick is doing nothing. And for the throttle, some of the buttons also don't go across. ![]() After I run the script, when I go to analyse, there is no input from the stick at all in the virtual "Thrustmaster Combined" controller. Just tried TARGET for the first time to run a custom script for my trigger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |