May 14, 201610 yr Author Ok, thanks a lot regarding the next update. I tried two times again, and, well, my check in at the tower frequency gets recognized. E.g. "Tower, good morning, callsign, ready for departure" or "Tower, good morning, callsign, at the holding point runway 33". MCE reacts on it. But it seems to me with Hotkey 0, not Hotkey 6. Well, at least I get exactly the same wrong answer when pressing Hotkey 0 manually. Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
May 14, 201610 yr Author An excerpt from PF3 logfile. I did not touch the keyboard during that, so it's only based on MCE voice recognition : 5/14/2016 6:00:45 PM: 990 - Transcript: 'Easy 462 Contact Tower on 118.3 '5/14/2016 6:01:03 PM: 110 - ****** HotKey #10 detected!5/14/2016 6:02:01 PM: 660 - ****** HotKey #0 detected!5/14/2016 6:02:03 PM: 840 - Transcript: 'Easy 462 stand by '5/14/2016 6:02:07 PM: 200 - Transcript: 'Easy 462 Roger. Taxi to holding point, runway 33 using taxiway Sierra ' Hotkey 10 gets send after my readback, That's fine. But Hotkey 0 gets send by MCE after my Tower check in phrase ("Tower, good morning, callsign, ready for departure"). Should be Hotkey 6. With "0" one gets the weird answer from PF3 above,because I am already at the holding point. Tower is the only facility which needs Hotkey 6. All others Hotkey 0. I'm new to PF3, I don't know if that was already the case in the previous PFE. Maybe not ? Of course not 100% sure, maybe there's another reason why MCE sends the "0" ?? Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
May 16, 201610 yr Commercial Member Of course not 100% sure, maybe there's another reason why MCE sends the "0" ?? Found the reason. There was another speech rule in the PFE grammar that would accept "Ground callsign is ready for departure" as part of request for ATC clearance. And it's a common, and valid verbiage to request clearance in Europe. Because the ATC clearance related rule was sitting above the one for takeoff request, speech engine picked it up and MCE sent key 0 thinking it was ATC request. Could be sorted without touching source code and simply removing the verbiage from ATC clearance request pool and replacing grammar in <CandC> folder However, need to maintain the flexibility, therefore, it will be handled internally in "mce.exe" to make sure the request is seen in the proper context and correct key sent accordingly. Gerald R https://www.multicrewxp.com
May 16, 201610 yr Author Oh, OK, I understand. So there will be another patch ? For the time being, what would be a proper phrase to check-in with Tower, just for testing ? I tried something like “Tower, good morning, Callsign, at the holding point Runway XX“. But that didn`t get recognised. Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
May 16, 201610 yr Commercial Member “Tower, good morning, Callsign, at the holding point Runway XX“. But that didn`t get recognised. It's a perfectly valid request and i should have been accepted. Again, it's a glitch in the Grammar. Normally there are 2 speech rules to handle first contact with ATC, some with Greeting in the beginning and others without. Somehow, when endlessly editing those grammar files, at some stage there was an error, and the "good morning" (or other forms of greeting) aren't expected there. Which means right now only “Tower, Callsign, at holding point Runway XX“ (and without the "the" in the middle, until grammar is updated yet again) is expected to be recognized. Instead or releasing another patch, suggest you get in touch with support and you will be sent updated grammar files today. The full MCE package will be updated later this week, as some people aren't comfortable with the patching process. Gerald R https://www.multicrewxp.com
May 16, 201610 yr Author Ok, will do. And thanks for the excellent support ! Mike 1. A320 home cockpit (FSLabs, Skalarki), P3Dv5 Main PC : I7-12700K, GTX3080Ti 2. FSLabs A3xx, P3Dv5. Gigabyte Aorus 17G YC, I7-10700K, RTX 3080
October 22, 20169 yr I have exactly the same issue as the OP. I installed the current version of both MCE and PF3 yesterday (full version of PF3). So can I ask what the status is with contacting Tower from the holding point or is there a work around? Thank you
October 23, 20169 yr For anyone else reading this thread it is critical that: 1. Change PF3 hotkeys to something like shift+c, shift+v etc 2. Remove corresponding conflicting key assignments in P3D After doing that I now get the taxi monitor. Onwards and upwards!
May 7, 20179 yr Mikealpha, is PF3 workable with the current MCE version or you just ditched the idea? Thanks,
Archived
This topic is now archived and is closed to further replies.