For me, the new problems I've encountered so far are: 1) On the b-747 & b-787, the auto V1 calls are gone. You now have to program them in the FMS if you want to hear them. 2) On all the jets with Auto Throttle Arming, the assignment has changed from "Set Auto Spoilers Arming" to "Toggle Arm Spoilers". But the problem is that on the B-747 & B-787, they are not working correctly, there's an annoying constant clicking as you roll down the runway. The A-320 is ok, it works fine after changing the assignment. 3) The B-787, is now very twitchy(sensitive) on the rudder. Before it was not. 4) The B-747 still has it' s GPWS 2500 Ft callout broken. Still calls it way off the correct radio altitude. 5) The B-787 has now lost it' s 400,300,200,100 GPWS callouts. It now only has the 2500, 500, 50,40,30,20,10.

On a positive side, now the b-787 can be trimmed manually instead of having to push or pull the yoke or stick as we do with the Airbus. This is what I've found so far. I still don't understand why things that work, end up not working after so many updates.

Mario 

 

1 hour ago, Marioalberto said:

You now have to program them in the FMS if you want to hear them.

This is accurate to the actual aircraft.

1 hour ago, Marioalberto said:

But the problem is that on the B-747 & B-787, they are not working correctly

You mention autothrottle, but then the two bindings you talk about are for spoilers only. Do you have more details? I'm a bit lost.

1 hour ago, Marioalberto said:

The B-787, is now very twitchy(sensitive) on the rudder.

Per type rated pilot feedback, the 787 has a good deal of rudder authority.

1 hour ago, Marioalberto said:

Still calls it way off the correct radio altitude.

Radio callouts are based on radar altitude above runway elevation and not the ground directly underneath you; thus they may not appear exactly at the time you think they should.

1 hour ago, Marioalberto said:

It now only has the 2500, 500, 50,40,30,20,10.

These are the correct set of callouts per the manufacturer provided documentation.

Edited June 23, 20232 yr by MattNischan

Hi Matt, thanks for your reply. On item 2, I meant to put "Auto Spoilers arming", not "Auto throttle", sorry. On item 4, I believe that it does seem way off because when I fly the 787 or the 320, the 2500 ft callout is way different on same airports/runways from the 747 (and it used to not be so before SU10 or SU11). On item 1, I guess that when you get used to the automatic callout of the V1, you get lazy to now have to input it into the FMS. On item 5, the same thing...we used to have all the altitude callouts and now we don't. Plus, depending on the airline, some do have the full altitude callouts on the 787, where, others as you stated, only have the ones that are now on our 787 after this update. And finally, on item 3, I'll just have to recalibrate the sensitivities and dead zones for this specific plane (because, unlike the 787, I noticed that nothing changed on the 747 & 320 after the update).

Anyway, thanks for your input, appreciate your time.

Regards,

Mario

2 hours ago, MattNischan said:

 

On the 787 rudder reaction as you mentioned is 95% correct simulated.

Regarding GPWS altitude voice annunciations during the approach as to

• 2,500 feet - TWENTY-FIVE HUNDRED

• 1,000 feet - ONE THOUSAND

• 500 feet - FIVE HUNDRED

• 50 feet - FIFTY

• 40 feet - FORTY

• 30 feet - THIRTY

• 20 feet - TWENTY

• 10 feet - TEN

• 5 feet - FIVE

are based on RA "above the ground" directly underneath. During the approach phase if you fly over a hilly area you might encounter repetitive calls like 2,500, 1,000, or even 500 based on actual minimum safe ground clearance. It should be noted that those calls can also be an option requested by the airline.

On the 748 there are also some discrepancies that need attention. If you wish you can send a PM and take it from there.

 

Hi LRBS, 

Thanks for the input, that's what I always thought about the RA altitude callouts, that they are based on exactly as to where are over at a given time.

As far as the 747 is concerned, I have already filed a Bug Report over at the MS Forum.

Thanks again & regards.

Mario