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.

Latest version, hard mute joystick button stopped working

Featured Replies

Hello,

I recently updated to the latest MSFS version (glad to see V speeds can be read from the PMDG again.)  I've encountered an issue though: my hard mute joystick button has stopped working (the button equivalent to pressing num lock.)  It worked correctly when I first loaded the new version, but stopped working after an MCE lockup halfway through the flight.  I restarted MCE successfully, but since then (even after a sim restart) the mute button on my joystick doesn't work.  Num lock still works normally.

The button in question (Warthog Joystick button 3) is listed correctly in the MCE.ini file. It is also shown in the MCE program interface, but I think that interface is intended to be able to change / assign a new button?  It is unresponsive to any button presses.  The button tests correctly in the windows controller dialog, and can be assigned to other sim functions, so I don't believe it's a button issue. 

I remember having this same issue several versions ago, but can't remember how to fix it.  Any suggestions? 

Thanks! 

Andrew Crowley

  • Commercial Member
34 minutes ago, Stearmandriver said:

Hello,

I recently updated to the latest MSFS version (glad to see V speeds can be read from the PMDG again.)  I've encountered an issue though: my hard mute joystick button has stopped working (the button equivalent to pressing num lock.)  It worked correctly when I first loaded the new version, but stopped working after an MCE lockup halfway through the flight.  I restarted MCE successfully, but since then (even after a sim restart) the mute button on my joystick doesn't work.  Num lock still works normally.

The button in question (Warthog Joystick button 3) is listed correctly in the MCE.ini file. It is also shown in the MCE program interface, but I think that interface is intended to be able to change / assign a new button?  It is unresponsive to any button presses.  The button tests correctly in the windows controller dialog, and can be assigned to other sim functions, so I don't believe it's a button issue. 

I remember having this same issue several versions ago, but can't remember how to fix it.  Any suggestions? 

Thanks! 

Since V3.0.0.0 we are now providing "Button control" (for some planes) for those intimidated by the need to speak English so they can have a passive experience with crew ambience triggered with a button press (F button for flows", (C for checklist) and R (for Requests).

You don't have to use them at all.

The aircraft scripts folder now has a <BTN> folder. These are for button control. Nothinghas changed with regards voice control

I suggest you save your "mce.ini" just in case, then reset MCE to factory settings.

You 'll have to go through the wizard again, but there is no need for speech training.

Re-assign joystick buttons as they were and just ignore the new P & C buttons. If you click them, they will prompt as to whether you want to assign a joystick button to simulate the button press, reply No.

There is now full Simbrief integration, with most info shown in MCE. If you need more displayed, just ask.

This opens the possibility for FO to setup the FMC CDU as he would have all the info he needs.

Obviously, mostly for those who don't know how to setup the FMC or just tired of inserting the data over and over.

You still have to insert SID STARs

The CDU automated preparation is still works in progress, but you can try the command "prepare fmc cdu".

The Fenix has a way to insert Simbrief flight plan via the secondary FPLN page.

Is there a reliable way to do that with PMDG?

 

 

 

  • Author

Ah, this makes some sense.  I saw the new softkeys on the upper left of the MCE panel, and since I didn't know what they did I promptly clicked them all.  😁  I probably activated that button click mode.  I'll do the wizard again. 

The PMDG can import a simbrief flight plan via the "request" prompt on the RTE 1 page.  It cannot pull directly from simbrief though; you need to have used the simbrief downloader utility to have exported the files needed for the flight - I believe you get a .rte and .wx file, which are then used to simulate datalinked route and winds info to the FMC.

Andrew Crowley

  • Author

Well, I restored MCE to default settings and re-ran the setup wizard.  Still having some problems with this version.

Both the first time I installed this version, and just now after restoring to default and running the wizard, I had a problem on initial launch:  after loading into the PMDG in MSFS (twice, to be sure) I launched MCE.  It hung on this first launch at "searching for simulator".  It did this the first time as well, and I used the task manager to force close it and then relaunch it.  Same thing happened this time; I let it sit for 10 minutes but it was good and hung.  Finally force closed it and ran it again.

MCE recognized the sim and aircraft this time, and loaded.  But within a few minutes (I did not touch any of the button controls this time), the MCE first officer was ignoring all my commands.  I closed and re-launched again, and did a few more minutes of testing.  I found that he would carry out commands now, but neither of my joystick mute buttons worked.  (Button one was set up in the wizard as my radio PTT, and I then set button three up in the MCE panel as my num lock emulation / hard mute.)  MCE heard me regardless of whether I was holding down my PTT, and button 3 - the numlock emulator - does not work at all.  Both of these buttons look to be currently defined in the mce.ini.  

Seems there's some instability here for me now, that wasn't here before.  What do you think; should I delete and try a re-install?  

I'll attach my .ini here. 

Thanks!

Spoiler

[WINDOW]
Left=341
Top=135
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=1
MoreResponsive=1
TrainingCompleted=1
RandomFailures=0
TweakFsConfig=0
AtcMikeUseIvao=0
ForceCopilot=1
AudioIn=
AudioOut=
PilotName=andrew            
ShowCommands=0
ForceCommands=0            //(deprecated. Do not use)
DisplayTime=3000
UseMacros=1            //(must be set to 1 For VoxKey to work)
UseNarrator=0
LoudData=0
EnableAnnouncements=0
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=1
AllowActionOnEvent=0
V1CalloutIsGO=0            //(Enable this to follow Lufthansa standard call-out procedures. PNF calls-out Go instead of V one)
ReduceChatter=1
AutoNotifyOnSilentFlowStart=1
UsingFullHardwareCockpit=0    //Enable this is using a simpit with all switching via hardware


[PROFICIENCY]
Level=3

[SPEECH]
CanDo=1
Volume=100
CpuUsage=75
SpeechPace=750
InprocReco=1
DisablePitchChange=0
MaxConcurrentTasks=4
NumLockKeyMutesReco=1

[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 =CereVoice Nathan - English (East Coast America),0,0,0,0
Voice1 =Richard,0,0,0,1
Voice2 =Stella,0,0,0,1
Voice3 =William,0,0,0,1
Voice4=Microsoft David Desktop,0,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=1
FsDialogs=1
FsKneeboard=1
ViewsAndViewpoint=1

[GAMEPAD]
JoyManID=Joystick - HOTAS Warthog
JoyProdID=Joystick - HOTAS Warthog
JoyButton=1
UseWithVoxATC=0        //(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)

[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=C:\Program Files (x86)\Multi Crew Experience

[TERMINATE]


[HARD_MUTE_JOY]
JoyManID=Joystick - HOTAS Warthog
JoyProdID=Joystick - HOTAS Warthog
JoyButton=3
[MSFS_CHECKLIST]
PMDG 737-700 Alaska Airlines (N612AS | 2019)=C:\Program Files (x86)\Multi Crew Experience\ChkLists\PMDG737-800_check_MINE.txt

 

Edited by Stearmandriver

Andrew Crowley

  • Author

And, some further data.  Got a couple quick flights in tonight, and noted a couple more glitches.  First, MCE often seems to not be muted even when I've used the num lock key to mute him, and the program has annunciated "speech off."  MCE still hears me talking and occasionally tries to interpret it as commands.

Also, I'm still getting the third voice, the guy who says "checks" a lot.  He always responds to my first officer's transition altitude / level calls, and he always responds "checks" to ten thousand.  I have been very careful not to activate the button press mode this time.

So, I think I've gotten something wrong here.  I expect it's something I did ;).  But if you have any further suggestions I'd appreciate it.

Andrew Crowley

  • Commercial Member
15 hours ago, Stearmandriver said:

And, some further data.  Got a couple quick flights in tonight, and noted a couple more glitches.  First, MCE often seems to not be muted even when I've used the num lock key to mute him, and the program has annunciated "speech off."  MCE still hears me talking and occasionally tries to interpret it as commands.

Also, I'm still getting the third voice, the guy who says "checks" a lot.  He always responds to my first officer's transition altitude / level calls, and he always responds "checks" to ten thousand.  I have been very careful not to activate the button press mode this time.

So, I think I've gotten something wrong here.  I expect it's something I did ;).  But if you have any further suggestions I'd appreciate it.

It appears to be a screw-up in the moist recent update related to the numerous joystick toggles in place. Thanks for reporting. Like unintended disabling of the commands because the wrong button was seen "down".

WIll be looked at today and probably a new package will follow later on.

 

 

 

Edited by FS++

  • Commercial Member
7 hours ago, Stearmandriver said:

Also, I'm still getting the third voice, the guy who says "checks" a lot.

We thought it would be a good idea to let the automated call-outs and subsequent "check" play whenever the speech engine isn't installed OR when the user disables speech reco, with the assumtion maybe just wants to switch to button control at night.

I know from your Twitch channel that you use the Mute button a lot and that's why you are getting them on takeoff.

There will be a patch to only allow them when the user setup isn't speech reco capable. In the long term, this will probably lead to a need for a new option say to "operate in Button mode only", "Mixed mode" or Voice control only.

 

Gerald,

I also am having issues with this version. I'm running FSX, my aircraft is the beech baron. With this latest version the copilot no longer responds to my flap requests.  Says the aircraft has no flaps settings of 15 or 30 which it clearly does in the aircraft.cfg file. Was working in all other versions. My flying partner uses the same aircraft and has the same problem.  

Thanks,

 

Tony J

 

 

  • 2 weeks later...

Hello.

 

It is also possible to implement this button feature on x-plane?

Regards.

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.