v-speeds too low

[ionic aspen]

Since a few days I am noticing the following:

• Create a flight plan in MSFS
• Load the A32nx cold and dark
• load passengers and fuel via the EFB (instant)
• Now I configure the MCDU, weight values are filled with RSK keys
• Same for perf page with v-speeds
• I do a pushback snd start engines
• After start I go to the ECAM to do a flight control test and trim
• When pushing t/o config test I get a warning that the v-speeds are too low
• With the LSK keys I can set the correct speeds...

Any clue? This always worked...

[prime remnant]

Stickied Message

If you are having an issue with Experimental or cFMS LNAV / VNAV, please search for similar issues prior to posting your issue.

If you are not using Experimental, please use #a32nx-support

Useful Links:
Install Guide
Known Issues
Beginner Guide
Custom Autopilot
Custom Flight Management System
Throttle Calibration Guide
LNAV/VNAV Guide

Support for Experimental is not guaranteed.

[shrewd zealot]

this issue is usually caused by missing entry on the init fuel pred, after engine start some values are automatically calculated leading to correct V Speeds being available

[ionic aspen]

In the init phase I use RSK to fill the ZFW/ZFWCG and BLOCK, what I always did.

[shrewd zealot]

I‘m not sure if the Block can be auto populated? I thought you‘d have to fill it from the loadsheet

[ionic aspen]

Yes, it is possible. It always worked that way (not using Simbrief etc.) just the default flightplanner/NavData. Using the EFB to load fuel and weight

[fierce idol]

Even if you used the MSFS flight planner and EFB to load fuel and weight, you still have to type in your Block Fuel in the CDU on the Init B page.