Gabreil

I guess we will have to wait. I think what is most frustrating is where we know the CDU is not fully functional, it was at least useable before a couple of updates ago.. I.e not having the screens go blank. I think in most cases, just having it back to the way it was would be good enough for now The other comment I'll make and does echo what Blaine has said. New functions and features are great and shows advancement, but without any supporting documentation or some notes is not especially useful. Like the hover page on the MFD's. Great addition but leaving the customer to figure it out is not great. For someone in the dev team who knows the how, what, when, where and why - it would only take 10-15mins to write enough to explain. I don't think that's too much to be asking for... ?

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