Just reinstalled following Kyle's steps to a T, and still getting the master caution for fuel and anti-ice when using the NGX SHORT panel state. When using the Before Pushback state from the EHAM-LOWI tutorial, I only got the master caution for the anti-ice.

Yeah. It's not the procedure causing it. It's the saved panel states. We're looking into it.

Just reinstalled following Kyle's steps to a T, and still getting the master caution for fuel and anti-ice when using the NGX SHORT panel state. When using the Before Pushback state from the EHAM-LOWI tutorial, I only got the master caution for the anti-ice.

 

 

 

Thomas, I loaded the default state, started the APU and shut down the engines, then saved a new state. Now it works! 

Followed Kyles suggested install method and confirm that I have the fuel lights issue. Total new reinstalled package.

Not a deal breaker but an issue all the same. Never had it with SP1c.

Regards

Tim Carter

Same problem here.

 

Regards

 

 

Santiago Villacorta

I think loading a saved panel state trigger failures, that is why you are seeing the Master Caution light illuminate. The failures displayed in the CDU match the warning lights.

I can also confirm the FUEL/ANTI-ICE warnings following the SP1D update (yes, followed the instructions closely).

 

Glad PMDG is already looking into it. Was a bit concerned there.

Load the default panel state. That will fix your issues.

Same problem for me (master caution on with fuel/anti ice alert)

I ve followed the pmdg procedure but the issue persist.

Same problem for me (master caution on with fuel/anti ice alert)

I ve followed the pmdg procedure but the issue persist.

Did you try loading the default, engines running panel state?

For now:

1. Load the plane with the engines running (if you've set a default panel state, hit DEL, click on the default panel state slot, and then hit EXEC - restart the sim).
2. Create your own panel states from that (the tutorials are a good guide to the get the plane in those states)

Hint: You can do all three at once. Do short first, then long, then C/D. They're all only a few button clicks off.

Thanks Kyle, as always, for all your help. Should (tailnumber).ini files from the previous version be an issue? Should we created new versions of those as well?

 

 

And do you know if it makes a difference which model is used to create the new panel states, since the panels are slightly different?

 

Dave

For now:

1. Load the plane with the engines running (if you've set a default panel state, hit DEL, click on the default panel state slot, and then hit EXEC - restart the sim).
2. Create your own panel states from that (the tutorials are a good guide to the get the plane in those states)

Hint: You can do all three at once. Do short first, then long, then C/D. They're all only a few button clicks off.

 

Kyle,

we have to do these steps each time that we start a flight?

I've had this problem, too. At first I thought it was a feature, not a bug I guess that's what we have the QRH for. Simple solution: Create and save your own start-up state(s). Delete the generic ones from the folder. I did exactly that and I have experienced no erroneous recall messages thus far. It was actually a good reason to create some more realistic states, for example one where the aircraft has already been powered up by the ground crew.

Kyle,

we have to do these steps each time that we start a flight?

 

Nope. Just the first time to get your plane into the default state. From there, you can save panel states that won't contain whatever error is in the current files.