paj

Another thank you! Deleting the TODO file allowed my Win10 upgrade to proceed too.

Hi, I am missing the hotspot to bring up the main FS2Crew panel in the virtual cockpit (only). The click spot *is* present on the 2D panel where it works fine. I can also bring up the main FS2Crew panel via the Views menu or the keyboard command. Any idea why the hotspot isn't working in VC? (I've tried switching between button and voice modes and also uninstalling/reinstalling FS2Crew... but I can't get the VC hot spot to work. I'm sure the hotspot worked originally in FSX... but I've just started trying to install FS2Crew into P3D and I think that has affected my FS2Crew installations which have the same clickspot problem in both FSX and P3D. I found this old post about the same issue but there was no resolution. I can confirm my gauge has been trusted in FSX and I have the VCockpit36 entry in my panel.cfg in both FSX and P3D) Thanks Peter . i Jones

I'm also struggling to get VoxATC (demo) and MCE to play happily together. When used in conjunction with VoxATC should MCE be set to NOT have "Exclusive access to recognizer” on its "Command" setting tab? Thanks Peter.

Hi all, Many thanks for the responses. I've found many of my problems were caused by my attempting to run MCE with user-access-control on. I had of course installed MCE with UAC off and always run it using the "as administrator" option. But on my Win7 x64 box it seems UAC=on stops several MCE commands working. Just in case it helps somebody else I found the following commands were recognized by MCE but resulted in no actions: engine generators on IRS to NAV Start switches continuous relight select tow-gar power start engine (1|2) - with UAC off this process required manual change of engine start switch to GND before it completed successfully set autobrake RTO release parking brake set flaps xx - with UAC off the first call to set flaps works, but subsequent calls move flaps to full deflection up/down only! equipment tests (GPWS, fire protection system, overspeed warning, lights, stick shaker, transponder etc) calls to ground and cabin crew That may seem like a lot of things not working but in fact most of the most common commands worked fine for me with UAC on. I was reluctant to turn UAC off permanently due to the fact that I've never needed to before, there is a (admittedly slight) increased security risk and mainly because I knew EZdocCamera (EZCA) does not work on my computer when UAC is off. I've since found a forum post suggesting uninstalling and reinstalling EZCA with UAC off will allow it to subsequently work regardless of the UAC setting. I've just tried this and I now have MCE and EZCA working with UAC=off and I'll continue to run my computer that way. Well, there are a few other small questions I have regarding MCE but I'll put those in another topic. Thanks again for your suggestions.

Hi, I've just purchased MCE and have so far only tried it with the PMDG 737NGX. I've hit a few problems which someone here may be able to assist me with. Here are my most pressing MCE issues: 1) Starting a new flight cold & dark I find I can't "set autobrake RTO" as the copilot replies "can't select rejected takeoff on the autobrake when we are airborne captain". We are most definitely on the ground. 2) When I request him to "release parking brake" his only response is to yell at me "do you want to destroy the gear on landing or what?" 3) Whilst I can get my co-pilot to set the vertical speed to a positive value I can't work out how to get him to set a negative VS. 4) How do I ask the copilot to retract the flaps by just one notch? (The only command I found in the 737NGX that allows extension of the flaps by one notch is "extend slats") 5) If I load a flightplan into FSX and then start MCE it successfully lists origin, destination, registration and crz alt on its ATC tab. But can this information in MCE be updated ? (eg If I load MCE before setting a flightplan the MCE ATC tab remains mostly blank and its "flight plan" button is always greyed out) Many thanks for any suggestions! Cheers Peter.

I too was interested in Multi Crew Experience.You should read this thread from PMDG: http://forum.avsim.net/topic/357841-pmdg-737ngx-with-multicrew-experience-finally-talking-to-your-fo/

Hi Fabrizio,Bryan addressed the issue of many voice commands (such as MCP course, altitude and speed) not being actioned prior to flight in this thread: http://forum.avsim.n...se-to-commands/I too would like to see the F/O respond to more voice instructions at all stages of a flight.

Hi Bryan,Many thanks for that answer. It's a relief to know FS2Crew is working as designed.It's not obvious to me which FS2Crew commands are restricted and when they can be used and when they are disabled (did I miss it in the online documentation?)But could I still urge you to consider removing the restrictions on when certain commands work - even if as an option?I would find it tremendously helpful to be able to use at any time the available FS2Crew voice commands for the MCP, overhead, center console and FMC.I find the the speech recognition to be very good and, judging by commands detected on the FS2Crew "green status bar", any errors are few and would not outweigh the benefits of using a broader range of FS2Crew's commands.CheersPeter.

Hi,I'm new to using FS2Crew but I installed the Voice version without difficulty and managed to get the flows working (...but I'm still looking forward to the Tutorials).My main problem at the moment is uncertainty as to when I can issue ad hoc commands to the F/O.For instance, I've found the F/O ignores requests to perform most of the MCP and Overhead commands unless we are flying. After engine-start I tried issuing "set heading xxx", "flaps 5", "select wipers on", "Select Seatbelts Off", "Select Seatbelts On", "Select TaxiLight Off" etc etc but the F/O did not do any of these tasks despite the commands being understood (ie displayed correctly in the green status bar).In fact, with the F/O refusing to do most of my instructions I assumed he was broken/dead and there was something wrong with my FS2Crew installation. I was surprised when I tried these same commands in the air and they worked! Why don't simple instructions such as turning the wipers on work during earlier phases of flight? Am I doing something wrong? (probably)ThanksPeter.

Many thanks guys for this fix in particular: My saved flights which failed to initialise under SP1b now work fine with SP1c.CheersPeter Jones

...and other causes+solutions for MSVCR90.dll crashes in this thread.

Michael, In my case the 737NGX crash was caused by just 4 lines within the runways.csv file. The four entries were for the airfield North Plains (1OR4). When I deleted all 4 lines for 1OR4 everything worked! Do you have this scenery for 1OR4 from OZx installed too? The error seems to be due to duplicate entries for the R09/R27 runway originating from these two files: OZx\OZx_NA\scenery\tm_1OR4_AFX.BGL ORBX\FTX_NA_PNW05_SCENERY\scenery\ADE_FTX_PNW_1OR4_North_Plains.bgl CheersPeter J.

I just solved my FSX crash (faulting module MSVCR90.DLL) which was triggered whenever I loaded the PMDG737NGX. My problem was caused by the presence of the file "runways.csv" in the root of my FSX folder. Simply disabling this file by renaming it allowed the 737NGX to load as normal. This solution was originally posted by Michael Gadeberg here. CheersPeter J.

OMG - Thank you! Removing runways.csv from the root of my FSX folder just fixed the MSVCR90.DLL crash which I was encountering whenever I loaded the PMDG737NGX! In my case I don't own Radar Contact 4. But I do own UltimateTraffic2 and SuperTrafficBoard which seem to use the runways.csv file. I'm not sure how I can continue to use both programs and still fly the 737NGX? CheersPeter J.

After a couple of weeks of successfully flying the 737NGX I loaded a flight tonight with the aircraft and experienced the same FSX crash involving MSVCR90.DLL as the OP! Why the 737NGX would suddenly start crashing FSX is baffling. I've now downloaded the latest full installer from PMDG, uninstalled/deleted stray files+folders/reinstalled the 737NGX, and still have the same crash-to-desktop error! I've just tried to submit a support ticket to PMDG... but their support site isn't responding (oh the irony!)... I'll try again later. RegardsPeter J