Brake stuck on 1 wheel?
-
Just did a short hop in the 146-300 and despite being reasonably heavy I couldn't work out why I was using 60-70% N1 to get rolling. Wasn't really paying much attention as I was only flying to try out the new Flo Pro, but when I landed I looked at my brake temps and while 3 of them were showing around 90 when parking, the right outboard brake was showing 297! I tried looking in the failure screen to see if something had triggered but nothing showed up there, and the wheel looks fine from an external view. Is this something I did by missing a step somewhere or have I actually found my first bug?
-
It happened again. Short hop from EGLL to EGLC to try out the steep approach, and again it took excessive power just to get moving, even with no pax and a meagre 2000kg of fuel. This time I did get a red message box at the top of the screen saying there had been a tyre failure, but once again no sign of anything in the EFB failures page nor on visual inspection from outside. Both times this has happened it has been on the right outboard brake/wheel.
For reference this is in 2024 with IniBuilds EGLL and default EGLC, Flow Pro and GSX running and using SPAD.next for controls just in case anything here has even a remote chance of interacting with the aircraft to cause an issue.
I'm cleaning up my system tomorrow and doing a complete reinstall of everything (long overdue, just need rid of all the usual crap that gums up a system after a long time) so I may or may not be able to reproduce this afterwards.
-
With a red message on top of the screen and nothing in the EFB, it sounds like a failure made by the native MSFS system instead. Once overspeed the flaps in the CJ4 - got a message box like that - and when i tried to use them again, I had asymmetric flap deployment.
When did the message show up?
Maybe something like pushback with brakes/chocks still on, or the release from a tug generating an unintentional high G-load could be triggering it.
Or random/planned failures could be on in the MSFS system (menus love changing themselves around after updates in MSFS). -
Just to note from our side, we don't simulate individual brake failures, and we don't trigger any warning messages other than the ones on the EFB and in the aircraft itself.
I seem to recall we have previously received reports of brake issues across all products, and they can be caused by a certain brake/friction setting within FS Realistic (sorry, I don't recall the exact name of the setting off the top of my head).
Mark - Just Flight
-
With a red message on top of the screen and nothing in the EFB, it sounds like a failure made by the native MSFS system instead. Once overspeed the flaps in the CJ4 - got a message box like that - and when i tried to use them again, I had asymmetric flap deployment.
When did the message show up?
Maybe something like pushback with brakes/chocks still on, or the release from a tug generating an unintentional high G-load could be triggering it.
Or random/planned failures could be on in the MSFS system (menus love changing themselves around after updates in MSFS).@Avionic said in Brake stuck on 1 wheel?:
When did the message show up?
Maybe something like pushback with brakes/chocks still on, or the release from a tug generating an unintentional high G-load could be triggering it.
Or random/planned failures could be on in the MSFS system (menus love changing themselves around after updates in MSFS).I got the message near the end of GSX pushback. Brakes/chocks definitely not set as I learned on my first flight once I realised that GSX doesn't handle the chocks and won't push unless you remove them yourself.
@Mark said in Brake stuck on 1 wheel?:
I seem to recall we have previously received reports of brake issues across all products, and they can be caused by a certain brake/friction setting within FS Realistic (sorry, I don't recall the exact name of the setting off the top of my head).
Defo not an issue with FSR as I don't have it.
-
I might have found a possible cause, but I'll need to test more to see if I've nailed it down. The error message seems to pop up right at the end of pushback as the tug lowers the nosewheel.
It seemed a bit unrealistic to have it lift the nosewheel for pushback at all as I've only ever seen 146s push with a towbar, so I went into "Customise Airplane" in GSX and unchecked "pushbackRaise" which was on by default. I started a new flight and didn't get an warnings about the gear, and can get rolling at a more realistic power setting.
So for now it seems to be an issue with the way GSX and the 146 interact in 2024. Watching from the external cam I did notice that the tug didn't actually lift the wheel, and the effect comes from the nose strut extending. I never looked at other planes though I'll have to check now, but I wonder if that might have some impact?
-
Sounds pretty likely. In other planes, I have had trackers for virtual airlines register it as an over-g load when GSX lowers the plane. So the sim might see it as a hard landing which has x % risk of causing a puncture.
On top of the nose strut extending, you might also have the VSI indicating a climb when the nose is lifted, so they are probably fudging a few things to get it to operate.
