Matrix Games Forums

I'm not sure if a bug or I'm missing something obvious. Here is the description below. If it sounds like something requiring further investigation I have a save game I will upload.

Bug Report
Game Version: 1.09 1825.15

Subject:

While playing the Rockstar Calling scenario I've noticed various aircraft getting stuck at certain altitudes.


Description:

Aircraft(individual or Groups) whether unassigned and following manual waypoints or on missions like AAW or Strike get stuck at certain altitudes and do not adjust to the desired altitudes whether given manual orders or at waypoints. Selecting briefly the 'Terrain Following - Above Ground' box either manually or at a waypoint fixes it temporarily and the units begin to adjust their attitude to the desired level. However when they reach the next waypoint, if the " Terrain Following - Above Ground" is not selected they will return to that original altitude they were stuck at and not maintain their current altitude or adjust to the desired altitude at least during missions that I've tested.

Unassigning an aircraft and giving it a RTB will also fix the issue however cancelling that and giving the unit a manual waypoint or returning it to it's original mission or adding another mission and it will immediately return to the original stuck altitude ignoring desired manual, waypoint or mission altitudes

In the scenario save I have two strike missions against individual ship targets with a pair of Skyraiders each, with manually adjusted flightplan waypoints. Mission flightplans are running parallel to each other. The one pair of Skyraiders on one mission are making adjustments and keeping to desired altitudes. The other pair on the other mission are stuck at a fixed altitude unless I intervene and make the changes via methods mentioned above. In this case bringing up the throttle adjustment menu, ticking the 'Terrain Following - Above Ground' box on and off and then going to every waypoint ahead and ticking the 'Terrain Following - Above Ground' box.

I've seen problems with a pair of Phantoms on a AAW patrol mission, the other two pairs on the same mission were fine. Likewise on a strike mission of two pairs of A4 Skyhawks got stuck while the other two pairs on their own strike missions worked fine.

I'll point out all these issues were noted while flying over the sea and I've been checking the ASL altitude numbers

I

Its impossible to do anything with just a description, we need a save or scen file

Here you go. Name of the offending unit is in the filename.

Thanks for the report, just be aware that if you want to change the altitude of a unit assigned to a flight plan, you need to unassign the unit since the flight plan overrides the manual altitude. In this case there might be something else going on

Logged 17304

blu3s wrote: Thu Apr 23, 2026 4:28 pm Thanks for the report, just be aware that if you want to change the altitude of a unit assigned to a flight plan, you need to unassign the unit since the flight plan overrides the manual altitude. In this case there might be something else going on

Logged 17304

Thank you. As I pointed out in the description this issue is affecting unassigned units as well.

Thank you, if you have other examples of an unassigned unit (that wasn't in a mission) ignoring altitude, please feel free to update those saves as well