ReflexArc

I was asked to clarify some after posting this to reddit, I'm copying my explanation here: By default, two-state switches like the Master ARM switch are only sent as one direct X button (Master Arm/up=Button 1; Master Safe/down=nothing/off) and three-state switches are two direct X buttons (Flaps UP/up=button 1; Flaps MVR/middle = nothing/off; Flaps DN/down = button 2). This requires custom HOTAS options which rely on button states and combinations of button states (button 1 On / button 1 Off = Flaps Auto / Flaps Half + button 2 On / Button 2 Off = Flaps Full / Flaps Half) but those state-dependent bindings aren't available for every plane in the game or for planes/spaceships in other games. My script makes two-state switches into two buttons (up = button 1 and down = button 2) and three-state switches into three buttons (up = button 1 middle = button 2 down = button 3). Virtually all planes have available bindings for discrete functions (Flaps Auto, Flaps Full, Flaps Half) which you can then bind to your now three button switch that you couldn't bind before (because it was only two buttons). I wrote all of the following before my better TL;DR above but I'm keeping it because it includes some additional info. If you're flying just the A-10C you're probably not missing anything. DCS includes bindings like "Master Arm On/Off HOTAS" which work correctly. But by default the master arm switch only sends a signal to the game every time you switch it to ARM ("On"). When you switch it to SAFE ("Off") it turns off that On signal but doesn't actually send any other info. My script is useful for other planes which typically have options for three states: Master Arm On/Off (Toggle), Master Arm On (ARM), and Master Arm Off (SAFE). With planes like that, a typical assignment would be to assign your master switch to the Toggle version. When you do that, the switch will only toggle between On and Off each time you flip the physical switch to Arm. (So switch up to turn on but switch down then up again to turn off.) If you use my Target Script, switching to ARM sends a signal and switching to SAFE also sends a separate signal. So then you can bind switch up and switch down to ARM and SAFE. You might also notice this when using the flaps switch, which has two On modes (up and down) and one Off mode (middle). Some planes will have Flaps Auto/Half (On/Off) and Flaps Full/Half (On/Off), which should work without using my script. Other planes will only have Flaps Auto, Flaps Half, and Flaps Full. By default, you can not bind all three options because only Switch Up and Switch Down send a Direct X button input to the game. With my script, Switch Up, Switch Middle, AND Switch Down all send button input to the game. So now you can bind all three flaps states to the switch. This is a similar issue with the pinky switch and lighting states. The reason I mentioned LUA scripting is that you can make "HOTAS" style bindings like in the A-10C yourself, but it requires a decent amount of easy but time-consuming LUA programming and you would have to remake all of those "HOTAS" style options for each plane that you fly. If you use my script, you don't need to make workarounds, because "Off" states actually send their own Direct X button, so you don't need custom LUA "Off/On" bindings (since only "On" states send button input by default but my script sends On and Off states as a button).

Not to self-promote, but I just got the TM Warthog, myself, and I also just posted a TARGET script which gives you effectively more switch-button outputs, for when you want to use it with other planes. This way, you don't have to make a bunch of custom LUA press-release commands by hand. The main downside of this approach is having to either rebind or disable TARGET when/if you want to play with the A-10C default profile.

After a lot of searching, I found enough information to make this profile and couldn't find a premade version. Contrary to popular belief and as mentioned in this thread , DX supports up to 120 buttons plus 8-way POV. So I used that file (required in your Thrustmaster TARGET Scripts folder) to create my script which assigns a DX button output for each switch position instead of the default of sending DX outputs only for the "on" positions. As currently configured, the buttons, 4-way switches, and speed brake on the throttle quadrant itself give default behavior outputs (hold = more output) while all of the boat and other rocker switches give a "pulse" output (send the event once despite being "held" in position.) If you want to change this behavior, just remove "PULSE+" from the appropriate line. Hope this helps someone else. Edit: Additional "installation" instructions. 1. Download targetdx128.zip from this thread 2. extract the zipped file to <Program Files (x86)\Thrustmaster\TARGET\scripts\> (or wherever your TARGET\scripts\ folder is located.) 3. download my file, WarthogThrottleALLSwitchPos.tmc.txt. 4. Change the name of the file to WarthogThrottleALLSwitchPos.tmc (remove .txt). 5. Open either TARGET GUI or TARGET Script Editor and run WarthogThrottleALLSwitchPos.tmc. Now your warthog throttle will send a unique direct-x button for every switch state (up/middle/down instead of just up and down). Quick disclaimer about the China hat and any other temporary state switches (MOTOR L/R IGN). "China Hat Middle" is also an available button but people generally use the china hat as a two-button switch. When you go to bind the china hat, hold it in the desired position until you've pressed "OK" on the binding. If you press it forward and let go, it'll instead bind the "china hat middle" state. Similarly, with Motor L IGN (up), hold it in the up/forward position until done binding, as NORM is also a potential button state. Edit 5/9/2020: Attaching the most recent version of the script that I've been using with the following peripherals attached: Warthog Throttle, Warthog Joystick, 3x Falcon MFD's, and T-Rudders WarthogThrottleALLSwitchPos.tmc.txt

I basically migrated my saved games configs into the DCS directory. This fixed the overlapping/competing config issue and everything now seems to be working fine. Is there any downside to this approach? I suspect that I don't actually understand the function of the new files and that my changes will be overridden the next time DCS is updated. Are custom configs still saved to the saved games folder? (as a diff of a diff now?)

Yes, your standard installation instructions (download + install the stable python 3.6 distro) should set that interpreter as the system default in the path variable when using default installation. I did a little reading and I think py.exe is relevant for when there are multiple interpreters on a system (listed in PATH), as it lets you set a shebang to specify which python version to use. My (obvious to most people who would have multiple versions installed) case was that I wasn't sure whether I could just run your program, knowing that I had python 3.4 and 3.6 installed but NOT set in PATH. The answer was obviously no (because there's no py.exe in the dcs liberation folder.) Yeah I'm weird and moved various default directories to various different drives, figured my post might help someone else with an atypical setup.

Hey man, this is awesome. I think that helicopters may spawn too close to each other or have some other parameters messed up. I should have pulled some logs to be more helpful, but if you want to try and re-create: I committed 4 KA-50's to my last mission. Two of them were so close on spawn that they almost immediately collided in mid-air (quick mission) and died. I spawned 4 or 5 KA-50's on another mission, with myself in one of them, and every time I loaded the game my helicopter went immediately and super hard nose up (despite input) and seemed to spawn nose-up for some reason. Unrecoverable. I fixed this one by editing the mission file so that I spawned lower and slower and it worked just fine. Random edge cases that I ran into: For anyone having issues running the batch file: the python 3.6 interpreter (python.exe) does need to be listed in the windows PATH environment variable. For anyone having issues starting missions: Your saved games folder needs to be in the default location with the usual DCS folders. [i had mine on a separate drive and just restored it to default.]

Thanks for this, very helpful. According to wikipedia, the Mk-20, CBU-99, and CBU-100 are all basically the same. I don't know if there is a difference in DCS.

In my case, it looks like the issue was that I was running 2.5.0. I updated to 2.5.2 beta and can now see and connect to the server. As an aside, is it normal to have 10GB DCS RAM usage when connected to the server?

I just tried connecting, server is verified up by Drex and I used direct connect 45.27.58.61:10310 (and also without the port specifier), but game says "server offline." I'm relatively tech savvy and happy to try things to troubleshoot, but not savvy enough to know what next to do on my end. Already verified I can ping his server from my comp.

Are you sure the throttle is working otherwise? Also, are you clicking in the right column? (Just making sure, these are all things I've done when I was trying to figure this out.)

Oh man, I wish I had searched for this thread before flying the mission a bunch of times. Thanks Mad Dog.

Anyone else having issues with the F-15C mission where you're supposed to protect the SEAD flight? They keep getting shot down by the anti-air... They're the ones who are supposed to be taking out the air defenses!

I suspect the issue is that you need to map your keys. I've attached my key mapping file and an excel file that I use as a reference. I use the base keys 7-12 as modifiers (e.g. hold 8 and press 6 to reset zoom) and everything else is joystick key 1-6 or hat. Zipped Excel file with key mapping. Zipped because I don't think this forum allows uploading straight .xlsx files. DCS Settings.zip Key map (place in your Saved Games folder which is usually a subfolder of your username folder on Windows). LogitechStickXboxSLEW.diff.lua If you have an XboxOne controller, you can use the xbox right stick and abxy buttons for the SU-25T camera (as it seems to require axis controls).