nvmbr

This is also happening in 2020 with the latest update from yesterday. Just like the others have reported, it only happens when the GSX tug is connected. it actually stops when the GSX tug pushes me backwards, but once the GSX push back stops moving , I start rolling and goes on until the GSX tug disconnects. I can't reliably reproduce it there but it's happened to me three times at two different airports.

Descending into KLAX. Got cleared for approach so I switched on LS and VV. Suddenly the speed, heading and altitude were no longer in managed mode. So I pushed each knob in. The PFD and NAV displays flashed for a moment and the dot next to the display came on for just a moment but it disappeared. I tried disengaging and re-engaging autopilot but that did not help. Even in non-managed mode, I could not get the aircraft to obey my selected heading, altitude or vertical speed. Autothrottle still worked and obeyed the speed on the FCU, but the other FCU knobs no longer worked. I was not able to put the aircraft into APPR mode either. AP was turned on, but pushing the APPR button did nothing. The descent rate just stayed with what it was on before the FCU stopped working. This comes at the tail end of a flight from EGLL. I've attached the autosaves, flight plan and screenshot of the console. There were no WASM crashes reported, just the FuelSystem "Could not create pump #n" but those occurred throughout the flight. Link to YouTube video with this bug Windows 11 MSFS 2020 7800X3D 7900XTX 1754168924.bin 1754169387.bin 1754169854.bin 1754170338.bin 1754170780.bin EGLLKLAX_PDF_1754171436.pdf

Issue: Text fields on the right side MFD lock the cursor when the user clicks in them but they don't accept physical keyboard input, including the enter key. The left side of the MFD does not behave this way. This bug is easily reproducible across all fields on all of the MFD pages on the right MFD. In the video, I am just trying to use the keyboard to input a test squawk code into the right MFD. I demonstrate that the cursor stays stuck in the textbox, it allows 1 random key (2) to be entered into the field even though I was typing several numbers. It also doesn't record the enter key press on the physical keyboard. As a result, the only way out of this is to click one of the virtual DIR, PERF, INIT, NAV AID, C/L MENU, F-PLN, DEST, SEC INDEX, SURV or ATC COM buttons to display other screens or click the virtual ESC button. The squawk code and any other field can be easily entered/edited on the left MFD. In addition to the bug described above, I also demonstrate a bug where the value that is displayed for that squawk field on the right MFD changes when I click into it, even though I haven't typed anything into it. I have observed this on multiple fields on the right MFD. I've attached the autosaves to this post. No WASM errors recorded during this. MSFS 2020 Windows 11 7900XTX 7800X3D 64GB RAM Example Video 1753134699.bin 1753135174.bin 1753135622.bin

I am seeing this same issue after inserting my company flight plan. Flight plan created in SimBrief (attached). Unable to manually enter wind. Unable to populate it via CPNY Wind Request + insert either. SimBrief is properly linked with the aircraft, as demonstrated by my ability to insert the company flight plan. Windows 11 MSFS2020 No WASM crashes in debug console 7800X3D 7900XTX 64GB RAM Using latest version of the A35K. flight-plan.pdf