I’ll tell you, it’s most likely just a bug of the dispatcher, you had to send your data from the tablet to atc so that there would be no disagreements, most likely you were not allowed to change the height at all
I understood it approximately from your screenshot
I think issue is not with OP aircraft but the instructions ATC is providing to the AI Live Traffic, to descend from a high FL to 2700ft.
@Cpu8088 : please do not delete the sections of the template, I have added them back. Fill in the description one so that devs/users can clearly understand what you are reporting. Thank you !
They are also always at the wrong altitude given how often ATC needs to tell them they are not at their assigned altitude and to climb/descend. They are also always at below 3000 feet for some reason, I have not seen anyone at high altitudes being told to change altitude.
EDIT: Upon reading it again this actually seems completely valid. They are told to descend and maintain 2700ft while we know they are above FL200. Discussion can be had on whether this is realistic or not but otherwise it seems fine.
Hi, the problem was that, imho the ATC is telling another aircraft (not the one I am in) to descend and maintain 2700ft while that specific aircraft is flying at probably 30000ft or in any case much higher than me being as you can see at 20000ft. So, even if in theory the message can be applied, it doesn’t make sense because these kind of flight level changes happen gradually and they are communicated by a Tower as part of an arrival procedure or approach procedure. If an aircraft is flying high at high speed you just should not receive a message like that.
Consider that there was also a mountain area at 2000ft so descend and maintain 2700ft with no airport in sight it doesn’t make sense.
That was all from my point of view but maybe they tell me: it’s not a bug but a feature …
I use FSTL, and all the aircraft that appear within my range, the ATC asks them to descend and maintain around 2,700 feet. That is, my aircraft is at cruising altitude, around 37,000 feet, a traffic aircraft appears, for example, at 35,000 feet, and the ATC simply asks it to descend to the said 2,700 feet, even though that traffic aircraft is still far from its destination, like several hours away! I’m using Little Navmap, and when I’m on the ground, I see planes taking off and staying at a very low altitude. Instead of climbing, they descend, making the simulation totally unrealistic.
That sounds more like the AI traffic clearance logic than a single bad phrase. If the aircraft is still enroute and far from its destination, a direct descent to 2700 ft is not very useful even if 2700 is a valid local altitude somewhere. For the bug report, I would include a Little Navmap screenshot with the AI aircraft selected, its altitude, destination or ETE if available, and your own position. That would make it easier to show that ATC is issuing terminal-style altitudes to enroute traffic rather than just giving an early descent.
Description of the issue: When having AI traffic enabled and listening to the radio comms, what I would assume are airliners are being assigned extremely low altitudes like under 5000 ft.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Almost every flight.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Overall, I don’t see a problem with these messages. I’ll explain why: first, all AI traffic operates based on its own internal data; second, you won’t run into them anyway. I’m concerned about a different issue: real‑time traffic disappeared from the tablet after the game update.
Experiencing the same issue. I was on a transatlantic flight, and all AI traffic was flying down the sea. ATC kept instructing them to descend and maintain 2 000 ft or so. This is definitely not realistic.
I experienced that whatever the AI Traffic source.
…
