GeorgeMB

That was interesting. That 737 in the video.

I fly the PMDG MD-11F mainly and that plane autolands beautifully. You're even able to keep the auto throttle on and engage reverse thrust. For the Boeings I believe auto throttle needs to be disengaged or the reverse thrust won't activate for you. From videos I've seen the pilot will disengage autopilot at or around 1000ft. Weather being a factor of course. Also at some airports and runways you may need to do a DME VOR approach with no ILS beam. So it's good that you want to know how to land manually. I would suggest you look up real world cockpit approach videos of the planes you fly and you will most likely be able to see or hear the procedures used for certain aircraft.

I couldn't find those two folders anywhere. I can't be the only FSX user who's having this problem. And I have gone directly to the Ezdok forums and posted and also emailed people from the dev team and I have not gotten a reply. Flight1 doesn't have a ticket option either for this software. I mean could there be something wrong with my FSX + Accel install? ''Application can not run. First start configure tool for registered components.'' I had v1.15 with the 1.17 update before and never did a flight without it since I bought it, so I know the program is great. But stuff like this is just And it's probably something simple but what else can I try? Thanks for the replies Poppet.

Thanks for the reply Poppet, I do have EZCA.exe running in Admin. Also I couldn't find any simconnects located in my main FSX folder. And I launched the configure tool, open options--> unregistry components. Then options--> registry components. I got two windows after. They looked like this: RegSvr32 DllRegisterServer in dx8vb.dll succeeded RegSvr32 DllRegisterServer in Ezsc.dll succeeded But still I got the ''Application can not run. First start configure tool for registered components.'' I have gone to the flight1 forums about this and even emailed support. But nothing from them yet.

Hello, Maybe someone can help me with this problem. I have been unable to use EZdok since trying to run the new 1.18.7 version. The V 1.15 with the 1.17 update ran fine for me in the past. So I download the exe and run it in administrator and everything seems to load fine. And I run the EZCA config.exe tool like it says but every time I start FSX I keep getting this message: ''Application can not run. First start configure tool for registered components.'' I have performed the options configure FSX files registry and unregistry components plus conflicting hotkeys and still no go. I have the config.exe desktop shortcut permanently to admin. I have run the registry components option again and again and still get the same error message. Also I have anti virus off and UAC off. What the install does for me automatically is it makes a folder called ''EZdok Software'' in my C:\ drive. That folder has two files called ''ezdokcam1.lic'' and ''EZdok-Setup-1.18.7.exe'' Then it makes a other folder in C:\Program Files (x86) called ''EZCA'' That one has 14 files 2 folders at 11.7 MB. And those are the only two locations that seem to have EZdok stuff. I also ran the file simconnect.msi and Ran the config tool. I did both registry and configure FSX files and then started the sim in that order and I'm still getting the same error message. I get a other message too it says: ''Found 3 installed simconnects in system. EZCA switched to 10.0.61259.0'' Is that a normal setup message? I have FSX Gold + Acceleration W7-64 Thanks for any help. Regards, George.

Okay I'll give it a shot. But I don't have any previous versions loaded in my system. I did a system restore of my computer it's been two years since I did that last and I'm in the process of reinstalling everything FSX related. I wasn't even aware of the update until a few days ago haha.

Thanks for the replies Jetsmell and Onebob. I'll try that but I don't know. I have uninstalled and reinstalled 1.18.7 a lot. And it's the same problem every time. I wish they'd have a up do date manual on installation of it and trouble shooting guide of some kind. Because I've read on some other forums unofficial ones though that you should have v1.15 installed first. And then others make no mention of it. And I have posted this same question on the official flight1's EZdok forum a couple days ago about where I can get a official v1.15 exe download but no reply. As for Googling EZDOC 1.15 I have but I can't find anything official. Just plenty of torrent sites that claim to have it but I'm not comfortable with those.

Hello, For some reason I can't get v1.18.7 working for me. Error massage appears saying check for registered components. I bought Ezdok some time ago and was running fine with the 1.17 update. But on the flight1 page where you download the product It only has v1.18.7 there. So I'd like to download the 1.15 base package exe again and just update to 1.17 but where can I find v1.15 again? I'm using FSX gold with Acceleration W7-64Bit Thanks for any help. George.

FS++, This fix has worked very good. Thank you for taking the time to look into it.

Well I hate to bug tech support over a small issue like this but I'll drop them a line about it as you suggest. Thanks for your time David.

Thanks for your reply David. I played around with the vox script phraseology as you suggested and it still didn't work. But I did notice that MCE never switches the MD-11 taxi lights switch to just taxi. It goes right to land. Even with a voice command. You flown the PMDG MD-11 before so you know how that plane has the two landing light switches and the taxi toggle switch has both taxi and land options. Well it seems that if the taxi light switch is on at all MCE thinks the two main landing light switches are on already too. But with the taxi light switch off the before take off flow works just fine. I'm still having issues with the flaps. I tried editing the landing flow script and added ''set flaps to twenty eight'' so a verbal command would not even be needed but it wasn't recognized. Small issues not a big deal if these things don't work. But the light thing is odd.

Hi, I been really enjoying MCE since I bought it. But I got a few issues with the add-on I'm hoping I can get some information on how to correct them. First issue I'm having is with a script flow and some of its actions not being performed. It's with the before take off flow script in the MD-11F which is the plane I mainly use with MCE Here is the script I use: I edited it a little. [OPTIONS] Suspend=0 Verbose=1 RequireConfirmation=0 [REPLIES] [COMPLETED] Completed1=ready for takeoff checklist [sCRIPT] high intensity lights on pause=1 landing lights on pause=1 taxi lights on pause=1 transponder on pause=1 The co-pilot always puts the high intensity lights to on with no issue but never the landing lights or taxi lights to on. He says landing lights on but the switch never moves to on. I have to do it manually. This seems to be the only flow I been having this issue with. A other issue I been having is with requesting flap settings. The co-pilot understands slats extend and flaps 10, 15, 35 and 50. But he never seems to understand flaps 28 which is a flap setting the MD-11 uses for approach. I say flaps 28 but I get 20 instead. Those are my questions for now thank you for any help. Regards, George.

That did the trick :smile: Thanks for taking the time to help me Charlie130.

Hi, I read that scripts and flows can be edited in MCE but I'm not 100% sure what file or files to do it to or how. I mainly just want the FO to not shutoff the Hi-intensity lights on his after takeoff flow because I don't believe that to be a SOP in the MD-11. Since those lights are it's strobe lights and those lights must be on all times when in the air is my understanding correct?

Well, I think I got this egg cracked finally. Well you guys did B) So I reinstalled GSX minus anti virus, MCE and FSUIPC4. Thanks for that anti virus catch Firehawk44. After GSX was reloaded I added the stand alone add-on manager, plus VC++2013 runtimes per FSDreamteam's support forum and FSX worked. Then I went on to add FSUIPC4 and later MCE and everything is installed and working fine with my FSX now. I'm not sure what the root cause of the problem was. I'll guess the visual runtimes were the big thing and the add-on manager but I don't get why FSUIPC4 was acting up because of it. But everything is coupled and working as of now. I thank you guys so much for the help, I would have never figured it by myself. How you guys can read those appcrash reports is magic in my eyes. Again big thanks AVSIM crew. Regards, George.

Well I just reinstalled GSX minus MCE. And got two CTD's. Sorry if I copied and pasted to much info from the appcrashviewer. Not sure what info is useful or not yet. I'm not getting anywhere fast with this problem though. :angry: #1 Version=1 EventType=APPCRASH EventTime=130694399721971918 ReportType=2 Consent=1 ReportIdentifier=7331b3e0-bdd0-11e4-91b2-00038a000015 IntegratorReportIdentifier=7331b3df-bdd0-11e4-91b2-00038a000015 WOW64=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61472.0 Sig[2].Name=Application Timestamp Sig[2].Value=475e17d3 Sig[3].Name=Fault Module Name Sig[3].Value=StackHash_0a9e Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=ffba0016 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=C:\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\syswow64\USERENV.dll LoadedModule[30]=C:\Windows\syswow64\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=C:\FSX\language.dll LoadedModule[61]=C:\FSX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=C:\FSX\ablscpt.dll LoadedModule[64]=C:\FSX\flight.dll LoadedModule[65]=C:\FSX\ai_player.dll LoadedModule[66]=C:\FSX\acontain.dll LoadedModule[67]=C:\FSX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=C:\FSX\fsui.dll LoadedModule[70]=C:\FSX\atc.dll LoadedModule[71]=C:\FSX\facilities.dll LoadedModule[72]=C:\FSX\demo.dll LoadedModule[73]=C:\FSX\main.dll LoadedModule[74]=C:\FSX\fe.dll LoadedModule[75]=C:\FSX\util.dll LoadedModule[76]=C:\FSX\simprop.dll LoadedModule[77]=C:\FSX\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=C:\FSX\g3d.dll LoadedModule[83]=C:\FSX\panels.dll LoadedModule[84]=C:\FSX\multiplayer.dll LoadedModule[85]=C:\FSX\ui.dll LoadedModule[86]=C:\FSX\sound.dll LoadedModule[87]=C:\FSX\sim1.dll LoadedModule[88]=C:\FSX\simscheduler.dll LoadedModule[89]=C:\FSX\visualfx.dll LoadedModule[90]=C:\FSX\window.dll LoadedModule[91]=C:\FSX\terrain.dll LoadedModule[92]=C:\FSX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=C:\FSX\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=C:\FSX\xuipc.dll LoadedModule[99]=C:\FSX\livingwater.dll LoadedModule[100]=C:\FSX\fs-traffic.dll LoadedModule[101]=C:\FSX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Windows\system32\RICHED20.DLL LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll LoadedModule[106]=C:\Windows\system32\rsaenh.dll LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[112]=C:\Windows\system32\wbemcomn.dll LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[118]=C:\Windows\system32\dxgi.dll LoadedModule[119]=C:\Windows\system32\d3d11.dll LoadedModule[120]=C:\Windows\system32\nvd3dum.dll LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[122]=C:\Windows\system32\nvspcap.dll LoadedModule[123]=C:\Windows\system32\nvapi.dll LoadedModule[124]=C:\Windows\system32\bcrypt.dll LoadedModule[125]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[126]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[127]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[128]=C:\Windows\system32\d3d10_1.dll LoadedModule[129]=C:\Windows\system32\d3d10_1core.dll LoadedModule[130]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[131]=C:\Windows\system32\dbghelp.dll LoadedModule[132]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[133]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[134]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[135]=C:\Windows\system32\winbrand.dll LoadedModule[136]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[137]=C:\Windows\system32\WINSTA.dll LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[141]=C:\Windows\SysWOW64\wer.dll LoadedModule[142]=C:\Windows\System32\Wpc.dll LoadedModule[143]=C:\Windows\System32\wevtapi.dll LoadedModule[144]=C:\Windows\System32\msxml6.dll LoadedModule[145]=C:\Windows\system32\SAMLIB.dll LoadedModule[146]=C:\Windows\system32\netutils.dll LoadedModule[147]=C:\FSX\uiautomationcore.dll LoadedModule[148]=C:\Windows\system32\OLEACC.dll LoadedModule[149]=C:\Windows\System32\MMDevApi.dll LoadedModule[150]=C:\Windows\System32\PROPSYS.dll LoadedModule[151]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[152]=C:\Windows\system32\HID.DLL LoadedModule[153]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[154]=C:\Windows\system32\wdmaud.drv LoadedModule[155]=C:\Windows\system32\ksuser.dll LoadedModule[156]=C:\Windows\system32\AVRT.dll LoadedModule[157]=C:\Windows\system32\msacm32.drv LoadedModule[158]=C:\Windows\system32\midimap.dll LoadedModule[159]=C:\Windows\system32\dinput.DLL LoadedModule[160]=C:\Windows\System32\wship6.dll LoadedModule[161]=C:\Windows\System32\wshtcpip.dll LoadedModule[162]=C:\FSX\bglmanx.dll LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[164]=C:\FSX\Modules\A2A_Feel.dll LoadedModule[165]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[166]=C:\FSX\Modules\AccuFeelMenu.dll LoadedModule[167]=C:\FSX\PMDG\DLLs\PMDGOptions.dll LoadedModule[168]=C:\FSX\PMDG_SimConnect_Ldr.dll LoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[170]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[172]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL LoadedModule[173]=C:\FSX\PMDG\DLLs\PMDGEvents.dll LoadedModule[174]=C:\FSX\PMDG\DLLs\PMDGSounds.dll LoadedModule[175]=C:\FSX\WaveLib.dll LoadedModule[176]=C:\FSX\fsInsider.dll LoadedModule[177]=C:\Program Files (x86)\AOL Desktop 9.7\idleproc.dll LoadedModule[178]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[179]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[180]=C:\Windows\system32\WINNSI.DLL FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\FSX\fsx.exe #2 Version=1 EventType=APPCRASH EventTime=130694398998433479 ReportType=2 Consent=1 ReportIdentifier=48026d81-bdd0-11e4-91b2-00038a000015 IntegratorReportIdentifier=48026d80-bdd0-11e4-91b2-00038a000015 WOW64=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61472.0 Sig[2].Name=Application Timestamp Sig[2].Value=475e17d3 Sig[3].Name=Fault Module Name Sig[3].Value=StackHash_0a9e Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=ffb80016 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=C:\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=C:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\syswow64\USERENV.dll LoadedModule[30]=C:\Windows\syswow64\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=C:\FSX\language.dll LoadedModule[61]=C:\FSX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=C:\FSX\ablscpt.dll LoadedModule[64]=C:\FSX\flight.dll LoadedModule[65]=C:\FSX\ai_player.dll LoadedModule[66]=C:\FSX\acontain.dll LoadedModule[67]=C:\FSX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=C:\FSX\fsui.dll LoadedModule[70]=C:\FSX\atc.dll LoadedModule[71]=C:\FSX\facilities.dll LoadedModule[72]=C:\FSX\demo.dll LoadedModule[73]=C:\FSX\main.dll LoadedModule[74]=C:\FSX\fe.dll LoadedModule[75]=C:\FSX\util.dll LoadedModule[76]=C:\FSX\simprop.dll LoadedModule[77]=C:\FSX\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=C:\FSX\g3d.dll LoadedModule[83]=C:\FSX\panels.dll LoadedModule[84]=C:\FSX\multiplayer.dll LoadedModule[85]=C:\FSX\ui.dll LoadedModule[86]=C:\FSX\sound.dll LoadedModule[87]=C:\FSX\sim1.dll LoadedModule[88]=C:\FSX\simscheduler.dll LoadedModule[89]=C:\FSX\visualfx.dll LoadedModule[90]=C:\FSX\window.dll LoadedModule[91]=C:\FSX\terrain.dll LoadedModule[92]=C:\FSX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=C:\FSX\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=C:\FSX\xuipc.dll LoadedModule[99]=C:\FSX\livingwater.dll LoadedModule[100]=C:\FSX\fs-traffic.dll LoadedModule[101]=C:\FSX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Windows\system32\RICHED20.DLL LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll LoadedModule[106]=C:\Windows\system32\rsaenh.dll LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[112]=C:\Windows\system32\wbemcomn.dll LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[118]=C:\Windows\system32\dxgi.dll LoadedModule[119]=C:\Windows\system32\d3d11.dll LoadedModule[120]=C:\Windows\system32\nvd3dum.dll LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[122]=C:\Windows\system32\nvspcap.dll LoadedModule[123]=C:\Windows\system32\nvapi.dll LoadedModule[124]=C:\Windows\system32\bcrypt.dll LoadedModule[125]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[126]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[127]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[128]=C:\Windows\system32\d3d10_1.dll LoadedModule[129]=C:\Windows\system32\d3d10_1core.dll LoadedModule[130]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[131]=C:\Windows\system32\dbghelp.dll LoadedModule[132]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[133]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[134]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[135]=C:\Windows\system32\winbrand.dll LoadedModule[136]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[137]=C:\Windows\system32\WINSTA.dll LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[141]=C:\Windows\SysWOW64\wer.dll LoadedModule[142]=C:\Windows\System32\Wpc.dll LoadedModule[143]=C:\Windows\System32\wevtapi.dll LoadedModule[144]=C:\Windows\System32\msxml6.dll LoadedModule[145]=C:\Windows\system32\SAMLIB.dll LoadedModule[146]=C:\Windows\system32\netutils.dll LoadedModule[147]=C:\FSX\uiautomationcore.dll LoadedModule[148]=C:\Windows\system32\OLEACC.dll LoadedModule[149]=C:\Windows\System32\MMDevApi.dll LoadedModule[150]=C:\Windows\System32\PROPSYS.dll LoadedModule[151]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[152]=C:\Windows\system32\HID.DLL LoadedModule[153]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[154]=C:\Windows\system32\wdmaud.drv LoadedModule[155]=C:\Windows\system32\ksuser.dll LoadedModule[156]=C:\Windows\system32\AVRT.dll LoadedModule[157]=C:\Windows\system32\msacm32.drv LoadedModule[158]=C:\Windows\system32\midimap.dll LoadedModule[159]=C:\Windows\system32\dinput.DLL LoadedModule[160]=C:\Windows\System32\wship6.dll LoadedModule[161]=C:\Windows\System32\wshtcpip.dll LoadedModule[162]=C:\Windows\syswow64\imagehlp.dll LoadedModule[163]=C:\Windows\system32\ncrypt.dll LoadedModule[164]=C:\Windows\system32\GPAPI.dll LoadedModule[165]=C:\Windows\system32\cryptnet.dll LoadedModule[166]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[167]=C:\Windows\system32\SensApi.dll LoadedModule[168]=C:\Windows\system32\EhStorShell.dll LoadedModule[169]=C:\Program Files (x86)\Kaspersky Lab\Kaspersky PURE 3.0\shellex.dll LoadedModule[170]=C:\Program Files (x86)\Kaspersky Lab\Kaspersky PURE 3.0\MSVCP100.dll LoadedModule[171]=C:\Program Files (x86)\Kaspersky Lab\Kaspersky PURE 3.0\MSVCR100.dll LoadedModule[172]=C:\Windows\system32\ntshrui.dll LoadedModule[173]=C:\Windows\system32\srvcli.dll LoadedModule[174]=C:\Windows\system32\cscapi.dll LoadedModule[175]=C:\Windows\system32\slc.dll LoadedModule[176]=C:\Program Files (x86)\AOL Desktop 9.7\idleproc.dll LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[178]=C:\FSX\bglmanx.dll LoadedModule[179]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[180]=C:\FSX\Modules\A2A_Feel.dll LoadedModule[181]=C:\Windows\SysWow64\XAudio2_6.dll LoadedModule[182]=C:\FSX\Modules\AccuFeelMenu.dll LoadedModule[183]=C:\FSX\PMDG\DLLs\PMDGOptions.dll LoadedModule[184]=C:\FSX\PMDG_SimConnect_Ldr.dll LoadedModule[185]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[186]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[187]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL LoadedModule[188]=C:\FSX\PMDG\DLLs\PMDGEvents.dll LoadedModule[189]=C:\FSX\PMDG\DLLs\PMDGSounds.dll LoadedModule[190]=C:\FSX\WaveLib.dll LoadedModule[191]=C:\FSX\fsInsider.dll LoadedModule[192]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[193]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[194]=C:\Windows\system32\WINNSI.DLL FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\FSX\fsx.exe

Well I didn't catch your post until I uninstalled MCE. But after I uninstalled MCE I reinstalled FSUIPC4.939 just for smiles and FSX loaded and operated okay. I did get the whole ''FSUIPC.DLL is a problem and do I want to login with it or without it'' warning but I clicked yes and it loaded okay this time. And after a re launch of the sim a second time, I got no warnings at all other then a MCE message saying there's components missing that it needs to work or something like that. Which is odd because I uninstalled it. But the sim did work okay. Now for the sake of seeing what will recreate the problem, which move should I make next? Do I reinstall MCE or GSX first?

I read through it. Not good. I'm kind of slow on the whole changing dll file names and replacing files here and there. Not sure if I should try uninstalling MCE and reinstalling FSUIPC to see if that program works after that. That's the only sequence I didn't try yet. Because as of now FSUIPC doesn't work with or without GSX installed so maybe MCE is a factor. Well, more installing and uninstalling today. :mad: Thanks for the reply.

Thanks for the reply Firehawk44 I don't know what's up with my event viewer log. It says I had 110 errors the past 7 days but I cant find anything FSX related. I do have TopCat and I think it uses FSUIPC or either WideClient to transfer Topcat data to the sim. Not sure what this WideClient is. So that kind of hurts. I will try reinstalling GSX after checking with FSdreamteam as suggested to see what happens. Hopefully no issue. Just in case I will download that AppCrashView that's in the CTD Guide. That dll.xml you mention just to confirm is that in the FSX appdata folder or in a FSX root folder?

Well I figured I'd start with uninstalling FSUIPC because the sim wasn't starting because of it. And then uninstalled GSX because that was the last add-on I installed before the problem yesterday. And since the sim ran okay after those two uninstalls I just assumed MCE was a non factor. I'll make sure to check out the FSdreamteam forum. Thank you for your reply.

Hello, Want to start by saying that my FSX as been running pretty well and steady up until I added two new add-ons. I first added Ultimate Multi Crew Experience and then GSX. For some reason I can't find any appcrash logs in my windows event viewer from yesterday. So I'll try to describe these CTD the best I can. One error message I got a lot was ''FSUIPC.DLL is a problem and do I want to login with it or without it.'' If I hit yes it would CTD. If I hit no it would start up to the FSX main menu but as soon as I went to select aircraft it would crash. Per a Pete Dowson post I found, was to hit yes again and again to load FSX. And that It's only the initial trust-checking which fails or a simconnect issue. ''When FSX has the correct Trust entry in its CFG file it works every time thereafter.'' But this just went on to long with no go. I did multiple reinstalls of GSX and FSUIPC4.939 with no luck. So I uninstalled FSUIPC939 and the sim loaded fine but then after selecting a aircraft again it crashed. After that I then uninstalled GSX and had no CTD's happen. Then I reloaded FSUIPC to see what would happen and still got that error message. So now I left out FSUIPC and GSX and the sim as been okay now. Again I had no issues with FSUIPC939 up until GSX was installed. So my main question is giving my actions up to this point where should I look to get technical support from. GSX or FSUIPC? Or could it be my install. Also I have had some simconnect issues with A2A aircraft but nothing that caused a total crash. Thanks for any help, George. My rig specs: HP bought in 2009 Model #: p6340f PCBRAND: Pavilion Processor: Intel® Core™2 Quad CPU Q8400 @ 2.66GHz 2.67GHz RAM: 8.00 GB Windows 7 64 bit OP Graphics Card: Nvidia GeForce GTX 770 Driver Version 340.52 FSX Add-ons I have installed: FSX Sp 1 and 2 REX OD FSUIPC4 V939 EZdok 1.17 A2A Accu-Feel V2 PMDG MD-11 FS2Crew MD-11 QW 757 Service Pack 3 A2A Cessna 172 Trainer A2A Piper Cherokee180 Carenado C152II Area51 C-5M Galaxy Navgragh FMS Manager Navigraph Charts

I just signed up to Simbrief.com it's neat but there doesn't seem to be a download option that loads like a rte flight plan file into FSX like Simroutes use to. Must have to put in the data by hand. Flying mostly the shorter 2 hour FDX and UPS routes that's not really a problem though. I now just want to make sure that PFPX is gonna work with the PMDG MD-11F. Once a couple people confirm I will buy it. Same for FSBuild but that being a older program I'm leaning towards PFPX. Again thanks for the replies.

Thanks for the replies everyone. I'm very happy to hear that PFPX and FSBuild don't need to run alongside FSX. That was a major concern for me since FSX along with REX need to eat so much. I'm guessing from Makdrive's screen shot of PFPX, the PMDG simulations box would be the one to use for the MD-11. And Ray Proudfoot, thank you for telling me about PC Aviator and their discounts. Much appreciated. Right now PFPX seems to be the way to go. And PFPX being a newer program I think running into compatibility issues with windows 7 64bit will be less likely. Regards.

Thank you for the reply Makdrive. So do you think both can be good for making routes for the FMC that's in the PMDG MD-11 cargo plane?

Hello, I'm thinking about buying a good flight planner for FSX. But I want something not over extreme in complexity, where I don't have to spend 50 minutes to preflight. I understand that's part of simulation but I can't do that every time. Also I mainly fly the PMDG MD-11 Cargo verison. I use to just use the free simroutes web site to get my rte flight plan files for the MD-11 but that site as not been working at all. I liked it because it was simple but it doesn't work anymore for PMDG. I have REX but that program's flight planner does not covert to rte files. FS build from I have seen is old and my not work with my Windows 7-64bit computer or the MD-11. I can get the PFPX + TOPCAT Bundle but I'm very worried about getting overwhelmed by them. I'm also very very worried that FS build and Professional Flight Planner X are programs that must be running while FSX is running too. Having to run REX for it's weather and a huge flight planner program at the same time could hurt my FSX performance big time. So I'm looking for some input on what route I should take. The big selling points for me will be if it works with the PMDG MD-11 and doesn't have to run alongside FSX Thank you for any replies best regards. My rig specs: HP bought in 2009 Model #: p6340f PCBRAND: Pavilion Processor: Intel® Core™2 Quad CPU Q8400 @ 2.66GHz 2.67GHz RAM: 8.00 GB Windows 7 64 bit OP Graphics Card: Nvidia GeForce GTX 770 Driver Version 332.21 FSX Add-ons I have installed in my rig: FSX Sp 1 and 2 REX OD FSUIPC4 + FSUIPC490 update EZdok 1.17 A2A Accu-Feel V2 PMDG MD-11 FS2Crew MD-11 QW 757 Navgragh FMS Manager Navgragh Carts 4