bjratchf

Thanks… that rules out the firmware being the problem. I’m having trouble getting my CDU to talk to spad at all. None of the buttons are responsive within the Spad screen- I’ve set up the pmdg for SDK reporting, and imported the CDU into spad along with the programming string from c0nnex that had all the buttons programmed. But the CDU device just sits there with the screen asking if I’m wanting to use the left or right CDU

I flashed to the latest firmware 1.5.4, and my CDU buttons are now not being recognized by SPAD.next. I'm convinced its a firmware problem, changing the hardware IDs and such. Is there a place to download older firmware to flash and try that?

My CDU screen/buttons are unresponsive with SPAD.next. 737_options.cfg SDK sections added CDU recognized in SPAD.NEXT, but not registering any buttons. (as in, when I press a button on the CDU, corresponding button DOES NOT light up in SPAD. Like with the radio panel, it jumps to whatever I press in SPAD- so spad isnt recognizing something) Updated to latest cockpitmaster CDU firmware 1.5.4

Is there a way to service the hydraulic quantities, or is the fluid level not modeled (It is basically going to be 60%/60%/45% on every flight?

I'm noticing in the CRJ Vol 1 page 1-1-11 that it instructs the user to place the empty weight CG all the way to the right. I'm reading numerous threads about how the EFB is used completely for W+B (there is bad communication between EFB+sim menus), and not to ever mess with values on the MSFS menus. Is this instruction to place the empty CG far right still current?

I've noticed after a few iterations of MSFS as well as my reinstalls that when honeycomb software is installs, it overwrites the exe.xml and obliterates whatever else was in there: FSUIPC and realsimgear interface. Once this happens, it is very difficult, from a user standpoint, to rebuild the exe.xml so that everything works. Here's what I've rebuilt, but I'm not sure it will allow both components to work unfortunately. <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>C:\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> <Launch.Addon> <Name>AFCBridge</Name> <Disabled>False</Disabled> <Path>C:\Users\Brendan\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\AFC_Bridge\bin\AFC_Bridge.exe</Path> </Launch.Addon> </SimBase.Document>

Trying the CDU out with the pmdg 777. Works very well- would be cool to have the option to switch to the FO and CENTER FMCs, since the center one will be used a lot for ACARS using PMDGs upcoming Global flight ops- a similar function to the 737 where we can already switch to the FO's FMC.

Just wondering if it is just me, or the turn coordinator ball is locked in the center when doing a slip/skid turn. It might have already been addressed, user error, or logged for an upcoming patch. Thanks! EDIT: autorudder somehow had become activated.

i'm having the same issue- I guess as explained it's an FS bug... Although I wish we could add some sort of light to brighten things up. Has anyone tried any of the shockwave stuff?

I'm in the same boat with the CDI... I can boot the GPS just fine, but it does not drive the CDI, on SIMPLE or REALISTIC radio settings. It appears in the VC that the GPS unit also pops up as a window embedded in the panel... Will do some more testing, I made sure in the realityxp configuration program that I had "link CDI/VOR" to have the GPS drive the gauge. -

Der link funktioniert nicht mehr, aber danke. Gibt es eine bessere Link dafür?