on the inibuilds EFB in the cockpit, click on any of the panel states to fix the issue. When initially loading the plane, the brake pressure is bugged and stuck on nearly full. Clicking a panel state resets it.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes, every time I start cold & dark in the A400M.
Provide extra information to complete the original description of the issue:
• There is always pressure on the brakes, even when the park brakes are off. With no engines running I was able to “empty” the pressure on the brakes down to 0 on the ECAM RAD screen. I recognized, that as soon as I activate engine 3 or engine 4, the pressure on the ECAM jumps back into an accebtable pressure range after a few seconds.
Nevertheless the airplane won’t move, even with “emptied” pressure on the brakes and just engine 1 and 2 running. Two engines are enough to move the plane (tried some weeks ago).
If relevant, provide additional screenshots/video:
•
I tried the G111 for the first time again yesterday and… it wasnt moving. Does it suffer from the same bug as the Beaver ? Wherein amphibious palnes can not move on land at all ?
The issue is NOT to do with chocks - it is brakes. Putting dev mode on clearly shows 100% brake force applied even though both parking and toe brakes are released.
I logged this in the ini support thread on discord and the answer was - yes we know, it’s a Asobo issue and we can’t fix.
As soon as ready to fly panel state is triggered you can see the brakes release in dev monitor and from that point on they and the plane behave correctly.
PLEASE fix this - simple to replicate and (surely) simple to fix.
Yeah very annoying bug. If I want to do cold start, I click “ON GPU” in EFB and after that remove the chocks, this also seems to release the brakes. Close enough “cold start” until this is fixed.
Hi @Twodogzz
Appreciate the link. As you probably noticed, both these bug reports are feedback-logged . Once logged in the internal bug-tacking system, we generally do not merge topics as this can cause unnecessary complications.
You are 100% correct - the LVAR is LVAR:INI_CHOCKS_ENABLED
It’s initialised to 1 at load. The EXT_CHOCKS vars are correctly set to 0 when removed on walkaround but the critical one isn’t.
I set a button on SPAD to toggle between 0 and 1 and as soon as forced to 0 the A400 will move correctly.
I’ve updated my thread in the ini discord so now it’s between whoever is accountable for applying the fix to do the thinjg. Given it’s 10 seconds (generously) work it would be great to see this is resolved for non external s/w users at SU3.