1405 Unable to set altitude in strike mission flight plans

[boogabooga]

I made a quick scenario to test out strike mission flight planning in the new beta, and it did not go well.

I've attached the scenario, and a video where I show the problem. Especially for the IP, the the user can not properly edit the altitude in the flight plan. First of all, the default altitude of 19802 ft is strange and not practical for the weapon type. Second, the Flightplan Editor does not recognize the user input. Third, if the Terrain Following box is checked, then a user-specified altitude change can be recognized by the Flightplan Editor, but it is the wrong number (seems to always be 3038ft).

I'm going to use this scenario as the basis of a few other bug reports.

[blu3s]

While there are other issues related to FPs and altitudes in the new beta (it's a work in progress) this issue should be already fixed.

Thanks for the other reports, we're aware of the different issues and working to fix them

[boogabooga]

While there are other issues related to FPs and altitudes in the new beta (it's a work in progress) this issue should be already fixed.

Thanks for the other reports, we're aware of the different issues and working to fix them

There seems to be an off-by-one error as it is (1436), where flights will take the altitude of the waypoint ahead of the one they are at.