Jump to content

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


Recommended Posts

Posted

Hi guys,

is it possible to set up a button for the f16 to centre the radar antenna?

Vertically 

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted (edited)
1 hour ago, speed-of-heat said:

Hi guys,

is it possible to set up a button for the f16 to centre the radar antenna?

Vertically 

Yes, if you are willing to add this line to the file "default.lua":

{down = hotas_commands.THROTTLE_ANT_ELEV_AXIS, value_down =  0.0, cockpit_device_id = devices.HOTAS, name = _('ANT ELEV Knob - Center'), category = {_('Throttle Grip'), _('HOTAS')}},

The zero value centers the axis vertically. I simply copied the line for the axis, replaced the "action" with a "down" expression and added the "value_down" expression. You can do this with all axis commands in all modules I have tried. You have to find the right value by trial and error as the axis range definitions vary.

Edited by LeCuvier
  • Thanks 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted
On 12/20/2024 at 12:09 PM, LeCuvier said:

Yes, if you are willing to add this line to the file "default.lua":

{down = hotas_commands.THROTTLE_ANT_ELEV_AXIS, value_down =  0.0, cockpit_device_id = devices.HOTAS, name = _('ANT ELEV Knob - Center'), category = {_('Throttle Grip'), _('HOTAS')}},

The zero value centers the axis vertically. I simply copied the line for the axis, replaced the "action" with a "down" expression and added the "value_down" expression. You can do this with all axis commands in all modules I have tried. You have to find the right value by trial and error as the axis range definitions vary.

Thanks that works really well!

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

  • 2 weeks later...
Posted

@LeCuvier this would be the equivalent on the F/A-18 then ?

 

Centre Antenna

{   down = hotas_commands.THROTTLE_ELEVATION_CONTROL_AXIS, value_down =  0.0, cockpit_device_id = devices.HOTAS, name = _('Centre Radar Elevation Control'),        category = {_('Throttle Grip'), _('HOTAS')}},

 

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted

hmmm i have tried a few different values 0 seems to have no effect, any number or fraction sends the antenna all the way to the top, any negative number/fraction  all the way to the bottom ?

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Posted
15 hours ago, speed-of-heat said:

hmmm i have tried a few different values 0 seems to have no effect, any number or fraction sends the antenna all the way to the top, any negative number/fraction  all the way to the bottom ?

you are out of luck here, because the Hornet's antenna elevation axis does not set an elevation value. Instead, it sets the speed at which the antenna will go up or down. There has been quite a bit of discontent about this, but apparently that's how the real thing works.

  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted
2 hours ago, LeCuvier said:

you are out of luck here, because the Hornet's antenna elevation axis does not set an elevation value. Instead, it sets the speed at which the antenna will go up or down. There has been quite a bit of discontent about this, but apparently that's how the real thing works.

ah okay at least i understood the principle 🙂 thanks 

SYSTEM SPECS: Hardware AMD 9800X3D, 64Gb RAM, 4090 FE, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

YOUTUBE CHANNEL: @speed-of-heat

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

  • 1 month later...
Posted

Hey guys. Have tried to get this to work for a few hours and seem to be spinning my wheels. Testing out Quaggles input command injector mod with Munkwolf's Community Keybinds.

First, my assumption is that I should see all of the community keybinds in the game that I see in the default.lua file, after the mod has been installed. If my assumption is wrong, please let me know. At this point, I have not tried to create any custom bindings myself. In my example, I'm looking at the F-14B module and focusing on the TACAN keybinds. Specifically wanting to test out the Mode Normal/Inverse and X/Y with 'or else' binds so I only need single throw switches to save on inputs.

Followed the instructions for setting up Open Mod Manager and adding the mods in what is the appropriate location, as best I can tell. Both mods are installed. In DCS, I don't see any of the additional keybinds for the F-14 that are in the community keybinds, default.lua file. Checked the dcs.log and am not seeing anything related.

Where am I going wrong? File paths are shown in the screenshots below. dcs.log is attached

Thank you

 image.png image.png

null

dcs.log

Posted


@ITR1102
Hi! Have you tested that Quaggles' file goes to the correct place? It's easy to test. Uninstall the mod. Find the original core file. Rename it, then reapply the mod, and check the file is there. It worked on the first try for me.
As for the Munkwolf repository, I did not bother to make a mod of it, as they are bypassed if I uninstall Quaggles'. I just followed the instructions to the letter and manually copied them to the correct folders.
Cheers!

Sent from my SM-A536B using Tapatalk

Posted
7 hours ago, MAXsenna said:


@ITR1102
Hi! Have you tested that Quaggles' file goes to the correct place? It's easy to test. Uninstall the mod. Find the original core file. Rename it, then reapply the mod, and check the file is there. It worked on the first try for me.
As for the Munkwolf repository, I did not bother to make a mod of it, as they are bypassed if I uninstall Quaggles'. I just followed the instructions to the letter and manually copied them to the correct folders.
Cheers!

Sent from my SM-A536B using Tapatalk
 

Manually installing the files worked but it doesn't seem that Open Mod Manager is working for some reason.

Posted
Manually installing the files worked but it doesn't seem that Open Mod Manager is working for some reason.
Which files? You mean the Quaggles file or the Munkwolf folders?
If you mean Quaggles, it's it puts the file in the wrong place. The mod does not work out of the box with OMM.

Sent from my SM-A536B using Tapatalk

Posted

I manually added the Quaggles files to the DCS folder per the instructions on GitHub and the Munkwolf files to the saved games folder, not using OMM at all. Very glad it’s working but I’m obviously missing key points of using OMM.


Sent from my iPhone using Tapatalk

  • Like 1
Posted

I have had no problem with the Quaggles mod in OMM.

Try the attached.

DCS-Input-Command-Injector-Quaggles v1.0.12.zip

  • Like 1

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Posted
2 hours ago, Quaggles said:

@ITR1102 Looking at the OMM screenshot you posted I think you downloaded the entire Github repository as a zip instead of downloading the release zip (DCS-Input-Command-Injector-Quaggles.zip) which is formatted to be OMM/OVGME compatible: https://github.com/Quaggles/dcs-input-command-injector/releases/tag/1.0.12

That's exactly what happened. It was incredibly simple after using the right zip file. Thanks for the help guys

  • Like 1
  • 4 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...