LeCuvier

I've been away from the A-1ßC-II for a long time. When the laser-uided rockets became available they quickly became my favourite weapon against IFV's, APC's, Shilkas and any other lightly armoured vehicles. They were highly effective and killed even the BMP-3 mostly with a single strike. Today I decided to refresh my skills with the hog, and I find that even the BMP-2 often requires multiple hits in order to disable it. It seems that the armour-piercing capabilöity of the M-282L has been downgraded. Now I'm wondering whether the original lethality was unrealistically hihj and has been corrected downward, or the current "weakness" is an "accident". Can someone with knowledge clarify please? Edit: I did some more testing, using M-151L rockets against the same kind of targets. To my surprise, I find that the M-151L repeatably kills a BMP-3 with 2 hits. It does as well as a M-282L. This does not look right to me. The BMP-3 has fairly solid armour I believe, and it should require armour-piercing wareheads for a kill. The way it looks to me, there is no significant difference between the two types of rockets in terms of lethality for IFV's and that does not seem right.

That's awful! Have you tried "Rescan Devices"? Thankfully the "Options" screens have been changed to take advantage of available physical screen size. Also, I have re-started the game 3 times and the devices were always in the same order. I will continue watching if the order remains stable.

The Ka-50 has this feature. I can direct any of my wingmen to attack my currently locked target. Only issue is, they sometimes try to attack an air defense target with gun or rockets (although they carry Vikhr ATGM's) and that gets them killed. So it would be good to have a command like "attack my target with Vikhr!"

In my experience the P-51 AI can take an incredible number of hits and continue flying. And even when their engine is dead they continue fly over incredible distance. The Mosquito on the other hand is very easy to kill. It's a huge targwet and it takes only a few hits to set it on fire.

No problem thanks to OvGME

This is a wish list, and the wish of the OP is a single-press Eject command to be provided by ED. 3rd party programs are just work-arounds for missing functionality; and whether they are "very useful solutions ... respecting everyone's needs" is debatable.

It's funny how many people are trying to tell us that our "wishes" are wrong. Maybe there should be a dedicated "Anti-Wishlist" subforum for them? Personally I have added the single-press command decribed above into the UI Layer "default.lua" and bound it to the right Window key on my keyboard. And should I accidentally press that key I shall feel nor pain nor regret - it's a game!

1. I'm referring to the file "default.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" (K being the Drive). 2. The best place for adding key commands is just below these lines at the top of the file so you can easily find your edits. local cockpit = folder.."../../../Cockpit/Scripts/" dofile(cockpit.."devices.lua") dofile(cockpit.."command_defs.lua") local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") join(res.keyCommands,{ 3. Make sure you don't miss any of the commas, parentheses, curly braces. Syntax errors may invalidate the entire file 4. Use a program editor like Notepad++ (no office program!)

Unless you choose to go down the "wishlist" path (good luck!), there are two solutions: 1. Use TARGET Thrustmaster's software (which I have stopped using so I cannot provide details but it's not difficult) 2. Edit the "default.lua" adding these two lines of code: {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, I bind (Pitch Autopilot) Altitude Hold to the upper position (PATH) and Attitude Hold to the down position (ALT). The middle position switches the Autopilot to OFF, no binding required. Link to tutorial for editing this file: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

Good point!

The German grammar hasn't changed, but (hallo-wach!) we had a spelling reform (Rechtschreibreform) in 1996.

I have never seen the triple command as a big problem, but there is a simple LUA edit to execute the underlying command "iCommandPlaneEject" 3 times with a single button press. To achieve this, I added the following line of code {down = iCommandPlaneEject, pressed = iCommandPlaneEject, up = iCommandPlaneEject, name = _('Eject (press once)'), category = _('Systems')}, into the file "default.lua" in the folder "K:\Eagle Dynamics\DCS World OpenBeta\Config\Input\UiLayer\keyboard". This creates the new keyboard command "Eject (press once)" in the UI Layer. This will make the command available for all modules that use the command ""iCommandPlaneEject" with a single binding. The remaining challenge is to find a key combination not yet used for any command, but the new 2.8 functionality helps with that. You could also make the command available for game controllers by adding it into the "default.lua" under "...\joystick".

Changes/additions in "default.lua" do not affect Integrity Check.

You can probably adjust the "speed" for all or most of these bindings by modifying parameters in the file "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick". Example HMCS knob: There are two lines of code for this: { pressed = hmcs_commands.IntKnob_ITER, cockpit_device_id = devices.HMCS, value_pressed = -0.3, name = _('HMCS SYMBOLOGY INT Knob - CCW/Decrease'), category = {_('Left Auxiliary Console')}}, { pressed = hmcs_commands.IntKnob_ITER, cockpit_device_id = devices.HMCS, value_pressed = 0.3, name = _('HMCS SYMBOLOGY INT Knob - CW/Increase'), category = {_('Left Auxiliary Console')}}, The parameters following "value_pressed" determines the rotation speed of the knob. The values -0.3/0.3 work fine for rotary encoders but are fast for pushbutton. If you reduce them to -0.05/0.05 you will find they work better for pushbuttons. For editing this file use the free Notepad++. Also, you need to make a backup copy of the modified file because Update or Repair will restore the original file. To get a better understanding of what you can do with the "default.lua" files, go to https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu and download the tutorial document.

Good information, thanks!

Seems a bit excessive; but if that's how the beast work I'll have to adjust. Glad to see it's not a problem with my joystick button! I had reported a sporadic issue some time ago, where a single press of the Weapon Release button fired two Vikhr missiles. That certainly got fixed!

If you want to use a different multi-monitor set-up for your upcoming session you have to 1. start the game 2. look up the "Options" parameters you want to use 3. Enter these options in Options/System and hit "OK" 4. wait for the game to shut down and re-load This is a cumbersome and time-consuming process. It should be possible to create "presets" (sets of parameters for different configuations) and chose from them before the game actually loads. This is probably wishful thinking, so I created a solution for myself using a MS Access database with some VBA programming. The solution imports the "Options.lua" and enters all lines into a table. Then it parses the text lines and extracts labels and values into separate lines. Going forward, I can now select from a short list of predefined settings and re-export the changed data to "Options.lua". This takes only a few seconds. Now I can start DCS World and it will load with the updated Option values right away. At this point in time, the presets include only 4 option items: Aspect Ratio, Sreen Height, Screen Width and the name of the multi-monitor setup file. These are the 4 values that require the time-consuming process. The design is such that further options could be easily added. This was an interesting project for me, but probably not useful for others because few people are comfortable with a database. Would be nice if ED could come up with an integrated solution to make this process quick and painless. I attach a screenshot of one of my forms for illustration.

You don't specify for what purpose you want to "load" the .diff.lua files. These files capture the the bindings of commands to buttons/keeys/knobs on game controllers or keyboard that you have added, removed, or changed (like curves). So I could guess somebody provided such files and you want to copy them into the right folder. But guessing is not good enough to answer a question that doesn't come with sufficient background. Generally speaking though, a file for keyboard bindings should go to "...\keyboard\"; but a file for a game controller should go to "...\joystick\".

These command bindings are already available. Look for "Mode Knob - CCW" and "Mode Knob - CW"!

Not sure if that would help, but I was able to create two bindings for pushbutton commands that rotate the knob and the dial with the needle CW and CCW respectively.

I have added several options in my "default.lua", for use with either a maintained ON/OFF switch, a set of 3 pushbuttons or a ON1-OFF-ON2 switch with spring return to OFF. I use the latter with an UP/DOWN toggle on my DSD button box. It would also work with a 3-position switch like the speedbrake switch on the Warthog throttle. This is achived by adding 2 lines of code: {down = 3006, up = 3007,cockpit_device_id = devices.CPT_MECH, value_down = 0.0, value_up = 0.0, name = _('Canopy CLOSE/HOLD'), category = _('Systems')}, {down = 3007, up = 3007, cockpit_device_id = 39, value_down = 1.0, value_up = 0.0, name = _('Canopy OPEN/HOLD'), category = _('Systems')},

Rather than trying to figure out what's going wrong and giving piecemeal advice, I suggest you download and read the tutorial under this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

I tried to send you my file per PM, but it says that you cannot receive messages. Why would that be? Can you try to send me a PM?

ED has added a lot of lines under "special for joystick", but the two items you mention are still not there. Historically, ED has been very slow adding such bindings although these are very low-hanging fruit. For the fuel dump switch I have added this line to "default.lua": {down = fuel_commands.DumpSw, up = fuel_commands.DumpSw, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Fuel Dump Switch 2-Pos ON/OFF'), category = {_('Left Console'), _('Fuel Control Panel')}},

That's a very error-prone process in my experience. Copy/paste is much safer.