slughead

That's a good idea! I'll give it some thought and see what I can do.

You’re going to need to talk to Thrustmaster. This is outside my sphere of influence.

Open the game controller windows after starting the script.

You need to install the dll yourself as far as I remember. There's a wiki about ovgme. Just type ovgme into google. It's the first hit in my search.

A few things: "Running script: C:\Users\Ameli\Desktop\LED Light Fix\TMHotasLEDSync-main\build\TMHotasLEDSync\TMHotasLEDSync.tmc" Where is says -main\build tells me you have installed the source code and not installed from the zip file. It probably won't make any difference. You should install only the zip file shown below, not from the source code(zip) or source code(tar.gz). Second, you say no axis. Is that just in DCS or Windows? Run joy.cpl from the start search bar and you will see get this: Then select your AVA Base and click on properties and you will see this: With the script running, do you see axis movement in the window shown above? You may need to start the script before opening the windows above for Windows to recognise the virtual devices and make sure the window above is the active window for movement to be seen.

I use a mod manager to install both dlss4 and dlss tweaks. DLSS tweaks is simple. No extra mucking about with the Nivida profile inspector or other things are required.

Method?

For the avoidance of doubt, can you please quote the actual versions of software and firmware that you have installed as reported by Windows, not the website.

I’m not sure that I can be of much help with this. The virtual controller is all managed internally by Thrustmaster and I have no control over it. What version of the Thrustmaster TARGET Script editor are you using? What firmware do you have installed in your Thrustmaster devices? Are the the latest versions?

Glad you got this solved. I have never been able to get a reliable connection between wireless keyboard/mice with the dongle at the back of a PC. There’s just too much metal for the signal to penetrate and create a reliable connection.

Hmm. That sounds as though it wasn’t charged. Either way, it’s great that it’s working again for you. Please get in touch via email if you have further problems.

That doesn't sound right at all. Please get in touch with me via email and we'll sort this out.

Exactly. There's no need to use anything else other than DLSSTWeaks. As I said above, K.I.S.S. (keep it simple, stupid).

I just use DLSS tweaks. No registry mucking about. K.I.S.S.

Let's take this to email please.

I re-read your message after having a coffee (or two). The devices must be plugged in before you run any Thrustmaster script. Otherwise, the Thrustmaster code can't find the device, and the script will therefore not be able to communicate with them. Hence, you see this: No USB HID devices - device "VID_044F&PID_0404" cannot be found No USB HID devices - device "VID_044F&PID_0412" cannot be found No USB HID devices - device "VID_044F&PID_0413" cannot be found No USB HID devices - device "VID_044F&PID_0416" cannot be found No USB HID devices - device "VID_044F&PID_0417" cannot be found No USB HID devices - device "VID_044F&PID_0415" cannot be found No USB HID devices - device "VID_044F&PID_0414" cannot be found Going back to my earlier request, try a Thrustmaster script supplied by Thrustmaster for the Viper. I really can't help you further than I have as the problem is a Thrustmaster/Microsoft issue. Other users that have experienced this filter issue have resolved it using the information I provided previously.

Is your PC on your left or right side? Dongle plugged into top or back or into a hub? If you put the right Slugmouse on your left hand is it any better?

Right. You’ve fixed the first problem. It now looks like you’re using an old version of the scripts as you shouldn’t be seeing the lines with 12 bytes received. Please check you are using the files from my github pages.

Are you using a motherboard with Bluetooth built into it or a Bluetooth dongle?

It's worked for others on this thread. Maybe you missed something. Either way, this is a Thrustmaster/Windows problem. You will need to raise this with Thrustmaster for further support. You'll probably have the same problem with a Thrustmaster-supplied script.

Here is the solution:

Can’t offer any advice without information as per the Need Help section of the first post in this thread.

I think you can use the override option in the nvidia settings as well.

I used the dxgi approach and it works ok.

See my post above.