Buhli Posted February 3, 2020 Posted February 3, 2020 Hello, i'm new to the forum here an i hope, i'm not disturbing you. HOTAS Warthog with the latest TARGET software and firmware My problem: I can bind the keys direct in the game, but if i load a profile with the TARGET software, the whole input crashes after the first input. so i can't do anything, Very frustrating, i had no issius under Windows 7. Not sure how it should be shown in game, i have the stick and the thottle separately under controlls. The energy settings for the USB HUBs are NOT controlled by Windows. Both controllers are pluged into an USB-2 Port. Does anyone have an idea, what i can change or set? Cheers Buhli
panton41 Posted February 3, 2020 Posted February 3, 2020 It wasn't a Warthog, but I had a Thrustmaster steering wheel have weird behaviors when plugged into a hub. Maybe it's something similar. Windows 10 64-bit | Ryzen 9 3900X 4.00GHz (OC) | Asus Strix B450-F | 64GB Corsair Vengeance @ 3000MHz | two Asus GeForce 1070 Founders Edition (second card used for CUDA only) | two Silicon Power 1TB NVMe in RAID-0 | Samsung 32" 1440p Monitor | two ASUS 23" 1080p monitors | ASUS Mixed Reality VR | Thrustmaster Warthog HOTAS | MFG Crosswind A-10C Warthog | AV-8B Harrier (N/A) | F/A-18C Hornet | F-16C Viper | F-14B Tomcat | UH-1H Huey | P-51D Mustang | F-86F Saber | Persian Gulf | NTTR
Buhli Posted February 3, 2020 Author Posted February 3, 2020 I guessed the same, but it is direct plugged to the PC.
Weegie Posted February 6, 2020 Posted February 6, 2020 I'm running one rev behind on the software and I use hubs without issue Are we talking GUI or Script Editor? Are you using keyboard commands in your TARGET profile (I assume yes) Have you tried using the Event Tester supplied bby TM to test that everything is working as it should there? I've had controllers not being recognized before but never anything that crashes the game, strange.
lxsapper Posted February 6, 2020 Posted February 6, 2020 I have to disconnect and reconnect Joystick and throttle from the USB ports in order to avoid the issue where they don't get virtually disconnected when running the TARGET profile. Sounds like you are having the same issue. When you run your profile they should turn into thrustmaste combined device.
Recommended Posts