Is it possible to suspend the CoPilot from announcing V1, VR and V2 while still retaining the other "monitoring and call-out" features?  

Is it possible to suspend the CoPilot from announcing V1, VR and V2 while still retaining the other "monitoring and call-out" features?  

 

Currently not, as these are parts of standard call-outs.

 

It would be easy to add yet another option to take them out of the loop.

 

Needs to be one of those "do it via the mce.ini" so that it doesn't affect other users.

 

I assume you want that because FO isn't in synch with aircraft Vspeeds. Which aircraft is that?

 

 

Some of the add-ons i use (e.g. QW 757 and LD 767) include VSpeed call-outs; thus, you get "double" V1, VR and V2 calls.  I'm surprised this hasn't been discussed before.

 

BTW, this will be the third time FS++ has been willing to alter their code to satisfy my personal request.  A number of years ago, I requested an option to prevent MCE from automatically disabling LD 767 embedded CoPilot.  Also, I asked for a mute option.  FS++ implemented both these options!  I ask you, would their competition do this?  Heck no, instead we get some ridiculous insertion that alterations are not possible because they don't follow SOPs.  Who's SOPs?  In short, buy MCE...YOU WON'T REGRET IT!    

 

 

Some of the add-ons i use (e.g. QW 757

 

After checking that one, it appears FO didn't have acces to V speeds in FMC. It was an oversight.

 

Sorted already. Just wait for next update.

 

Do you still want the option to prevent FO making call-outs?

"Do you still want the option to prevent FO making call-outs?"

I think that would be wise, Gerald.  After all, almost all the aircraft you support have integrated vspeed calls, which you can't be disabled via the aircraft.    This way, you won't hear each Vspeed duplicated.  Also, while I'm making suggestions, could you make it possible to enter the takeoff and landing runways via the GUI?  I'm have a difficult time "telling" my copilot to set this data.  BTW, this is the only voice recognition issue I'm have having.     

 

BTW, you guys are amazing!  I'm continual perplexed to understand why this program isn't more widely used.  In short, $60.00 is a steal for the capabilities MCE offers.  I know I've mentioned this numerous times, but I can't for the life of me explain why our fellow simmers continually pay $40.00+ for the same product again and again; albeit packaged differently.  In short, keep up the great work...you have the superior product!  The Voxscripts are really amazing. 

 

"Do you still want the option to prevent FO making call-outs?"

I think that would be wise, Gerald.  After all, almost all the aircraft you support have integrated vspeed calls, which you can't be disabled via the aircraft.    This way, you won't hear each Vspeed duplicated.  Also, while I'm making suggestions, could you make it possible to enter the takeoff and landing runways via the GUI?  I'm have a difficult time "telling" my copilot to set this data.  BTW, this is the only voice recognition issue I'm have having.     

 

BTW, you guys are amazing!  I'm continual perplexed to understand why this program isn't more widely used.  In short, $60.00 is a steal for the capabilities MCE offers.  I know I've mentioned this numerous times, but I can't for the life of me explain why our fellow simmers continually pay $40.00+ for the same product again and again; albeit packaged differently.  In short, keep up the great work...you have the superior product!  The Voxscripts are really amazing. 

 

Thank you for your vocal support.

 

Another little known use for Voxscript, besides creating custom flows, is to act as a translator. Let's say you speak a completely unknown language, and let's pretend in your virtual language, "cabin crew close all doors" is spoken as "ding van dag troj" (made it up).

 

You create the custom voice command in Voxscript, tie it to the existing English command, and voila. A live translator for you.

 

Regarding 70/80/100 as well as V1, VR callouts....

 

I'm pleased to report it won't even require a new option. In fact, you can disable Vspeeds call-outs by simply clicking "Discard data" in <Monitor> tab of the UI.

 

Granted, the option is unclear as to what it does.

 

Just need to exclude V2, and "positive climb" under that option in next update.

 

Runway assignment appears to be the result of FO being too picky, insisting on having the runway designator match what he has in his docs. Sometimes, user scenery may lead to discrepancies in terms of what actual runways are available at any given airport. A case in point is Heathrow (EGLL) runways shifting between 27L, 27R and 28L and 28R.

 

 

Will try to do something about it. Worst case scenario, will just get him to accept whatever runway you tell him is the active.

 

 

Some of the add-ons i use (e.g. QW 757 and LD 767) include VSpeed call-outs; thus, you get "double" V1, VR and V2 calls. I'm surprised this hasn't been discussed before.

 

Since no announcment was made regarding V2.6.22, just to say...

 

Ability to remove takeoff callouts now built-in via the "use data" option in monitor page.

Fixed a couple of switches not working as expected with QW757: FLCH button and ground power switch in overhead panel.

You can now tell FO "our decision height is XXX" or "our minimum decision altitude is XXX" and he will make the "minimums " callouts accordingly.

 

http://www.multicrewxp.com/Downloads.html (V2.6.2.2)

 

 

BTW, you guys are amazing! I'm continual perplexed to understand why this program isn't more widely used. In short, $60.00 is a steal for the capabilities MCE offers. I know I've mentioned this numerous times, but I can't for the life of me explain why our fellow simmers continually pay $40.00+ for the same product again and again; albeit packaged differently. In short, keep up the great work...you have the superior product! The Voxscripts are really amazing.

 

I agree 100%, I have been using only for the last 3-4 weeks and wonder why I didnt get MCE earlier. And the responsiveness of FS++ team is amazing....

I agree 100%, I have been using only for the last 3-4 weeks and wonder why I didnt get MCE earlier. And the responsiveness of FS++ team is amazing....

You're telling me, Oz.  These guy have taken 3 of my suggestions and integrated them into their program; just to satisfy a SINGLE customer.  If you have idea, email them, if it makes sense, they'll take care of you.  IMO, they have best product for FS....

& +100% from me too ...... since first release !!

 

now, my tweak question :

 

with the aerosoft airbus recent release ... & using mce command / monitor (but no FMA calls) and my own checklist..... there are a few altitude callouts which are duplicated & the caution / warning callouts are a bit redundant.

 

is there an mce file one can edit and / or delete and / or alter these duplications ?

 

thanks

i guessed the answer .... thanks