dcs-input-command-injector VS dcs-bios

Munkwolf's DCS Community Keybinds + Quaggles' DCS Input Command Injector

DCS Input Command Injector - https://github.com/Quaggles/dcs-input-command-injector

I'd like to know if the Program with the red lines (DCS? This? https://github.com/Quaggles/dcs-input-command-injector ) is using the raw gyro pitch/yaw/roll speed values or the quaternion. I suspect it's the latter but I'll look into it. I'd also be interested to know the same for the VSCView.

First mod is DCS Input Command Injector by Quaggles, which is a baseline requirement for the second mod, DCS Community Keybinds. Ever want to bind something in a module, and the devs never added it? Maybe you want the volume knobs to turn faster, or light knobs to turn slower? Someone has added it here!

you can use quaggles input command injector mod to be able to put custom keybinds into your saved games folder where they won't get overwritten by updates: https://github.com/Quaggles/dcs-input-command-injector

Try Quaggles's DCS Input Command Injector together with DCS Community Keybinds instead, maybe someone added the commands you need.

Regarding the Warthog on/off switches and DCS bindings, Warthog owners should probably have a look at Quaggle's DCS input injector and the DCS community bindings for an elegant solution that basically removes any limitation, without the need to run additional software while flying DCS.

Files in there are formatted for use with Quaggles command injector mod: https://github.com/Quaggles/dcs-input-command-injector/releases

I recommend using DCS-Input-Command-Injector mod https://github.com/Quaggles/dcs-input-command-injector that allows you to configure custom input commands inside your Saved Games/DCS/ folder instead of inside your game folder.

tldr about the project: Adds extra keybinds. Requires Quaggles mod.

can't you just use dcs bios?

My program would not be possible without DCS BIOS (specifically the Flightpanels fork, which is still actively maintained), so a special thank you to the contributors to that project. Also thanks to the creator of, and contributors to, pyWinAuto, another essential program for many of my startup scripts. I would also like to credit DiCE and DCSTheWay for some inspiration for what is possible, even though I ended up taking a different path.

I've been working with DCS BIOS quite a bit recently and may be able to answer some of these. First, make sure you're using the Flightpanels fork of DCS BIOS and not the original DCS BIOS. The Flightpanels fork is up to date, while the original has not been updated in a couple years.

Check out this fork, myself and others have been working to keep it up to date and it typically has new aircraft added the week they are released. And yes, it has the Mossie :)

There's an up to date fork here.

I'm not sure exactly what you're trying to do (not familiar with "ExportScripts") but we've been plugging away at getting everything added to dcs-bios. Still a ways to go, but you may find some of this useful https://github.com/DCSFlightpanels/dcs-bios/blob/master/Scripts/DCS-BIOS/lib/Mi-24P.lua

Okay I'm definitely putting this in the box of things to have a good look at later (haven't even played DCS yet). Just did a quick search and there's actually a pretty well documented mod for interfacing controllers with it like this DCS-BIOS which should make it actually not too hard to implement.