zachlog

This worked but no cockpit/ground communication chatter. I looked at the options and "Interactive Pushback Audio" is OFF but also grayed-out. Any ideas about this one ? Thanks.

In my case I don't remember if the tug moved but the A/C did not go anywhere. As a matter of fact, after hitting MANUAL PUSHBACK it grayed-out and there was no further communication chatter with ground.

Well, I tried it with the parking brake off but this time nothing happened when I hit MANUAL PUSHBACK....no movement whatsoever.

So, release the parking brake then start MANUAL PUSHBACK. This could induce A/C movement when the tug is being connected but I guess this can be prevented by applying manual brakes. Yet one more instance of flying MSFS 2024-style 🥲 Thanks.

Neither have I thus the OP.

In MSFS2024 when MANUAL PUSHBACK is selected, the front of the PMDG 300-ER lifts similar to the the profile when rotated on the runway for takeoff. When PUSHBACK is stopped, the front of the A/C drops to the tarmac.....and ready for pushback again. This problem does not happen with MSFS 2020. Is anyone else having this problem ? Is there a fix ? Known issue ?

If you already own the PMDG B777-300ER, there is no fee for downloading the updates to MSFS 2020 or for adding it to MSFS 2024. This A/C is now managed via Operations Center 3 (OC3) and it can be downloaded from: pmdg.com | More | Downloads

It looks like you, jcomm and I are in the same configuration range with the same challenges so here is some feedback. I am beginning to ease into MSFS 2024 by establishing an availability and performance baseline. My configuration is mid-range at best so I know I cannot just add a component simply because I like it. It's add, measure and decide ! Thus far I have had a stutter-free experience testing with the Cessna Citation Longitude, FSLTL (some flights). Checked the FPS 2-3 times. It's consistently in the 37-42 FPS range. I am not the FPS type. I just care about stutter-free performance. All scenery is what comes with the product, my Community folder has only FSLTL. I am now waiting for the PMDG B77W and for Fenix to release their BFU. Hopefully my experience with these products will be the same as the Longitude and be able to use them. If not, my flight simulation future will be lots of MSFS 2020 and a little MSFS 2024. I have no intention of upgrading my current configuration, which has been performing very well for 2.5 years. Here is my configuration: CPU i7-12700K Memory 32GB DDR5-4400 GPU Nvidia 3070ti 8GB VRAM Monitor 2560 x 1440 (Max refresh rate 144 MHz) HAGS is OFF HDR is OFF

The Controls directory is <Appdata>\Local\Packages\Microsoft.Limitless_xxxxxxxxxx\SystemAppData\wgs. To backup the General | Graphics and some other settings, you need to backup file usercfg.opt in directory <Appdata>\Local\Packages\Microsoft.Limitless_xxxxxxxx\LocalCache. These directories might vary a bit depending the MSFS 2024 version you have. Mine is the MS Store version.

In case you're still having this problem....I had the same problem yesterday. This is what worked for me (no laughing now !): I backed-up usercfg.opt and controls directory in case of problems. I did a repair and reset in Xbox for MSFS 2024. This did not fix the problem. Since this was an Xbox sync issue, I wanted to make sure MSFS 2020 still worked so I started it. I got the same error starting MSFS 2020 but only momentarily and then the error message box disappeared and it started normally. I exited MSFS2020 and restarted MSFS 2024. MSFS 2024 started normally. I am not in the SU3 beta.

After jcomm's very helpful direction, I did a couple of very brief flights with LEGACY and with the TCA joystick, and all looks good....thus far.

This is a good one and thanks for the heads-up. I am currently transitioning, albeit slowly, to MSFS 2024 and doing some initial testing so I have not done any serious flights (PMDG or Fenix). Overriding my runway selection is a no bueno so I will keep an eye out for this one.

Character Voice was my problem. The rest were already set correctly. Thanks again.

I have a follow-up on this. Even after setting AI RADIO COMMUNICATIONS (ATC) to OFF, I am still hearing ATC asking me to respond. This is immediately after takeoff during the initial climb. Is there perhaps a bug related to this ? This setting is OFF and it was OFF even before the OP.

Thanks for the guidance.