Jump to content

Munkwolf

Members
 View Profile  See their activity

  • Posts

    455

  • Joined

  • Last visited

 Content Type 

Posts posted by Munkwolf

    Quaggles - DCS Input Command Injector Mod - Store custom input commands safely in Saved Games instead of merging them with developer changes each update

    in DCS Modding

    Posted · Edited by Munkwolf

    15 hours ago, FroznAK said:

    Wow, this is great. Thank you so much!  I have some more hardware testing to do before I can try it.  I wanted to confirm it was possible before getting the soldering iron out.  My intent is to use this with the A-10C II module, but in theory it could be used with any TACAN control.  I'm going to use a STM32 board and FreeJoy and bind the rotaries as axis-to-buttons.  Still proof of concept, but I think it will be doable.

    Edit to add:  Looking through the default.lua files in DCS, it doesn't appear that the A-10 has absolute value commands available for the TACAN control.  I may not be looking in the right place.  Might have to change plans and use a Pro Mirco board and the joystick.h library to do what I want.

     

    You're welcome. Taking a quick glance, it does looks like the A-10 just has one set of controls for each TACAN channel control, but then kinda odd it looks like the tens one is relative and the ones one is absolute and looks like they are both relative and no absolute ones are available. But I'll dig into it more later. A-10 is one of the older modules where it's structured differently than newer ones.

    • Like 1

    Quaggles - DCS Input Command Injector Mod - Store custom input commands safely in Saved Games instead of merging them with developer changes each update

    in DCS Modding

    Posted · Edited by Munkwolf

    1 hour ago, FroznAK said:

    I haven't needed to use the Input Command Injector Mod yet, but I've looked through various threads I could find and the Github documentation and can't find what I'm looking to do yet.  Here's my specific use case:  I have a TACAN control panel that adjusts the 10's and 1's channels through rotary switches.  DCS only has commands for increase/decrease for these controls.  What I'd like to do is have separate command inputs for each position of the rotary.  Which would be 13 buttons for the 10's and 10 for the 1's.  I can program clockwise and counter-clockwise rotations of the rotary to register as increase/decrease button presses, but I want the TACAN mechanical channel display to match what is in-game.  I can sync my panel with the game by running a full rotation of the dials, but it would be more convenient if I didn't have to do that every time.

    Yup, that should be doable, but it depends on how the module was built. Like newer modules are usually really good at having relative and absolute controls available even if they dont always wire up both versions to the input files. Some of the older modules can be hit-or-miss with what commands are available.

    I did a similar thing by request for the Mig-21 with the RSBN controls: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/MiG-21bis/Input/MiG-21/joystick/default.lua#L180

    But I havent done that for any TACAN controls that I remember. Which module(s)?

    Using F-14 as example.. HB extends the joystick controls from the keyboard controls, where you'll find the TACAN controls in DCS\Mods\aircraft\F14\Input\F-14B-Pilot\keyboard\default.lua: 

    {down = device_commands.TACAN_Knob_Chnl_Tens_Step_Pilot, cockpit_device_id = devices.TACAN, value_down = 1, value_up = 0, name = _('TACAN Channel 10 Inc'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Step_Pilot, cockpit_device_id = devices.TACAN, value_down = -1, value_up = 0, name = _('TACAN Channel 10 Dec'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Step_Pilot, cockpit_device_id = devices.TACAN, value_down = 1, value_up = 0, name = _('TACAN Channel 1 Inc'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Step_Pilot, cockpit_device_id = devices.TACAN, value_down = -1, value_up = 0, name = _('TACAN Channel 1 Dec'), category = _('TACAN')},

    See that 'Step'? Thats where its relative increase/decrease. To see all the TACAN commands available to wire-up, you have to go back a couple of folders to F14\Config\command_defs.lua: 

    TACAN_Knob_Chnl_Tens_Pilot = counter(),
TACAN_Knob_Chnl_Tens_Step_Pilot = counter(),
TACAN_Knob_Chnl_Ones_Pilot = counter(),
TACAN_Knob_Chnl_Ones_Step_Pilot = counter(),

    There's the step ones, and non-step ones, which will/should be the absolute commands for the TACAN channels.

    Then sometimes I'll check clickabledata.lua to see how the clickable cockpit version of that command is configured: 

    elements["PNT_TACAN_OUTER_TWIST_PILOT"] = multiposition_switch_limited(_("TACAN Channel Wheel (Tens)"), devices.TACAN, device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_args.TACAN_Dial_Outer_Pilot, 13, 1/12, false, 0)

    13 options, each click changing by 1/12.. so then we'll end up with some lua like this for the absolute controls: 

    {down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 0/12, name = _('TACAN Channel 10 - 0'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 1/12, name = _('TACAN Channel 10 - 1'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 2/12, name = _('TACAN Channel 10 - 2'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 3/12, name = _('TACAN Channel 10 - 3'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 4/12, name = _('TACAN Channel 10 - 4'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 5/12, name = _('TACAN Channel 10 - 5'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 6/12, name = _('TACAN Channel 10 - 6'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 7/12, name = _('TACAN Channel 10 - 7'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 8/12, name = _('TACAN Channel 10 - 8'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 9/12, name = _('TACAN Channel 10 - 9'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 10/12, name = _('TACAN Channel 10 - 10'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 11/12, name = _('TACAN Channel 10 - 11'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Tens_Pilot, cockpit_device_id = devices.TACAN, value_down = 12/12, name = _('TACAN Channel 10 - 12'), category = _('TACAN')},

    Havent tested it yet but should work.

    Then I would highly suggest using quaggles command injector. Then you'd drop that snippet into a lua file in your saved games dcs folder and not have to touch it again. Modifying the base game files you'd have to re-add it after each update, or use a mod manager to replace the base game file.. in which case you'd need to do the update again if the base game file changes.

    I'll get these added this weekend to the community keybinds for the F-14 since I'm halfway there anyway, and if you have any other modules in mind let me know which ones and I'll take a look. I've been taking a break from the keybinds project and dcs in general, but got the flight rig set back up last weekend and am gonna start a refresh of the keybinds project soon. Mirage F1 and F15E keybinds are definitely in need of a refresh.

    edit: one controls 

    {down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 0/9, name = _('TACAN Channel 1 - 0'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 1/9, name = _('TACAN Channel 1 - 1'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 2/9, name = _('TACAN Channel 1 - 2'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 3/9, name = _('TACAN Channel 1 - 3'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 4/9, name = _('TACAN Channel 1 - 4'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 5/9, name = _('TACAN Channel 1 - 5'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 6/9, name = _('TACAN Channel 1 - 6'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 7/9, name = _('TACAN Channel 1 - 7'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 8/9, name = _('TACAN Channel 1 - 8'), category = _('TACAN')},
{down = device_commands.TACAN_Knob_Chnl_Ones_Pilot, cockpit_device_id = devices.TACAN, value_down = 9/9, name = _('TACAN Channel 1 - 9'), category = _('TACAN')},

     

    • Like 1

    Where, exactly, are Joystick and Keyboard bindings stored? Easy Backup?

    in Controller & Assignment Bugs - General

    Posted

    On 9/15/2023 at 6:42 PM, MAXsenna said:

    @Antix70
    The files in "InputCommands" don't change, or I would have lost all my special settings every time I update new keybinds from Munkwolf. I just download the whole shebang and overwrite. The changes are in the diff files to my knowledge, but let's ping @Munkwolf and ask.

    Cheers!

    Sent from my MAR-LX1A using Tapatalk
     

     

    On 9/16/2023 at 10:08 AM, Antix70 said:

    I think the quaggles mod "moves" the special keybinds normally placed in the DCS installation folder, to your saved games folder, and the dcs-community-keybinds somehow interacts with that.

     

    @MAXsenna is correct, the InputCommands files don't change (unless updating to a new version of community keybinds). Quaggles mod references that folder to add commands to the commands defined in the base game files in DCS\Mods\aircraft\<aircraft>\Input. It doesn't move any files around, think of it as extending from the commands in the DCS installation folder.

    Saved Games\InputUserProfiles is the default save location for control profiles saved in game, and then in Saved Games\Config\Input are the snapshots of last configured bindings for each module, files named by device name and GUID.

    Saved Games\Config\Input would be the important one to save your current bindings, but if your device GUIDs change then it could require some updating of the filenames to get them going again. I recommend saving all bindings using the profiles in-game if you dont do that already. I do that and backup the Saved Games\InputUserProfiles folder to save my bindings.

    • Like 2
    • Thanks 1

    Community Keybinds Project 22.1.22 Release

    in PC Hardware and Related Software

    Posted

    2 hours ago, MAXsenna said:

    Thank you!
    I see, will look into this. Unfortunately it seems it doesn't have a middle position. That's what I was afraid of. I was thinking there might be other places to look.

    Cheers!

    Sent from my MAR-LX1A using Tapatalk
     

    Ah, sorry I didn't understand. Looking at the lua files i only saw commands for landing, up, and then then up/landing toggle. There might be a middle position command available - is there another FC3 module that has it?

    Save and recall a view/camera?

    in DCS 2.9

    Posted

    On 8/6/2023 at 8:24 PM, MAXsenna said:

    Oh! Good question. Didn't think of that.
    Need to ask the experts.

    @Quaggles @Munkwolf

    So, guys. What happens with default commands if one changes them?


    Cheers!

    Sent from my MAR-LX1A using Tapatalk
     

    Afaik the way quaggles mod works is by the device/command/value combinations, where it won't include commands that are the same as ones already defined. This is why all the custom Viggen keybinds disappeared once HB included them in their code instead of duplicates appearing. So a different label or categories, but same device/command/value - not included.

    But some modules quantize the values so that they will always map to a valid position. You could use this to include a custom command alongside the default command. Where say the default command uses a value of 1, the custom command could reference same device, command, but then use a value of 1.0001. Since the value is different, it should be included, but whether it'd work would depend on how the modules handle that value.

    Like for some of the custom axis in the keybinds project where they control a multi-position rotary.. in some modules, that will work properly where it only changes to one of the valid positions. In other modules that weren't built with that in mind, using an axis for that rotary means the rotary is positioned exactly where the axis is, and can be really difficult to get it to register on one of the valid positions.

    • Like 2

    Community Keybinds Project 22.1.22 Release

    in PC Hardware and Related Software

    Posted

    Glad to hear it @MAXsenna!

    Yeah afaik it's possible - FC3 have the same config/input LUA file structure, just much more limited with what flavors of commands are available. Like there might just be one toggle command available for a control to map to the input LUA files, where recent full-fidelity module will have relative and absolute commands available for most controls.

    Keybinds project has the folders and files setup for the FC3 modules but they're blank.

    Looking at Su-25 flaps lever.. we got the default.lua in 'DCS\Mods\aircraft\Flaming Cliffs\Input\su-25\joystick'.. that includes 'Config/Input/Aircrafts/base_joystick_binding.lua'.. in there is what we're looking for: 

    {down = iCommandPlaneFlapsOn,				name = _('Flaps Landing Position'),		category = _('Systems')},
{down = iCommandPlaneFlapsOff,				name = _('Flaps Up'),					category = _('Systems')},

    If you see iCommand prefixes - those are realy basic shared commands, and they have a device and value baked into them.

    Then should be able to drop this in to your 'InputCommands\Flaming Cliffs\su-25\joystick\default.lua' for flaps down-else-up? Haven't tested it yet. 

    {down = iCommandPlaneFlapsOn, up = iCommandPlaneFlapsOff, name = _('Flaps Landing Position else Up (2-way Switch)'), category = {_('Systems'), _('Custom')}},

     

    VKB HOTAS, Phase One

    in VKB-SIM Flight Gear

    Posted

    2 hours ago, Outlaw24 said:

    Been waiting a long time for these to be release. But I think I'll wait a little longer to see what phase two has to offer, before I make a purchase.

    Same.

    One disappointment for me is there are no more lever axis to the sides of the throttles. The preview image of TECS years ago had a lever on each side, which was perfect imo. Warbirds, F-14, Harrier, etc.. for lots of modules there's a benefit to having at least one extra lever to go along with the main throttles.

    Like with the preview version of TECS and the F-14, the left outside lever perfect for flaps, and right outside lever perfect for wing sweep. Now with STECS we have 2 buttons and a 5 position rotary on the right? Much less useful imo.

    • Like 2

    Quaggles - DCS Input Command Injector Mod - Store custom input commands safely in Saved Games instead of merging them with developer changes each update

    in DCS Modding

    Posted

    3 hours ago, LeCuvier said:

    So my question is: If I want to add an axis section, should the key section be terminated wih a comma?

    Welcome to the cult of quaggles @LeCuvier! 🙂

    That is correct, if adding an axis section then the key section should have a comma after it (main structure is an object of objects). Blank structure for keys plus axis should look like: 

    return {
	keyCommands = {
		
	},
	axisCommands = {
		
	}
}

    Do you have the return in your file? Returning the whole object of objects is a key difference of how quaggles command injector files are formatted vs the stock lua files. Also you probably saw it but in case not, there is the blank InputCommands in Quaggles mod, which is the InputCommands_Skeleton from the community keybinds - both have all the folders setup with blank lua files for all modules.

    also, if you have any issues with the binds loading, there is often a log entry added to dcs.log, search for 'inputcommand' in the log and it'll oftentimes point you in the right direction.

    • Like 1

    Ability to set WSO switches before start up in "Solo Flight"

    in Wish List

    Posted

    On 7/1/2023 at 10:28 PM, Nealius said:

    I don't recall the manual having any checklists/direction for solo flights. Also, "as required" means just that: as required. If you're not going into combat then you leave those switches off because they aren't required....

    That said, I do feel there needs to be more keybinds for WSO switches that can be operated from the pilot seat. We have keybinds for the TPOD ON/STBY/OFF and the CMD Chaff/Flare/Both, so why can't we get keybinds for laser arm, RWR, and CMD knob?

     

    I've been working through adding custom keybinds.. i do see keybinds for laser arm and cmd knob for pilot seat?

    "CMD Operational Mode", "TGP Laser Switch", etc.. in same "Rear Cockpit" group as the tpod power and cmd dispenser selection.

    will add controls for rwr later today. just finished up first pass at wso keybinds.

    pilot: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/F-15E/Input/F-15E/joystick/default.lua
    wso: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/F-15E/Input/F-15E_WSO/joystick/default.lua

    • Like 1

    Any community binds for missing axis/switch controls?

    in Controller Questions and Bugs

    Posted

    2 hours ago, imacken said:

    Got you!

     Thanks a lot. 

    you're welcome! just pushed an update.

    added radar mode knob to axis.

    added proper controls for the canopy handle (locked/down/hold/up)

    the relative controls for volume knobs and the nav flir brightness/gain are broken. I added 0%/33%/50%/66%/75%/100% absolute controls as a workaround for now (i use a 2x2 block of buttons with 0/33/66/100 options).

    fix for where the binds for the fuel totals selector knob were offset by a position (i didn't realize BIT was negative value instead of 0).

    added 'pressed' commands for the lighting knobs. Default is with 'down' where it changes by 10% per press instead of being able to hold down the button.

    time to start on wso seat.

    • Like 1
    • Thanks 1

    Any community binds for missing axis/switch controls?

    in Controller Questions and Bugs

    Posted · Edited by Munkwolf

    3 hours ago, imacken said:

    Great piece of work. Thanks.

    Just a couple of things.  Firstly, the radar selection knob is missing from the axes.  I manually put it in for the moment as per @LeCuvier post earlier in this thread.

    Wasn't sure what you meant by the 'kudos to razbam' para.  I still have to set all axis knobs to slider with a user curve starting at 50% for these new commands.

    thanks for the heads up. i will have an update later with the radar knob and some other fixes.

    kudos part was for the controls quantizing properly with axis values. like with the radar selection and ins knobs. where on a rotary, they will snap to valid positions. compared to some other modules (or the fuel totalizer knob) where trying to use an axis doesn't snap to valid values and unusable with an axis no matter what is done with user curves.

    • Like 1

    Any community binds for missing axis/switch controls?

    in Controller Questions and Bugs

    Posted

    just committed my first pass at pilot seat binds: https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/F-15E/Input/F-15E/joystick/default.lua

    thank you to @shdwp for doing the initial commit and noticing the 'joystick abstractions' commands weren't bindable to keyboard and that it would be useful to be able to do so.

    also kudos to razbam to quantizing some of the multiposition controls so they work ok with axis (fuel totalizer knob being the exception i noticed). some modules don't do this so it's nice when it is done. most have to be inverted and half saturation. i tested all of the custom axis binds - canopy lever and landing gear lever work well as axis. i haven't tested most of the custom button binds yet.

    will cut an actual release on github this weekend after i do more testing get through the wso seat.

    • Like 1

    Ability to set WSO switches before start up in "Solo Flight"

    in Wish List

    Posted

    On 7/2/2023 at 3:44 PM, LeCuvier said:

    I have never tried the Quaggles injector, but if they are in the injected repository and in the updated stock file you will have duplicates, won't you?

    No duplicates (usually). If the device/command/value are the same for a stock command and an injected command, then Quaggles mod doesn't include the injected command. Sometimes there will be a duplicate if for some reason a different value is used. The label will change over if it's different than the injected one. The assigned keybind persists too (since it goes by the device/command/value). If using custom keybinds there's really no reason not to use Quaggles injector unless one is averse to mods or likes doing things the hard way.

    • Like 1

    Ability to set WSO switches before start up in "Solo Flight"

    in Wish List

    Posted

    On 7/2/2023 at 10:55 AM, MAXsenna said:

    Well, Rudel ain't wrong. Too many users are shooting down perfectly reasonable wishes. 😉

     

    I might be totally incorrect here. But if one is good with editing the lua control files, maybe it's possible to open the WSO lua and copy the relevant controls to the pilot controls? 

    @Munkwolf @LeCuvier

    I'm a totally off for suggesting this? 

    Cheers! 

    Edit: To be honest. I think most WSO controls should be available from the pilot's seat so we can make our own "Jester" through VoiceAttack. 

     

    Yup, that's right. All commands for modules are available for each seat - the distinction is just what is defined in the input lua files. Can copy all commands for one seat into the other's input lua file and it should work.

    • Like 1

    Please restore axis controls for volume and lighting

    in Controller Questions and Bugs

    Posted · Edited by Munkwolf

    9 minutes ago, Raisuli said:

    Alright, fine!  You've made it impossible not to take another look!  🙃

    But first, since Cairo International Airport has shut down operations and cleared out all their equipment so I have a place to lean how to fly the AH-64 I should go crash fly one while the opportunity is there.

    Haha 🙂 Success!

    One advantage of Quaggles mod vs manually doing them is how it appends the custom keybinds to to official file - it's not an overwrite. So if/when modules do get keybinds updated, you don't have to update any of your custom lua files. And if the same input/command of the custom keybind gets added, then Quaggles mod just doesn't include it - no duplicate binds if it's the same command.

    Quote

    and I need separate controls for each.

    Also, for that, I've tried to add as many of those as I can in the community keybinds. Sometimes it's not possible based on how the module was built. But I've gone through each command in the lua for almost every module (haven't done MB-339 or F-15E yet) and added as much as I can, even if the instrument is non-functional (original goal for project was if it's clickable it should be bindable). Even if you don't use Quaggles you could copy-paste from the keybinds project into your own lua files.

    Like these snippets from A-10C for the video controls and IFF: 

    -- DVADR

{down = 3002, cockpit_device_id = 73, value_down = 0, name = _('Video Selector Switch HUD'), category = {_('Custom'), _('DVADR Remote Control Panel')}},
{down = 3002, cockpit_device_id = 73, value_down = 0.1, name = _('Video Selector Switch Off'), category = {_('Custom'), _('DVADR Remote Control Panel')}},
{down = 3002, cockpit_device_id = 73, value_down = 0.2, name = _('Video Selector Switch TVM'), category = {_('Custom'), _('DVADR Remote Control Panel')}},

-- IFF

{down = 3008, cockpit_device_id = 43, value_down = 0, name = _('Master Dial Off'), category = {_('Custom'), _('IFF')}},
{down = 3008, cockpit_device_id = 43, value_down = 0.1, name = _('Master Dial Standby'), category = {_('Custom'), _('IFF')}},
{down = 3008, cockpit_device_id = 43, value_down = 0.2, name = _('Master Dial Low'), category = {_('Custom'), _('IFF')}},
{down = 3008, cockpit_device_id = 43, value_down = 0.3, name = _('Master Dial Normal'), category = {_('Custom'), _('IFF')}},
{down = 3008, cockpit_device_id = 43, value_down = 0.4, name = _('Master Dial Emergency'), category = {_('Custom'), _('IFF')}},

{down = 3007, cockpit_device_id = 43, value_down = -1, name = _('Code Dial Decrease'), category = {_('Custom'), _('IFF')}},
{down = 3007, cockpit_device_id = 43, value_down = 1, name = _('Code Dial Increase'), category = {_('Custom'), _('IFF')}},

{down = 3009, cockpit_device_id = 43, value_down = 1, name = _('Audio/light Audio'), category = {_('Custom'), _('IFF')}},
{down = 3009, cockpit_device_id = 43, value_down = 0, name = _('Audio/light Out'), category = {_('Custom'), _('IFF')}},
{down = 3009, cockpit_device_id = 43, value_down = -1, name = _('Audio/light Light'), category = {_('Custom'), _('IFF')}},

{down = 3017, up = 3017, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('Reply Button'), category = {_('Custom'), _('IFF')}},
{down = 3018, up = 3018, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('Test Button'), category = {_('Custom'), _('IFF')}},

{down = 3010, up = 3010, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('M-1 Test'), category = {_('Custom'), _('IFF')}},
{down = 3010, cockpit_device_id = 43, value_down = 0, name = _('M-1 On'), category = {_('Custom'), _('IFF')}},
{down = 3010, cockpit_device_id = 43, value_down = -1, name = _('M-1 Out'), category = {_('Custom'), _('IFF')}},
{down = 3011, up = 3011, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('M-2 Test'), category = {_('Custom'), _('IFF')}},
{down = 3011, cockpit_device_id = 43, value_down = 0, name = _('M-2 On'), category = {_('Custom'), _('IFF')}},
{down = 3011, cockpit_device_id = 43, value_down = -1, name = _('M-2 Out'), category = {_('Custom'), _('IFF')}},
{down = 3012, up = 3012, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('M-3A Test'), category = {_('Custom'), _('IFF')}},
{down = 3012, cockpit_device_id = 43, value_down = 0, name = _('M-3A On'), category = {_('Custom'), _('IFF')}},
{down = 3012, cockpit_device_id = 43, value_down = -1, name = _('M-3A Out'), category = {_('Custom'), _('IFF')}},
{down = 3013, up = 3013, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('M-C Test'), category = {_('Custom'), _('IFF')}},
{down = 3013, cockpit_device_id = 43, value_down = 0, name = _('M-C On'), category = {_('Custom'), _('IFF')}},
{down = 3013, cockpit_device_id = 43, value_down = -1, name = _('M-C Out'), category = {_('Custom'), _('IFF')}},

{down = 3014, up = 3014, cockpit_device_id = 43, value_down = 1, value_up = 0, name = _('RAD Test/Mon Test'), category = {_('Custom'), _('IFF')}},
{down = 3014, cockpit_device_id = 43, value_down = 0, name = _('RAD Test/Mon Out'), category = {_('Custom'), _('IFF')}},
{down = 3014, cockpit_device_id = 43, value_down = -1, name = _('RAD Test/Mon Mon'), category = {_('Custom'), _('IFF')}},

{down = 3015, cockpit_device_id = 43, value_down = 1, name = _('Ident/Mic Ident'), category = {_('Custom'), _('IFF')}},
{down = 3015, cockpit_device_id = 43, value_down = 0, name = _('Ident/Mic Out'), category = {_('Custom'), _('IFF')}},
{down = 3015, cockpit_device_id = 43, value_down = -1, name = _('Ident/Mic Mic'), category = {_('Custom'), _('IFF')}},

{down = 3016, cockpit_device_id = 43, value_down = 1, name = _('IFF On/Out On'), category = {_('Custom'), _('IFF')}},
{down = 3016, cockpit_device_id = 43, value_down = 0, name = _('IFF On/Out Out'), category = {_('Custom'), _('IFF')}},

{down = 3001, cockpit_device_id = 43, value_down = 0, name = _('Mode 1 Wheel 1 0'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 1 Wheel 1 1'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 1 Wheel 1 2'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 1 Wheel 1 3'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.4, name = _('Mode 1 Wheel 1 4'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.5, name = _('Mode 1 Wheel 1 5'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.6, name = _('Mode 1 Wheel 1 6'), category = {_('Custom'), _('IFF')}},
{down = 3001, cockpit_device_id = 43, value_down = 0.7, name = _('Mode 1 Wheel 1 7'), category = {_('Custom'), _('IFF')}},

{down = 3002, cockpit_device_id = 43, value_down = 0, name = _('Mode 1 Wheel 2 0'), category = {_('Custom'), _('IFF')}},
{down = 3002, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 1 Wheel 2 1'), category = {_('Custom'), _('IFF')}},
{down = 3002, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 1 Wheel 2 2'), category = {_('Custom'), _('IFF')}},
{down = 3002, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 1 Wheel 2 3'), category = {_('Custom'), _('IFF')}},

{down = 3003, cockpit_device_id = 43, value_down = 0, name = _('Mode 3A Wheel 1 0'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 3A Wheel 1 1'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 3A Wheel 1 2'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 3A Wheel 1 3'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.4, name = _('Mode 3A Wheel 1 4'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.5, name = _('Mode 3A Wheel 1 5'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.6, name = _('Mode 3A Wheel 1 6'), category = {_('Custom'), _('IFF')}},
{down = 3003, cockpit_device_id = 43, value_down = 0.7, name = _('Mode 3A Wheel 1 7'), category = {_('Custom'), _('IFF')}},

{down = 3004, cockpit_device_id = 43, value_down = 0, name = _('Mode 3A Wheel 2 0'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 3A Wheel 2 1'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 3A Wheel 2 2'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 3A Wheel 2 3'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.4, name = _('Mode 3A Wheel 2 4'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.5, name = _('Mode 3A Wheel 2 5'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.6, name = _('Mode 3A Wheel 2 6'), category = {_('Custom'), _('IFF')}},
{down = 3004, cockpit_device_id = 43, value_down = 0.7, name = _('Mode 3A Wheel 2 7'), category = {_('Custom'), _('IFF')}},

{down = 3005, cockpit_device_id = 43, value_down = 0, name = _('Mode 3A Wheel 3 0'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 3A Wheel 3 1'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 3A Wheel 3 2'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 3A Wheel 3 3'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.4, name = _('Mode 3A Wheel 3 4'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.5, name = _('Mode 3A Wheel 3 5'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.6, name = _('Mode 3A Wheel 3 6'), category = {_('Custom'), _('IFF')}},
{down = 3005, cockpit_device_id = 43, value_down = 0.7, name = _('Mode 3A Wheel 3 7'), category = {_('Custom'), _('IFF')}},

{down = 3006, cockpit_device_id = 43, value_down = 0, name = _('Mode 3A Wheel 4 0'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.1, name = _('Mode 3A Wheel 4 1'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.2, name = _('Mode 3A Wheel 4 2'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.3, name = _('Mode 3A Wheel 4 3'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.4, name = _('Mode 3A Wheel 4 4'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.5, name = _('Mode 3A Wheel 4 5'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.6, name = _('Mode 3A Wheel 4 6'), category = {_('Custom'), _('IFF')}},
{down = 3006, cockpit_device_id = 43, value_down = 0.7, name = _('Mode 3A Wheel 4 7'), category = {_('Custom'), _('IFF')}},

     

    • Like 1

    Please restore axis controls for volume and lighting

    in Controller Questions and Bugs

    Posted

    13 minutes ago, Raisuli said:

    Not a fan.  I have one mod (Community A4C) installed.  Mod managers proved to be more trouble than I like and Quaggles is a mod to do what I'm already doing in a different way; in either case a script is required, and I really do have something like 368 individual controls.  LeCuvier's additions are a fraction of what I need, and if I remember correctly they're mostly on/ff and I need separate controls for each.

    Since ED has gone to a release a month, if that, I just look at the notes and decide if it's worth the trouble.  The lack of bindings, the inconsistency between modules for how those bindings are implemented, and the fragility of the binding management files is huge reason I don't fly more modules than I do.  It takes about an hour to configure an aircraft once I have the bindings, and if something goofy happens with USB addresses all that goes away in and instant and I can start over from scratch.

    In the end ED is letting other people cobble band-aids for problems they don't consider important enough to solve.  That's certainly their prerogative.  It is a little disappointing that the F/A-18 had about 90% of the binding already done, and the A-10C II has about 10%.  Between them I have a whole aircraft!

    After all, this is a game.  About the time I get frustrated I try to remember that  🙂

    Ok, if you want to do it the hard way go ahead and do your thing 🙂

    I started the community keybinds project to share all the keybinds I've found useful. I've got over a thousand controls on my simrig, and I like having lots of options to use all of them to the fullest. Seemed like what you were looking for.

    • Like 1

    Please restore axis controls for volume and lighting

    in Controller Questions and Bugs

    Posted

    15 minutes ago, Yurgon said:

    If it was possible to add personal keybinds in Saved Games, we'd be a good step forward. In fact that would make it relatively simple for people to maintain a repository for addon-keybinds and somewhat take the heat off ED and the 3rd parties.

    That's exactly what Quaggles mod and the Community Keybinds project I linked to above do 🙂 HB included the Viggen keybinds from the Community Keybinds in a recent update (and I'll be removing the Viggen binds from the Community Keybinds once that update is released to stable branch)

    • Like 2

    Please restore axis controls for volume and lighting

    in Controller Questions and Bugs

    Posted · Edited by Munkwolf

    Here's the extra binds I have available in the keybinds project for the A-10, including lighting and volume controls. No need to be adding them yourself.

    https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/A-10C_2/Input/A-10C_2/joystick/default.lua

    Note that the commands the lighting controls hook into work as half an axis - to use the full range of your axis you have to use axis tune and change the saturation. Here's an example: https://imgur.com/gallery/Bv8KH23

    Files are formatted for use with Quaggles Input Command Injector Mod - where you place custom binds in your saved games folder so they persist across DCS updates:

    https://github.com/Quaggles/dcs-input-command-injector

    • Like 2

    missing control button

    in DCS: C-101 AvioJet

    Posted

    On 6/25/2023 at 4:36 AM, Vibora said:

    Hi Ours. It would help if you could make a list of such buttons/controls and needed positions. In any case, this is in a low priority level for us.

    @Vibora Here's the commands I added as part of the keybinds project, including on and off commands as requested by ours:

    https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/C-101/Input/C-101CC/joystick/default.lua

    https://github.com/Munkwolf/dcs-community-keybinds/blob/main/InputCommands/C-101/Input/C-101EB/joystick/default.lua

    Please feel free to incorporate any/all of them into your module!

    @MAXsenna Thank you for the recommendation and kind words!

    • Like 2

    Input Configuration Mode to Allow Control Setup by Clicking Controls in Cockpit

    in DCS Core Wish List

    Posted

    I would like to be able to configure controls by clicking on controls in the cockpit instead of searching through the list of controls in the current input commands view.

    Add a UI Layer or General keybind along the lines of 'Toggle Input Configuration Mode'. When that mode is enabled, clicking on a control in the cockpit launches the control configuration window. I feel like that could save a lot of time during initial setup. Hovering over controls when the configuration mode is enabled could show the currently assigned keybind.

    Also, please keep moving more general controls (cockpit view left/right/up/down/etc, kneeboard) out of modules to General or UI Layer. Could keep them at module-level, where module-level configurations are blank by default but when defined would override the General or UI Layer configuration.

×
×
  • Create New...