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.

What can it do ?

Featured Replies

  • Author

I will give it a shot hopefully it doesn't detect that the old demo was already installed earlier and denies me the new demo, I'll wait till Saturday get nice 3 full days off it. Hopefully !

  • Author

Ok I confirm that the new Demo does work OK and I was able to try it, I still have 2 days left and some starts.

So far I like the part of telling him to set ALT/HDG/Flaps etc.. this seems to work OK for the most part, sometimes I tell him to set something to XXX he keeps on re-asking me that for some reason. I find the copilot very hectic in his behavior, I turn off "speak a lot".

Not really sure what's up with the checklist.. I am thinking I am expected to know the sequence of FLOW's (fair enough).. checklists are easy as they are listed on main panel in sequence, but the copilot doesn't do anything (flips switches) just reads checklist, later I see i have to call for flows they are listed somewhere in VOXSCRIPT I think it was called.. that made the copilot do some stuff in rather again hectic way.. but he did it in A320FBW "kinda"... it was ok...

In Aerosoft CRJ the only thing that seemed to work was having him change Heading and if i recall ALTITUDE that's about it, checklist would not allow to be enabled kept on reverting to OFF Unchecked in main programs panel.

Suggestion (unless I missed it) add a mute button for when I am talking to VATSIM controller or something. I think i saw somewhere NUMLOCK suppose to do it.. not sure.. again I just played with it for short time.

Anyhow, I will try it a bit more .. but I think it will be a pass for me.

Thanks for fixing the DEMO !

Andy

  • Commercial Member
On 4/3/2022 at 6:43 PM, AndyCYXU said:

Ok I confirm that the new Demo does work OK and I was able to try it, I still have 2 days left and some starts.

So far I like the part of telling him to set ALT/HDG/Flaps etc.. this seems to work OK for the most part, sometimes I tell him to set something to XXX he keeps on re-asking me that for some reason. I find the copilot very hectic in his behavior, I turn off "speak a lot".

Not really sure what's up with the checklist.. I am thinking I am expected to know the sequence of FLOW's (fair enough).. checklists are easy as they are listed on main panel in sequence, but the copilot doesn't do anything (flips switches) just reads checklist, later I see i have to call for flows they are listed somewhere in VOXSCRIPT I think it was called.. that made the copilot do some stuff in rather again hectic way.. but he did it in A320FBW "kinda"... it was ok...

In Aerosoft CRJ the only thing that seemed to work was having him change Heading and if i recall ALTITUDE that's about it, checklist would not allow to be enabled kept on reverting to OFF Unchecked in main programs panel.

Suggestion (unless I missed it) add a mute button for when I am talking to VATSIM controller or something. I think i saw somewhere NUMLOCK suppose to do it.. not sure.. again I just played with it for short time.

Anyhow, I will try it a bit more .. but I think it will be a pass for me.

Thanks for fixing the DEMO !

Andy

Checklists aren't tied to flows (like need to do this before that). The headers are shown in "Checklist" tab. To call any of them, speak the header and append the word "checklist" or "check".

Just like in the real world, a PF would call "before start check". or "after takeoff checklist"

Because the headers are retrieved from a possible custom checklist, you can even have sections to handle abnormal procedures.

As for the CRJ, you need to set it as the default plane MSFS loads on startup, then wait until aircraft is ready to fly and only then start MCE. It is fully supported and FO can handle pretty much any switch, either via a direct speech command or using commands in a flow.

Read document Start->Multi Crew Experience->Using MCE with FS2020

It's possible to adjust the pace at which FO handles the switches.

In Voxscript panel, select a flow and click "Edit".

Disable "Verbose" option for silent execution (it's enabled by default)

In next screen, click <Edit script commands".

You should see a list of actions FO will be performing as part of that specific flow.

It's a matter of removing anything you'd like to handle yourself and eventually adding pauses if he's going too fast to your liking.

That way, you'll have the perfect task sharing for ANY real world or virtual airline

A flow is just a task, you may or may not want to trigger. It doesn't "drive" the simulation.

You could add custom tasks, educate your FO to understand "your speak" etc...

For Vatsim, assuming you already assigned a joystick PTT for native ATC, go to the "Atc" tab and click the '+' sign at the bottom as many times as required until you get to "Other Atc" (which covers Vatsim, Pilot2Atc, VoxAtc or whatever).

Click <Activate> button and restart MCE.

From then on, when you hold PTT button or Keyboard DEL key down, MCE will suspend all speech recognition until you release them.

EDIT: One more thing in case why you wonder FO occasionally questioning the request.

We have rounded up many of the critical actions that may happen by accident when the speech engine picks them up for some reason. And it's the very reason VoiceAttack isn't really suitable for flight simulation.

Here are a few examples:

"start engine one" or "start engine two". If you haven't started one yet, FO will make sure you mean it before executing the command.

"shut down both engines", "shutdown engine two". Again, without confirmation not going to happen.

Even turning off things l;ike ATS, autopilot, IRS when airborne will need to be confirmed. Therefore, be prepared to reply with any of these: Affirmative, affirm, yes, positive, go ahead, do it, execute, carry on, definitely, ...... many many other variations

Although you could reply with "negative", "ignore this", "ignore that"....etc, by default keeping silent following a prompt for about 10 seconds means "disregard last command".

This way, the user can relax and not worry about saying something that will screw up the flight.

 

Edited by FS++

  • Commercial Member
On 3/28/2022 at 10:21 PM, charlie130 said:

In MSFS its a different game!

MCE cant dial coms  radio freqs.

Just wanted to clarify things regarding this, as you are using Pilot2Atc and may have forgotten this

FO can dial 25 khz spaced frequencies like 118.700, 118.725, 118750, 118.775,.

Try...

com one, one eighteen seven

radio one frequency one tow three decimal seven two five.

com two frequency one twenty four point five

He currently refrains from dialing 5 khz spaced freqs like 118.015., 118.135

This is to prevent putting the radio into an inconsistent state

It's just a matter of time before he handles all of them SDK update or other ways

If Pilot2Atc can do it, then there must be a way.

 

 

Edited by FS++

  • 4 weeks later...
On 4/5/2022 at 2:01 PM, FS++ said:

Just wanted to clarify things regarding this, as you are using Pilot2Atc and may have forgotten this

FO can dial 25 khz spaced frequencies like 118.700, 118.725, 118750, 118.775,.

Try...

com one, one eighteen seven

radio one frequency one tow three decimal seven two five.

com two frequency one twenty four point five

He currently refrains from dialing 5 khz spaced freqs like 118.015., 118.135

This is to prevent putting the radio into an inconsistent state

It's just a matter of time before he handles all of them SDK update or other ways

If Pilot2Atc can do it, then there must be a way.

 

 

Yay way to go MCE!

Thanks!

 

Archived

This topic is now archived and is closed to further replies.

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.