All buttons going crazy in game (night vision stuck?) #24
Comments
|
This seems to be persisting outside this one incident now, and I have no idea why. I am only running the profile from the TARGET script editor, and not ED to troubleshoot. Somehow buttons are erroneously ending up triggering the night vision function. So far I have seen this with both index and thumb POV switches (in all directions), as well as the boat switch. When any direction is pressed on the POV switch, night vision toggles on and off as the press/release events are fired. When the boat switch is flipped to the forward position (in attempt to open the galaxy map), the night vision function toggles on and off indefinitely, until the boat switch is flipped back to the middle position. The TARGET output will continuously stream I recompiled the script and restarted my computer to no avail. I cloned a new copy of this repo and followed the installation instructions again just to be sure, and the issue persists even in the new clone. This has to mean the issue is local to me, but I'm really not sure what would cause this or where to begin looking. Any chance something like this has been seen before? |
|
Sounds like a USB or HOTAS issue. Fire up the TARGET script editor and before loading or running the script try using the event tester and/or device analyzer. Next, grab the v5.0.0 (Odyssey) version of the script. Use that. Another thing to look at...the HOTAS should be plugged into a USB on the motherboard or into a POWERED USB hub. Report back and we'll go from there. Note: Aussiedroid has not worked on this script for 3 years. |
Hello,
I was using this setup while playing earlier tonight, and somehow it all went haywire as I was landing on a planet. I tried turning on my outside lights and suddenly multiple inputs were being passed over and over and I could not control my ship. I managed to regain some control and attempted to complete the landing, but when I went to use the yaw function on the throttle, it started again and worse this time. During all this, the lights on the throttle unit were flashing and changing brightness at a rapid pace. I ultimately had to unplug the USB devices from my PC to get it to stop.
Upon looking at the output from TARGET (below), it definitely seems that something got stuck and was possibly unaccounted for in a control loop. I have no idea if I did anything to cause this, as I was just performing a landing in the way I normally do. The only change to user preferences I have made are
CruiseOnThrottle 0andUseRuddersT16000 0.OS: Windows 10
Elite Dangerous: 18.07
TARGET: v3.0.23.1205
Script version: v4.3.0 (
4b555427d4b6bf71203e4c5c0c8da5d04663866b)If more information is necessary, please let me know.
Thanks!
Output from TARGET during issue
The text was updated successfully, but these errors were encountered: