Sign in to follow this  
kingm56

Ground Interaction

Recommended Posts

F++ team,

 

Any ideas why the ground interaction would just stop working?  After I reset all MCE settings to "factory default," the ground interaction feature work; however, on the very next flight, and every subsequent flight, I can't seem to contact ground for push back.  I'm not using any third-party utilities(eg. AES or GSX), just vanilla FSX. Any ideas wold be appreciated.    

 

mce.ini settings:

 

[WINDOW]
Left=1335
Top=7
NoActivate=1 //(1 to make sure MCE doesn't take the focus out of the sim, when the UI is clicked, 0 otherwise)
NoSound=0 //(set value 1 if you want to cut the various UI sounds emitted when clicking buttons or MCE minimises)
NoFullScreenDraw=0 //(set to 1, 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 //(set to 1, and every time MCE starts, the UI will not appear unless you click on the icon in system tray)
 
[FEATURES]
ExecuteCaptainOrders=1
ReadCheckListWhenAsked=1
PilotSpeaksToAtc=0
CopilotReportsFailures=1
EnableInterfaceVoice=1
 
[OPTIONS]
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
MikeTuneOnStartup=0
EnableOptimizations=1
AutoStartWithFS=0
MinimizeToTray=0
MoreResponsive=1
TrainingCompleted=1
RandomFailures=0
TweakFsConfig=0
AtcMikeUseIvao=0
ForceCopilot=1
AudioIn=
AudioOut=
PilotName=matthew king
ShowCommands=1
ForceCommands=0 //(deprecated. Do not use)
DisplayTime=3000
UseMacros=1 //(must be set to 1 For VoxKey to work)
UseNarrator=0
LoudData=0
EnableAnnouncements=1
UseVoxScripts=1
DisableNagging=1
GroundServicesMode=Native
NoBadLanguage=1
NoFMAcallouts=0 //(set this to 1 if you don't want FO to monitor FMA (Flight Mode Annuciator))
NoEngineStartCallouts=0
AllowActionOnEvent=0
V1CalloutIsGO=0 //(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=1
 
[PROFICIENCY]
Level=1
 
[sPEECH]
Volume=100
CpuUsage=75
SpeechPace=750
InprocReco=1
DisablePitchChange=0
MaxConcurrentTasks=4
NumLockKeyMutesReco=0
 
[sKILL]
Tol3=030,030,400,900,100,100,100,050
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 =Trav,0,0,0,1
Voice1 =William,0,0,0,1
Voice2 =Stella,0,0,0,1
Voice3 =Andy,0,0,0,1
Voice4 =Microsoft Anna,0,0,0 
 
[ATC]
Mode=Native
PreventNativeATCCancellation=0
UseRadioNoise=1
StaticNoiseLevel=1
SecondaryNeedAtcWindow=0
atc1=0
atc2=0
atc3=1
atc4=1
atc5=1
UseRadarContact=0
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
FlightPlansPath=
 
 
[sIMCONTROL]
FsPanels=1
FsMenus=0
FsDialogs=0
FsKneeboard=1
ViewsAndViewpoint=0
 
[GAMEPAD]
JoyManID=Saitek Pro Flight Yoke
JoyProdID=Saitek Pro Flight Yoke
JoyButton=1
UseWithVoxATC=1 //(set to 1 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 //(set to 1 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)
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 //(set to 1 if you want FO to be very professional with the checklist. Cuts out the banter)
Virtualcol - De Havilland Canada Dash8Q100 - Delta=F:\FSX\MCE\ChkLists\Bombardier_100.txt
Bombardier CRJ 700 Comair=F:\FSX\MCE\ChkLists\CRJ700.txt
CS 777-200LR Captain Paint1=F:\FSX\MCE\ChkLists\777CS_check.txt
Boeing 737-832NGX Delta Air Lines Winglets=F:\FSX\MCE\ChkLists\PMDG_737_NGX.txt
 
 
 
[MECHANIC]
PushWithGSXandAES=0
 
 
[RAMP]
NoRampToOfficeTalk=0
NoPaxDoorsAutoHandling=0
NoCargoDoorsAutoHandling=0
 
 
[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
 
[VATSIM]
NotifyPTTstate=0
 
[PILOTS]
 
[MISC]
Path=F:\FSX\MCE
 
 
 
[TERMINATE]

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

 Hello

I find this useful piece of information:

The mce.ini inside MCE installation folder should never be edited. It serves as backup in case the one in |AppData\Roaming\ folder gets messed up. When you select "Restore factory settings", the ini in installation folder will overwrite the other one with the default settings, which work for the majority of users.(FS++ Team) 

 

http://www.avsim.com/topic/376091-useful-information-about-mce/

Post #4

 

Do you think have something to do?

You can reinstall.

Share this post


Link to post
Share on other sites

 

 


Any ideas why the ground interaction would just stop working?  After I reset all MCE settings to "factory default," the ground interaction feature work;

 

OK, will be investigated during the week.

 

In general, the only scenario where you can expect the mechanic to go AWOL is when flying some aircraft that isn't fully supported, and somehow MCE doesn't get the correct engine status. If it (wrongly) sees all engines running, the Mechanic won't talk to you, even if the command is recognized.

Share this post


Link to post
Share on other sites

 

 


In general, the only scenario where you can expect the mechanic to go AWOL is when flying some aircraft that isn't fully supported

 

Well, MCE has spoiled me; so, prior to procuring any aircraft it must be MCE supported...it's kind of a deal breaker.  If I could, I would recommend adding a button option to talk with the ground team; this option would allow you to forgo any conditional statements, with the exception of the Aircraft being airborne, to facilitate comms with the ground.  For example, if I press the "end" key, I would communicate with ground regardless of engine status.  I think this could be useful.  

 

Also, do you think it would be possible to add a variable in mce.ini to automatically disable MCE's "use data" option via the monitor tab?  Most aircraft have copilots the call-out Vspeeds, it can get a little annoying to hear duplicate sounds when forgetting to remove the x from "use data" option. 

 

Again, i can't thank you enough for producing the best add-on I've used for FSX!  

Share this post


Link to post
Share on other sites

I am probably wrong here but I notice the following :-

 

"[MECHANIC]
PushWithGSXandAES=0"
 
Shouldn't the zero be replaced with 1 to enable ground operations?

Share this post


Link to post
Share on other sites

 

 


Shouldn't the zero be replaced with 1 to enable ground operations

 

Only if you're using one of those utilities; however, I'm using default FSX pushback.  Thanks for taking the time to look over the post though!  

Share this post


Link to post
Share on other sites

 

 


I'm using default FSX pushback

Thanks.  Obviously my speed reading skills need to improve.

Share this post


Link to post
Share on other sites

I too am having this problem with the mechanic and also with the purser. I have no one to get catering, refueling, boarding etc on the way. In fact the only thing that works is the F/O reading the checklist(s).

 

I just began using SIM-A in my full trainer. Is that why, SIM-A?

 

Tkx!!

Doug

Share this post


Link to post
Share on other sites

 

 


I too am having this problem with the mechanic

 

Could be affected by same issue reported by Djembe, one that is related to your particular usage scenario, with almost all features turned OFF, except "Checklist".

 

That wasn't a heavily tested scenario, until Djembe brought it up and has been fixed since.

 

Suggest you wait for next update, by the end of this week and should be plain sailing after that.

Share this post


Link to post
Share on other sites

I was thinking that you have problems AFTER return to "factory default" ... 

My first post was out of the problem.  :Whistle: 

 

Did you try to say "cockpit to ground"? have to work in that way.

Share this post


Link to post
Share on other sites

 

 


Also, do you think it would be possible to add a variable in mce.ini to automatically disable MCE's "use data" option via the monitor tab

 

It's implemented in latest package V2.6.5.2

 

Add the following to [OPTIONS] section in mce ini and Vspeeds call-outs will be disabled.

 

UseVspeeds=0

 

Default is enabled when option is missing in ini file

Share this post


Link to post
Share on other sites

It's implemented in latest package V2.6.5.2

 

Add the following to [OPTIONS] section in mce ini and Vspeeds call-outs will be disabled.

 

UseVspeeds=0

 

Default is enabled when option is missing in ini file

Thank you, Gerald!

 

Did you guys make any alterations to ground operations?  

Share this post


Link to post
Share on other sites

Thank you, Gerald!

 

Did you guys make any alterations to ground operations?  

 

You're welcome.

 

No changes to interaction with Mechanic.

 

Only addressed some unforeseen issues when user disables all MCE features and wants to communicate with ground mechanic or GSX exclusively.

Share this post


Link to post
Share on other sites

Safe to install over the top of the existing MCE? 

 

Not recommended.

 

If you try that, Windows Installer will kick in and ask whether you want to Repair or Remove. If you click repair it would use the cached installer in C:\Programdata\Package cache\ folder to re-install the previous version.

 

A lot of installers will typically have a cached package there. For those using SSD with limited space, it pays to go there every now and then and recover some space.

For instance, P3D would have something like 10 to 12 GB installer backup package there. MCE, about 600 MB

 

Just un-install via Windows Control Panel, then run "InstallMCE" on the new package. Do not manually delete the \Multi Crew experience\ installation folder as both license.key and installed extra voice packs will remain there.

 

If you care about the newly supported aircraft (in this case CS 737), a quick run of the wizard (without going through speech training) is required. Its main purpose is to copy the CS 737 pre-made scripts to the relevant folder.

Share this post


Link to post
Share on other sites

Is there any point installing the latest version/update? I am a bit concerned about having to reinstall everything (not very easy, I struggled to get it going the first time)...

Does the new version improve a few things or does it just allow use of the extra aircraft (I forgot the name of)?

I don't really want to mess up my set up.....

Thanks 

Share this post


Link to post
Share on other sites

When you reinstall MCE you do not need to setup all again. The mce.ini is not deleted.

Just take a few minuts and you do not need to setup nothing after reinstall.

Share this post


Link to post
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
Sign in to follow this