PFD's show incomplete data

[nickmciniboy]

Since 1.8.1 I have this. I'm on FS2024 beta SU4. British Airways livery with default cabin (because BA cabin causes me to see NO cockpit). I'm seriously beyond this rubbish. FS2024 is still a pile of you know what, and the bugs and performance of this aircraft are pretty in line with the Redmond Asobo chancers.

 

Edited November 29 by nickmciniboy
Added detail.

[Peter]

Known bug in SU4.. revert back to SU3, and that wont happen

[Farlis]

10 hours ago, Peter said:

Known bug in SU4.. revert back to SU3, and that wont happen

Then why don't I see that? I'm in the beta as well.

[tipcat612]

I had to go out of Beta SU4  back to SU3 and then install Beta again and that fixed my issue with PFD because I was having the same issue.

[iniSteven]

5 hours ago, Farlis said:

Then why don't I see that? I'm in the beta as well.

It's doesn't always happen, but there is an issue in Su4 where the WASM doesn't always fully initialize. Often restarting the flight fixes it, but sometimes you have to restart a few times to get the WASM package to fully initialize.

[LineDX]

Run the sim as admin once after clearing the wasm folder. 

[frank_m]

When the "Shift+C" is shown to enter the plane, just wait a few seconds till the plane and all ground equipment is fully loaded and enter then the plane. Afterwards it works reliable.

[LineDX]

20 hours ago, frank_m said:

When the "Shift+C" is shown to enter the plane, just wait a few seconds till the plane and all ground equipment is fully loaded and enter then the plane. Afterwards it works reliable.

That's right. Wait for a few seconds and then jump into the cockpit, displays work as expected. 

Last night I loaded to the runway and had the same issue. Restaring the flight fixed it. 

[Farlis]

On 11/30/2025 at 6:54 PM, iniSteven said:

It's doesn't always happen, but there is an issue in Su4 where the WASM doesn't always fully initialize. Often restarting the flight fixes it, but sometimes you have to restart a few times to get the WASM package to fully initialize.

Had it happen to me now as well. 

Good that you gave the hint with the restart. That solved it.