Jump to content

Fenix A320 takeoff flaps script doesn't work


Recommended Posts

  • Commercial Member
2 hours ago, Balint Szarka said:

Sorry for being so active on here and possible annoying with this too, but just curious. Would there be a list of all the functions that one can insert in the mce.ini?

It's very difficult to piece them all together from hundreds of pages of Avsim forum topics.

It's OK, I don't mind at all.

These days, there is no need to read MCE documentation.

For anything to do with the user interface, you could click the '?' blue icon (cursor changes to question mark), then click any area in the UI and an audio explanation is given. Audio can even be in 5 other supported languages (German, Spanish, French, Portuguese and Italian), Subject to MCE detecting Windows version in those languages and having at least one TTS voice in the local language installed (Windows lets you install such voices for free). Otherwise will be in English.

The other way, is to pretend you are visually impaired (we do have a number of visually impaired pilots using this app), right-click MCE UI and select "Use screen narrator". Then move the mouse gently over the MCE UI and you'll get various explanations at each step. You'll also get notifications about MSFS ATC (if using that system) when options have changed "New ATC options" and the flight phase you are deemed in.

For speech commands, go to "Script Commands" panel and click <command> button.

You should see many voice commands that apply to the currently loaded plane. Dialling commands not listed because they cannot be added to a flow, but switches are almost all there. So, if you wanted to build a new task for the co-pilot to execute, it's just a matter of adding sequenced commands, perhaps a few delays here and there, notifications if needed).

 

 

Link to comment
Share on other sites

17 minutes ago, FS++ said:

It's OK, I don't mind at all.

These days, there is no need to read MCE documentation.

For anything to do with the user interface, you could click the '?' blue icon (cursor changes to question mark), then click any area in the UI and an audio explanation is given. Audio can even be in 5 other supported languages (German, Spanish, French, Portuguese and Italian), Subject to MCE detecting Windows version in those languages and having at least one TTS voice in the local language installed (Windows lets you install such voices for free). Otherwise will be in English.

The other way, is to pretend you are visually impaired (we do have a number of visually impaired pilots using this app), right-click MCE UI and select "Use screen narrator". Then move the mouse gently over the MCE UI and you'll get various explanations at each step. You'll also get notifications about MSFS ATC (if using that system) when options have changed "New ATC options" and the flight phase you are deemed in.

For speech commands, go to "Script Commands" panel and click <command> button.

You should see many voice commands that apply to the currently loaded plane. Dialling commands not listed because they cannot be added to a flow, but switches are almost all there. So, if you wanted to build a new task for the co-pilot to execute, it's just a matter of adding sequenced commands, perhaps a few delays here and there, notifications if needed).

 

 

I see 😉 But I meant, if you would know all the entries that are possible inside the mce.ini? Like for example the CAT3 calls etc. Would there be more? As these all seem to be undocumented… But if they were once coded someone should kind of have a list no? I just wonder if you would know them? Just to see if I could find some more options that could be helpful for me.

  • Like 1

Balint Szarka

CPU Intel i9 9900K OC'd to 5Ghz

RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB)

GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER

 

Link to comment
Share on other sites

37 minutes ago, FS++ said:

Thank you

To clarify, I'm not the main dev at FS++

This functionality gets requested about once every 3 years.

Let me explain why we won't go that route.

We need to keep MCE as mostly a speech based app, with no programming skills required.

Even naming "Voxscript" was a mistake. Should have been called "VoxFlow". Essentially putting speech commands in a sequence to make a custom task for the crew to perform..

If we start adding conditions and things like that, we would make perhaps 50 to 100 people very happy, but we could alienate many others who would wrongly think it's that "voice control for programmers".

Also, not all Lvars are settable, and sometimes they get renamed or removed.

I agree that it should not be over complicated. I have myself dealt with enough complex add-ons that were difficult to use. However could this not be added as an addition to the current program which then could be enabled or disabled? I would even happily pay for it as it would open “doors” with almost unlimited capabilities. Imagine that one could write somewhat in human language: if descending through 10000 feet call out 10000 feet (or FL100) and carry out “command 1” + “command 2” etc. Obviously unless the program would be able to translate all that into computer language it would have to be written a lot more in mathematical terms / computer language however it would open endless possibilities that one could perform with it without having to ask for flows to be done. As we all know it that in real life most airlines’ pilots won’t say do this flow and that flow, but one thing flows into another because of non verbal language. That kind of non verbal language is a big thing missing in my opinion. Of course MCE can do so many things but there could be so much more done with it with some advancements in the future. 

Balint Szarka

CPU Intel i9 9900K OC'd to 5Ghz

RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB)

GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER

 

Link to comment
Share on other sites

  • Commercial Member
22 hours ago, Balint Szarka said:

I see 😉 But I meant, if you would know all the entries that are possible inside the mce.ini? Like for example the CAT3 calls etc. Would there be more? As these all seem to be undocumented… But if they were once coded someone should kind of have a list no? I just wonder if you would know them? Just to see if I could find some more options that could be helpful for me.

Indeed, CAT3 entries poorly documented

[CAT_III]

FlightCalloutHeight=    (set custom height at which FO will make some custom_airline_specific_statement

FlightCalloutText=what_airline_specific_statement_you_want_FO-to_utter_when_performing_CATIII_Approach_prior_to_landing

GroundCalloutSpeed=    (set custom_speed at which FO will make some custom airline_specific_statement_When_on_CATIII_rollout

GroundCalloutText=what_statement_you_want_FO-to_utter_on_ground_when_performing_a_CATIII_rollout

These are only relevant when you brief the FO that you intend to perform a CAT III approach, with these commands...

      we will perform a category three ils approach
      we will perform a cat three ils approach
      we will perform a category three approach
      we will perform a cat three approach
      will perform a category three ils approach
      will perform a category three approach
      it will be a category three ils approach
      it will be a category three approach
      it will be a cat three ils approach
      it will be a cat three approach
      approach will be category three ils
      approach will be cat three ils
      approach will be category three
      approach will be cat three

 

Link to comment
Share on other sites

10 minutes ago, FS++ said:

Indeed, CAT3 entries poorly documented

[CAT_III]

FlightCalloutHeight=    (set custom height at which FO will make some custom_airline_specific_statement

FlightCalloutText=what_airline_specific_statement_you_want_FO-to_utter_when_performing_CATIII_Approach_prior_to_landing

GroundCalloutSpeed=    (set custom_speed at which FO will make some custom airline_specific_statement_When_on_CATIII_rollout

GroundCalloutText=what_statement_you_want_FO-to_utter_on_ground_when_performing_a_CATIII_rollout

These are only relevant when you brief the FO that you intend to perform a CAT III approach, with these commands...

      we will perform a category three ils approach
      we will perform a cat three ils approach
      we will perform a category three approach
      we will perform a cat three approach
      will perform a category three ils approach
      will perform a category three approach
      it will be a category three ils approach
      it will be a category three approach
      it will be a cat three ils approach
      it will be a cat three approach
      approach will be category three ils
      approach will be cat three ils
      approach will be category three
      approach will be cat three

 

Oh nice I didn’t know any of this. Thanks. Any other entries that one can make in the mce.ini? There seems to be loads that one can enter but they are nowhere written, so I am wonder if I might be missing out on a few?

Balint Szarka

CPU Intel i9 9900K OC'd to 5Ghz

RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB)

GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER

 

Link to comment
Share on other sites

I agree it would be great to have a list of all the possible mce.ini entries. Maybe just as a textfile included in the docs.

Over the years I've been using MCE you told me so many "secret" entries I could add to the mce.ini to make MCE act exactly like I wanted it to.

I've made a few backups of my mce.ini but still I'm always afraid I will lose all of these undocumented entries when my mce.ini should get deleted somehow and I will never find these hints again that are buried deep inside this forum.

 

  • Upvote 1
Link to comment
Share on other sites

2 hours ago, FS++ said:

OK, will add more comments to ini files and ensure all optiions are there

Thank you ☺️ that’s going to be awesome 🙌 

Balint Szarka

CPU Intel i9 9900K OC'd to 5Ghz

RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB)

GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER

 

Link to comment
Share on other sites

  • Commercial Member
On 8/29/2024 at 2:22 AM, Balint Szarka said:

Thank you ☺️ that’s going to be awesome 🙌 

//Almost all options in this config file are settable via the user interface. Therefoe only adjust those that need to be set via this file.
 
[WINDOW]
Left=10            //(saves the last MCE UI window position left coordinate)
Top=10            //(saves the last MCE UI window position top coordinate)
NoActivate=1        //(enable to make sure MCE doesn't take the focus out of the sim, when the UI is clicked)
NoSound=0        //(enable if you want to cut the various UI sounds emitted when clicking buttons or MCE minimises)
NoFullScreenDraw=0    //(enable to avoid the occasional graphics artefacts than can happen when MCE UI tries to draw, and the sim is in full screen mode)
StartToTray=0        //(enable and every time MCE starts, the UI will not appear unless you click on the icon in system tray)

[FEATURES]
ExecuteCaptainOrders=1       //corresponds to the cew coordination feature in UI
ReadCheckListWhenAsked=1      //corresponds to the interactive checklist feature in UI
PilotSpeaksToAtc=1        //corresponds to the Talk to ATC feature in UI
CopilotReportsFailures=1    //corresponds to the "Call-outs and monitoring" feature in UI
EnableInterfaceVoice=1        //corresponds to the "User interface voice control" feature in UI.

[OPTIONS]a
Debug=0            //(only set this to 1 when instructd by support)
PilotIsBVI=0        //(must be set to 1 for Blind Visually Impaired Pilots)
UIlanguage=1033        //the ID of the user language MCE has detected. 1033 for English. To have the UI in German set 1031, for French 1036, for Spanish 3082, for Portuguese 1046, for Italian 1040
MikeTuneOnStartup=0    //correspnds to the "Tune mike n startup" option in UI
EnableOptimizations=1    //correspnds to the "Tune mike on startup" option in UI
AutoStartWithFS=0    //correspnds to the "Auto start with FS" option in UI. Applies to FSX & P3D only)
MinimizeToTray=0    //correspnds to the "Start to Tray" option in UI
MoreResponsive=1    //enable to make the speech engine more aggressive with resources usage
TrainingCompleted=0    //automatically set by the wizard once it has completed its first run
RandomFailures=0    //Applies to FSX only
TweakFsConfig=0        //Applies to FSX only
AtcMikeUseIvao=0
ForceCopilot=1            //(set to 1 to enable co-pilot on aircraft that normally wouldn't have one)
AudioIn=
AudioOut=
PilotName=Captain            
ShowCommands=1            //(set to 1 will display spoken commands in red font text. Set to 0, no display)
ForceCommands=0            //(deprecated. Do not use)
DisplayTime=3000        //(it's the amount of time in milliseconds the spoken text remains displayed on the screen before another command is spoken. Use values between 2000 and 5000)
UseMacros=1            //(must be set to 1 For VoxKey to work)
UseNarrator=0            //(must be set to 1 for Blind Visually Impaired Pilots)
LoudData=0            //(must be set to 1 for Blind Visually Impaired Pilots)
EnableAnnouncements=1        //(must be set to 1 for Blind Visually Impaired Pilots)
UseVoxScripts=1            //(must be to 1 for VoxScript to work)
DisableNagging=1        //(set this to 1 to prevent Copilot monitoring your flying)
GroundServicesMode=Native    //(MCE will try to detect GSX. If available, will automatically switch to GSX as the active mode. You can set it to GSX)
NoBadLanguage=1            //(set this to 1 to prevent detection of mild insults)
NoFMAcallouts=0            //(set this to 1 if you don't want FO to monitor FMA (Flight Mode Annuciator). Applies mostly to Aibus types)
NoEngineStartCallouts=0        //(corresponds to the "engine start call-outs" option in UI)
AllowActionOnEvent=0        // When enabled makes it possible for the FO to react to some events like spoiler arming-disarming. Currently not available in MSFS)
V1CalloutIsGO=0            //(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=0            //(Enable this if you want to cutout on the amount of FO speech. FO would be more concise)
AutoNotifyOnSilentFlowStart=1    //(disable if you don't want the FO to speak the flow that doesn't have custom replies he's about to execute)
UsingFullHardwareCockpit=0    //Enable this is using a simpit with all switching via hardware. Prevents Fo setting switches in VC that would make them out of synch with hardware.
DisableVolumeFade=1        //when enabled, you get a pop-up panel once a day to tell Windows audio not to reduce any audio when apps like Skype kick in
UseAlternateGrammar=0        //enable this option if you wnt to use a custom flow triggered with "gear up" and "gear down" where the FO performs more actions than just raising or lowering the gear.
UsingMetricSystem=0        //MCE automatically tries to detect CDU input type. Metric vs Imperial. Enale it if you're always using the Metric system
CheckSpeed=1            //when enabled, Fo will always check speed before extending flaps or gear which is the norm. Some people get irritated by that and want straight action, hence the option

[PROFICIENCY]
Level=3            //corresponds o the "Proficiency" level in Monitor tab. Trainee....ATPL

[SPEECH]
CanDo=1            //automatically set by the wizard to indicate an English speech engine is available, thus voice control possible. Otherwise button control only.
Volume=100        //corresponds to the Volume slider in UI
CpuUsage=75        //corresponds to the Cpu usage slider in UI
SpeechPace=750        //corresponds to the Speech pace slider in UI. Small values favor "fast talkers", higher values for "slow talkers"
InprocReco=1        //sets the speech engine to run inside "mce.exe" which is the preferred option. Do not disable unless you have other speech based apps that need the speech engine in "shared mode".
DisablePitchChange=0    //Applies to TTS voices. By default MCE dynamically adjusts pitch fr prompts and other things. Enable if you don't want the effect.
MaxConcurrentTasks=4    //MCE being multi-threade, if we don't manage Fo behaviour, he could be performing many tasks simultaneously. This sets the limit in this regard.
NumLockKeyMutesReco=0    //corresponds to "NumLock mutes reco" in Advanced options" panel. When toggled ON, keyboard light ON, MCE suspends all speech reco until you toggle it off
NotifySRstateAudio=1    //when enabled, you get "speech off" notification when MCE is muted as well as "listening" when MCE unmutes. Disale if you find that annoying

[SKILL]
Tol3=030,030,400,900,100,100,100,050    //these correspond to the Tolerances settable in Monitor tab. No need to mess with them in this ini file
Tol2=020,020,200,700,075,075,075,030
Tol1=010,010,100,500,050,050,050,020
Tol0=005,005,050,300,025,025,025,010

[VOICES]
Voice0 =Clive,0,0,0,1        //Corresponds to the currently selected Fo voice
Voice1 =Richard,0,0,0,1        //Corresponds to the currently selected Mechanic voice
Voice2 =Stella,0,0,0,1        //Corresponds to the currently selected Purser voice
Voice3 =Trav,0,0,0,1        //Corresponds to the flight engineer voice for planes that have one
Voice4=Microsoft David Desktop,0,0,0,0        //Corresponds to TTS notification voice. Depends on WIndows edition


[ATC]
Mode=Native            //By default MCE sets itself on Native ATC integration. Can be set to "PFE", "RC4", or "OTHER" (Vatsim, Pilot2Atc, VoxATC, BeyondAtc...etc)
PreventNativeATCCancellation=0    //Applies to native ATC witch MCE sending requests for repeats in order to prevent ATC terminating your flight after going AWOL for a while.
UseRadioNoise=1            //settable from drop-down menu (right-click MCE UI). You get a humming background noise indicating MCE has switched to ATC mode where only ATC commands can be recognized
StaticNoiseLevel=1        //settable from drop-down menu (right-click MCE UI). How loud you want the humming background noise to be.
SecondaryNeedAtcWindow=0    //Legacy FSX ATC related. Deprecated
atc1=0                //Corresponds to "auto-hide ATC window" option in UI
atc2=0                //Corresponds to "accurate call-sin required" option in UI
atc3=1                //Corresponds to "auto-hide ATC window" option in UI
atc4=1                //Corresponds to "Use DEL key to transmit" option in UI. You cannot diabled this unless you have a joystick button assigned
atc5=0                //Corresponds to "use whatever joystick button" option in UI. You cannot diabled this unless you have option "Use DEL key for transmission" enabled
UseRadarContact=0    //Normally not required as MCE ATC mode determines this. Use it to override, indicating you want to use Radar Contact and not other ATC
IgnoreRC4Registry=0    //(Set this to 1 when RC4 isn't installed on the same machine as MCE)
RC4path=        
IgnorePFERegistry=0    //(Set this to 1 when PFE isn't installed on the same machine as MCE)
PFEpath=
IgnoreFlightPlan=0    //(Applies to FSX and Pepar3D. Prevents MCE issuing text notifications about inability to detect current flight plan)
FlightPlansPath=


[SIMCONTROL]
FsPanels=1        //Corresponds to the first option in Sim tab in UI. Changes based on currently detected flight sim
FsMenus=1        //Corresponds to the second option in Sim tab in UI. Changes based on currently detected flight sim
FsDialogs=1        //Corresponds to the third option in Sim tab in UI. Changes based on currently detected flight sim
FsKneeboard=1        //Corresponds to the first option in Sim tab in UI. Not applicable to MSFS.
ViewsAndViewpoint=1    //Corresponds to the first option in Sim tab in UI. Not applicable to MSFS.

[GAMEPAD]
JoyManID=
JoyProdID=
JoyButton=        //the currently selected button ID used for ATC transmission
UseWithVoxATC=0        //(enable if you want to use the same joystick assignment with VoxATC. It will ensure FO doesn't listen to your speech while the joystick button is held down using VoxATC)

[GO-FLIGHT]
Use=1            //(enable for MCE to monitor the manual radio dialling process. Whether you do that via mouse-clicks or by rotating Go-Flight or other hardware modules. FSX & P3D only)
TimeOut=3000        //(sets the amount of time in milliseconds that must elapse after you last click on the radio switches in VC panel, or physically rotate a button on the radio rack, before MCE assumes you are finished with dialling. Values between 2000 and 5000 are accepted)


[CHECKLIST]
NoStateCheck=0        //(when set to 1, co-pilot will just read the checklist aloud, wait for any answer and move on, without challenging you on any item. Useful for people running simpits with hardware switches. It can be difficult for FO to read these)
Strict=1        //("strict checklist" option in UI which when enabled causes the Fo to challenge once on an item, then eventually try to set it as per checklist and move on

 

[MECHANIC]
PushWithGSXandAES=0     //corresponds to the "Kepp mech on push" option in UI. When enabled and GSX push guy chimes in, the MCE meh will remain around until you tell him to leaave.
ConfirmFuel=1        //When enabled, mechanic will always prompt you to confirm the fuel figure when the fuel truck arrives.         
NotUsingMechanic=0    //enable if you don't want to use MCE Mechanic at all

[RAMP]
NoRampToOfficeTalk=0            //enable option to prevent you hearing exchanges between ramp agent and dispatch office
NoPaxDoorsAutoHandling=0        //enable to prevent MCE automatically reacting to GSX requests to open or cloce service doors)
NoCargoDoorsAutoHandling=0        //enable to prevent MCE automatically reacting to GSX requests to open or cloce cargo doors)
AlwaysInitiateMsfsRampServices=0    //when enabled, MCE will automatically call default Asobo ground services on start-up.
CanHurtMechanic=1            //disable if you often forget to release mechanic... causing him to tell you off.

[PACE]
ActionDelay=1500     //The simulated delay that takes place before FO takes action. Values from 0 to 4000 milliseconds)
MCPdial=100       //The pace at which FO increments or decrements MCP values from 100 to 250 milliseconds). Doesn't apply to some aircraft where the value is hard coded
ButtonPress=800       //The simulated time in milliseconds it takes the FO to flip a single switch. Values 500 to 2500 are accepted
VoxKeyAction=1000  //The delay in milliseconds between two consecutive VoxKey actions. Valid entries 0 to 4000.


[SPLASH]
NoSound=0    //Enable to prevent splash screen playing its audio

[VATSIM]
NotifyPTTstate=0    //For Vatsim users. Enable this option so you can get red text notification when MCE has disabled speech reco

[PILOTS]

[MISC]

[CALLOUTS]
80knots=1
100knots=1
V1=1
VR=1
PositiveRate=1
V2=1
TransitionAltitude=1
TenThousandClimbing=1
TenThousandDescending=1
TransitionLevel=1
OneThousandFinal=1
FiveHundredFinal=1
Minimums=1
SpoilersUp=1
ReversersOn=1
80KnotsDecel=0
70KnotsDecel=0
60KnotsDecel=1

[TERMINATE]

 

 

Edited by FS++
  • Like 1
Link to comment
Share on other sites

7 hours ago, FS++ said:

//Almost all options in this config file are settable via the user interface. Therefoe only adjust those that need to be set via this file.
 
[WINDOW]
Left=10            //(saves the last MCE UI window position left coordinate)
Top=10            //(saves the last MCE UI window position top coordinate)
NoActivate=1        //(enable to make sure MCE doesn't take the focus out of the sim, when the UI is clicked)
NoSound=0        //(enable if you want to cut the various UI sounds emitted when clicking buttons or MCE minimises)
NoFullScreenDraw=0    //(enable to avoid the occasional graphics artefacts than can happen when MCE UI tries to draw, and the sim is in full screen mode)
StartToTray=0        //(enable and every time MCE starts, the UI will not appear unless you click on the icon in system tray)

[FEATURES]
ExecuteCaptainOrders=1       //corresponds to the cew coordination feature in UI
ReadCheckListWhenAsked=1      //corresponds to the interactive checklist feature in UI
PilotSpeaksToAtc=1        //corresponds to the Talk to ATC feature in UI
CopilotReportsFailures=1    //corresponds to the "Call-outs and monitoring" feature in UI
EnableInterfaceVoice=1        //corresponds to the "User interface voice control" feature in UI.

[OPTIONS]a
Debug=0            //(only set this to 1 when instructd by support)
PilotIsBVI=0        //(must be set to 1 for Blind Visually Impaired Pilots)
UIlanguage=1033        //the ID of the user language MCE has detected. 1033 for English. To have the UI in German set 1031, for French 1036, for Spanish 4082, for Portuguese 1046, for Italian 1040
MikeTuneOnStartup=0    //correspnds to the "Tune mike n startup" option in UI
EnableOptimizations=1    //correspnds to the "Tune mike on startup" option in UI
AutoStartWithFS=0    //correspnds to the "Auto start with FS" option in UI. Applies to FSX & P3D only)
MinimizeToTray=0    //correspnds to the "Start to Tray" option in UI
MoreResponsive=1    //enable to make the speech engine more aggressive with resources usage
TrainingCompleted=0    //automatically set by the wizard once it has completed its first run
RandomFailures=0    //Applies to FSX only
TweakFsConfig=0        //Applies to FSX only
AtcMikeUseIvao=0
ForceCopilot=1            //(set to 1 to enable co-pilot on aircraft that normally wouldn't have one)
AudioIn=
AudioOut=
PilotName=Captain            
ShowCommands=1            //(set to 1 will display spoken commands in red font text. Set to 0, no display)
ForceCommands=0            //(deprecated. Do not use)
DisplayTime=3000        //(it's the amount of time in milliseconds the spoken text remains displayed on the screen before another command is spoken. Use values between 2000 and 5000)
UseMacros=1            //(must be set to 1 For VoxKey to work)
UseNarrator=0            //(must be set to 1 for Blind Visually Impaired Pilots)
LoudData=0            //(must be set to 1 for Blind Visually Impaired Pilots)
EnableAnnouncements=1        //(must be set to 1 for Blind Visually Impaired Pilots)
UseVoxScripts=1            //(must be to 1 for VoxScript to work)
DisableNagging=1        //(set this to 1 to prevent Copilot monitoring your flying)
GroundServicesMode=Native    //(MCE will try to detect GSX. If available, will automatically switch to GSX as the active mode. You can set it to GSX)
NoBadLanguage=1            //(set this to 1 to prevent detection of mild insults)
NoFMAcallouts=0            //(set this to 1 if you don't want FO to monitor FMA (Flight Mode Annuciator). Applies mostly to Aibus types)
NoEngineStartCallouts=0        //(corresponds to the "engine start call-outs" option in UI)
AllowActionOnEvent=0        // When enabled makes it possible for the FO to react to some events like spoiler arming-disarming. Currently not available in MSFS)
V1CalloutIsGO=0            //(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=0            //(Enable this if you want to cutout on the amount of FO speech. FO would be more concise)
AutoNotifyOnSilentFlowStart=1    //(disable if you don't want the FO to speak the flow that doesn't have custom replies he's about to execute)
UsingFullHardwareCockpit=0    //Enable this is using a simpit with all switching via hardware. Prevents Fo setting switches in VC that would make them out of synch with hardware.
DisableVolumeFade=1        //when enabled, you get a pop-up panel once a day to tell Windows audio not to reduce any audio when apps like Skype kick in
UseAlternateGrammar=0        //enable this option if you wnt to use a custom flow triggered with "gear up" and "gear down" where the FO performs more actions than just raising or lowering the gear.
UsingMetricSystem=0        //MCE automatically tries to detect CDU input type. Metric vs Imperial. Enale it if you're always using the Metric system
CheckSpeed=1            //when enabled, Fo will always check speed before extending flaps or gear which is the norm. Some people get irritated by that and want straight action, hence the option

[PROFICIENCY]
Level=3            //corresponds o the "Proficiency" level in Monitor tab. Trainee....ATPL

[SPEECH]
CanDo=1            //automatically set by the wizard to indicate an English speech engine is available, thus voice control possible. Otherwise button control only.
Volume=100        //corresponds to the Volume slider in UI
CpuUsage=75        //corresponds to the Cpu usage slider in UI
SpeechPace=750        //corresponds to the Speech pace slider in UI. Small values favor "fast talkers", higher values for "slow talkers"
InprocReco=1        //sets the speech engine to run inside "mce.exe" which is the preferred option. Do not disable unless you have other speech based apps that need the speech engine in "shared mode".
DisablePitchChange=0    //Applies to TTS voices. By default MCE dynamically adjusts pitch fr prompts and other things. Enable if you don't want the effect.
MaxConcurrentTasks=4    //MCE being multi-threade, if we don't manage Fo behaviour, he could be performing many tasks simultaneously. This sets the limit in this regard.
NumLockKeyMutesReco=0    //corresponds to "NumLock mutes reco" in Advanced options" panel. When toggled ON, keyboard light ON, MCE suspends all speech reco until you toggle it off
NotifySRstateAudio=1    //when enabled, you get "speech off" notification when MCE is muted as well as "listening" when MCE unmutes. Disale if you find that annoying

[SKILL]
Tol3=030,030,400,900,100,100,100,050    //these correspond to the Tolerances settable in Monitor tab. No need to mess with them in this ini file
Tol2=020,020,200,700,075,075,075,030
Tol1=010,010,100,500,050,050,050,020
Tol0=005,005,050,300,025,025,025,010

[VOICES]
Voice0 =Clive,0,0,0,1        //Corresponds to the currently selected Fo voice
Voice1 =Richard,0,0,0,1        //Corresponds to the currently selected Mechanic voice
Voice2 =Stella,0,0,0,1        //Corresponds to the currently selected Purser voice
Voice3 =Trav,0,0,0,1        //Corresponds to the flight engineer voice for planes that have one
Voice4=Microsoft David Desktop,0,0,0,0        //Corresponds to TTS notification voice. Depends on WIndows edition


[ATC]
Mode=Native            //By default MCE sets itself on Native ATC integration. Can be set to "PFE", "RC4", or "OTHER" (Vatsim, Pilot2Atc, VoxATC, BeyondAtc...etc)
PreventNativeATCCancellation=0    //Applies to native ATC witch MCE sending requests for repeats in order to prevent ATC terminating your flight after going AWOL for a while.
UseRadioNoise=1            //settable from drop-down menu (right-click MCE UI). You get a humming background noise indicating MCE has switched to ATC mode where only ATC commands can be recognized
StaticNoiseLevel=1        //settable from drop-down menu (right-click MCE UI). How loud you want the humming background noise to be.
SecondaryNeedAtcWindow=0    //Legacy FSX ATC related. Deprecated
atc1=0                //Corresponds to "auto-hide ATC window" option in UI
atc2=0                //Corresponds to "accurate call-sin required" option in UI
atc3=1                //Corresponds to "auto-hide ATC window" option in UI
atc4=1                //Corresponds to "Use DEL key to transmit" option in UI. You cannot diabled this unless you have a joystick button assigned
atc5=0                //Corresponds to "use whatever joystick button" option in UI. You cannot diabled this unless you have option "Use DEL key for transmission" enabled
UseRadarContact=0    //Normally not required as MCE ATC mode determines this. Use it to override, indicating you want to use Radar Contact and not other ATC
IgnoreRC4Registry=0    //(Set this to 1 when RC4 isn't installed on the same machine as MCE)
RC4path=        
IgnorePFERegistry=0    //(Set this to 1 when PFE isn't installed on the same machine as MCE)
PFEpath=
IgnoreFlightPlan=0    //(Applies to FSX and Pepar3D. Prevents MCE issuing text notifications about inability to detect current flight plan)
FlightPlansPath=


[SIMCONTROL]
FsPanels=1        //Corresponds to the first option in Sim tab in UI. Changes based on currently detected flight sim
FsMenus=1        //Corresponds to the second option in Sim tab in UI. Changes based on currently detected flight sim
FsDialogs=1        //Corresponds to the third option in Sim tab in UI. Changes based on currently detected flight sim
FsKneeboard=1        //Corresponds to the first option in Sim tab in UI. Not applicable to MSFS.
ViewsAndViewpoint=1    //Corresponds to the first option in Sim tab in UI. Not applicable to MSFS.

[GAMEPAD]
JoyManID=
JoyProdID=
JoyButton=        //the currently selected button ID used for ATC transmission
UseWithVoxATC=0        //(enable if you want to use the same joystick assignment with VoxATC. It will ensure FO doesn't listen to your speech while the joystick button is held down using VoxATC)

[GO-FLIGHT]
Use=1            //(enable for MCE to monitor the manual radio dialling process. Whether you do that via mouse-clicks or by rotating Go-Flight or other hardware modules. FSX & P3D only)
TimeOut=3000        //(sets the amount of time in milliseconds that must elapse after you last click on the radio switches in VC panel, or physically rotate a button on the radio rack, before MCE assumes you are finished with dialling. Values between 2000 and 5000 are accepted)


[CHECKLIST]
NoStateCheck=0        //(when set to 1, co-pilot will just read the checklist aloud, wait for any answer and move on, without challenging you on any item. Useful for people running simpits with hardware switches. It can be difficult for FO to read these)
Strict=1        //("strict checklist" option in UI which when enabled causes the Fo to challenge once on an item, then eventually try to set it as per checklist and move on

 

[MECHANIC]
PushWithGSXandAES=0     //corresponds to the "Kepp mech on push" option in UI. When enabled and GSX push guy chimes in, the MCE meh will remain around until you tell him to leaave.
ConfirmFuel=1        //When enabled, mechanic will always prompt you to confirm the fuel figure when the fuel truck arrives.         
NotUsingMechanic=0    //enable if you don't want to use MCE Mechanic at all

[RAMP]
NoRampToOfficeTalk=0            //enable option to prevent you hearing exchanges between ramp agent and dispatch office
NoPaxDoorsAutoHandling=0        //enable to prevent MCE automatically reacting to GSX requests to open or cloce service doors)
NoCargoDoorsAutoHandling=0        //enable to prevent MCE automatically reacting to GSX requests to open or cloce cargo doors)
AlwaysInitiateMsfsRampServices=0    //when enabled, MCE will automatically call default Asobo ground services on start-up.
CanHurtMechanic=1            //disable if you often forget to release mechanic... causing him to tell you off.

[PACE]
ActionDelay=1500     //The simulated delay that takes place before FO takes action. Values from 0 to 4000 milliseconds)
MCPdial=100       //The pace at which FO increments or decrements MCP values from 100 to 250 milliseconds). Doesn't apply to some aircraft where the value is hard coded
ButtonPress=800       //The simulated time in milliseconds it takes the FO to flip a single switch. Values 500 to 2500 are accepted
VoxKeyAction=1000  //The delay in milliseconds between two consecutive VoxKey actions. Valid entries 0 to 4000.


[SPLASH]
NoSound=0    //Enable to prevent splash screen playing its audio

[VATSIM]
NotifyPTTstate=0    //For Vatsim users. Enable this option so you can get red text notification when MCE has disabled speech reco

[PILOTS]

[MISC]

[CALLOUTS]
80knots=1
100knots=1
V1=1
VR=1
PositiveRate=1
V2=1
TransitionAltitude=1
TenThousandClimbing=1
TenThousandDescending=1
TransitionLevel=1
OneThousandFinal=1
FiveHundredFinal=1
Minimums=1
SpoilersUp=1
ReversersOn=1
80KnotsDecel=0
70KnotsDecel=0
60KnotsDecel=1

[TERMINATE]

 

 

Thank you so much. Lots of help, I very much appreciate it 😊

  • Like 1

Balint Szarka

CPU Intel i9 9900K OC'd to 5Ghz

RAM 32GB Corsair Vengeance DDR4 3000MHz (2 x 16GB)

GPU 8GB NVIDIA GEFORCE RTX 2070 SUPER

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...