Jump to content

F-14B Additional Key Binding (Pilot)


Alerax

Recommended Posts

On 3/19/2022 at 9:46 AM, BlackLibrary said:

i search for a switch function for

HUD Brightness DECR / INCR 
VSDI Screen Brightness DECR / INCR
VSDI Screen Contrast DECR / INCR
HSD Brightness DECR / INCR

one switch for DECR and an other for INCR

 

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

  • 7 months later...
1 hour ago, PSYKOnz said:

Is this mod still going? Still alive? I hope so cause it's filling a void that definitely needs filling lol

Depends on what you need. Many binds might have already been added since.

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

I would like to see two keybindings for pilot to increase and decrease radar range for Jester AI. Currently there are fixed bindings for this; "Radar Range - 25/50/100/200/400". Instead of using 5 buttons on Hotas to map all the ranges, we can use only two buttons instead. Right now due to lack of available buttons I'm only mapping the 50 and 100 ones to my Hotas. I believe there are other modules that already support this.

Thanks!

Link to comment
Share on other sites

On 11/17/2022 at 9:36 PM, Shahriar0 said:

I would like to see two keybindings for pilot to increase and decrease radar range for Jester AI. Currently there are fixed bindings for this; "Radar Range - 25/50/100/200/400". Instead of using 5 buttons on Hotas to map all the ranges, we can use only two buttons instead. Right now due to lack of available buttons I'm only mapping the 50 and 100 ones to my Hotas. I believe there are other modules that already support this.

Thanks!

Hi, for instance you can add those keybinds from the RIO to the PILOT (copy past these in "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Input\F-14B-Pilot\keyboard\default.lua", i placed those additional keybinds just under ILS section, you can do the same if you want):

--************************************* Additional keybinds  ******************************************************************
{down = device_commands.TID_range_knob_step, cockpit_device_id=devices.TID, value_down = 1.0, name = _('TID range +'), category = _('TID')},
{down = device_commands.TID_range_knob_step, cockpit_device_id=devices.TID, value_down = -1.0, name = _('TID range -'), category = _('TID')},

Should look like this:

image.png

Then you can map those keybinds in-game. Remember to always ask Jester a fixed TID Range before using those keybinds, otherwise, he'll change it by himself a few seconds after your inputs.


Edited by Xl-45
Link to comment
Share on other sites

2 hours ago, Xl-45 said:

Hi, for instance you can add those keybinds from the RIO to the PILOT (copy past these in "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Input\F-14B-Pilot\keyboard\default.lua", i placed those additional keybinds just under ILS section, you can do the same if you want):

--************************************* Additional keybinds  ******************************************************************
{down = device_commands.TID_range_knob_step, cockpit_device_id=devices.TID, value_down = 1.0, name = _('TID range +'), category = _('TID')},
{down = device_commands.TID_range_knob_step, cockpit_device_id=devices.TID, value_down = -1.0, name = _('TID range -'), category = _('TID')},

Should look like this:

image.png

Then you can map those keybinds in-game. Remember to always ask Jester a fixed TID Range before using those keybinds, otherwise, he'll change it by himself a few seconds after your inputs.

 

This is exactly what I was looking for.  Many many thanks!

Link to comment
Share on other sites

  • 6 months later...

Need help please, I'm trying to make a bind for the F14 Asymmetric thrust limiter off and cover open, else on and closed. I tried creating a line of code based off what Heatblur has in there for the master arm switch "master arm on and cover open else safe and closed" but I've had no luck. Any help would be greatly appreciated, below is what i tried without success:

{down = device_commands.ENGINE_Asym_Limiter_And_Cover,     up = device_commands.ENGINE_Asym_Limiter_And_Cover, value_down = 1, value_up = 0, cockpit_device_id=devices.ENGINE, name = _('Asymmetric Thrust Limiter Off and Cover Open, else On and Closed'), category = _('Engine Control Panel')},

Modules: F-14A/B | F-15C | F-16C | F/A-18C | SU-33 | Spitfire Mk IX | AH-64D | UH-1 | Super Carrier | Combined Arms | Persian Gulf | Syria | NTTR

Setup: VKB Gunfighter Mk.III F-14 CE HOTAS | Thrustmaster TWCS Throttle | MFG Crosswind V3 | Custom switch panel | Tek Creations F14 Display Panel | Custom F14 Left Vertical Console | Custom IR Tracker | Custom butt kicker

PC: i7 11700K | 64GB G-Skill DDR4 3600MHz | EVGA GeForce RTX 3080Ti FTW3 | DCS dedicated 2TB M.2 NVMe SSD | 3440x1440 144hz 34" ultrawide

Link to comment
Share on other sites

42 minutes ago, Hector45 said:

device_commands.ENGINE_Asym_Limiter_And_Cover

If it doesn't exist in clickable.lua it won't work afaik - make a request here:

https://forum.dcs.world/topic/201044-running-request-bindable-button-axis-options/page/13/#comment-5224447

and in the meantime you can work this out with external app for making combos.

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

1 hour ago, draconus said:

If it doesn't exist in clickable.lua it won't work afaik - make a request here:

https://forum.dcs.world/topic/201044-running-request-bindable-button-axis-options/page/13/#comment-5224447

and in the meantime you can work this out with external app for making combos.

Thanks draconus, whats the name of the external app? Is it DCS Bios?

Modules: F-14A/B | F-15C | F-16C | F/A-18C | SU-33 | Spitfire Mk IX | AH-64D | UH-1 | Super Carrier | Combined Arms | Persian Gulf | Syria | NTTR

Setup: VKB Gunfighter Mk.III F-14 CE HOTAS | Thrustmaster TWCS Throttle | MFG Crosswind V3 | Custom switch panel | Tek Creations F14 Display Panel | Custom F14 Left Vertical Console | Custom IR Tracker | Custom butt kicker

PC: i7 11700K | 64GB G-Skill DDR4 3600MHz | EVGA GeForce RTX 3080Ti FTW3 | DCS dedicated 2TB M.2 NVMe SSD | 3440x1440 144hz 34" ultrawide

Link to comment
Share on other sites

1 hour ago, Hector45 said:

Thanks draconus, whats the name of the external app? Is it DCS Bios?

TM TARGET, Joystick Gremlin etc.

🖥️ Win10  i7-10700KF  32GB  RTX3060   🥽 Rift S   🕹️ T16000M  TWCS  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Link to comment
Share on other sites

Have you tried without binding open the cover? I tried something like that in advance for when I can actually use it (I only have a single throttle atm), I thought it worked as intended though I'm not really sure. Otherwise using an external app you can use a single command to trigger both.

AMD Ryzen 5600G, RX7900 XTX, 48GB 27" 1440P monitor and Oculus Quest 2. WinWing Orion 2 w/ FA18 throttle, VKB Gladiator EVO w/ F14 grip, Logitech G rudder pedals, TrackIR 5, WinWing MFD and Voice Attack.

Planes: F14A/B Tomcat, mostly the B, F/A 18 C Hornet

Modules/ maps: Super carrier, Nevada, Persian Gulf

Link to comment
Share on other sites

  • Recently Browsing   0 members

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