When I load a flight plan from my app to the sim, the CRZ ALT maxes out at FL280, when the loaded altitude is higher (10668m -> 34,996.72 ft). If I set lower CRZ ALT it works great, and if I press the MCDU/FMC button, it gets the right data. Tested on Airbus and Boeing planes too.
CRZ FL FL280 maxes out on flight plan loading
-
Jet-Pack (IPACS)
July 23, 2026 at 9:44 PM Moved the thread from forum Bug Reports - General to forum Modding & User Content. -
- Official Post
When loading the route the sim computes the maximum possible altitude for the distance to fly and reduces the planned cruise altitude if needed.
The cruise altitude that you enter in the MCDU is not the same as the one from the route, it's a different aircraft state. It gets deleted when the descent phase is reached, where as the cruise altitude of the route remains unchanged.
-
When loading the route the sim computes the maximum possible altitude for the distance to fly and reduces the planned cruise altitude if needed.
The cruise altitude that you enter in the MCDU is not the same as the one from the route, it's a different aircraft state. It gets deleted when the descent phase is reached, where as the cruise altitude of the route remains unchanged.
When I modify the main.mcf with my app, it sets the altituide to FL350. When I open the sim with this options, I got the FL280.
Then I set the same route in the in sim editor, it works with the FL350 instantly.
But if I restart the sim, it drops the CRZ FL again. And never made a manual input in the MCDU or changed the CRZ FL after setting it.
So it is something with the reading from the main.mcf.
Computing the maximum altitude for the distance would work with 1 type of aircraft, but not with many. Tested it with all the A320 family and the 737 family. Tested it on longer routes, like the LHBP-EGLL, which is more than enough for FL350 or more.
