Can DCS keyboard controls be shared before the module is released?

[Dudikoff]

Would it be possible for someone (dev team, beta testers, etc.) to export and share the keyboard assignments assigned in DCS for the F-14 module? And perhaps a screenshot of all of the possible axis assignments?

 

Those are needed so we could have the custom HOTAS profiles (e.g. for TM Target) ready before the module is released.

 

Thanks.

[mkosmo]

Would it be possible for someone (dev team, beta testers, etc.) to export and share the keyboard assignments assigned in DCS for the F-14 module? And perhaps a screenshot of all of the possible axis assignments?

 

Those are needed so we could have the custom HOTAS profiles (e.g. for TM Target) ready before the module is released.

 

Thanks.

 

That doesn't seem particularly likely or precedented. After release, what's the big deal in the hour or so it'll take to start working up a profile?

[Dudikoff]

That doesn't seem particularly likely or precedented. After release, what's the big deal in the hour or so it'll take to start working up a profile?

 

Hour or so? Yeah, right. It would take more just to type in all the commands assigned in DCS, let alone how many hours to program the script file to use them.

 

I forgot to mention that I'm programming the Cougar MFD's as well, hence why there's a bunch of commands needed and why it will take me a lot of time. So, I'd rather do it this week and be ready for release.

 

But, why would this be unlikely or require a precedent? There's a bunch of people flying out there and these commands are not classified and won't change till release. It takes only a few clicks to export an html profile for the keyboard category.

Edited March 5, 2019 by Dudikoff

[Sergeant_Hamlet]

Dunno about keyboard bindings, but I asked a question about the HOTAS a couple of weeks ago and strikeeagle posted this:

 

 

 

Credit goes to Jabbers; he made it for reddit. Hope it helps!

[Eldur]

HB probably just should dump or let someone dump the current Mods\aircraft\F-14B\Input\keyboard\default.lua in here

[shagrat]

If I understood one of Jabbers or Magz comments correctly, the F-14 comes with a predefined default setup for the Thrustmaster Warthog. He mentioned that he did not need to change anything and was very happy with the default bind.

My guess, is Heatblur has this covered already.

[Strikeeagle345]

If I understood one of Jabbers or Magz comments correctly, the F-14 comes with a predefined default setup for the Thrustmaster Warthog. He mentioned that he did not need to change anything and was very happy with the default bind.

My guess, is Heatblur has this covered already.

 

see two post above for the default mapping for the TM Warthog.

[Dudikoff]

HB probably just should dump or let someone dump the current Mods\aircraft\F-14B\Input\keyboard\default.lua in here

 

Yeah, I wouldn't expect that to be a problem, but..

 

If I understood one of Jabbers or Magz comments correctly, the F-14 comes with a predefined default setup for the Thrustmaster Warthog. He mentioned that he did not need to change anything and was very happy with the default bind.

My guess, is Heatblur has this covered already.

 

I need all the keyboard commands as I want to make a custom Target profile including both the HOTAS and the Cougar MFDs. I don't use default profiles.

Edited March 5, 2019 by Dudikoff

[Raisuli]

I will need to make overlays and set up a few extra bindings...For some reason people think I get obsessive. Not sure why.

 

 

 

[Victory205]

Good man. ^^^^

[Larkis]

I want do know if i can Bind DLC on an Axis or use an axis as digital input.

 

The Rudder on the T16000 Hotas is really made for this to use it the intendet Way. Has anyone infos about that?

[FZG_Immel]

I will need to make overlays and set up a few extra bindings...For some reason people think I get obsessive. Not sure why.

 

 

 

 

Did you build these ? Where did you get the parts ? What controller card ?

[Sn8ke_iis]

Concur for the key call backs for TARGET. I use custom profiles with modifiers. With the key call backs I can integrate the default setup into my usual layers and default view and a UFC. If they end up changing a few keybinds in an update I'm OK with that. It usually takes me awhile as well and is part of the study and familiarization process. If they already posted the documentation, why not the key callbacks?

[Dudikoff]

Concur for the key call backs for TARGET. I use custom profiles with modifiers. With the key call backs I can integrate the default setup into my usual layers and default view and a UFC. If they end up changing a few keybinds in an update I'm OK with that. It usually takes me awhile as well and is part of the study and familiarization process. If they already posted the documentation, why not the key callbacks?

 

Thanks, same here. It takes quite a while to study, organize and arrange all these commands and shifted states/modifiers to something which is intuitive to me before trying it out in the real airplane and I'd rather do it ahead of the module release instead of not being to try out the plane comfortably for days after.

 

For instance, currently, I have no idea if cockpit switches will be made as toggles or there will be separate keys for each position or both.

Edited March 6, 2019 by Dudikoff

[Raisuli]

Did you build these ? Where did you get the parts ? What controller card ?

 

 

Yes.

 

 

 

The faces are fiberglass, switches are NKK (and a couple ALCO I had laying around), rotaries are Greyhill, pots are ALPHA; the volume pots have detents. Most of the switches came from Mouser, run off Teensy controllers and programmed to look like KB/Mouse/Joysticks. Both, and in some cases all three, positions on the toggles have associated switches, so I need to program all positions in DCS, which is a pain when all they have exposed in DCS is a toggle (there are three or four of those in F/A-18 and it's annoying).

 

 

It's set up to allow putting an overlay with different labels on the faces, which is good because replacing the base labels is a pain and I screwed them up. Held on magnetically, and magically you have labels for another aircraft.

 

 

One of those has three switches (7 positions) more than fits on the Teensy 3.6, so there's a Cat 6 cable between that one and the skinny guy, which has positions to spare. Not my fault I can't count. The one with the fewest digital ports is the one with all the push buttons. That's a switch matrix. I could configure one of the buttons as a mode switch, but I've never met an aircraft that has a need for that many.

 

 

There's more on my plate; one will have a mode button and 12 buttons powered by XKeys; either push buttons or momentary toggles. I'll decide when I get around to making it. I want to put monitors behind my MFDs first. I have all the parts, just need to take the time.

Edited March 6, 2019 by Raisuli

[Dudikoff]

Well, pretty much none of the cockpit controls are assigned by default, so quite a lot of work ahead.

 

Does anyone get the difference between e.g. "ACM Cover Toggle", "ACM Cover Closed, Else Open", "ACM Cover Open, Else Closed"..

 

Of course, there's also "ACM Cover On" and "ACM Cover Off" to complicate the logic further.