These seem obvious probably but i had to cover them. If yes to these then TARGET is working, if no try reinstalling TARGET and be sure you are running RC3. )Īnd when you run the device analyzer ( with script running ) do you get normal responses from all your buttons and axis? ( on my setup the cougar is listed because I still use older rudder pedals via the cougar base, so yours might not list that. 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 Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** When you run the script in TARGET do you get the green text similar to this? : I figured the people here are my next best hope.) As soon as I disable TARGET, Windows re-detects both devices and they work as intended.Īs far as software, I installed the hardware drivers and updated to the latest firmware (I believe?) as well as the TARGET software.Īnyone heard of this problem before or know of anything I could be doing wrong? (I know I don't need TARGET for DCS: A-10, but no one else seems to know what's going on. This is also the case in the Windows Game Controller panel. Unfortunately, I would like to use some of the nice features that the TARGET software allows, so I'd like to be able to use it.Īlso, the device manager shows that my joystick works, but my throttles get no response. As soon as the TARGET profile is turned off my throttles function again. I tried multiple games and none of them would recognize any inputs from the throttle/control panel at all. When I run any kind of profile on the TARGET software my entire throttle/control panel no longer functions at all. I'm using a Thrustmaster Warthog on Windows XP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |