Gabreil

Here you go: https://www.amazon.co.uk/dp/B0BHHQLKPY?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_3

As stated above, we dont know what drives the dev's to decide what and what is not included, added, fixed etc. I guess we should just be pleased that most updates do contain CH47 changes.. and just have to go with what we're given. I still stand my point that its sometimes difficult to understand why fundamental features that used to work and now dont are further down the list. Hopefully in the next update

Who knows why it happend. I really should try Quaggles again. I did try before.. I'll have to try again

I do get it.. But a surely a broken flight insturment required for flying would surely prompt a bit of urgency. Perhaps i'm just plain wrong here

What was it supposed to fix? You'd have thought as a priority the CDU going blank when buttons are pressed might have been a priority for this update.. I guess not. I know there are lots of bugs and fixes for all aircraft etc that need to be done - but not fixing basic everyday and widely used functions (which up till recently worked) is i'm afraid a bit short sighted. Perhaps i'm missing something were quality of textures out weighs functionality?

@jonsky7 So i got things working adding your code.. Got the Hi & Lo on a rotary which work nicely. The values work nicely to move the Hi & Lo markers around the dial I added the following for the RAlt Test {pressed = device_commands.Button_1, up = device_commands.Button_1, value_pressed = 1, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT Test'), category = {_("RAD ALT")}}, That also works nicely for the test function ** I'll add this as happend to me when i added the changes to DCSWorld\Mods\aircraft\CH-47\Input\Keyboard & Joystick default.lua... After adding the lines above and starting DCS, when assigning a keybind/button i was asked to restart DCS when i id done that. What i didnt realise was it pretty much wiped all my other keybindings and joystick buttons - the ones located in Saved Games\DCCS\Config\Input\CH-47\Joystick & Keyboard. I recomemend backing these up before making the changes to It may or may not have been something i did wrong.. but dont take the chance!

@jonsky7 Awesome! I'll get those added in the morning. both will be bound to a rotary - so i doubt i'll need to make any changes. I did do a bit of a dive into this to see if i could do it.. but got hoplessly lost. As i was digging around i found the refrernce in the CH47 clickabledata.lua for the alt hi/lo - i think i got pre-occupied by the the args which if i recall were 1193,1194 and 1195.. I found the reference to APN_209. How did you determine these - or are they just relevant names? RAD ALT LO SET DOWN RAD ALT LO SET UP RAD ALT HI SET DOWN RAD ALT HI SET UP

@muniman69 Gotya. Thats a neat way of doing it. Thanks.

@JohnW71 yep. I was reading back through other posts and comments and someone commented that it seems rather strainge that the circuit breakers (which i very much doubt are used by many are all modelled - yet keybinds for functions we want to use are omitted. I just wish i had the skills to understand how to map functional items to keyboard/joystick actions.. One day no doubt we'll see all keybinds.

Where the Rad Alt knobs work in the cockpit with mouse clicks etc. Either i'm searching for the wrong keybind - tried alt, rad and all things like that.. I cant find a keybind. I'd like to map a rotary encoder to the Hi/Lo Rad Alt settings. Has anyone figured this out - I'm betting @jonsky7 has the answer!!

@muniman69 True, but unless you know what the button presses are after you press presets in the CDU. When you press presents the screen goes blank.!

I did try that. Not sure if it was something in the way i was doing it.. After selecting the radio, then freq preset followed by pressing tune it did not change on the MFD to the selected frequency. I did find an answer to do it via the CDU: CNI > Radio > Presets (when screen goes black) Type Freq you want (250) > Top Right Arrow > Top Left Arrow > CNI.

With the current CDU problem with it going blank on certain key presses - Its somewhat of a challenge to change the Frequencies for SRS. I want to set UHF 250.000. I Or, Is there a .lua that can be edited so it always powers on on a desired frequency - again in my case 250.000 Thanks as always.

@jonsky7 You're da man!! Absolute star. Really apprecaite the very quick response and fix. All woring

@jonsky7 So it looks like ED have done their own MFD bindings in the latest update. However, what they have done is create bindings for the Outer, Inner and Central MFDs - but not for both Pilot and Copilot.. The keybinds are now relative to the MFDs depending on which seat you're sitting in!! Kinda neat, but no no control of the Copilots MFD via a keyboard keybind if you use the likes of Streamdeck. Dunno if this is something you've already seen.. I guess the question are you or would you be able to work your magic to make all the MFD keybinds per MFD rather than by seat?

Yeah a warning would be good.. At least you could better prepare and make some notes etc.. and @Tom Kazansky you are right, its not the best method.. but till now something was better than nothing! I started rebinding earlier.. The hardest part is remembering if you used On, Off or on/off toggle and such like. Just to add - I've now got Quaggles all working.. I took onboard the comments about overwriting. Thanks for pointing that out.

I've just read an article on the helios website regarding the helios profile stopping working after the update. It seems to indicate that the reason things have stopped working is due to the addtion of new keybinds and shifting keybinds id's. From what i can deduce - e.g. if Your button was bound to a DCS CH47 command which for example had an ID of 100, the update now makes ID 100 something else... hence saved joystick/keyboard .lua files now not working. Thats how i understand it... i may be wrong.

@Rudel_chw Thanks. Your image showing the list of joysticks and their ID numbers is exactly what i have for the CH47. None of the controllers have changed. As i mentioned the method i've used for the past couple of years has worked flawlessly, so i am quite happy with the way ive tried to restore saved files. This is directly related to the CH47 - and i think the addition of extra keybinds is the most likely cause. I now have lots of Red ! in my config setup which were not there prior to the update.

Before i did the update to the latest version, as always, i did a full backup of DCS World folder and Saved Games folder. Normally, after the update i copy/paste the backup input folders back into DCS which restores all the keybinds for my various controllers. I've done this numerous times in the past and its always worked. This time, doing the same thing has resulted in almost nothing working. A few keybinds work but for the most, when looking in DCS Contorller configs, there are no keybinds listed against the device. Has something fundamentally changed with the way the controllers now work with the associated joystick and keyboard .lua files? For the CH47, its pretty much put me back to square one.. with hours and hours of configuration down the drain. I'd be keen to hear if others have experiend this and if its had the same impact as it has for me.. and perhaps if you've managed to get around this? For reference i've replaced from backups: DCS\mods\aircraft\CH47\Inputs (which normally restores all my saved keybinds) Saved Games\config\inputs\CH47 Saved Games\DCS\InputCommands\CH47 Just to add... Even if ED could give a brief explanation on whats changed and if its even possible to re-import backups would be helpful.

I've not updated as yet.. So, no idea if the install has updated doucmenation embedded. @BIGNEWY is there documentation to explain the new features please?

So looking forward to seeing this in DCS. I grew up watching the BO105 (civilan version) doing work on Lighthouses.. The sound it makes and the sleek look is amazing... and just thinking about it sends tingles down my spine... Keep up the great work

Thanks... Finally got it working. Having never tried it before, even with the keybinds the indicator did not show up when in the pilots seat. I flipped to the Gunner seat and did the keybings that then worked. Back in the pilots seat the keybinds then worked. It as if something needed to be written to a .lua file when in the gunner seat to then work in the pilot seat. But all good now... Glad its working as its pretty awesome..

Does the Gazelle Minigun variant have AI for the Mingun?

To be fair, once you learn the cockpit.. which with its simpisity is quite quick, the english labels are not really needed. Helpful for a couple of days when learning.

I finally figured it out. When changes are made - they are saved in the options.lua (Saved Games\DCS\Config). I forgot that i am using Baileys app to run different DCS.exe files which i use for when at the PC and connecting remotely - each of which have a different options.lua associated. So, when i was making changes in DCS, they were not saving.. A quick edit of the option.lua for the .exe files and all working now. @Gladius I'm using this mod to convert to english cockpit https://www.digitalcombatsimulator.com/en/files/1956481/