Steel Jaw Posted February 25, 2022 Posted February 25, 2022 TM Warthog running a custom script. Seemingly at random it locks up and the only way to unlock it is to shut off the script and restart the TARGET script editor. A major drag in VR of course. Happening to anyone else, any other way to fix this in sim? Thoughts? Cheers. "You see, IronHand is my thing" My specs: W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.
SGT Coyle Posted February 25, 2022 Posted February 25, 2022 (edited) No issues as you describe. Post your script. Edited February 25, 2022 by SGT Coyle Night Ops in the Harrier IYAOYAS
Drakoz Posted February 25, 2022 Posted February 25, 2022 I know people have had issues with this over the years for various reasons. There are a few threads that discuss it in details so a search should find some solutions. I don't know the general solution as I haven't experienced it. What version of TARGET are you running? They just released a new version to support the TCA Boeing yoke and throttle quadrant. I haven't tried that version yet, but previous versions have been very stable for me. USB can sometimes be finicky and that might cause TARGET to crash. So maybe plug your devices into a different hub or different connectors on your PC. It isn't common that a script can lock up TARGET, even if you are doing custom C programming, but yes, please post your script. Normally script errors just cause the script to stop running. Locking up TARGET is usually more indicative of an overall software or hardware issue. Sometimes completely removing and reinstalling all Thrustmaster drivers (like your Warthog drivers) and TARGET can help, though in previous threads on this, many try that and still have issues - leading me to believe it is more specific to an individual computer. Hence why I comment on trying different USB ports or a different USB hub.
Steel Jaw Posted March 23, 2022 Author Posted March 23, 2022 So here is what the cause was...on my Warthog throttle there is a switch I use for he speed brake that forward holds and back is momentary. When left forward on hold no other keystrokes are seen by the sim, I guess the held open stroke was blocking. "You see, IronHand is my thing" My specs: W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.
SGT Coyle Posted March 24, 2022 Posted March 24, 2022 OH yeah! I've been there. It's not fun. You should use a "PULSE +" on all non-momentary switches. Night Ops in the Harrier IYAOYAS
Recommended Posts