Cerppo

Hello, CH47 pilots can now This mean that when you press 1 or 2 , the CDU switches accordingly which is "perfect" with the strange way of binding "Active CDU" keys only Choosing PLT or CPLT will work (and override by seat position ) It requires to update your DCS Bios with DCS-BIOS Nightly 2025-09-21 ( or later)

I already preordered it . but i don't expect the cdu information to be available in DcsBios at launch.

Just in case someone is also having issue when the ch47f Linked lighting is ticked The Dim / Brt are doing nothing in the aircraft -> should change the screen brightness , but do not work. So, i provided a way to dim the physical CDU by linking it to the Key backlight information - if you check the CH47F linked ... Everything is controlled by the cdu knobs . You start the aircraft , fine, then the program receives the position of the knob -> 0 by default . This set all brightness level to 0 ! Just turn the knob and it should react. if you want it to behave like in DCS , leave the CH47 checkbox unticked. And i you don't want light management at all, tick the Global option that says that

you have the wrong dcs bios version , it's written in the README , you need to DL the latest build , not the 0.8.4 nightly build required for CH-47F here too For CH-47F: Download nightly build (or later than 0.8.4)

Just released https://github.com/landre-cerp/WWCduDcsBiosBridge/releases if it crashes or do not start it's not related to the menu key, you should have something misconfigured.

Install latest, as it is in the code of the version you are using. ( the menu handler was not removed after aircraft selection in older versions ) Latest removed this behavior ( and the menu handler is disabled after aircraft is selected ) By the way , i'm just about to release a new version to get rid off console and command line options. This should be easier for new users. (forces dcsbios config before start , etc .. )

Thanks for pointing this out. I will certainly remove this default behavior it's useless. Edit : Removed in 1.5 and later.

1st be sure to use the latest verstion ( 1.4 beta at this time , but here are the releases https://github.com/landre-cerp/WWCduDcsBiosBridge/releases ) and the readme instructions. https://github.com/landre-cerp/WWCduDcsBiosBridge/blob/main/README.md Common mistakes: Check DcsBiosLocationPath uses \\ not \ "c:\\Users ...." Note that i changes the .Exe name to WWCdu instaed of MCdu . i will update the Readme accordingly.

Hi, there's another thread that was started as a question "Can we use Winwing MCDU with DCS". But now that we know that it works, and not only for the A320 Mcdu, start this post to List possible solutions @Kurisu rust Implementation [ Tested with PFP3N , ?] https://github.com/Kurisu003/UWACS Not sure of plane support. and my implementation (c#) [ Tested with PFP7 , MCDU , PFP3N ] https://github.com/landre-cerp/WWCduDcsBiosBridge/releases Works with A10C CH-47F ( pilot and copilot if you have 2 CDU) AH64D FA18C F15E Have a nice flight in your preferred DCS Aircraft

I just pushed a 1.3 beta https://github.com/landre-cerp/McduDcsBiosBridge/releases Now handles 2 cdu for ch47 PLT and CPLT, So if you own 2 wwing devices, you can plug them both and choose on each if it's supposed to display PLT ou CPLT cdu. Not sure how to handle this correctly with actual DCS binding way ... I suggest binding the PLT and use CPLT display , but change CPLT with Aircraft click. My other idea was to double bind "Active" on both the MCDU / PFP7 and switch position with 1 & 2 ( not tested ) . Previous version linked the Screen Brightness to the Knob ( it's not working this way in the aircraft, but as it seems bug , there's no other way to adjust screen brightness ). It's now unlinked by defaut. If you want to link it back use -ch47lbg options launching the program. This also fxes A10C missing option parsing in 1.2 ...

Working on this This needs to always use them at the same "place" ( because of DCS bindings one as PLT and the other as CPLT keys . ) , but seems to work. Need more testing before release. DCS bindings are strange as you can only bind the Active CDU ( mean the one corresponding to the place you're sited at )

Fixed . https://github.com/landre-cerp/McduDcsBiosBridge/releases Cdu knobs on center panel controls the Backlight of the screen / leds / keys . ** Looks like in the Aircraft , Backlight is not controlled by the Rocker BRT DIM either ? so i decided to link it to the knob ** . Should it be corrected one day , i'll separate them .

That's something i didn't pay attention to, but will look at it . Thanks for the report. by the way , feel free to use "issues" to report what you think is wrong , or improvments https://github.com/landre-cerp/McduDcsBiosBridge/issues

Hello, here's the new build https://github.com/landre-cerp/McduDcsBiosBridge/releases Note the breaking change in the config.json file. ( naming convention fix)

I'll push a new version next week.

Nope , not coded. you mean this ? I'll take a look if i can add it easily

Edit : https://github.com/landre-cerp/McduDcsBiosBridge/releases Any feedback / bug report welcome ( please use Issue on github ) I plan to allow Switching ( or choosing at startup ) between Pilot and Copilot , and to have BOTH ! if you own 2 ww cdus ( a PFP7 and a MCDU for example )

I like what i'm seeing !!

As this device is not really in the DCS Mood , i suspect "panel" owners already own Winwing combat dedicated devices, which is x100 more immersive i think. But if you own the FCU / EFIS , would you be interested in displaying things on it. EFIS QNH could be useful ( easier to set than often unprecise "clocks" in aircrafts ) FCU VS , Speed , HDG ? ( often on the plane HUD ) I could try to map DcsBios info to this device.

By the way, i can see that you are using the Pfp3n and it confirms that it works on this device too ! ( I was not able to test on this one ) . I'm not sure the "UFC radio report" is that useful on the AH64D, as you have this directly in front of you as a pilot . but leaving the keyboard display alone was "strange" . If you have any / suggestion let me know with direct message. Based on your experience, i added some error handling on config , and log files and this should be the 1.0 ! https://github.com/landre-cerp/McduDcsBiosBridge/releases/ ( edit use the latest beta if you are installing for the first time )

There's some informations in the Readme file https://github.com/landre-cerp/McduDcsBiosBridge i suspect misconfig in the config.json to point to the dcsbios files. Let me know if it helps.

I'm very happy to read this ! Leaving the button mapping to user was a design choice. It's not that long to do and let everyone do it the way they want, feel used to or natural. For the ch47 CDU, i agree ! i counted the lines LSK and RSK , match , i asked the dcsbios team if i could help on making it available but looks like it's not that easy. I'm monitoring it regularly and as soon it's available i'll add it to the project. Again, glad to read that my project helped you. And the physical CDU in the A10C is a real game changer / fun to have.

you can use the latest beta. it should work fine. https://github.com/landre-cerp/McduDcsBiosBridge/releases

Mcdu-dotnet lib i use was updated by vradar and now handles PFP7 ( and 3N but i cannot test on this one ) . I will release a version later this evening .

I also own a PFP7, so i'm curious to see what Kurisu did to get the PFP3 work, as i would be able to either clone or adapt the mcdu-dotnet lib i used to get the A10C work with the A320 Mcdu. Should come sooner as he updated the Lib to now handle the 777 too !