slughead

Sadly, this year, I will be giving the taxman lots! A change of job has pushed my salary beyond the realms of regular tax returns! I'm not complaining.... ok, I am. I don't have the room for a dedicated "cockpit" setup, which is why I developed the Slugmouse. It allows you to point and click with your hands rather than reach for a mouse. It's the closest thing to actual cockpit interaction without a physical cockpit and passthrough. It's probably a good thing that I don't have the space, or I would be spending a small fortune in gear!

Happy Birthday! Did you get any flight som treats? A WinWing ICP perhaps?

Yes. The other file is misnamed, although the file's name shouldn't matter. I will correct it.

Please make sure you are using all of the files from the zip files. Some have changed and some haven’t. So best to replace all of them.

You’re welcome! Enjoy!

You will need both.

New release! New features! The following F-16C lamps will be replicated on the second column of LEDS from top to bottom: JFS RUN MAIN GEN STBY GEN FLCS RLY EPU RUN The following F-18C lamps will be replicated on the first LED, with the lower four LEDs indicating the speed brake position. APU RUN Note that the Warthog minimum background lighting level will be level 1 instead of off. Otherwise, the column of LEDs will always be off when the console lighting dial is set to off or the generators are not producing power. I will add other indications for the F-18C and the A-10C/A-10C2 soon. Let me know if you have any suggestions for the F-18C and A-10C LEDs.

That's good news! I will check the change into github. The virtual game controller vs combined controller might just be down to a newer driver; yours potentially being newer than mine. I'd not worry about it.

The thread for the script is here: Read through the thread and see if your problems are answered. Also, read the instructions on the GitHub pages. Simapp pro has nothing to do with my scripts. They are entirely mutually exclusive.

@Desertdawg @Red Panda Can you try this new script please? Rename your old copy of the file so you don't overwrite it, then copy this file to the same folder and give it a whirl. TMHotasLEDSync.tmc

Hmm. I have the F-18 and the F-16 stick. I haven’t tried the scripts with the F-18 stick attached. I will give it a go and see if that replicates the problem. What stick are you using on your AVA base?

No. My scripts do nothing with the joystick axis. Yes, I mentioned that a couple of replies back. You need to speak to Thrustmaster as the creation of the combined controller is all done internally by Thrustmaster. It’s their bug. Thrustmaster forgot to provide any control over the backlight/console brightness for the Viper. I have asked them if they would add it when I was in contact with the development team. That was a good year ago so I wouldn’t hold your breath.

Is your Windows account an admin account or a normal user account? Have you tried running the Thrustmaster software with admin privileges?

Mine looks like this when the script is running: I get the "Thrustmaster Combined," which is created by Thrustmaster when the script is executed, but I also retain the AVA Base. Please speak with Thrustmaster for assistance.

Can you share a screenshot of what you see as the virtual controller?

Yes. Create it in the saved games folder.

Who can say? However, I have had a report of a hub causing problems with the Viper although I don’t have such problems with mine. Always best to strip back to bare minimum when trying to fault find.

Just a thought. Are you connecting your Viper via a USB hub? If you are, try connecting it directly to your PC instead.

I do not think this is the case, as you use NVPI to change the game profile, not the global profile.

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.