DukeGamma Posted October 23, 2021 Posted October 23, 2021 (edited) This profile (https://www.digitalcombatsimulator.com/en/files/3300626/) is the one I'm trying to use. Loading the config in TARGET causes the stick to become unresponsive. Disabling the profile the stick is still unresponsive until I unplug it and plug it back in. edit: to clarify, the joystick no longer responds in Windows. I have to unplug and plug it back in for the controller config to register movement/button presses from the joystick. Edited October 24, 2021 by DukeGamma
jstnj Posted October 24, 2021 Posted October 24, 2021 (edited) 7 hours ago, DukeGamma said: This profile (https://www.digitalcombatsimulator.com/en/files/3300626/) is the one I'm trying to use. Loading the config in TARGET causes the stick to become unresponsive. Disabling the profile the stick is still unresponsive until I unplug it and plug it back in. Ive never heard of anyone having good luck with TARGET. At all. It never worked for me, I only use the software itself to turn down the throttle LEDs. Every time I ran the configs, they fail and do not actually compile. I assume that's what is happening to you. I dont use TARGET, and I dont feel I'm missing out on anything. Edited October 24, 2021 by jstnj
Lange_666 Posted October 24, 2021 Posted October 24, 2021 Has nothing to do with TARGET but with binding conflict in DCS. TARGET is just a powerfull tool, if you know how to push it's buttons. If your scripts fail to compile it means there are errors in them, caused by you, not TARGET (it would be the same if you use any other programming language for whatever so don't blame it on TARGET). Best thing to do is clear the Touch controller bindings and the throttle/collective binding in DCS, restart DCS and bind them again. Problem solved (without touching TARGET). Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
DukeGamma Posted October 24, 2021 Author Posted October 24, 2021 9 hours ago, Lange_666 said: Has nothing to do with TARGET but with binding conflict in DCS. TARGET is just a powerfull tool, if you know how to push it's buttons. If your scripts fail to compile it means there are errors in them, caused by you, not TARGET (it would be the same if you use any other programming language for whatever so don't blame it on TARGET). Best thing to do is clear the Touch controller bindings and the throttle/collective binding in DCS, restart DCS and bind them again. Problem solved (without touching TARGET). I'm not using Oculus though. Whatever is happening in TARGET with the linked profile is completely disabling the joystick, ie. it isn't responsive even in the Windows controller config
Lange_666 Posted October 24, 2021 Posted October 24, 2021 My bad, did read the topic wrong, since i did read "virtual" i thought it handled the problem described in my post. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
sedenion Posted October 25, 2021 Posted October 25, 2021 (edited) On 10/23/2021 at 7:23 PM, DukeGamma said: This profile (https://www.digitalcombatsimulator.com/en/files/3300626/) is the one I'm trying to use. Loading the config in TARGET causes the stick to become unresponsive. Disabling the profile the stick is still unresponsive until I unplug it and plug it back in. edit: to clarify, the joystick no longer responds in Windows. I have to unplug and plug it back in for the controller config to register movement/button presses from the joystick. The profile itself is not the problem, it is more probably related to drivers, softwares or USB ports. Uninstall all TARGET software and drivers related to TM Warthog Download latest TM Warthog drivers and TARGET software : https://support.thrustmaster.com/en/product/hotaswarthogflightstick-en/ Package drivers - Hotas Warthog - 2018_TMHW_1 + Firmware T.A.R.G.E.T - Software v3.0.20.826 Install TM Warthog drivers Install TARGET Software Update throtthle and stick firmware following this procedure : https://ts.thrustmaster.com/download/accessories/pc/hotas/manual/HOTAS_Warthog/HWarthog_Firmware_Update.pdf Try again. If the problem occure again, please copy-past here the content of the script output log that appear when you run the script. Edited October 25, 2021 by sedenion
Recommended Posts