aaronpriest

Changing it to these numbers worked for me, waiting to hear from my cousin: const screenXY = "left:30px; top:62px;"; const screenWidthHeight = "width:654px; height:440px;"; Also set the white borders to transparent on the buttons. Thanks!!!

The popout was correct (when we could see it before it disappeared, sometimes it would stay, sometimes it would vanish); it's the web browser that was not. On the previous version of the P180 the web-based MCDU was fine for both of us. I'm hopping in it now to do some more testing.

I have three identical monitors, same resolution and DPI on all three. I'm using Brave for a browser. The aspect ratio of the PNG file in the webpage is not the same as the file opened in the Photos app (or Photoshop either) from Windows Explorer, it's resized. The text box itself appears to be the correct size and aspect ratio, but the PNG frame around it is not on the P180 so it's chopping off the entire bottom line and a little bit of the right side. Same for my cousin and he's running a different size monitor and resolution than me (both his 13" iPad Pro and his 1440p 27" local monitor, I guess he didn't try his 4K screen yet). I didn't try my 11" iPad yet. I don't know what clydefj is running, but his description sounds identical to ours. I haven't had time to mess with the config files yet, still in the middle of a very long flight in a DC3, hehe!

Yeah, that's happening to my cousin and I as well. He is running 4K and I'm running 1920x1200 and it's off the same amount for both of us. I'll do some tweaking later today.

Hi Lorby! On the P180, I think the aspect ratio of the screen in the sim is slightly wider than the frame used in the web page, so it's cropping part of the text, particularly the bottom line and some of the right. Although the cdu.png image file itself looks correct, so maybe it's the pixel dimensions in index.html or config.js?

It still has 2020 avionics (I confirmed this with Working Title) so a lot of things are broke in 2024, like custom waypoints from the EFB. The other Carenado planes like the C400 and C408 have the same problem. In fact, quite a few stock 2024 planes are outdated at launch and don't work with the EFB.

One of the WT team members in the Working Title group on Discord said they stopped writing those LVars in part due to performance reasons. They plan to publish updated documentation soon, but all those LNAV LVars were removed in the latest version of the avionics SDK. He gave me a substitute to use instead that is working great though: (A:GPS WP DESIRED TRACK, Degrees) (>A:AUTOPILOT HEADING LOCK DIR, Degrees)

In MSFS 2020 I made a button for my Streamdeck that synced the autopilot HDG with the flightplan DTK for the next waypoint. I did it with the following script: (L:WT_LNavData_DTK_Mag, Degrees) (>A:AUTOPILOT HEADING LOCK DIR, Degrees) The first variable, L:WT_LNavData_DTK_Mag, does not seem to exist anymore under MSFS 2024. Any idea how to look this up now? I'm not finding any information online yet, nor anything that matches under DevMode, Behaviors, and Variables. I found the previous variable from this website, but haven't found an equivalent resource for 2024 yet: https://microsoft.github.io/msfs-avionics-mirror/docs/framework/enums/LNavDataVars/

Yup, that was it! Notepad++ must have added the spacing when I cut and pasted to move that section to the bottom of the file and I didn't notice. Thanks for steering me in the right direction!

Speaking of that, I just noticed the indentations on the last three lines, removing those and trying again.

This section was already in the 777_Options.ini file, but I moved it to the bottom and made sure there was an extra blank line below. I've also deleted the last line and added it back (since it was there before, but not mentioned in the readme.txt). I don't see any misspellings, but I copied and pasted it again to be certain. I am very dyslexic so sometimes I can stare at something for hours and not see it. [SDK] EnableDataBroadcast=1 EnableCDUBroadcast.0=1 EnableCDUBroadcast.1=1

Howdy! I have not been able to get the 777 WebCDU to work. The buttons work, but the text on the display does not. The text works with the 737, but I get a blank screen with the 777 (or a cached screen from the 737 if I was last in that plane--the 737 WebCDU does the same). It's like I'm missing PMDG-PMDG_777_CDU and PMDG-PMDG_777_Data as a script, but I've triple checked that they are loaded. And I've checked my 777_Options.ini file.