Spectre-63

I appreciate that majapahit, but I don't want to get into TARGET again - I used TM's programming tools for years, but TARGET is just a hot mess. Last year I lost the ability to program my Warthog because of a Windows update (driver change) and I won't put myself into that position again, especially after TM's lack of response.

One more question: Last time I did this, I saw issues where the switches would not initially function because the in-plane control position did not match the switch position on my controls. Any workaround suggestions?

Sorry to bring this back up, but the recent patch overwrote my modifications to the default.lua files so I've now lost the changes I had made :( Here's the goal: my Warthog Throttle has two-way switches (EAC and RDR ALTM) that I want to map to F/A-18's gear and hook controls respectively. Unfortunately, Thrustmaster has setup the switches so that it only sends one DX button press when the switch is turned to the 'ON' position and sends nothing when going to 'OFF' The goal is to map these to Gear Up or Hook Up when in the 'ON' position and Gear/Hook Down when in the off position. NOTE: I DO NOT wish to use TARGET scripting to accomplish this. I'm aware of the Press/Release functionality, but don't want to load different profiles as I'm notoriously bad at remembering :D Two questions: 1.) Is it going to be required to create a different function in the Keyboard Default.lua file that will work with Press and release of the switch? My concern is once again losing the work. 2.) Any way of mapping this into my user.lua files so that I don't lose them? Thanks!

Disregard - found some additional documentation that explained the interrelationship between the .lua files. :)

Thanks for your hard work and documentation on this LeCuvier...it made making the desired modifications to my .lua files much easier to understand :pilotfly:

Forgive the thread necromancy - I'm trying to replicate what you've done, but am running into some issues. Should the command you show be listed in the default.lua or the .diff.lua specific to the controller? Thanks!

Thanks - out of curiosity, what video card(s) are you running?

Another question: how are you supporting all the displays? Am I counting right that you have 8 in the pit itself?

Guppy - I'm just getting started down this (EXTREMELY) slippery slope =) If you had it do over again, would you stick with individual monitors for each MFD, or go with a single 24" touch screen? I worry about the framerate hit for 3x1024 screens for the MPDs and one for the UFC, especially when my primary monitor is a 4K? I'm running on an i5-7600K and an NVidia 1080ti Thx!

Also very interested in this info :pilotfly:

Apologies for the thread necromancy but I ran into this same issue last night in Windows 10 after receiving an update - in short, the Thrustmaster Combined drivers are being rejected by Windows 10. I had to revert to the version before the update, but I was hoping folks might have some insight here? Not surprisingly, a request to support to Guillemot has gone unanswered. :(

Disregard - I located my problem. In my case, I had an application not related to DCS that was silently crashing. Each time it did it caused Windows to steal focus from DCS. I identified the issue by reviewing the Windows Application Event Log. Hope this might help someone else who runs into a similar problem.

First - allow me to apologize for raising this from the dead but I'm a new DCS A-10 flier and I'm having issues with the sim self-minimizing mid-flight. Unlike StageFright, I'm running a single monitor while in flight. I have a second, but it's shut off prior to launching the sim. Like StageFright, I'm on an ATI 7970 card and am using the 13.4 driver set. Any suggestions would be greatly appreciated!

Apologies for the thread resurrection, but do you have a new location where I can download these skins? The 190th flies in my backyard and I'd love to wear their skin in honor of their service. Thx!