Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Helix1250

Members
  • Joined

  • Last visited

  1. I have to say I've seen a huge difference in the response recognition since swapping to the clearance log method. I've also tried using TTS voice packs and was stunned to hear my FO request clearance to the airport name (Arlanda) and not use the ICAO ESSA. I hope it works for you Starter. Rob
  2. Hi Starter, Can I ask if your using closed captions or the PF3 log file method? I ask as I've been experiencing recently my FO not responding to PF3 and not responding to reedbacks. Anyway I turned off closed captions and started using the PF3 log method. This improved things a great deal, I just miss the visual confirmation on screen. Might be worth you trying this and see how you get on. Rob
  3. Is MCE utilising the PF3 log file or does it still require Closed captions? Rob
  4. Sorry can you tell me in idiot form how this is done please? I have got pretty much everything working, with the exception of the contact ground after landing. i just want to tweak things to how I want to say them. Rob
  5. I'll give it a try in a few days! I managed to destroy data on my windows and sim drive! I was a 14 carrot plank and clicked a wrong button.
  6. Tonight my MCE just stoped working, first it picked up what I was saying and did nothing, then stopped picking up the things I said altogether. This lead to a MCE hang, and I had to close it. nothing else was affected and I finished my flight manually. My Event log is as follows. The program mce.exe version 2.7.1.6 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 1d5c Start Time: 01d2ed192c2aa9f7 Termination Time: 5 Application Path: C:\Program Files (x86)\Multi Crew Experience\mce.exe Report Id: 916ea4f9-79eb-47e5-bbe6-b6cace0f288c Faulting package full name: Faulting package-relative application ID: Rob
  7. Huge thank you to you guys at FS++! I did my first flight with the Dash with the latest update and not only have you fixed the ARCDU (incorrect inputs) issue but the FO was able to deal with all aspects of comms with out a hitch. I only had to intervene with a runway change, other than that it was perfect! I look forward to testing other functions on my next flight! I just hope others have had the same positive experience with the latest update. Rob
  8. Lets hope that's a couple of the irritating things of your list RALF9636 :)
  9. Thanks for the reply, I'll change my PTT key to caps lock for tonight's flight. Cheers Rob
  10. Is that the PPT mute, or the Auto Mute that you need to use the tick box your referring to? This is where it gets confusing Rob
  11. Can I confirm that you mean the PF3 Auto mute must be now checked? am I reading the comment below correctly? "After running tests with extreme traffic at Heathrow, it's obvious there is no way one can do without that PF3 mute key. Therefore, from now on, MCE will ensure the option (Hotkey 22) is always enabled." Maybe once all the dust settles with the latest updates and new releases we could have a standard setup document produced to confirm what we actually need to activate or deactivate to get MCE and PF3 to interface correctly. So far I am just trying to piece the installation together from snippets of posts. Rob
  12. Sorry to say that I am back to having MCE hang while running a flow (which is taking forever in PvDv3.4) and using PF3. always sees to happen when my FO might be reading back a frequency he's just dialed in.
  13. Okay I have done a quick test and I have found out possibly why I am having trouble getting departure clearance. I have been trying to get departure from LIRN, this airport does not have a clearance/delivery frequency. So I have tuned to ground (121.90) and asked for departure clearance "Jersey 3570 requesting IFR clearance to Corsica", with this I get odd stuff being picked up, runway changes etc. But if I stay on 121.900( Ground) and use " Clearance jersey 3570 requesting IFR clearance to Corsica" Bingo it works. I have tested this a few times now and it comes back the same each time. Basically you can not use the word "Ground" even though your connected to ground for clearance, you have to call ground "Clearance" and then it works. No I am not saying that what I am experiencing is the same for others, but certainly in my case. With the new Patch I have not had any hangs and CTD, I will continue testing and feed back what I find. Rob edit: I don't seem to be able to get taxi clearance if I ask for it myself, I used "Ground Jersey 3570 ready to taxi", maybe I'm not using the correct term. My FO has no issues with obtaining taxi clearance.
  14. Thanks I'll give the patch a try tomorrow night. To answer your questions, no I have turned auto mute off in PF3, I'm using a saitek yoke and have PTT set to button 2. And no I have not emulated it via FSUIPC, I try to keep things as simple as possible. ill test the new patch tomorrow and let you know how I get on :) Rob
  15. Hi Richard, I have just been trying the "jersey 3570 ready to copy IFR clearance to LFKJ" but still no joy I am afraid! This time the fire truck was called as result of my request :) I have also found that MCE has stopped picking up my yoke button press at times. Rob I have had to uninstall the latest patch and go back to 2.7.0.6 in an attempt to stop MCE crashing. 2.7.0.6 picks up my commands and doesn't crash, so not sure what has changed in the latest updates.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.