Bahger Posted January 13, 2019 Share Posted January 13, 2019 I am new to the TM Warthog HOTAS and the TARGET software. I'm using a user-made profile in DCS. I've been told that when TARGET loads the profile, making a "virtual device", windows can no longer see the joystick and this is fine but sometimes my otherwise flawless Warthog joystick stays disabled after I quit TARGET and I have to fiddle anxiously with unplugging and plugging its USB connection in again before it comes back to life, even though, oddly, Windows sees it. Can anyone comment on this and even suggest a workaround or solution? Many thanks. Link to comment Share on other sites More sharing options...
RedeyeStorm Posted January 14, 2019 Share Posted January 14, 2019 Well I don’t have that issue. Sometimes when I load a Targetprofile my stick isn’t recognised but the throttle is. I solve this by stopping the profile and run it again. After a couple times the joystick is recognised. I check the working of the stick with the devicechecker (I believe, but the left most button after profile run). Good luck Link to comment Share on other sites More sharing options...
DeepDrummer Posted January 15, 2019 Share Posted January 15, 2019 (edited) It used to happen to me often. Are you plugging in and unplugging other HID devices? Cam, phone? Other controllers for other things? That can mess up the enumeration. Sometimes hitting the enumeration button on the device analyzer helps. Pic attached. I have had to uninstall Target and the TM drivers and re-install the drivers and then Target. If you then plug in a cam or other Hid device especially if the TM stuff is unplugged, it can re-order. Everything that ever gets plugged in, stays plugged in on my machine. TM stuff gets installed Last. Windows still sees the stick and throttle as one unit when combined. run joy.cpl to verify. I haven't had that problem in over a year now. That is just one possibility. Static electricity will kick things out of kilter as well. In winter when it is cold and dry like now, I touch a bare usb connection to ground myself before touching the stick or throttle. Edited January 15, 2019 by DeepDrummer spelling Win 10 pro 64 bit. Intel i7 4790 4 Ghz running at 4.6. Asus z97 pro wifi main board, 32 gig 2400 ddr3 gold ram, 50 inch 4K UHD and HDR TV for monitor. H80 cpu cooler. 8 other cooling fans in full tower server case. Soundblaster ZX sound card. EVGA 1080 TI FTW3. TM Hotas Wartog. TM T.16000M MFG Crosswinds Pedals. Trackir 5. "Everyone should fly a Spitfire at least once" John S. Blyth Link to comment Share on other sites More sharing options...
DeepDrummer Posted January 15, 2019 Share Posted January 15, 2019 I have also at times in the past removed every usb device in the devices except the mouse and then reboot which will find and install drivers for most things. Then install the Target stuff last with the joystick first and then the throttle. Win 10 pro 64 bit. Intel i7 4790 4 Ghz running at 4.6. Asus z97 pro wifi main board, 32 gig 2400 ddr3 gold ram, 50 inch 4K UHD and HDR TV for monitor. H80 cpu cooler. 8 other cooling fans in full tower server case. Soundblaster ZX sound card. EVGA 1080 TI FTW3. TM Hotas Wartog. TM T.16000M MFG Crosswinds Pedals. Trackir 5. "Everyone should fly a Spitfire at least once" John S. Blyth Link to comment Share on other sites More sharing options...
Recommended Posts