dburne Posted April 19, 2014 Posted April 19, 2014 Hey gang, I just recently noticed on the two scripts I have created with the script editor in TARGET, after I click on run and get the message below, it references some USB HID devices not found. Is this anything I should be concerned about? Scripts seem to run fine, just has me curious: Compile Succeeded. Physical USB HID devices managed by script! Currently plugged USB HID devices[2]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2AF4D4D8&0&5) selected USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&DF05C04&0&3) selected USB HID device with hardware id "VID_044F&PID_b351" 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_0400" cannot be found USB HID device with hardware id "VID_044F&PID_B10A" cannot be found Virtual HID devices managed by script! Connecting virtual joystick...Done Device name set to Thrustmaster Combined Connecting virtual keyboard...Done Connecting virtual mouse...Done Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Rogue Trooper Posted April 20, 2014 Posted April 20, 2014 Does this happen every time with this script or is it sporadic? Have you seen this type of error on other scripts that used to work fine? HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled. DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!. Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.
dburne Posted April 20, 2014 Author Posted April 20, 2014 (edited) Does this happen every time with this script or is it sporadic? Have you seen this type of error on other scripts that used to work fine? I have two scripts now that I have created with the Script Editor, for two different flight sims. I have just noticed those messages after I click on run on the scripts, they may have always been there. The scripts appear to work just fine in my flight sims. I was mainly wondering if this should be a cause for concern and why those " not found" messages might be there? Thanks, Edit: Ok did some searching in google, which took me to some earlier posts on both SimHQ and here on the ED forums, apparently those messages I am seeing about some hardware id not found are normal when running a script. May have something to do with not having MFD's, etc... Thanks gang, it appears all is well and I should not be concerned. Edited April 20, 2014 by dburne Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Madog Posted April 21, 2014 Posted April 21, 2014 Hey, yes i think its the other components that can be managed with TARGET. For example, this is what i get when i run a script: [...] Currently plugged USB HID devices[4]: 1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100" 2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100" 3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100" 4: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100" [...] Note, the USB Ids for the MFDs are the same as in your error message. I think what TARGET is trying to tell you, is that you do not have the MFDs and supposetly the cougar connected.
Recommended Posts