flying engineer

In regards to ATC menu selections at small non-towered strips. Has anyone come up with a fix for the wrong wording in the ATC menu for West departure or was this a hard coded error made by the ACES? North, South and East departure all look normal.

Would someone please explain what the two following MCE UI Options are expected to do. How do they improve the MCE/FSX performance? "Enable Optimization" & "More Responsiveness". Edwin Brown Keremeos BC Canada

FS++ got back to me with some new files and no more alarms on shut down.

dental12 You are not alone in the frustrating struggle to get what you expected out of MCE. Have been trying for 3 years to get successful simple VFR flight in the single engine Default FSX Cessna with no copilot. All I wanted was to broadcast blind at non-towered strips and the usual communications at towered strips. MCE comes up with all kinds of weird ATC happenings that make no sense at all. Best I ever had was a long time ago when forum member Dick B came up with his No Copilot Wanted fix. The FS++ Crew has had all kinds of suggestions but no luck so far. Hate to give up but I'd rather be flying than chasing down mysterious problems. Edwin Brown Keremeos BC Canada.

Sorry to report that the same error beep is back and I have no idea why? Went through the Active Sky Next x-gauge uninstall again but no luck this time. No error shows if I don't start/use MCE? Event viewer data same as before -- fsx.exe & panels.dll. No big deal but it means something is not right and I'd like to find out what it is.

Believe I have found the reason for the shutdown error message etc. Active Sky Next has an option to install their X Gauge and I had elected to install this on ALL the FSX aircraft. As soon as I uninstalled these through the ASN options panel I got no more shutdown errors. ASN must have gone into the panels.dll and made the changes that caused the problem as far as I can tell. Thanks to all and specially the FS++ Support Crew. Edwin Brown Keremeos BC Canada

Thanks for the heads up. I used to be on the MCE e-mail notification some time ago but maybe they have stopped this practice. Downloading now.

Made a number of flights with several default FSX aircraft and fsInsider disabled. No errors on shutdown of FSX. Today I enabled the fsInsider and got the Windows error beep on shutdown of FSX. Just the beep --- no other error popup window. Also had the very same poor ATC voice connection as before. Part of the event viewer data description shows: "faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14" "faulting module name: panels.dll, version: 10.0.61637.0, time stamp: 0x46fadb50" I have no idea what this means but obviously I have a problem when trying to use MCE. Not sure what to now? Should I e-mail FS++ with the event viewer data as an attachment? (Don't know how to copy and paste here).

MCE license was renewed April 16 2014 in an attempt to fix other problems. MCE V2.6.0.6 install date shows 6/5/2014. fsInsider.dll properties shows version 2.6.0.6 dated 6/5/2014. Tried my favorite Quest Kodiak on identical flight from KIGM to KIFP and had no error popup on shutdown. Will make a few more flights with fsInsider.dll disabled.

Went into the FSX installation folder and renamed "fsInsider.dll" to "disabled-fsInsider.dll" as suggested. Started FSX and set up options to run as prior to MCE installation. Brought in Active Sky Next for real weather. Flew the FSX Cessna Skyhawk from Kingman (KIGM) to Laughlin, Bullhead Int'l (KIFP). All ATC worked as it should with all text coming up and audio through the USB headphone. Parked at the assigned spot and shut the Skyhawk down to cold & dark. Saved the KIFP spot as default for next start up. Shut down FSX as I normally do using the "End Flight" option, checked the log book and then "X" out of FSX. No error popup this time ?? Shut down Active Sky Next as usual. Now see that the "disabled-fsInsider.dll" has disappeared and am wondering what to do now? My bad --- the "disabled-fsInsider.dll" has not disappeared. Got moved in the folder of course!!!

I fly single engine aircraft and don't want a copilot. Here is what I have checked off in the tabs: General Tab --- Talk to ATC controllers ATC Tab --- use btn1: ch flight sim yoke USB Options Tab --- Enable optimization & More responsiveness Other Option Panel --- Show Commands in FS The error I'm getting on shutting down FSX is; Microsoft Visual C++ Runtime Library Runtime Error! Program: F\Microsoft Flight Simulator X\fsx.exe R6025 pure virtual function call The Event Viewer data seems to point to a problem in the FSX panels.dll which I don't understand at all. All this is much beyond my limited computer knowledge. Thanks for the interest.

Anyone else getting the Windows alarm sound on shutdown? Haven't been able to find out what is causing his since installing v 2.6.0.6.

Getting the Windows 7 Pro 64 default beep when shutting down FSX since installing MCE version 2.6.0.6 Reinstall does not stop the problem. MCE also not responding anywhere near as expected on attempts to talk to ATC with USB headphone/mic setup. Have had this poor ATC problem since 2011. Have asked for help through e-mail to FS++ but no reply yet. Edwin Brown Keremeos BC Canada

Glad to report MCE works much better in the "big iron" and the co-pilot, for the most part, does his thing OK. My problem still happens when flying the singles between non-towered strips. No co-pilot aboard of course. MCE ATC communications still very unpredictable -- works OK sometime through entire leg and then, for whatever reason, doesn't get through at some point of the leg and I have to resort to voice command selections of the ATC options. The frustrating part is that the exact same phrases I am using are then coming up when I make the voice command selection. Am still enjoying FSX though.

FS++ Crew sent me the link for version 2.5.8.2 on December 15 2013 and that is what I've been using. After the last uninstall I went through my entire computer system and removed anything to do with MCE. All folders on any drive, and every thing in the registry. All I left was the main folder for MCE with my license code. The last install cured the mic/speaker sound problem ??????? I have not put in the "Dick is here" nor altered anything in the mce.ini file. I have everything set up in the GUI for what I want, including not to insist on an accurate call sign. My two favorite aircraft are the RealAir Scout and the Quest Kodiak but I use the FSX default Skyhawk for testing out MCE. Not that I think any particular aircraft is the problem. Am going to take up an FSX default twin, with a fully functional default GUI, and that pesky co-pilot to see if he can have more luck communicating. Thanks again for the help.

Have lost track of how many times I've uninstalled and reinstalled MCE version 2.5.7.8. Last installation, for whatever reason, cleared up the voice sounds problem I had. Now having that same old problem of no recognition when transmitting to ATC for landing instructions and no recognition from Ground Control for taxi instructions. Even though I use the same words that come up when I finally give up and just use voice command to select whatever ATC number I need. Have been making the same flight every time and have copied down the words. Have tried the new FS++ crew suggested "vGaAtcCtrlFsx.cfg" but makes no difference that I can see. Have run out of ideas and patience. Thanks for the reply. (I still remember the "Dick is here" help you gave me some time ago.

Had everything working very well thanks to FS++ crew help. Now, for some unknown reason, the ATC and ATIS sounds are coming through the speakers instead of the headphone. Have checked Windows 7 Control Panel/Sound settings and all still the same. Playback = Speakers Creative SB X-Fi as default device Recording = Microphone 2-USB Audio Device as default FSX sound set up is the same as before. Have cycled back and forth here but no help. Have gone through the MCE Assign Sound Device again. The Speech Application Programming Interface (SAPI) does it's thing as always. Have also gone through the APP Wizard again. Not sure what to look for now. Would really like to get back to all Radio sounds through headphones and aircraft etc sounds through speakers. Any ideas out there? Edwin Brown Keremeos BC Canada

FSX is on it's own SSD and has been there for some time. Have never used "xPack.msi" for any installation. MCE is in the registry; HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\FS++\MCE Am up and running again. Thanks for the help.

There was no MCE dlls folder in the root FSX. Copied & pasted as you suggested and now have things looking better. Now have to try and get MCE to work with voice commands. Is there some logical explanation as to why 3 uninstall - reinstalls failed to create the MCE dlls folder. Thanks for the help.

Originally bought MCE back in July 2011. Just got back into FSX after some time away. Installed MCE version 2.5.7.2 and then 2.5.7.8. Installation all goes OK and able to get total success at all stages. However, both versions end up giving me the same problem. Procedure being used; Start up FSX from a saved flight with a default aircraft as instructed. Use alt/enter to shrink FSX screen down to get access to MCE desktop icon. Start MCE via desktop icon. MCE UI comes up and all 6 tabs options set up as preferred. MCE UI does it's shrink down to small bar as expected. This is when FSX locks up in the minimized screen view and nothing can be done. Both versions end up with this locked up FSX screen and no way out but to go to Task Master and disable FSX. Hope someone can help. Ed Brown Keremeos BC Canada

GHarrall, That explains why I've been seeing cores 5 & 6 activity go up with MCE running with the "enable optimization" checked. Never did expect to see that and there is no info anywhere in the MCE manuals that I could find. Good thing to know. Re the "more reponsiveness" -- how does MCE go about raising it's own priority and where does it do this? Does anything get bumped down in this priority -- wherever that is? Thanks for the reply. Edwin Brown Keremeos BC Canada.

GHarrall, So do you ever get the yellow print out in the ATC box showing what you said coming into a non-towered strip? Every once in a while I do get it. That indicates to me that MCE can in fact handle communications around non-towered strips. Will continue testing in the hopes that the answer can be found. Thanks for the reply. Edwin Brown Keremeos BC Canada.

Installed latest version to give MCE another try. (Started out with version 2.4.4.8 way back in 2011) VFR, no copilot wanted, small aircraft flight simmer still can't get position announcements coming into non-towered strips. I know there are other MCE users who don't use anything but the ATC function reporting good results. I sure would like to join that group but have had very limited success on position announcements -- most often, in frustration, just saying the ATC number to get my transmission through. FS++ Crew has been involved in this from day 1 and have done their best to try and help me. Their latest reply states that it is a "dark art" for a technician to solve but they are trying! Have done the same flight over and over again from Kelowna (CYLW) to Penticton (CYYF) as a test for every suggestion and solution problem solving hint that anyone has passed on. The frustrating part is that I am saying exactly what the ATC number selection comes up with if I select that. Any suggestions from a VFR, no copilot wanted simmer to add? Edwin Brown Keremeos BC Canada.

Thanks CoolP, As you can see by my sig I should have no problem having these both checked. Have been using the Task Manager, CPUID & Core Temp for quite some time to monitor things. Edwin Brown Keremeos BC Canada.

In the User Interface General Options tab there are two items; enable optimization more responsiveness Exactly what do each of these do if checked? Edwin Brown Keremeos BC Canada.