New key binds wanted

[Tango]

* Landing gear could use a toggle key (down -> neutral -> up -> neutral -> down )

 

* Flaps need keyboard shortcut for each position and Warthog flap switch support would be welcome

 

* Air brake needs toggle key

[YoYo]

I did profile for Warthog, see in MiG21 part of Forum, worked well, but some of key in final version was missed and changed.

 

http://forums.eagle.ru/showthread.php?t=129553

[Nobody96]

Why does ED not provide an API to standardize this? Seems like every 3rd party is trying to reinvent the wheel here. Fiirst Belsimtek with their toggle-switches only approach, now Letherneck with their no toggle-swichtes approach.

 

-Mathias

[Oesau]

Restart Mission key binding - really helpful for practice mission for fast reloads versus having to wait for the briefing screen

[cichlidfan]

Why does ED not provide an API to standardize this? Seems like every 3rd party is trying to reinvent the wheel here. Fiirst Belsimtek with their toggle-switches only approach, now Letherneck with their no toggle-swichtes approach.

 

-Mathias

 

Agreed. :thumbup:

 

This is one area where a standard practice needs to be put in place and adhered to by everyone. I don't mind constructing a few creative commands for my Warthog profiles but it seems that every other aircraft requires a different approach to get to the same place.

[aemvee]

Briefing window LAlt+B please.

[Winfield_Gold]

yep the key bindings are a bit dodgy, I can't open or close the canopy, just keeps making a hissing sound.

 

Brakes are annoying, not being able to bind the rudder to joystick buttons are also annoying. Many keys can not be bound to the joystick. I agree with the above that key bindings should be standardized across all modules. Other new switches can be added with modifiers but the main keys such as brakes and flaps and canopy should be the same across the board

[NeilWillis]

Not just standardized, but a comprehensive, workable joystick setting for each and all the current popular joystick combinations. Once written for one module, surely it could be made available to all developers for inclusion within their modules.

[[DBS]TH0R]

Seconded.

 

So many switches that have on and off position require two binds. That is all nice and dandy for someone building a full simpit, but for the majority of us a toggle key that does on and off would do just fine.

 

For the example drag chute and gear cover require two binds while one would me more than enough. Same goes for nose wheel braking, etc...

Edited September 20, 2014 by T}{OR

[Flagrum]

I was wondering if some of these issues could be solved by defining some own macros, similar to how the autostart cheat (LWIN+HOME) is implemented.

 

Yeah, fml. The macros are hardcoded in the .DLL and not as .LUA code as in every other module. :hmm: Seems the 21 is really meant to be not moddable.:cry:

[Dolphin887]

Flagrum,

 

we had to move the macro from Lua to C++, since it refused to execute in Lua.

 

If macros prove to work in Lua, I don't see why anyone can't write one.

[etcher]

I'm actually pretty happy with the system so far.

 

The "on/off requires two button" is easily solved by editing "default.lua". Agreed, it's a bit of work, but once it's done it's done and the end-result is something that very precisely does what you want it to do.

 

Besides lua editing, there are so much possible solutions out there (Target, HELIOS, XPadder, any kind of "smart" keyboard/mouse/*thing with buttons*, etc.). I frankly am convinced that there already are tons of solutions for every concern raised in this thread, and that among them anyone would be able to find one that satisfies them fully.

 

IMO it's a good thing that the system is as modular as it is, and that every 3rd party is able to do as they please. We would lose so much of the potential for pit-building, or even simple tweaking, if everything had to "fit in the box". There is so much to learn from the other people's approach to a problem, and being able to change things on a very low level gives way for all kind of tinkering. That is something I'm very fond of with DCS =)

 

(also @ED: thank you so much for the diff.lua, I still have the occasional nightmare about the update process before that :beer:)

[Flagrum]

I'm actually pretty happy with the system so far.

 

The "on/off requires two button" is easily solved by editing "default.lua". Agreed, it's a bit of work, but once it's done it's done and the end-result is something that very precisely does what you want it to do.

 

Besides lua editing, there are so much possible solutions out there (Target, HELIOS, XPadder, any kind of "smart" keyboard/mouse/*thing with buttons*, etc.). I frankly am convinced that there already are tons of solutions for every concern raised in this thread, and that among them anyone would be able to find one that satisfies them fully.

 

IMO it's a good thing that the system is as modular as it is, and that every 3rd party is able to do as they please. We would lose so much of the potential for pit-building, or even simple tweaking, if everything had to "fit in the box". There is so much to learn from the other people's approach to a problem, and being able to change things on a very low level gives way for all kind of tinkering. That is something I'm very fond of with DCS =)

 

(also @ED: thank you so much for the diff.lua, I still have the occasional nightmare about the update process before that :beer:)

A fine grained modularity here is certainly a good thing and it is obvious that LNS took the concerns and suggestions of the community regarding this topic in the past into account. Props to LNS for that!

 

But now the "middle ground" it is lacking a bit, ways of how to plug all the low level stuff together to something, hrm, more user-friendly - for users of standard, off the shelf HOTAS devices. Yes, it is possible to do that with external software, but frankly, I don't want to program my G940 and "waste" one of it's precious buttons for, i.e. the Gear Up/Down functionality. I don't need that within the reach of my fingers all the time - I need it only 1, 2, or mabe even 4 times in a mission and therefore I was always happy to hit the G on my keyboard for that. But without a pre-defined input function this is not possible with the MiG-21 atm.

[[DBS]TH0R]

I'm actually pretty happy with the system so far.

 

The "on/off requires two button" is easily solved by editing "default.lua". Agreed, it's a bit of work, but once it's done it's done and the end-result is something that very precisely does what you want it to do.

 

Besides lua editing, there are so much possible solutions out there (Target, HELIOS, XPadder, any kind of "smart" keyboard/mouse/*thing with buttons*, etc.). I frankly am convinced that there already are tons of solutions for every concern raised in this thread, and that among them anyone would be able to find one that satisfies them fully.

 

As a person who doesn't have the time to modify .lua files to get a simple pinky switch on TM Hog to act as toggle on and off for nose wheel brake, I am not happy with this solution.

 

In the latest patch, Fw-190D9 module introduced on and off keys for EZ42 gunsight while maintaining the old one-key bind toggles as well. That works for everyone. Not the case with Mig-21Bis.

[GregP]

As far as other keybinds that would be nice to have, I'd like to request the following:

 

Radar Lock Cancel (CM52)

ASP Angular Correction Knob (CU25)

Radar Low Speed Target Mode (CM50)

Edited September 20, 2014 by GregP

[Dustoff74]

As a first step it would be nice, to make all keyboard commands available for joystick. E.g. the flaps can be raised and lowered via the keyboard, but for the stick I can only assign the specific positions. Also there are a couple of axis, like radar range, wing span, etc, that can not be linked to a stick axis.

 

I really love that module and will be forever grateful, but please keep all those guys without sophisticated homecockpits in mind :smilewink:

My HOTAS has to do the job and it has only so many buttons. This will be even more important, when the Oculus Rift finally hits the shelfs! :joystick:

[lxsapper]

Agree with the requests made so far, particulary the flaps and airbrakes.

Would like to add that the Throttle off/idle needs a two position command not just toggle (it's actually sort of wierd that LD with their mostly no Toggle aproach left this as tottle only or Inc./dec. in case of the flaps).

[IonicRipper]

A toggle button for the mirror would be nice too. I usually fly with mirrors off because of the FPS hit but would like to turn it on for landings to make sure my chute deploys and jettisons.

[IonicRipper]

Ohh and one more thing that would be nice: A next and previous button for the weapon selector. That way I could assign it to the scroll wheel on my X-55 :thumbup:

[borisff]

* Landing gear could use a toggle key (down -> neutral -> up -> neutral -> down )

 

* Flaps need keyboard shortcut for each position and Warthog flap switch support would be welcome

 

* Air brake needs toggle key

 

Afterburner toggle on/off

Emergency Afterburner toggle on/off

[CoBlue]

Briefing window LAlt+B please.

Need that for multiplayer:thumbup:

[F31x]

Well at the moment I'm trying to have my first hours with the MiG 21, but this also drives me crazy. Especially "normal" operations like flaps, gears etc. I'm using the X55 so I have enough switches especially on my Throttle to be mapped but for some standard things (e.g. airbrakes, gears etc.) I have to use two buttons, really?

 

Problem is that I'm trying to have a "standard" layout of the main switches, which I have for all of the planes. I know this can be changed in the files itself but...well yes, please do a patch for that.

 

The MiG 21 is the highest quality Add-On we've seen so far, so please LSN finish it also in this subjects.

Edited February 4, 2015 by F31!x

[rrohde]

Seconded.

 

So many switches that have on and off position require two binds. That is all nice and dandy for someone building a full simpit, but for the majority of us a toggle key that does on and off would do just fine.

 

+1

[kn5]

I'd like to request the following:

-weapon selector (rotary)(left/right)

-general more toggle/rotary if possible, pls

[some1]

No exactly a key bind, but it would be useful to use the mouse wheel to tune RSBN/PRMG channels and radios, like in the other modules, instead of clicking 30 times to get to the Kobuleti channel (15) on both receivers.