Minor Bugs in v3.2.0

[scott-j-smith]

Hi Erik,

Started playing on the new version yesterday and noted a few bugs that are the same on at least 3 different airports:

1. Fly Heading (fhxxx) command not working

2. Audio voice read-back of commands sometimes says current altitude instead of target altitude when issuing a climb or descend (e.g. if at FL80 and issue command "d 40" the audio will read back " maintain 8000"), but the aircraft will still descend.

3. Arriving aircraft change heading to 360 at the end of their assigned routes now

Let me know if you need further details.
Thanks,
Scott

[Shirtail]

I've got the same problem Scott. It just started acting up as of yesterday.

[eliuuk]

The fly heading command has changed, it's no longer fh### but instead fh ### with the space. There are some efforts at the moment to update the in-game tutorial.

[n8rzz]

@scott-j-smith @Shirtail

Hey guys!

1. was very much intentional. We completely re-wrote the CommandParser with this release and, as such, that command has changed.

2. is a known issue in my fork (After completing flightplan, aircraft all turn to heading 360 n8rzz/atc#206) and will be addressed sometime soon.

3. seems legit, we will have to investigate that one a little more.

[scott-j-smith]

Thanks for the note about he command parsing. I guess I should read the release notes. :-)

Regarding #3, I also saw the same behavior for departing aircraft playing on LKPR - maybe I didn't see it on the other airports I played because they left the airspace before reaching the end of their routes?

And I had an issue on LKPR where I had a departing aircraft waiting to take off, while another one was landing. When the arriving aircraft switched to ground and was removed from the screen, the game also removed the departing one waiting to take off! The flight strip was still on the right side, but the white dot and the box were gone -- and I could not issue it any commands (like the command line was frozen -- I didn't even get the "command not understood" read back). I could still work with other planes though, and the rest of it seemed to still work. Sorry, but I closed the window by mistake when I mean to resize it to take a screenshot, so I don't have a console view or anything else for you to help explain it. If I see this again I'll let you know more details.

Thanks,
Scott

[scott-j-smith]

Well, that last issue I just reported (call it #4) happened again on the same airport. Screen shot below.

Flight CSA814 was waiting and another plane just landed and switched to ground... now CSA814 disappeared from the map view, and is frozen.

There are a lot of departure route errors in the console view too, but probably unrelated?

[Forthwrong]

In addition to encountering 2 and 3, in EGLL I also experienced arrivals that were greyed out even after entering well into my airspace. I believe this has to do with altitude, as I only received descending aircraft. On several occasions, I encountered arrivals that stayed at a particular altitude and always stayed greyed out, out of my control, after passing the last fix in their route (and obviously then heading to 360, as mentioned earlier).

[erikquinn]

in EGLL I also experienced arrivals that were greyed out even after entering well into my airspace. I believe this has to do with altitude, as I only received descending aircraft. On several occasions, I encountered arrivals that stayed at a particular altitude and always stayed greyed out, out of my control, after passing the last fix in their route (and obviously then heading to 360, as mentioned earlier).

This sounds to me like an airport design problem... like perhaps they are at an altitude that is outside of the altitude range of the airspace?

[eliuuk]

@erikquinn Probably, I'll have a look at that. The only problem is that EGLL has a fictional airspace, and descend altitudes are not clearly documented on charts as controllers in the UK descend each aircraft manually, and not through a 'descend via STAR' command.

[Shirtail]

A/c clrd to a lower altitude on initial contact, a/c responds "maintaining" whatever the assigned enroute altitude is, but then descends to the lower altitude anyway. Happens at all a/ps as far as I know .

[scott-j-smith]

Issue 4 is not airport specific - same thing happened to me just now playing LOWW. The game deletes the plane from the waiting queue, it disappears from the map view, and you can issue the takeoff command to the next plane in line (what was number 2 before) and it works... but it leaves the flight strip for the deleted plane on the right hand side.

[georgeenciu]

Happened to me before and this one looks like it's going the same way. After the exit point (OSPEN in this case) the plane will turn heading north, re-enter the radar, exit, and award me 10 extra points :)

[Fechulo]

Issue 5: assigning an altitude to an aircraft before being cleared as filed doesn't work and throws the following error

[panther2]

Yes, issue 5 is addressed here:
n8rzz#228

[erikquinn]

Notice to airmen:

If additional new issues are encountered, please add individual issues for them rather than adding on to this one; that will make the tracking of the fixes much easier. :)

EQ

[erikquinn]

1. working properly (command syntax changed)
2. Covered in Improper altitude readbacks #769.
3. Covered in After completing flightplan, aircraft all turn to heading 360 n8rzz/atc#206, part of v3.2.1 (which is still pending)
4. Covered in Arrivals' landings cause "waiting" departures to be deleted #770.
   4a. (inaccessible "greyed out" aircraft) Root cause is covered in Aircraft do not always reach target altitudes #777.
5. Covered in Cannot assign altitudes... n8rzz/atc#228.

All items are addressed in other issues. Closing.