124thATCv2 Forum

Using 124th (60RC27) to control my flight from Cardiff to Amsterdam (EGFF - EHAM) I noticed during the descent phase there is still the problem where the "to" part of the message is missing please see below exerts from my log showing all 3 descent sections, in each case the "calling descent to: XXX" is issued but during the communication to the pilot only the word "descend" is used, in the Bug Tracker 319 is marked as resolved but not tested, looks like there is still a problem

exerts from my log

124thATC v2.0-a60RC27 20:33:51: calling descent to: 15000
124thATC v2.0-a60RC27 20:33:51: Success opening registry, writing key...
124thATC v2.0-a60RC27 20:33:51: Switching voice for Klm @1060@: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\TTS_MS_EN-GB_HAZEL_11.0
124thATC v2.0-a60RC27 20:33:51: Success writing to Registry.
124thATC v2.0-a60RC27 20:33:51: Communication: Klm 1060, descend flight level 150

124thATC v2.0-a60RC27 20:52:25: calling descent to: 7000
QNH adjusted!
124thATC v2.0-a60RC27 20:52:33: Success opening registry, writing key...
124thATC v2.0-a60RC27 20:52:33: Switching voice for Klm @1060@: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\TTS_MS_EN-US_DAVID_11.0
124thATC v2.0-a60RC27 20:52:33: Success writing to Registry.
124thATC v2.0-a60RC27 20:52:34: Communication: Klm 1060, descend flight level 70

124thATC v2.0-a60RC27 20:56:21: calling descent to: 2900
124thATC v2.0-a60RC27 20:56:21: Success opening registry, writing key...
124thATC v2.0-a60RC27 20:56:21: Switching voice for Klm @1060@: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\TTS_MS_EN-US_DAVID_11.0
124thATC v2.0-a60RC27 20:56:21: Success writing to Registry.
124thATC v2.0-a60RC27 20:56:21: Communication: Klm 1060, descend 2900 feet, QNH 1013, transition level 60


the "calling descent to" get issued but the "descend to" command does not get issued in the communication, only the "descend", the "to" is still missing

Shane Dallimore

find attatched

bugreport & screenshot (no TO comment ISSUE 319) taken as lowest descent command is issued

Hi Shane,
happy to see you back. Bug confirmed, it should be addressed in the next build, thanks for reporting.

a.