February 28, 20215 yr Hi Gerald, since the latest update of PF3 from a few days ago, the initial contact by the FO is not recognized by PF3. The weird thing is, that it happen most for departure and the first center after it. The FO makes the initial contact to departure and after a short while departure comes up with "Traffic at FL blabla squawking 1234, contact departure on 123.45" the FO doesn´t respond then so i have to hit the "0" key for PF3. Same happens again when the FO is told to contact the center after departure. But the handover from then on from center to center seems to work as normal. May you could have a look on this.😊 Cheers Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
February 28, 20215 yr Commercial Member 19 hours ago, BerndB said: Hi Gerald, since the latest update of PF3 from a few days ago, the initial contact by the FO is not recognized by PF3. The weird thing is, that it happen most for departure and the first center after it. The FO makes the initial contact to departure and after a short while departure comes up with "Traffic at FL blabla squawking 1234, contact departure on 123.45" the FO doesn´t respond then so i have to hit the "0" key for PF3. Same happens again when the FO is told to contact the center after departure. But the handover from then on from center to center seems to work as normal. May you could have a look on this.😊 Cheers Although nothing has changed MCE+PF3 wise within the last month, you never know. Would appreciate is someone else could confirm this so that it becomes priority task. Gerald R https://www.multicrewxp.com
February 28, 20215 yr I haven't done a flight with MCE and the latest PF3 version yet. But whenever I got the "traffic at ... squawking ..." call by PF3 it turned out that the sim window was not the window in focus, because I had been handling the charts on the navigraph charts window, or looked something up on any other window while or before MCE was transmitting. The sim window needs to be in focus for PF3 to recognize the hotkey sent by MCE. Bernd, are you sure the sim window was in focus when you encountered this issue?
February 28, 20215 yr Author 38 minutes ago, RALF9636 said: Bernd, are you sure the sim window was in focus when you encountered this issue? Honestly speaking, of course i´am not.🤔 Because i´am using a homecockpit my SIM is always focused as i´am not using other windows on the P3D-PC. But you never know. I will make sure that the Sim is in focus and will see if it comes up again. Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
February 28, 20215 yr Author 1 hour ago, FS++ said: Although nothing has changed MCE+PF3 wise within the last month, you never know. Would appreciate is someone else could confirm this so that it becomes priority task. By the way, Gerald, wouldn´t it be cool if the MCE FO could also recognizes the call "Traffic at FL blabla, squawking 1234...." and establish the initial contact once again?!?! 😏🧐 Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
February 28, 20215 yr 6 minutes ago, BerndB said: By the way, Gerald, wouldn´t it be cool if the MCE FO could also recognizes the call "Traffic at FL blabla, squawking 1234...." and establish the initial contact once again?!?! 😏🧐 I second that. 😉
March 1, 20215 yr I just completed a flight with the latest MCE and PF3 versions using the FBW A320 in MSFS: Everything worked flawlessly here. It was a most enjoyable flight in every regard.
March 2, 20215 yr Author On 2/28/2021 at 10:42 PM, BerndB said: By the way, Gerald, wouldn´t it be cool if the MCE FO could also recognizes the call "Traffic at FL blabla, squawking 1234...." and establish the initial contact once again?!?! 😏🧐 .hmm...2 days went by already....and no patch! Still. 🤔😔 Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
March 3, 20215 yr Commercial Member 15 hours ago, BerndB said: .hmm...2 days went by already....and no patch! Still. 🤔😔 Espresso is brewing and will be ready within minutes 🙂 Joking aside... Changes were already implemeted to catch that "Traffic at FL blabla, squawking 1234...." some time ago, so that Fo can see it as an instruction to tune frequency when he was earlier seeing it as some message to other traffic (and ignored it). Not sure why he isn't, so we'll have to refine things further. I suggest you send the Clearance.log next time it happens. Need to see wording used and whether it varies. At the moment, FO looks for "Aircraft at" as a hint. Maybe should be on the look-out for "traffic at" as well, assuming all instructions start with only those 2 variations. Gerald R https://www.multicrewxp.com
March 3, 20215 yr Author 1 hour ago, FS++ said: Espresso is brewing and will be ready within minutes 🙂 Joking aside... Changes were already implemeted to catch that "Traffic at FL blabla, squawking 1234...." some time ago, so that Fo can see it as an instruction to tune frequency when he was earlier seeing it as some message to other traffic (and ignored it). Not sure why he isn't, so we'll have to refine things further. I suggest you send the Clearance.log next time it happens. Need to see wording used and whether it varies. At the moment, FO looks for "Aircraft at" as a hint. Maybe should be on the look-out for "traffic at" as well, assuming all instructions start with only those 2 variations. i knew you´ll get it right.😁 I will provide you with the log, of course. I can confirm that i have heard only "traffic at.." yet, never "aircraft". Edited March 3, 20215 yr by BerndB Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
March 3, 20215 yr Commercial Member On 3/3/2021 at 1:22 PM, BerndB said: i knew you´ll get it right.😁 I will provide you with the log, of course. I can confirm that i have heard only "traffic at.." yet, never "aircraft". I actually regret posting the above "un-professional" reply. Sorry about that😟 To raise to "raelonmasters" perceived support standards, let me re-phrase it... Official statement. As you all know, the world has been badly affected by the pandemic and not spared anyone. It has become a real challenge delivering software in a timely manner. We are doing our best to coordinate efforts via Zoom technology with our International workforce spread all over the world.. Your issue has been logged and will be sequenced. We are currently weighing up our options as to how to best address your particular issue. At some point, a package will be built, then submitted to Alpha testers, followed by Beta testers for a final quality control run, at which point package will be deemed fit for release. We are realistically looking at June 2021 time frame at the ealiest. Thank you for using our products. While waiting for this fix, you may want to explore the range of products on offer Yours respectfully. Edited March 9, 20215 yr by FS++ typo Gerald R https://www.multicrewxp.com
March 6, 20215 yr Author On 3/3/2021 at 1:03 PM, FS++ said: I suggest you send the Clearance.log next time it happens. Need to see wording used and whether it varies. At the moment, FO looks for "Aircraft at" as a hint. Maybe should be on the look-out for "traffic at" as well, assuming all instructions start with only those 2 variations. Hi Gerald, as i promised i would provide you a clearace.log, i have attached one of my last flight, where i happened again that the FO missed the handover to center. I have also made sure that the SIM window was allways "in focus". Hope this helps. Delivery Easy 8986 at the terminal IFR with information Victor Easy 8986 Cleared as filed. Squawk 2362 Delta Papa at Flight Level 310 departure Squawk 2362 Delta Papa at Flight Level 310 departure Easy 8986 Easy 8986 Readback correct. Contact Ground on 121.82 When ready to taxi 121.82 Easy 8986 Delivery Lufthansa 2104 at the terminal IFR with information Victor Lufthansa 2104 Cleared as filed. Squawk 6351 Delta Papa at Flight Level 310 departure Squawk 6351 Delta Papa at Flight Level 310 departure Lufthansa 2104 Lufthansa 2104 Readback correct. Contact Ground on 121.82 When ready to taxi 121.82 Lufthansa 2104 Good day Delivery Hansa Line 1938 at the terminal IFR with information Victor Hansa Line 1938 Cleared as filed. Squawk 6535 Delta Papa at Flight Level 310 departure Squawk 6535 Delta Papa at Flight Level 310 departure Hansa Line 1938 Hansa Line 1938 Readback correct. Contact Ground on 121.82 When ready to taxi 121.82 Hansa Line 1938 Lufthansa 1714 cleared to Lima Delta Zulu Alpha on Delta Papa departure Climb to Flight Level 300 Squawk 4234 Lufthansa 1714 Readback correct. QNH 1028 Contact Ground on 121.82 for push and start Easy 8985 Clear of the active runway Easy 8985 taxi to terminal taxi to terminal Easy 8985 Ground Lufthansa 2118 Ready to taxi. Lufthansa 2118 taxi to runway and hold runway 08 right taxi to runway and hold runway 08 right Lufthansa 2118 Ground Lufthansa 2294 Ready to taxi. Lufthansa 2294 taxi to runway and hold runway 08 right taxi to runway and hold runway 08 right Lufthansa 2294 Lufthansa 1714 push and start approved Report When ready to taxi Dolomiti 8253 Clear of the active runway Dolomiti 8253 taxi to terminal taxi to terminal Dolomiti 8253 Lufthansa 1993 Clear of the active runway Lufthansa 1993 taxi to terminal taxi to terminal Lufthansa 1993 Lufthansa 2049 Clear of the active runway Lufthansa 2049 taxi to terminal taxi to terminal Lufthansa 2049 Turkish 1637 Clear of the active runway Turkish 1637 taxi to terminal taxi to terminal Turkish 1637 Lufthansa 1714 stand by Lufthansa 1714 Roger. Taxi to holding point, runway 08 Left using taxiway Oscar 2 Whiskey 2 November 3 November Alpha 2 Alpha 1 Ground Adria 157 Ready to taxi. Adria 157 taxi to runway and hold runway 08 right taxi to runway and hold runway 08 right Adria 157 Dolomiti 8247 Clear of the active runway Dolomiti 8247 taxi to terminal taxi to terminal Dolomiti 8247 Ground Transavia 5202 Ready to taxi. Transavia 5202 taxi to runway and hold runway 08 right taxi to runway and hold runway 08 right Transavia 5202 Ground Lufthansa 2054 Ready to taxi. Lufthansa 2054 taxi to runway and hold runway 08 right taxi to runway and hold runway 08 right Lufthansa 2054 Dolomiti 1967 Clear of the active runway Dolomiti 1967 taxi to terminal taxi to terminal Dolomiti 1967 Lufthansa 1714 Contact Tower on 120.5 Lufthansa 1714 runway 08 Left Hold short Lufthansa 2118 Winds 040 at 8 Cleared for takeoff runway 08 right Cleared for takeoff Lufthansa 2118 Adria 157 Line up and wait runway 08 right Roger runway 08 right Line up and wait Adria 157 Lufthansa 2118 Contact departure on 123.6 Roger 123.6 Lufthansa 2118 Lufthansa 1714 Line up and wait runway 08 Left Hansa Line 2163 exit runway at next available taxiway Contact Ground on 121.82 when clear of the active next available taxiway Contact Ground when clear of the active Hansa Line 2163 Adria 157 Contact departure on 123.6 123.6 Adria 157 Lufthansa 1714 Winds 040 at 8 runway 08 Left Cleared for takeoff Tower Hansa Line 2151 at 8 Miles for Landing Hansa Line 2151 Continue present heading Continue present heading Hansa Line 2151 Tower Pollot 375 at 9 Miles for Landing Pollot 375 continue Approach Continue present heading Pollot 375 Lufthansa 1714 Contact departure on 123.6 Lufthansa 1714 Roger Squawk Ident QNH 1028 Lufthansa 1714 No speed restriction Transavia 5202 Turn right heading 080 Turn right heading 080 Transavia 5202 Lufthansa 2118 Turn left heading 335 Turn left heading 335 Lufthansa 2118 Lufthansa 1714 Contact Munich Radar on 118.35 Lufthansa 1714 Roger Munich Radar Austrian 288 Level at Flight Level 150 Austrian 288 Roger Transavia 5202 Climb and maintain Flight Level 150 Climb and maintain Flight Level 150 Transavia 5202 Munich Radar Easy 2072 with you level Flight Level 110 Easy 2072 Roger Easy 2072 Climb Flight Level 150 Climb Flight Level 150 Easy 2072 Austrian 288 Descend and maintain Flight Level 110 Descend and maintain Flight Level 110 Austrian 288 Munich Radar Lufthansa 2054 Level at Flight Level 100 Roger Lufthansa 2054 Munich Radar Easy 1486 with you Flight Level 320 Easy 1486 Roger Continue present heading Easy 1486 Lufthansa 1714 Climb and maintain Flight Level 300 Munich Radar Emirates 76 is with you, level at Flight Level 390 Emirates 76 Roger Munich Radar Etihad 38 Out of Flight Level 370 Etihad 38 Roger Lufthansa 1714 Contact Control on 125.45 Control 450 Level at Flight Level 260 Control Etihad 38 is with you at Flight Level 370 Roger Etihad 38 Traffic at Flight Level 245 squawking 4234 Contact Control on 125.45 Traffic at Flight Level 260 squawking 4234 Contact Control on 125.45 Lufthansa 1714 Roger Control Croatia 491 Level at Flight Level 330 Roger Croatia 491 Control Victor Oscar Lima 1467 with you out of Flight Level 240 Victor Oscar Lima 1467 Roger Lufthansa 1714 Climb Flight Level 340 Lufthansa 1714 Contact Vienna Radar on 129.2 Lufthansa 1714 Roger Lufthansa 1714 Traffic at 12 o'clock 10 Miles Flight Level 320 Heading West 310 Kestrel 1301 Traffic at 12 o'clock 10 Miles Flight Level 315 Heading East 110 Traffic at 12 o'clock Kestrel 1301 Vienna Radar Etihad 38 is with you, out of Flight Level 370 Etihad 38 Roger Continue present heading Etihad 38 Vienna Radar Victor Oscar Lima 1467 with you out of Flight Level 180 Roger Victor Oscar Lima 1467 Victor Oscar Lima 1467 Descend to Flight Level 160 Roger Down to Flight Level 160 Victor Oscar Lima 1467 Vienna Radar Kestrel 1301 with you Flight Level 320 Roger Kestrel 1301 Lufthansa 1714 Climb and maintain Flight Level 350 Lufthansa 1714 Contact Control on 130.6 Lufthansa 1714 Roger Control Etihad 38 Out of Flight Level 370 Etihad 38 Roger Lufthansa 1714 Descend to Flight Level 330 Lufthansa 1714 Descend to Flight Level 330 Lufthansa 1714 Descend to Flight Level 250 Lufthansa 1714 Traffic at 9 o'clock 5 Miles Flight Level 340 Heading West 310 TUI Jet 4103 Traffic at 10 o'clock 5 Miles Flight Level 340 Heading South 135 has the traffic TUI Jet 4103 Lufthansa 1714 Descend to Flight Level 200 Lufthansa 1714 Descend to Flight Level 180 Lufthansa 1714 Descend to Flight Level 140 Lufthansa 1714 Reduce speed to 280 Lufthansa 1714 Descend and maintain Flight Level 90 Lufthansa 1714 Reduce speed to 260 Lufthansa 1714 Contact Approach on 128.5 Lufthansa 1714 Lufthansa 1714 at Kilo Oscar Tango Oscar Romeo Descend and maintain 3 thousand on 1025 Cleared to final for Sierra Tango Approach runway 04 when ready Contact Tower on 118.3 when established. Lufthansa 1714 Reduce speed to 220 Lufthansa 1714 Reduce speed to 200 Lufthansa 1714 continue Approach you're number 1 for Landing Lufthansa 1714 Winds 040 at 6 QNH 1025 Cleared to land runway 04 Lufthansa 1714 exit Right next available taxiway Contact Ground on 121.85 when clear of the active Lufthansa 1714 hold your position Lufthansa 1714 hold your position Lufthansa 1714 Roger. Taxi to Stand Echo 6 using taxiway Edited March 6, 20215 yr by BerndB Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
March 20, 20215 yr Commercial Member On 2/28/2021 at 1:00 AM, BerndB said: Hi Gerald, since the latest update of PF3 from a few days ago, the initial contact by the FO is not recognized by PF3. The weird thing is, that it happen most for departure and the first center after it. The FO makes the initial contact to departure and after a short while departure comes up with "Traffic at FL blabla squawking 1234, contact departure on 123.45" the FO doesn´t respond then so i have to hit the "0" key for PF3. Same happens again when the FO is told to contact the center after departure. But the handover from then on from center to center seems to work as normal. May you could have a look on this.😊 Cheers Should be sorted in latest patch Gerald R https://www.multicrewxp.com
March 21, 20215 yr Author Hi Gerald, thank you much for the patch. I´ve installed it and, yes now the FO responds perfect to "traffic at FL123, sqawking....", but it seems something else is messed up with PF3. First thing, i have monitored that my FO has correctly called the next center for initial contact like, "Munich Radar, Lufthansa 123 out of blabla..". Then nothing comes back. After few seconds they call "traffic at blabla..." and my FO responds by tune the frequency and make the initial contact again. But again no response and instead again the call "traffic at..." which is answered by the FO in another initial contact. It took 4 tries and after the last Munich radar came back with "Roger Lufthansa 123". Second misbehavior is, if i am at cruise at lets say FL350 and want to descent earlier, i usually ask my FO "request FL300" and it worked perfect in the past. Now it happened that he´s not call for decent to lower altitude, but he ask for LH123 reqest higher altitude FL 300. and PF3 responds with "Roger climb to FL 380. 🤨 Third issue is that now the FO seems not to see the next frequencies. Usually at approach after handed off by approach controller for final i command the FO "going to tower" and allways he tuned the correct freq. and responds like "Presto, Com1, 118.05,...done!" But since the patch he can´t see the freq and responds like "Sorry missed that, what frequency?" An i need to tune the correct freq myself. Bernd P3D V6 - PC spec: Intel i9-9900 overclocked 5 GHz HT off, 32 GB RAM, GPU Nvidia RTX3090 24GB, 2xM2 SSD, Skalarki HomeCockpit and Jeehell FMGS on a dedicated Server, PF3 for ATC, MCE, GSX, EFB, AS+ASCA+ENV and OrbX
March 22, 20215 yr Commercial Member 18 hours ago, BerndB said: Hi Gerald, thank you much for the patch. I´ve installed it and, yes now the FO responds perfect to "traffic at FL123, sqawking....", but it seems something else is messed up with PF3. First thing, i have monitored that my FO has correctly called the next center for initial contact like, "Munich Radar, Lufthansa 123 out of blabla..". Then nothing comes back. After few seconds they call "traffic at blabla..." and my FO responds by tune the frequency and make the initial contact again. But again no response and instead again the call "traffic at..." which is answered by the FO in another initial contact. It took 4 tries and after the last Munich radar came back with "Roger Lufthansa 123". Second misbehavior is, if i am at cruise at lets say FL350 and want to descent earlier, i usually ask my FO "request FL300" and it worked perfect in the past. Now it happened that he´s not call for decent to lower altitude, but he ask for LH123 reqest higher altitude FL 300. and PF3 responds with "Roger climb to FL 380. 🤨 Third issue is that now the FO seems not to see the next frequencies. Usually at approach after handed off by approach controller for final i command the FO "going to tower" and allways he tuned the correct freq. and responds like "Presto, Com1, 118.05,...done!" But since the patch he can´t see the freq and responds like "Sorry missed that, what frequency?" An i need to tune the correct freq myself. In MSFS, there is a limitation with regards which Frequencies Fo can dial. The current SDK only increments/decrements VHF freqs by 25 khz. Asobo introduced 5 khz capability but didn't update SDK. With native ATC, MCE FO will typically select the option in menu so that it gets dialled by the sim itself. In PF3, could be better off running in FSX/Prepar3D compatibility mode (PF3 has that) so that Fo can dial as usual. Eventually, could get Fo to notify you to dial a specific freq when he wouldn't be able to do that himself. Nothing has changed with regards hotkey to request higher or lower for many, many months. It is assumed when you made request for FL 380, you had 35000 showing in autopilot. Which plane by the way? Gerald R https://www.multicrewxp.com
Archived
This topic is now archived and is closed to further replies.