A400M Refuses to move when spawned cold and dark

I used the EFB to set the plane’s state to “Ready For Takeoff” after performing all preflight checks and it removed the chocks and allowed me to taxi.

I’ve tested this in SU2 Beta v1.4.18.0 and cannot repro the EFB / Chocks issue. Repro steps were:

  • Spawn cold-n-dark at parking spot 4 at MMZO (temp > 0C).
  • Completed the walkaround (including removing the chocks).
  • Entered the cockpit and completed the first six preflight sections of the in-sim EFB checklist (but I skipped the EFIS & FMS section, as I was not going to take off and fly somewhere).
  • Removed the visual of the GPU unit by toggling the GPU option in the aircraft-specific EFB.
  • Released the parking brakes.

I was then able to move away from the parking spot & start taxiing to the runway without an issue.

Although there is no “Remove Chocks” item in the aircraft-specific EFB, clicking this (now missing item) no longer appears to be a necessary step to get the aircraft moving.

Note that there was a another bug topic created in November 2024:
A330 chocks cannot be removed from EFB - Bug Reporting Hub / Aircraft & Systems - Microsoft Flight Simulator Forums
which was tagged as bug-logged
Speculation: The “Remove Chocks” item in the aircraft-specific EFB may have removed by the developers as part of the resolution of this bug.

What was the OAT at MMZO when you did this test? If I recall, part of this bug (or perhaps another entirely) was that the A400M refused to move when spawned cold and dark in cold (I believe <10C) temperatures.

1 Like

I did not check, but MMZO is in Mexico, so at this time of year, I’d expect pretty warm (was using live weather). The test above was to check the EFB/Chocks issue.

The original OP’s issue with moving - providing that the OAT is low - is still present (I re-ran my repro at BGJN in Greenland with an OAT of -21C). Manually changing the temp in the weather widget in the game to zero allowed the aircraft to move.

1 Like

I am also encountering this issue in SU2 beta, and it’s the same if I start from the runway with everything running, too.

Also having the same issue in the SU2 Beta - Shame, hadn’t touched the plane in a while and was looking forward to it but it does not want to move. The “Chocks” item in the EFB is no more so its no longer a workable solution.

This was at EGVN in the UK where the temperature is fine.

Edit: Seems if you use the panel state “Ready For Takeoff” - It will remove the chocks (even though they aren’t visible) and will allow you to taxi. Hope this one is fixed so we don’t have to do that in future.

1 Like

Same for me, no taxi after start on parking spot. Start on runway, no problem.

I have the same issue, it looks like the game thinks the chocks are still on. I have SU2.

Same with SU2: if i remove the chocks on the outside by clicking on them, i still cannot move the airplane and the button in the EFB to remove the chocks has disappeared. Its nice that Cold & Dark now “works” but I still cant use it because the airplane cant be moved.

Have you tried slew mode?

Sorry but im not sure, is this a serious question?
I would like to taxi to my runway after a Cold & Dark start. I dont want to teleport or anything else, i thought this is a simulator and it fails because of the simplest things.

I understand, but was just wondering if it would unstick the aircraft if you slew back a meter or so. You can try to find a workaround or wait another month or two for a fix.

This…

1 Like

Okay, yes i knew there was a workaround but I’ve been waiting since the release of MSFS24 to be able to use this plane properly. The A400M was the only real reason for me to switch from 2020 and every time a thing is fixed 2 new things are broken, i m just extremely frustrated.

@BanKhokklan thx

You are my hero. Thank you.

Still an issue with SU3 beta 1.5.1

Someone said (can’t find it anymore, maybe the A400 main thread) that it’s a brake issue, and I think that is correct.

Starting C&D, the brakes are fully on, even if you don’t use them. Pressure does not change, even if you release the parking brake.
Go into the brake menu, you can see it.
If you use the CTRL-E quickstart shortcut, the brake indicator releases as it should, brake pressure goes down and the plane can be moved.

So: probably not a chock, but a stuck brake issue.

If only devs would be allowed (and willing) to comment instead of leaving their customers guessing!

Edit: I have replaced the screenshot to not get anyone confused, as in that moment “parking brake on” was visible in the first screenshot :wink:

1 Like

Personal Comments and Observations

If other folks can repro this, you might be better off trying to report it directly to Ini on their Discord.

I’m not a big believer of this practice, but Devs tend to see and action reports on their own channels faster (for a variety of reasons) than trying to report this here, even though Ini is a Dev Partner in addition to independent Third Party. The implication is that MS wants the tickets routed through them back to the Dev Partner for triage and assignment. Carenado was hardcore on this approach in 2020 (and to my knowledge, still is).

But I get your feeling, I want nerfing defects like this fixed sooner.

1 Like

Personal Comments and Observations

I have 5 bug reports for the A400M from iniBuilds open for months and all 5 of them here in the forum and then again in the IniBuilds forum, in their forum all reports were completely ignored, no reaction nothing.

Sometimes they aren’t going to move unless MS tells them to. It’s all about the Contract they signed and what they do for post-launch support. Some studios operate very transparently and quickly. Others follow the MS playbook and if it doesn’t get logged as an actionable ticket, it doesn’t get fixed.

I have SU2 and I DIDN"T have this issue until I got the update. Temp is 20c and I have tried it several times and attempted a number of the workarounds. Looking from the outside it sure looks like the chocks are in place but they aren’t and the option no longer appears in the EFB.