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.

FS++

Commercial Member
  • Joined

  • Last visited

Solutions

  1. FS++'s post in 2 Questions pronunciation & Call sign was marked as the answer   
    1 - I assume you have some reason for wnting to use TTS voices instead of the already available 9 human recorded co-pilot voices.
    I'm not sure, but I believe you can adjust a few things like pronounciation under "voice properties" in IVONA panel.
     
    2 - If you're referring to Native FSX or Prepar3D, MCE would typically read the current aircraft callsign. It varies from one aircraft to the other. You can change it as follows..
     
    Click FSX menu Aircraft settings. When the dialog box appears, click <Details> button. You will get the option to select an airline and a flight number.
     
    Once you close the dialog box, MCE should retrieve the new call sign and you can ask co-pilot. "what is our call-sign?" to find out if he's in synch.
  2. FS++'s post in Purser Voice too feeble was marked as the answer   
    It's on purpose. Since she'd be instructing her colleagues to close the doors via the cabin PA system, it's barely audible to you (assuming cockpit door is closed). You only hear purser properly, when she/he pops-in the cockpit to report something or confirm what you requested is done.
  3. FS++'s post in After takeoff flow and checklist was marked as the answer   
    Affirmative, you've got the hang of it.
     
    Simply add actions or remove some and you will have the perfect SOP for the real world or virtual airline you're flying. No arguing about who opens the fuel levers or handles the landing lights.
  4. FS++'s post in FO Runway Confusion was marked as the answer   
    There are 2 possible ways to address the issue.
     
    1 - Update files in \Multi Crew Experience\NavData\ folder to reflect the changes.
     
    2 - Get co-pilot to ask you to confirm the runway you mentioned is the correct one, when there is a discrepancy.
     
    Will try to implement option 2 in next update, so for expected runway say 22, 21 or 23 (and the variants, L, R, C) would be considered acceptable answers.
  5. FS++'s post in MCE-GSX Strange pushback behavior was marked as the answer   
    This has been reported in the "If you find something not working..." thread. Solved since.
     
    Just install latest GSX and latest MCE V2.6.3.9
     
    http://www.multicrewxp.com/Downloads.html
  6. FS++'s post in Speech recognition configure was marked as the answer   
    Not sure what version you're running. Suggest you download and install latest
     
    http://www.multicrewxp.com/Downloads.html
     
    If running Windows 8, you may eventually try running the wizard (xpwiz.exe) in Win 7 compatibility mode
  7. FS++'s post in Mechanic, Ground com not working was marked as the answer   
    There are conditions in place to prevent mechanic popping-up by accident.
     
    Assuming you are running one of the latest versions, if all engines are running, MCE assumes the command was given (detected) by accident. You must shut at least one engine down.
     
    Also, to make sure your "mce.ini" config file is in synch with latest releases, restore MCE to factory settings
     
    Click Start->All Programs->Multi Crew Experience->Tools->Restore factory settings.
     
    That will force you to go through the wizard. No need for speech training though.
  8. FS++'s post in MCE not working to make any physical changes to aircraft was marked as the answer   
    In addition to what Will mentioned above.
     
    Make sure fsx.exe is set to run as administrator.
     
    If you want to keep Windows UAC enabled, you'll need to install MCE to default \Program Files...\ folder.
     
    You may as well update to 2.5.7.8
  9. FS++'s post in Option for toggling the startup scenery scan was marked as the answer   
    The purpose is to find every single "aircraft.cfg" file
     
    A few years ago, it used to scan only the <Simobjects> folder.
     
    Some users drew our attention to the fact some imported FS9 aircraft may reside outside that folder, therefore it will scan the whole FSX folder.
     
    It doesn't actually open any files. Just enumerates the files in every folder and takes note of the path when it finds "aircraft.cfg".
     
    All found aircraft.cfg files paths are stored in "fscfgPaths.cfg" file found i same folder as "mce.ini"
     
    Maybe it's taking a minute because you have massive amounts of AI traffic, possibly duplicates (backups).
     
    Could you send your "fscfgPaths.cfg" file?
     
    Thanks
  10. FS++'s post in 737NGX intermittent problem with MCP was marked as the answer   
    It can happen sometimes when you start MCE before the NGX has finished initializing itself.
     
    Avoid giving verbal commands until you see "[MCE] ready to go"  in red font 
     
    No need to re-install NGX, FSX or MCE.
     
    Make sure "fsx.exe" is set to run as administrator.

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.