Red Panda

@slughead My guy, it works like magic now. I dunno what lines you changed, but THANK YOU! It works perfectly and flawlessly now.

I’ve looked at those! They seem pretty cool. And I’ve gotta clean up the space I wanna put that chair in. The place I live has a pretty decent little niche spot that can easily hold my junk, plus a decent sized workstation/painting station for my partner. That’s the plan for our spring cleaning; getting that area better organized and set up the way we wanna use it.

Saving up the Pennies for a seat right now, actually. (I may also be waiting on a tax return to roll in.. ahem. But I digress.) That WinWing ICP is on my “want” list though. See, my logic is pretty solid here… if I can ultimately have one of those nice NLR Military edition chairs with the mounts, just get a smaller front mount for the ICPs, I could, in theory, just use the ICP without passthrough because everything will pretty much be in-line enough for me to just reach out with my hand and touch it/use it quicker than I could screwing around with the mouse. Soon. Thanks again for the response; I’ll definitely be checking this script out soon.

@slughead I am so sorry for the late response! I’m actually celebrating my birthday today, so this comes as a VERY pleasant surprise! I’ll be trying this new script out and seeing if it works. Thanks!!

I’ll see how that improves things this evening. Why would that affect it though? I’m legit curious.

This sounds like a similar issue I am having with the TARGET Software and getting the Viper TQS lights to sync using @slughead's fix for that nagging problem. The TARGET software will completely LOSE the axis controls for my AVA base, and it just disappears completely. I'm getting ready to contact Thrustmaster about the issue. I have yet to find any kind of fixes that alleviate the problem, up to and including completely removing drivers, firmware, and the devices entirely using the Device Manager tool. If I come up with something, I'll let you know.

@slughead This was my worst fear. Honestly, this doesn't change my opinion on the TQS that much; the unit itself is still a solid piece of kit and I've enjoyed it so far. I just wanted to get the cool lights to work. I kinda wish TM had the fore-withal to actually consider that users may want the functionality that your script provides and actually provide proprietary, written code for it in their software packages that's supported... Maybe if enough people pitch a fit about it, they'll actually look into it more. Thank you for trying to help, Slug, and I do appreciate you taking the time to try and help a weary internet wanderer. Have a cookie for your troubles. P.S. - If anyone runs into a similar issue, please give me a ping, especially if you have found an actual fix. This almost drove me mad.

@slughead Recorded the process in which I opened things up. The same process is how I came to screencaps 4, 5 and 6 in the previous response. P.S. - I did repeat the process and opened the Game Controllers dialogue after I ran the script. It doesn't matter; the same thing occurs. Screen Recording 2025-02-19 190025.mp4

Will do. I’ll be back at the computer in roughly 30 minutes, and attempt to replicate/record what I’m doing.

@slughead - Hey again! As promised: I am currently running v 3.0.24.618 of the TARGET software. The directory you reference in the first point here - I did as told with what files were available from the GitHub repositories. They were unzipped and put into files where I could find them, and then moved per instructions given. If there is something that I'm apparently missing (I don't really do much with GitHub normally and this is the first time I've ever ran into a problem with getting files from GitHub to work), please provide me a more direct link to the exact file(s) I should be getting. When I run the script, this is what screens I see. First cap: The script editor, pre script start. Second cap: Game controllers dialogue, Pre-script start Third Cap: Script editor, Post-Script Start Fourth Cap: Game Controllers dialogue, post-script start Fifth Cap: AVA Base controller settings dialogue as above, pre-script run, which allows me to check ROM on the axis - which it is there. The AVA base completely disappears after I begin running the script, as referenced in Cap 4. Sixth Cap: The Game Controllers Dialogue settings for the Virtual Device that the script makes, which has NO axis input whatsoever. This is obviously not the TM dialogue you should be expecting me to get. null null null null nullnull

I’ll be glad to once I’m home in a few hours time. Damn time zones. PS: I know that I probably sound annoyed, and being fair, I righteously am— but not at you. This is very much a Thrustmaster issue that they won’t admit they overlooked when getting ready to market this product. I’m more peeved at them that an advertised function won’t work unless you do some kind of wild workaround.

Re: TARGET software; it is the freshest install available from TM on their proprietary website, I haven’t followed any other download links. Re: devices are new and the latest version of the Firmware was downloaded when I picked up both pieces of kit last week. I would venture to guess that there hasn’t been a firmware update on the AVA base or the Viper TQS since 11FEB. so.. I dunno, man. It just decimates my use of the AVA base. I dunno what else to tell you, other than “this definitely ain’t working with whatever configuration I have” and I can’t begin to tell you how I came to this juncture other than by continuing to dump log files.

@slughead Hi! I have tried to replicate the same steps as found in this video by MrCalm. I have also tried multiple times to replicate success with this script and hook combo using your instructions as outlined in this post and in the GitHub posts. I have had absolutely zero success; the reason I say I have had no success is because when I start the script, it creates a new virtual controller that has no axis input whatsoever, except from the Viper TQS itself; it eats any kind of input from my AVA stick base and doesn't accept input from the axis on it. Including the following for you from the Script editor: Running script: C:\Users\Ameli\Desktop\LED Light Fix\TMHotasLEDSync-main\build\TMHotasLEDSync\TMHotasLEDSync.tmc *** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll" Compile Succeeded. TMHotasLEDSync v1.0.4 Physical USB HID devices managed by script! Currently plugged USB HID devices[2]: 1: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200" 2: "Viper TQS" - "USB\VID_044F&PID_0412&REV_0200" USB HID device with hardware id "VID_044F&PID_0404" cannot be found USB HID device "Viper TQS"(USB\VID_044F&PID_0412\3665348C3031) selected USB HID device with hardware id "VID_044F&PID_0413" cannot be found USB HID device with hardware id "VID_044F&PID_0416" cannot be found USB HID device with hardware id "VID_044F&PID_0417" cannot be found USB HID device "AVA Base"(USB\VID_044F&PID_0415\208F316A4B4B) selected USB HID device with hardware id "VID_044F&PID_0414" 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 (absolute axes)...Done Server socket listening on TCP port 2323 main returned 0 Also attaching my dcs.log file from my most recent attempt at getting it to work. I am begging you for help because I have tried, deleted files, tried again, and deleted again so many times that I feel like I'm going crazy. The funny part? If I start DCS as normal and everything else, the lights work... I just can't fly my plane. Please help. T_T P.S. - MrCalm found a potential issue and linked me to the info from this Reddit post. I had one brief moment of success where when I ran the script, it kept seeing my AVA base AND created the virtual controller... but after that, I had to restart my computer and I have had no success in replicating the results since then, and I don't really know what I did. P.P.S - I just did a little experiment and I've found that no axis controls exist at all on the thing after running the script, and using the Virtual controller. Nothing. Nada. Zip. Zero. dcs.log