Bravo020

I'm not using Midikey2, I am using Bome Midi Translator Pro, I bought this quite some time ago, taking a look at their website, it is available for €59 (https://www.bome.com/products/miditranslator) There is a trial version that only runs for max of 20mins before it has to be restarted, certainly a way to figure out if you want to proceed with it or not. Now, it is a programming interface, and not always the most intuitive if I'm totally honest, but once you get over that hurdle, and understand the nuances of the interface, the programming capabilities I've found it very useful. Programming it takes a long time for use with DCS, because there are just so many key combos to handle and you need to think about how you'd like the layout to be defined and how the buttons should behave etc. But I've found it very useful with DCS so far, and you can make your own overlays or buy overlays that you can customise etc. Of course BOME doesn't just have to handle this midi device, and will handle any midi device, and you can create your own profiles for different games, or s/w. I use mine with both Photoshop and Davinci Resolve for example.

No, the patch is available today. https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.9.8.1214/

Just to share something that I've been working on. I'm a big fan of the XTouch Mini MIDI controller, and I've been leveraging it in conjunction with Bome MIDI Translator Pro, this s/w is a programmable interface for MIDI controllers. Cut a long story short, it allows me to map the MIDI controller to keyboard mappings for use with DCS. The following are a couple of layers that I've been working on, and I hope to get this wrapped up sometime soon. The goal is to get most of the functionality available and in combination with HOTAS bindings avoid using the keyboard altogether. The idea is that the left most 2 buttons (1 and 9) are reserved. Button 1 can shift between 3 modes, and can either be accessed via the button itself (Off, On, Blinking), and a different set of mappings are available for each mode. The behaviour can also be performed by a HOTAS binding as well. Also with this setup, you also have 2 layers, A and B and again you can switch between shift modes and layers and the buttons lights are remembered between each layer and mode. There are 8 encoders (dials) and those are assigned to different tasks, and the encoders can also be clicked to mimic push/hold/release/toggle etc. Also for some setups I've also added additional buttons to select other systems, for example one button can switch between TACACS and UHF, and another can switch between lights etc. Further programming is used for some situations, for example, 3 buttons are used for SLATS/FLAPS, and if one option is selected then the others are deactivated and vice versa. Button 9 is dedicated to integrating with the Jester UI, open it, navigate via encoder 1, select items, etc., and again this is common across any of the shift modes and layers selected. Anyway, something that I've been looking at recently and thought I'd share it with the folks here, and always keen to hear of anyone else using MIDI controllers with DCS. Thanks.

Hi, I know that we have individual bindings available for each of the different TACAN Modes via the TACAN Control Panel (Right Console - Front) TACAN Mode - A/A Receive TACAN Mode - A/A T/R TACAN Mode - Off TACAN Mode - Receive Only TACAN Mode - T/R However, I was wondering if we are also going to get CW, CCW and Next bindings. As it is easier to bind this to a dial/encoder than individually. Thanks.

Hi, Just noticed that the Radio Command Light Brightness dial operates in reverse. Radio Command Light Brightness - [Dec] - Increases the brightness Radio Command Light Brightness - [Inc] - Decreases the brightness. Regards,

The issue is that the default mapping for this entry is invalid. For whatever reason the default is setup with LShift as the key, and P as the modifier, which is the cause of the issue. You can clear the binding, and that will resolve the issue, but if you return to default settings it will reappear, again because the default mapping is invalid. Once the binding has been cleared, and you have assigned a new mapping to the key. If you then save that profile layout, you can then modify the file and add the following to your lua profile file. Obviously, ensure that the hash value matches your own value, and then include the ["removed"] section shown below, this will remove the incorrect binding. ["d3026pnilu3026cd7vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "/", ["reformers"] = { [1] = "RCtrl", }, }, }, ["name"] = "First Person Pilot Body - [Toggle]", ["removed"] = { [1] = { ["key"] = "LShift", ["reformers"] = { [1] = "P", }, }, }, }, In this way you can still load a default setup and then import your updated profile to remove/add the correct binding you want to use. Hope this helps until such time that HB fix this mapping.

Did you do anything to get it to work? None of mine work yet... Complete silence from ED on this issue isn't very helpful either.

Same issue as well. Yet another terrible patch release from ED without sufficient QA. These are not isolated issues, this is poor test planning and execution.

OMG! What a state this update has caused. Sheesh, and this was after additional testing....damn...this is an absolute joke. And all my existing FC aircraft are now unauthorized, and that is with the DCS folder excluded from my AV s/w..... Thanks ED, stellar performance on this release!

I had the same issue happen last week. My AV decided to quarantine a jester dll, upon restoring the quarantined file and adding an exception to the file I had no issues with running the F4 again. I've heard that this can sometimes happen, and was the first time in a very long time that I've had this issue. It happens, sometimes AV s/w generates false positives. It's your own call as to what to do, trust or not trust, or see if anything else unusual starts happening. While no s/w company intends to ship infected s/w, I've seen it happen numerous times over the past 30+ years that I've been working in the s/w industry. From PC magazine publishers releasing infected disks to their readers, to s/w getting hacked via their supply chain (Solarwinds style). Then again even with the vulnerability of Intel chips with Meltdown and Spectre, didn't stop anyone from turning on their PCs... But in a nutshell, looks like it is purely a false positive, I've seen no unexpected behaviour on my PC, and I'm reasonably confident that everything is fine, but it isn't ideal when you get false positives, but I'd rather get false positives than missed alerts imho.

Silly question, but I couldn't find anywhere to make key bindings for the Radar Altimeter, or for the Standby Attitude Indicator (Cage/Uncage). Are there any? Thanks.

For what it is worth, the latest version of Bome Midi Translator Pro (BMTP) version 1.9.1 includes a very useful feature called "Perform", this allows for multiple actions to be performed. For example, with the F4-E and you want to perform an Engine Ignition, you would normally expect to press and hold the key-binding, for example RAlt + Home. The way that I have this defined in BMTP is a single press of a button acts like a toggle, press/release once within 1 second and the button LED is set to ON and triggers 2 actions, RAlt Key Down, Home Key Down. Then if I press/release the same button again, the LED is OFF, and it triggers both RAlt Released and Home Released. I added a further option to the same button, in that if I press and hold the button > 1sec, then the button LED Flashes instead and sends an Engine Idle Detent instead using RAlt + End, this being just a press and release of the combo rather than an hold down. So one button and 3 possible actions. If the button LED is Flashing, a single press of the button will return it to LED off, but no keystroke(s) are sent. Of course, you could also just setup a single button to send a sequence of keystrokes when it is pressed, and another set of keystrokes on release. But you can program the buttons as you see fit for the purpose you want. What is quite nice also with this setup on the X-Touch Mini, is that it is quite cheap, the BMTP s/w is also very reasonably priced given the functionality that it offers. You can get overlays to write your mappings down etc. So you would think that with just 16 buttons that there is a low limit as to what you can do. Not really, there is a Layer A (16 buttons, 8 encoders (each with a click), same again if you switch to Layer B. But what is also quite cool, is that I have the first button setup so that 1) LED off = Shift State 0. 2) LED on = Shift State 1, 3) LED Blinking = Shift State 2. So I can press the first button twice rapidly and if goes to Switch State 1, press it 3 times rapidly and it goes to Switch State 2, press it once and it goes to Switch State 0. That means that on LayerA with the 3 different states for Button 1, all the buttons in each different state can have a different purpose. 15 buttons, 8 encoders, 8 push encoders: Multiplied by 3 different States, Multiplied by 2 Layers = 90 buttons, 48 encoders, 48 push encoders at a minimum. I say a minimum because some buttons could have 2 states (Press/Release), some could have 3 states (LED ON, LED OFF, LED Blinking), or more. I plan to make a vanilla template which includes these capabilities and put together some documentation on how this all comes together, hopefully it will be of use for those that are trying to use their midi controllers with DCS. Well I got round to making a template for an X-Touch Mini, in combination with Bome Midi Translator Pro ver 1.9.1 You will need version 1.9.1 of BMTP as it leverages functionality that is only present in that version. Hopefully it should be easy enough to follow. But in a nutshell. The following should help. Use the Layer buttons to switch between Layer A or Layer B. Pressing button 1 (once) will set the shift state to 0 for whichever layer is active. Pressing Button 1 (twice) with each press within 500ms, will set the shift state to 1. for the active layer. If you switch layers then the shift state is saved for the previous layer, so you can have different shift states for layer A and B. Pressing Button 1 (three times) with each press within 500ms, will set the shift state to 2 for the active layer. Again, each layer can have its own different shift state. Shift States are visible based on the LED of Button 1, (OFF = Switch State 0, ON = Switch State 1, BLINK = Switch State 2). Buttons 2 - 16 can be in 3 different states. OFF, ON or BLINK. All these buttons have been setup with the following behaviour. Press any of these 15 buttons once and release, and the LED goes to ON. A keystroke or set of keystrokes can then be assigned to that function. This can be a keystroke or combination, or could be a combination of keys held down. The choice is up to you on how you want the button to behave. Press any of these 15 buttons once more and release, and the LED goes to OFF. Again a keystroke can be assigned to this behaviour as well. This could be a different set of keystrokes, or it could be setup to release the keys previously held down. Again, the choice is yours. Finally, holding any of these 15 buttons pressed for 1second or longer, changes the LED state to BLINK. No keystrokes associated for LED ON or LED OFF are sent, but instead a different keystroke combination can be sent for this 3rd state. Whatever the state of the buttons are in when switching Layers are retained, and the LED state is restored upon returning to the previous layer. Of course, you'll need to make sure that keys are not kept in a pressed down state if that is not the behaviour that you want. For example, if on Layer A you assigned button X to perform a Ralt+Home (down) when it is in an ON state. If that button is left ON, and you switch to another layer, the button keypress is still active..So take care on what you want etc. I guess, what would be nice, but I haven't implemented yet are things like. Use a joystick pinkie switch to change between the shift states, or use another button to switch between Layer A and Layer B etc. Final note is that the encoders are also supported, and again depending on the shift state of button 1, they also can have different functions. Although the LED state of the encoders isn't retained across different shift states unlike the buttons. Anyway, have fun for those that have a X-Touch mini and Bome 1.9.1 DCS_BMTP_Template_v0.bmtp

I had the pleasure of having to use punched cards around that time.. So thankful that I don't have to deal with them anymore....

Thanks, looks like HeatblurJester.dll is now getting flagged as a Trojan....

Hi, I have had no issues previously with running DCS and access to my DLC. Today, however I get the following message when starting DCS. Authorization is valid for 2d 23h 59m The following DLCs are not authorized and will be disabled: F-4E-45MC How to resolve this. Thanks.