LeCuvier

@v2tec: I see 4 lighting control knobs in the cockpit. I could probably create bindings for axis commands by adding 4 lines to "default.lua". Would you be willing to a little LUA editing (just copying and pasting 4 lines of code)? If you want to wait for ED doing this: good luck!

You cannot create new "iCommand..." that way. A working solution for the TGP ON/OFF 2-position switch is in the thread with my tutorial document in this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4691602_menu (4th LUA line)

Not genius, just learning from others and a bit of reverse engineering. I documented what I learned; the document is in this post: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

You need to try what works best for yourself. Your encoders may not have the same spec as mine. You can set up a series of test versions in "default.lua" and then try out in an instant action which works best. Example with just 2 versions for HDG SET: {pressed = ehsi_commands.RightKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.03, name = _('CRS Set / Brightness Control Knob - CCW/Decrease Fast1'), category = {_('Instrument Panel')}}, {pressed = ehsi_commands.RightKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.03, name = _('CRS Set / Brightness Control Knob - CW/Increase Fast1'), category = {_('Instrument Panel')}}, {pressed = ehsi_commands.RightKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.06, name = _('CRS Set / Brightness Control Knob - CCW/Decrease Fast2'), category = {_('Instrument Panel')}}, {pressed = ehsi_commands.RightKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.06, name = _('CRS Set / Brightness Control Knob - CW/Increase Fast2'), category = {_('Instrument Panel')}}, You can set it up with versions for all values between 0.1 and 1.0, so you don't need to restart the game for each test. Just make sure every version has a distinct name. The 0.3 seemed slow for me, and the 0.6 a bit fast. So maybe 0.5 would be right, but it's subjective. I don't use these as I have only two rotary encoders on my button box and they are taken for other commands.

I sent it to you via PM.

I had a crazy thought: did you manually edit the folder name of "l10n"? In case you did, there is potential for confusion. The folder name in file explorer looks like a capital "I" in "India" but it's actually an "l" like in "lake". But if you did a repair, that would have been fixed I believe.

There is a way. I understand you want to use a rotary encoder on your keyboard. Therefore you need to modify the file "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard". It has 2 relevant lines of code: {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = 0.3, name = _('ICP HUD Symbology Intensity Knob - Up/Increase'), category = {_('Instrument Panel'), _('ICP')}}, {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = -0.3, name = _('ICP HUD Symbology Intensity Knob - Down/Decrease'), category = {_('Instrument Panel'), _('ICP')}}, The value of the parameter "value_pressed" determines how fast the knob in the cockpit rotates. I recommend you leave the original lines alone and add the two lines below for a "fast" version of the command: {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = 1.0, name = _('ICP HUD Symbology Intensity Knob - Up/Increase Fast'), category = {_('Instrument Panel'), _('ICP')}}, {pressed = ufc_commands.SYM_Knob_ITER, cockpit_device_id = devices.UFC, value_pressed = -1.0, name = _('ICP HUD Symbology Intensity Knob - Down/Decrease Fast'), category = {_('Instrument Panel'), _('ICP')}}, Alternatively, you could change the values of the original lines. If you do that you must still change the name so it's different from that of the original command. This is because the command also exists in the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick". So, if you change just the values and not the names, the Options/Controls screen would show you duplicate lines in orange font, because you have different commands with the same name. And you would not know which lines to bind. And don't forget: Any update or repair will restore the original file. So you need to back up your modified file.

In the context of your problem, only the file under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES" is relevant. Most of the aircraft modules do have the I10n folder structure, but the "messages.mo" files are mostly empty. Don't worry about these!

Yes, as I said, the Spit as well as the Mosquito and P-47 use the same localization mechanism. That mechanism is active even if you use English. Did you verify that you have the file "input.mo" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES", file size 218 KB?

You need to open a ticket with the support desk!

I tried in OB ST, latest version (2.8.4.39313) and it displays correctly (see attached screenshot). Are you using the latest OB version? I suppose you are not using a localized version like German or French? Edit: as far as I know the conversion from internal identifiers to command names is based on the file "input.mo" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES", file size 218 KB. Do you have that file? If it's the same bug as we had some time ago, you would see the same problem with the Spit. P-47 and Mosquito. They all use this strange structure to facilitate localization.

I do not see this in OB MT. In which version do you see this? It looks like a bug we had some time ago. It's related to the localization, the bug presents the internal command identifiers rather than the localized command names.

I have bound this switch to the Autopilot switch on my TM WH throttle which is a maintained 3-position ON1-OFF-ON2 switch. I have always had this switch in its center position (which means "medium") at mission start, and never switched it to anything else. And I did not get the double-launch at all. Now I get it more often than not. I checked a bit more and found that the cockpit at mission start (hot start) shows the switch in the DOWN (= short burst) position. I suspect that the software does not reliably scan the switch positions, and that there is some random behaviour. So sometimes it ignores the OFF (=Center) state of my switch and fires a single Vikhr, and sometimes it does update the switch state and fires 2. During my last mission last night I did not get the double launch at all! Conclusion: I will make sure going forward that I have the switch in the down position when using the Vikhr. And I will update this post based on the result. Thanks for your input!

Since yesterday's update I experience this issue. Each time I press the Weapon Release button for the Vikhr ATGM, the Black Shark launches 2 Vikhr missiles, which depletes my weapon payload very quickly. I have seen this same behaviour a long time ago. It was fixed I think when the long button-press was introduced. Track attached. Edit: I did some more testing and sometimes I manage to shoot just one Vikhr at a time. It seems to depend on the duration of the button press. Ka-50_3 Vikhr Double Launch.trk

So if I don't want to use the script, I have to put the sound file into the mission folder in order to open it from the ME. And when the ME has swallowed it into the .MIZ, I can delete the file from the folder. A weird process! I can live with a weird process but at least ED should document it in the user guide! Thank you so much!

I found that the .WAV/.OGG files used by the trigger actions are stored inside the .MIZ files. However, I see no clear way for assigning a sound file that's packaged into the .MIZ file to a trigger action. With the "Open" function I can only select files that are directly accessible in a folder, I cannot select a file that's in a .MIZ file. The User Guide is no help in this. Can someone tell me what the right process is please?

It operates exactly as described in the manual. The UP position (Drift C/O) is maintained while the DOWN position (WARN RESET) spring-returns to the center position (NORM). For correct (realistic) operation (with the 3-position commands) you need to bind this to a 3-position switch where one of the 2 ON positions is maintained and the other is momentary, i.e., it spring-returns to the Center = OFF position. The "ENG OPER" switches on the TM Warthog throttle work that way. The MOTOR position is maintained and the IGN position is momentary. If you don't have such a switch, I guess the best solution is to bind the commands "ICP DRIFT CUTOUT/WARN RESET Switch - Down" and "ICP DRIFT CUTOUT/WARN RESET Switch - Up" to a pair of pushbuttons or an equivalent 3-position rocker switch with spring return to center from bot ON positions. This will allow you to cycle through the 3 positions in an almost realistic manner.

I use OvGME to avoid this nuisance. Before allowing an update I back out all mods and move them back in after the update. Without that tool I would go nuts as I have lots of modified LUA files. Unfortunately the developer no longer supports the software and it has disappeared from Github, but it works without problems and I kept a copy of the install.

I agree. Most bugs are nasty but this one is cute. And because it's so nice ED will probably fix it quickly.

It's already reported as a bug. See this thread: https://forum.dcs.world/topic/321349-skhval-wrong-texture-with-mt/#elControls_5172779_menu

I have always seen the Shkval display as monochrome, sometimes greenish, sometimes greyish. Under MT now it displays full color. While I'm not complaining about this luxury I suspect it's not meant to be this nice. Can an expert comment please? I attach a screenshot which I took from an exported view for better quality. The display on the main monitor shows the same colours.

I use the left throttle on my TMWH throttle. Works fine. If you have a game controller (e.g. button box) with rotary encoders, try one of these. They produce extremely short input pulses and usually work well with over-sensitive key inputs.

I have to apologize: The reason why I have these axis commands is that I have added them to "default.lua". The stock file does not have them, and the reason I have added them a long time ago is that the stock file didn't include them at the time. And I doubt that it ever did. If you want to wait for ED to make the addition you might need a huge amount of patience. I suspect it's a low priority because few people have axis input devices to spare. If you want to make the addition, here are the lines of LUA code i added: {action = 3001, cockpit_device_id = 49, name = _('Engine Instruments Lights Axis')}, {action = 3002, cockpit_device_id = 49, name = _('Flight Instruments Lights Axis')}, {action = 3003, cockpit_device_id = 49, name = _('Auxiliary Instruments Lights Axis')}, {action = 3005, cockpit_device_id = 49, name = _('Flood Light Axis')}, {action = 3006, cockpit_device_id = 49, name = _('Console Light Axis')}, {action = 3011, cockpit_device_id = 54, name = _('UHF Radio Volume Axis')}, {action = 3005, cockpit_device_id = 55, name = _('VHF AM Radio Volume Axis')}, {action = 3005, cockpit_device_id = 56, name = _('VHF FM Radio Volume Axis')}, {action = 3013, cockpit_device_id = 38, name = _('Yaw Trim Knob Axis')}, This post is obviously not a solution, just a work-around.

I checked in Open Beta and all the axis command lines are there as far as I can see. See attached screen shot. These are the same lines as in the stable release which has not changed for a long time. What lines are you missing? Please post a screen shot of the page!

I have my HMD knob bound to a rotary encoder on my button box, which works very well. Wanted to see whether the problem reported here is a general issue. So I bound the HMD Axis to the slider on my TM WH throttle. Result: No issue here. I can set the HMD over the full range from OFF to 100%, and it does not jump back to a different position.