There are still numerous issues with the F-PLN page that have been reported for a long time.

The predicted speed for waypoints in cruise are still given in IAS rather than MACH.

There are duplicate (T/D) pseudo waypoints.

3 way switches still have inconsistent scroll wheel behaviour.

For example compare the BRK A/SKD or the LDG Light switches with the FD/FPV and CONSOLE FLOOD LT switches. For the first two if you scroll up the switch moves up, but with the last two, if you scroll up the switch moves down. It is really annoying.

The level-off arrow and the banana on the ND also need work just like all the other airbus aircraft in your fleet.

Clicking on the LSK to Auto Populate the ZFWCG does not work. Below is a video showing that.

https://www.youtube.com/watch?v=_k8hp714E_U


Many thanks for your continued work on this aircraft. I must say it hand flies very nicely, the best flight model of your aircraft by far I think in terms of hand flying!

Edited 6 hours ago6 hr by dectenor2

In addition.

Here there is a SPD Limit of 180 at EMA9





But the aircraft is then trying to accelerate afterwards to 210 at IEM82, where there is no SPD restriction (but even if there was, it would stay at 180, as 180 still satisfies MAX 210.








You can also see that the (SPD)(LIM) waypoint is in the wrong place. The aircraft does not need to slow to 250 for 10000ft at all because there is a waypoint VELAG with a speed restriction of 250kts at FL123, so the aircraft will already be at 250 for 10000ft. Therefore no deceleration required. So the (SPD)(LIM) pseudo waypoint should not even be there at all.

If the aircraft does need to slow to 250kts at 10000ft (because there is no waypoint with a restriction of 250kts that the aircraft will be at before it reaches 10000ft) then the (SPD)(LIM) waypoint should be at the point in the flight plan when the aircraft will begin to decelerate. This altitude will depend on the calculated econ descent speed before it needs to decelerate but generally around FL120-FL105. So the (SPD)(LIM) waypoint should be sequenced in the flight plan between the two waypoints that have a predicted altitude immediately above and below the altitude at which it will begin the deceleration. (Sorry that is quite hard to explain in words, much easier when you can speak it and point to the F-PLN page)!

Thanks.

Sorry, yet another thing.

I have set the aircraft to be completely empty.

There is no payload and no fuel.

So surely the ZFW and the GW should be exactly the same as GW = ZFW plus fuel.

Here there is an extra 160kg somehow.

This is messing up the aircraft weight calculations, and also at odds with simbrief, because the profile gives the empty weight as 80000, but the actual empty weight is 80161.7kg.

Maybe it is including two pilots in this 80.16 GW, but the pilots should be factored in to the OEW and thus the ZFW. So if you want to simulate the weight of the pilots, the OEW and thus ZFW with no payload needs to be 80.16 and then the simbrief profile will need updating. At the moment we are always getting a 160kg discrepancy.



You can see the actual ZFW and GW using Any2GSX, so you can tell that the aircraft itself is reading the ZFW incorrectly.

Hope this makes sense.

Thanks

Edited 5 hours ago5 hr by dectenor2

I'll get this logged for the team, thank you for taking the time to break these down and provide references/media. The efforts are always greatly appreciated by myself and the team :)

19 minutes ago, IniJamir said:

I'll get this logged for the team, thank you for taking the time to break these down and provide references/media. The efforts are always greatly appreciated by myself and the team :)

No problem!

Any time, getting a bit cooler for a few days so I can do a bit more!

It’s always annoying that the updates come out and so I try them out and then notice stuff ha. I wish I had the sixth sense to do some flying in these aircraft whilst the updates are being prepared!