Winwing MCDU -can it be used in DCS - for other aircraft

[GregP]

Just wanted to say thanks for developing this program! I got my CDU working with the A-10 last night and it's fantastic, really adds to the immersion.

[Noraku16]

Yes indeed, thank you. Everything has been working as expected.

[Polar-eX]

Great work, thank you!

[Cowboy10uk]

Mmmmm not sure what I’ve done wrong here.  I can get output on my pfp7, I can interact with DCS a treat. The issue I’m having is the mcdudcsbiosbridge keeps shutting down with zero error messages. 
 

if I restart it, things start working again, but then it closes down again. 
 

any ideas? 

[Cerppo]

On 9/19/2025 at 8:51 PM, Cowboy10uk said:

Mmmmm not sure what I’ve done wrong here.  I can get output on my pfp7, I can interact with DCS a treat. The issue I’m having is the mcdudcsbiosbridge keeps shutting down with zero error messages. 
 

if I restart it, things start working again, but then it closes down again. 
 

any ideas? 

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. 
 

Edited 13 hours ago by Cerppo

[Taffster]

17 hours ago, Cowboy10uk said:

Mmmmm not sure what I’ve done wrong here.  I can get output on my pfp7, I can interact with DCS a treat. The issue I’m having is the mcdudcsbiosbridge keeps shutting down with zero error messages. 
 

if I restart it, things start working again, but then it closes down again. 
 

any ideas? 

I had the same issue until I realised I had bound the MCDU MENU key; this key shuts down the bridging app. 

[Cerppo]

5 hours ago, Taffster said:

I had the same issue until I realised I had bound the MCDU MENU key; this key shuts down the bridging app. 

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

Edited yesterday at 05:25 PM by Cerppo

[Cowboy10uk]

8 hours ago, Taffster said:

I had the same issue until I realised I had bound the MCDU MENU key; this key shuts down the bridging app. 

Ohhh , yep I do have all the keys bound on my pfp7.   I’ll unbind and see if that works. 
 

thanks. 

7 hours ago, Cerppo said:

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

Even better, I’ll just download the latest version.   That was pretty quick work.

 

thanks.

[dahui]

I have the same issue, that the Applicatiuon closes after a few seconds. Where do i check if the MENU Key is binded or not? In DCS?

[Cerppo]

24 minutes ago, dahui said:

I have the same issue, that the Applicatiuon closes after a few seconds. Where do i check if the MENU Key is binded or not? In DCS?

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 .. ) 

[dahui]

Did now twice, exactly according to the readme's. It seems that i am to stupid. Ill wait for the New Version

[Cerppo]

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. 

[dahui]

Got it so far, that the Progam Starts and the MCDU shows the available Modules

When i press "CH-47 PLT)" The following Message appears on the BIOS Program

I have the Buttons assigned

 

EDIT: When i Press for example AH64, it shows "Bridge Started successfully"

Edited 4 hours ago by dahui

[Cerppo]

1 hour ago, dahui said:

ording to the readme's. It seems that i am to stupid. Ill wait for

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)
  
   

Edited 4 hours ago by Cerppo

[dahui]

ffs, i was shure i downloaded the last version, but maybe during troubleshooting, i messed up. Thanks a lot for your help!

[Cerppo]

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