AirplaneEnjoyer

Do step climbs/auto step climbs work for you? Whenever I input them, I get weird UTC times as shown in the screenshot above from another post. No orange screens or anything.

I never had a WASM crash with this bug, there was just an issue with the UTC times displayed on the flight plan page of the FMS. The UTC times would show as negative values only when step climbs were input in the flight plan. As a result, the plane wont auto step climb, and the EFOB calculation is messed up, among other things. Seems to be like an Xbox only problem. I recently discovered when doing YSSY-KLAX, the UTC times were normal and all the step climbs were fine throughout the whole flight. Every other route i’ve tried does not work. Not sure why this specific route works, but having the plane work as intended on a whole flight was great. Last i checked, Xbox is still on 1.2.2. If anyone knows how long it usually takes, or why it’s taking so long, for these updates to come to Xbox, that’d be awesome!

Has this worked for you on Xbox? I’ve only ever manually entered them and have never had the automatic step climb entry turned on, and i’ve yet to have a flight where it isn’t broken at some point. I’ve had cases where 2 step climbs I enter will display and work okay (FL360 and FL400), but the third one (FL380, second step climb that I enter) will cause the erroneous UTC times, not display, and cause errors in trip time and fuel burn. Thank you for reaching out, I really appreciate any help or suggestions I can get. I love the A350 and want to figure out a work around, but it’s just not working for me.

Hi, I have the A350 on Xbox series X, and we are currently on v1.2.2. Given that fact the A350 is virtually un-flyable on long hauls with the step climb/UTC bug, I was curious of when updates reach Xbox? With 1.2.4 recently being released, what does the time line usually look like for these updates to come to Xbox? I understand it takes some time for the updates to go through Microsoft, but I was just curious what that usually looks like. Thanks

Was this issue fixed? @IniJamir Thank you

Thank you! I’m new to this whole forum, where can I check for updates on when it’s fixed?

Same issue, on xbox as well. Before T/C, all fixes UTCs seemed fine and logical. Only issue was DEST EFOB warning was displaying. Predicted fuel at destination was about -75. Fixes after T/C seemed fine as well, until my first step climb, which was displaying UTC times anywhere from -30 to 30. Once auto step climb performed my first step climb, that is when all UTC times went “rogue”. I deleted all step climbs from “STEP ALTS” in the perf page and re-inserted STAR and approach. This brought back the VNAV path on the bottom of ND. UTC times are now jumping back and forth between logical times, and somewhere between -30 to 30 with DEST EFOB warnings turning on and off. After a little, it eventually goes back to the way the picture shows above from OP. Only way to fix is to re-insert STAR and approach from which point the cycle repeats itself. I purchased the A350 yesterday, and my first flight (KATL-KDFW) to figure the airplane out, did not require a step climb, and everything went smoothly. This leads me to believe it’s an issue with step climb. Any help or suggestions would be greatly appreciated! Update: After going to F-PLN page, clicking destination airport, and only selecting my intended runway (STAR stayed) then inserting into flight plan, everything seems to be normal. I even inserted a step climb later in the route and there are no erroneous UTC times. No more DEST EFOB errors either. Something I didn’t notice either was my cruise speed dropped to M.81, but now is back to M.85. Honestly not sure what I did, but any explanation/advice to avoid this in the future would be awesome.