Colseg

Sorry for the wait guys, got a ready to drop in beta version in the OP, as has been said before the lights related switches don't work at the moment so I disabled them in the beta version until I get the chance to dig into the changes made to their controls, as has also been said the afterburner maximum switch functions other than it visually appearing stuck in the down position, thanks for sticking around guys and happy flying.

I have been working on it, so far I have tried value_down=device_commands.ASPlauncherSelect+0.1 which doesn't create an error but doesn't seem to do anything when used for a keybinding and pressing the keybinding, I have also tried using a for loop and creating local variables like seen in the devices.lua but have not been able to get them to produce any results, I still do not know if the default.lua is something where code can be repeated persistently or if it only runs once. Thanks for the bindings, I never thought about mimicking a 4 position in that way, will definitely add it in the file as an alternative binding to the 3 position version.

It is as ApoNOOB said, the reason for such a large number of 3 position switches is to give people the option of which they would like to use for themselves, there are also 2 position versions available for two of the 3 position switches ("Alternate Landing Lights Land 2 Position Only" "Alternate Weapon AA Mode - IR Missile 2 Position Only") I have been meaning to test if it is possible to use things like increments and decrements as you have said for the weapon selector and other dials for a while and keep forgetting to try, I will look into it.

After having created and maintained my "TM Warthog Keybinds For 3 and 2 Position Switches" lua file for the MiG-21Bis which can be found here http://forums.eagle.ru/showthread.php?t=130459 I saw just how differently Leatherneck Simulations has structured their keybinds in comparison to other modules and have decided to create this guide on their structure as seen in the MiG-21Bis and I predict will continue to be used in subsequent Leatherneck modules. I have made the explanation of certain aspects (namely comments) rather explicit in the hopes of making it easier to understand for people who have not worked with code previously. (1)--Alternate Airbrakes {down=(2)device_commands.Airbrakes,(3)up=device_commands.Airbrakes, (4)cockpit_device_id=devices.AIRBRAKE,(5)value_down=1.0,value_up=0.0, (6)name='Alternate Airbrakes On',(7)category='Flight Controls'}, Above I have taken a line from my MiG-21BIS Custom Controls lua and added reference marks in the form of numbers in parenthesis(note that all numbers with parenthesis shown in the above line should not be included in an actual controls lua as they will render it non-functional and are shown here for reference purposes) (1) "--" this double minus symbol, when placed at the beginning of a line, will identify that line as a comment, a comment is simply a line of text and/or symbols that will be ignored by the program and can be used for creating anything from organization headers, to comments for others who open the file to read, to temporary disabling a line of code for buggfixing reason (2) "device_commands." device_commands. identifies which command is being given a value by your "value_down" or "value_up" from later within this line, the . is followed immediately by a defined command, all commands can be found in the "Eagle Dynamics\DCS World\Mods\aircraft\MiG-21BIS\Cockpit\command_defs.lua" file or the equivalent file in future leatherneck products (keep in mind that some commands that have not been used in the final product may be included here, this can be great if it happens to include one that you needed for your keybinds but can also include commands that still include bugs and therefore could produce odd or even unintendedly useful results or simply do absolutely nothing) (3) "down=" and "up=" these define what device_commands will be used when the button is pressed down and released respectively and these can differ if needed for your keybind (4) "cockpit_device_id=" defines the device id of the device being given a command by your "device_commands." earlier in the line, all of the device ids can be found in the "Eagle Dynamics\DCS World\Mods\aircraft\MiG-21BIS\Cockpit\devices.lua" file and the same warning from the commands explanation applies (5) "value_down=,value_up=," "value_down" identifies the value of the command identified by your "down=" which will be sent to the device identified in your "cockpit_device_id=", "value_up" does the same but identifies the value of your "down=" command instead (6) "name=" identifies the name of this keybind that it will show up under in the DCS keybinds menu (7) "category=" identifies the category that this keybind will show up under in the DCS keybinds menu

I have updated the default.lua for the newest bf-109k-4 containing update.

I have uploaded a new version of the file based on the new default.lua, everyone on the newest version of dcs world will need this update to avoid control issues stemming from changing definitions unless you have already copied the custom section to the new version. Update Updated with the newest controls file since the mini update "1.2.11.34087".

Thanks for the heads up, I will watch for the update and work to resolve the problems as soon as I can after it drops.

You don't need TARGET for this, this just adds new bindings under the names listed in the first post to the keybinds menu that are setup such that when the bind is triggered(the switch is flipped up) the up position is set and when the bind is released(the switch is flipped down) the down position is triggered for 2 way switches and more or less the same system for 3 way switches. What that all means for you is just install the mod as mentioned in the post and then bind the 2 way switches to the 2 way switches on your warthog and the 3 way switches to the up and down positions on any of the warthog's 3 way switches.

I found why I couldn't replicate it, for some reason my dcs didn't find the update yesterday so I am getting it now and should have a fix up for you guys shortly. Since it is based on the old version it doesn't have the new axis or the new standard for the tdc pipper size+/- so if you need it fixed before I can upload the file just copy the custom section out of the modded file and add it just above the --************** Planseta, sorry for the wait, I didn't have much time to look for the problem the last few days. UPDATE I have uploaded the new copy now that is based on the new version of the keybinds file, sorry I took so long, I have been a little busy lately and on top of that my client wouldn't realize there was an update yesterday but the mod should be fully up to date right now and the tdc pipper span+/- binding and the new axis should all be working.

Sorry I haven't had a chance to reply until now. I have not been able to figure out why it might not be working for you, on my end it is working with the current version of dcs world, are you sure your dcs world is up to date?

I have now updated the file in the op with the fix for the TDC Pipper Span Bug, thanks go to Lenop for his contribution.

I have reuploaded the new file with "Alternate Afterburner/Maximum On" since the forum problems seem to have affected files, I remember someone had posted about a problem with setting tdc/pipper size +/- keybinds to the throttle before the forum problems caused the loss of the last few posts, has anyone else experienced this issue?

Update Added those two and uploaded the new file, thanks for your suggestion.

As far as I know it shouldn't get rid of them unless a change is made to the specific file, however the most recent update did seem to replace it with a fresh copy so my recommendation would be to check your keybinds after any update to make sure they haven't disappeared and if they have disappeared to download a new copy of the file, after replacing the file your saved keybinds should also return. UPDATE: Also since I missed the fact that the default.lua file had been updated a few days ago I have uploaded a new version of my default.lua that just adds the same new keybinds to the new version of the file just in case there were any bugfixes made by the devs to it.

You replace the existing one, this is just the normal .lua with some things added at the top. After you replace the default.lua in joystick with this and launch the game you will find a bunch of new Keybinds for the MiG-21Bis that all begin with the word alternate, for the 3 way switches simply bind the up position and down position of your warthog's 3 way switch to the alternate up and down options for that switch and the middle will work as an extension of that without a further binding, for the 2 way switches just bind the up position on the hog's switch to the alternate up position binding and the down position will work without further binding.

I suppose I could also ask for a sticky from the LN guys so more people who need this can see it, I just don't really know what the etiquette around asking for stickies is here. Have any of you ever asked to have a thread stickied? Update: I sent a PM to Cobra847 and the thread is now stickied. Thank you Cobra847.

Not that I know of yet, though there are probably more tricks to get new and interesting functionality out of these that I don't know about yet, I am planning on looking through the defaul.lua of the other modules to see if any of them use any less common techniques. It works just like explained in the op, to elaborate using the specific example of 3 way flaps, go into your controls and find the bindings "Alternate Flaps Up" and "Alternate Flaps Down", then bind the up position on your 3 way switch to the flaps up and the down position on your 3 way switch to flaps down, both of these new bindings are set such that when the button they are bound to is released they set the switch to the middle position, what that means for you is that the 3 way switch in your aircraft will do exactly what you are doing with your warthog's 3 way switch, just like in DCS A-10C.

Sorry I haven't had a chance to respond to you until now, as long as the up position counts as a button, the middle position is nothing, and the down position is also a button you should be able to assign it just like anyone else who does not use target, the only difference should be the name of said button. If you mean to say all of your buttons are represented in game as keyboard keys it should work just as well as long as the above still applies, the only extra trouble would be that you need to put the file under "Eagle Dynamics\DCS World\Mods\aircraft\MiG-21BIS\Input\MiG-21\keyboard" rather than the joystick folder if you want to map things that dcs considers keyboard buttons to them.

New release is in the op, adds the suggestions from GregP. Thanks for the suggestions, I have written version of those into the new release that is in the op now, so far I have been keeping to the habit of ensuring the switches all correspond to the ways they move in the cockpit myself so have used that form for the newly added switches as well. I have been trying to get a binding like this working but have had no luck so far, I will need to sift through the binding of the other modules at some point and see if an example of this exists anywhere.

Sure, I will put that in the next release. It can be done for any module really, I actually already have one up for the f-86f here http://forums.eagle.ru/showthread.php?p=2145613 but since I don't fly the f-86f very often at the moment it only has the idle detent. Also I have been looking into the engine idle/off lever binding and it seems it isn't possible to get a useful setup for it with the currently available functions, when you click the lever it moves it up and then back down, which is able to move the throttle out of or into the off position, the binding by default will keep toggling the switch infinitely while the binding is being triggered and the only other way I have found to set it up makes the switch go up on one trigger and down on the next, so with that you would have to keep taking your throttle in and out of the idle detent twice every time you actually want to move the throttle either direction and on top of that since it isn't really designed to be used like that it can be a bit buggy too.

Edit:New upload is in the op, it adds "Alternate Weapon AA Mode - IR Missile"/"Alternate Weapon AA Mode - SAR Missile" "Alternate Radar On"/"Alternate Radar Off" "Alternate APU On" "Alternate Master Mode - Air" Thank you, adding those shortly. I haven't given up yet, I have one more idea I will try when I have some time today or tomorrow to get it working, stay tuned. No problem, I will add that in in the next upload.

That is odd, this {combos={{key='E',reformers={'LWin','LShift'}}},pressed=device_commands.RUDStop_lock,up=device_commands.RUDStop_lock,cockpit_device_id=devices.ENGINE_START_DEVICE,value_pressed=1.0,value_up=0.0,name='Throttle Start/Stop Position Toggle',category='Engine'}, is the line for that bind in the default.lua, it should only trigger the off position when first pressed if I am reading it right, are you binding both throttle detents to it or just one?

Thanks for the recommendation, added Emergency Afterburner, Air Start, and Nosegear Brake to the .lua in the op, already had landing lights except with taxi as the middle position rather than off as per Cyb0rg's suggestion.

Thanks, added my own rewrite of those binding, it is in the OP now. Thanks, I guess I never thought of it that way but it is cool to be the first modder on a new module. I believe {combos={{key='E',reformers={'LWin','LShift'}}},pressed=device_commands.RUDStop_lock,up=device_commands.RUDStop_lock,cockpit_device_id=devices.ENGINE_START_DEVICE,value_pressed=1.0,value_up=0.0,name='Throttle Start/Stop Position Toggle',category='Engine'}, this line from the default.lua may be referring to the keybind you are looking for in which case it should be in already under the Engine category with the name Throttle Start/Stop Position Toggle, however I do not know if this is the specific function you are referring to.

This {combos={{key='.'}},down=iCommandMissionResourcesManagement,name='Rearming and Refueling Window',category='General'}, is already in the .lua out of the box and is showing up in my mig-21bis keybinds under general as it should.