The A400 fuel consumption is wrong. The shown used fuel on the ECAM shows the correct fuel amount the aircraft should use. However, the fuel in the tanks decreases far too slowly and does not match the indicated fuel consumption.
Every flight in the A400.
What peripherals are you using, if relevant:
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
same here sadly….
Thank you for the bug report.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Just chiming in to also report that this issue exists in the MSFS 2020 version of the aircraft. After two hours flight time the disparity is already at over 1 tonne.
So as stated in the changelog of SU5, the A400 should have now the correct fuel flow. I tested it but my fuel flow thats shown on the fuel page is still different than my actual fuel usage.
So as seen here in this screenshot “fu all eng” should be 780kg. I took off with only 200kg and still have 100kg left in my tanks. So its way less fuel burn than it should be. I double checked with a friend of mine and he is having the same issue. Can anyone check this and report back if your A400 uses the correct fuel or if you experience the same issue
For reference:
And the fuel usage is still incorrect. Thats also in the changelog for the A400 but its still not burning enough fuel. Here in this screenshot you can see “fuel used all eng” should be 780kg, but i only took off with 200kg and still have 100kg left. Ridiculous they have things in their changelog but didnt change them
Do you mind letting me know what package version you’re seeing in the My Library tab if you’ve locally downloaded the product? I’m going to verify this with our Dev Team to make sure it’s the correct version!
Cheers
Im on 7.25.0
Thank you, I’ll pass this information on and get back to you if I hear more today 
All the fixes in SU 5 for the A400M haven’t made it into the sim. The shocks are still there. Fuel consumption is still marginal, and everything listed as fixed in the release notes for the A400M isn’t fixed. This has been a typical MSFS 2024 mystery for a year and a half now: updates from Microsoft’s partners either arrive in the sim very late or not at all, even though they constantly release updates and upgrades. This affects aircraft, airports, wind turbines, and so on. Even after SUs, the bug fixes for these things aren’t always immediately available in the sim, even though they’re always listed in the release notes.
Please, Chewwy94, this needs to land on Jörg’s desk.
I’ve been writing about this mystery for over a year now because I’m testing these things, but it seems like no one’s listening.
The fact that the bug fixes for the aforementioned things are only listed in the release notes, but don’t actually appear in the sim until after several SUs, is also confirmed by some of the partner developers I’ve spoken to about this.
Often, the same bug fixes appear repeatedly in the release notes of several consecutive SUs because they failed to make it into the sim multiple times in a row.
It’s as if the improvements from the partner developers aren’t included in the final SU package each time, because it was forgotten
So, last night the update for the A400M arrived, and I installed it, which was strange.
After the installation, the aircraft was deactivated for some reason, even though I had previously installed it and wasn’t streaming it anymore. The installed add-ons also explicitly state that they cannot be deactivated (they must first be uninstalled). Anyway, I had to reactivate the A400M.
When I activated it, the previously installed update disappeared, and I received another notification that there was an update available for the A400M.
So I downloaded and installed this update again.
This time, the aircraft remained installed at version 7.25.0 (“activated”?).
During today’s test flight, I couldn’t fly the A400M in Cold & Dark without the Chocks mod from Flightsim.to, so the fix for the Chocks bug is still not implemented.
I think the “GPU moves with rudder input” fix has been implemented in the sim.
The minimap is definitely fixed, and the cargo boxes are now visualized. The terrain display also seems to be showing something now, although I don’t understand exactly what it displays.
I also don’t understand the recurring copy-pasted release note points in so many sections of the SU 5 release notes and previous SUs, where the same text is repeated over and over, just like in the final points of the A400M release notes:
“Fixed - INI_REQ_FINAL_FLT=1 set incorrectly in approach.flt.
Fixed - ExecuteCareerCode(true).
Fixed - [CAREER] [A400M] [CARGO OPS] [HEAVY] After skipping the cruise with A400M, flaps are set at an incorrect position and trigger an aviator performance.
Fixed - INI_REQ_FINAL_FLT=1 set incorrectly in approach.flt.
Fixed - ExecuteCareerCode(true).
Fixed - flt variable causing black screens in approach.flt.”
This makes the release notes list artificially longer.
Now we come to Fuel.
I flew with a Simbrief FPL from Basel LFSB to Nice LFMN.
Simbrief calculated a block fuel of 8448 kg for me, and the aircraft calculated that I would likely have 1.6 t of remaining fuel in Nice.
I actually had 7515 kg in the main tanks when I deboarded in Nice.
So the fuel consumption is still completely unrealistic!
That’s exactly what I’ve been saying for over a year.
The bug fixes for certain partner add-ons in the release notes don’t all appear, not always, and sometimes even after several SUs in the final SU. Here’s confirmation of that again.
The next SU 6 release notes will contain things like:
-“Fixed - [Community][Airbus A400M] [2024] Fuel Used is correct, however Fuel On Board does not decrement Correctly.
-Fixed - [Airbus A400M] From A Cold & Dark Start Chocks Remain in Place Despite Being Removed.”
etc.
And they might not be fixed again.
Same issue on the other Airbuses.
It was also an issue when 2024 launched and was disabled because of it.
For some reason they reenabled it without fixing it.
ini’s aircraft use a custom terrain raider instead of the default Asobo one, and it’s broken in 2024.
So, another fix that’s only mentioned in the release notes, making the release notes unnecessarily long.
Who remembers when you could actually rely on release notes?
A310’s changelog mentions the same bugfix 4 times lmao
No, because they did re-enable the terrain radar. They didn’t say that it would work properly.
, hilarious 
Some real monkey’s paw shenanigans going on here
certainly
.
