Jump to content

cbalow

Frozen-Inactivity
  • Content Count

    17
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by cbalow

  1. To finally bring closure to this. First time sending the issue to PC Aviators' support desk vs. MegasceneryEarth, I got a response back from Robert, the CEO. He apologized for the lack of response and sent me the physical disks. As soon as I installed the physical disks vs. the download and install, all issues resolved. But along the way, I picked up some excellent pointers, thank you guys for the advise!!!! Chris
  2. Jim, Load times are much better, excellent piece of advise!!! I had a new issue with my computer (Full C:\ drive). Was causing additional issues. So I have spent the last week dealing with that. Once I was done, I was hoping it might be related to my CTD issues, but unfortunately it was not. I am still optimistic though. I am going to try to re-install from the beginning hoping that somehow my full drive was causing issues with the install. Should be able to update this week on that progress. Thanks again Jim. Ironically, I have still heard nothing from the megasceneryearth after 3 e-mails from their website to the customer service team. I was hoping to be able to just pay the difference and have the disks sent.
  3. Glad to hear Ken. I however am giving up. I have downloaded and reinstalled Colorado 2x times and Utah several times. I still get consistent CTD at the same location. I might contact them and see if they will send me discs. For I think the issue is somewhere in the download and installation.
  4. Ken, I am with you. I really don't think it is an in game performance thing. However, I am starting to believe it IS in installation performance thing. I thought I had Utah resolved, but in depth testing has revealed that I have not fixed the issue. I have literally been reviewing the results 1 tile at a time. (I have a good process going, thank goodness for multiple monitors) I am finding that if I find a tile that fails, (not file, but tile) I can re-install just that tile and it will fix it 80% of the time. Interestingly enough, I find that the ones I cannot resolve are where the airport lies across more than 1 tile. I am also doing this @ ground level. Maybe @ FL300 they won't fail because I can zoom out in map view and be perfectly fine (no CTD). I am slowly making progress and confident that I will be able to run without issue at some point, I have decided that I will not be doing this for every state I purchase, so unless I can find a system resolution, no more MSE2.0 states for me. Now, with that said, Jim just brought to my attention another system config thing to check. I dramatically increased my bufferpool size per another forum thread, before I started having these issues. It appeared to have no impact (positive or negative) so I figured it was one of those irrelevant things. But I now have another rabbit hole I can go down :rolleyes:
  5. Ken, For what it is worth, I completely re-installed UT and CT again. 1 file @ a time. Bingo, no issues. I have not tried reinstalling CO, or NE yet. The only difference for me was I had 1 process going @ a time. I installed CO,NE,UT,CT all at the same time so I was flying through the install process having 2 or 3 files unzipping at a time while having another file or 2 installing. My guess is something was not installed correctly. I am going to take this approach with CO and NE and if it works, I will believe it was simply my impatience that caused my grief. (aka, ID10T error) Else..... I will visit Newegg.com and buy MORE POWER!!!! :rolleyes: (or just follow the other suggestions.)
  6. Jim, Thank you. I will start following the "enable only what you need approach". I am also going to check out that Microsoft fix. On a side note, I simply deleted and re installed Utah and all seems good. I was installing about 4 states at one time flying through the unzip folder / install routine, were I had several processes going at one time. My gut feeling is something did not install correctly in that process. For the first states I did, I took my time (1 file @ a time) and I had no issues. I did that this time with the Utah re-install, and then bingo..... problems solved.
  7. Thanks, I think I have concluded the same. I have started the re-download process and will re-install. I will advise if that solves the issue. I am just curious how they are getting corrupt. I am flying through the install process, so maybe I just need to slow down
  8. I was able to nail it down to 6 tiles last night before I ran out of time. (Not sure all 6 are an issue, but by removing the set of 6, I was able to fly around with no issue and with great FPS.) So I am feeling pretty confident that it is a corrupt tile. I was not able to re-install those tiles yet (I of course deleted the installation files, so I need to re-download all of them) But I am hoping it was just an installation issue. If not, I will definitely try using the ProcessExplorer tool you suggested. Thank you all for your help. CaptainKen, please keep me posted if you are fortunate enough to find resolution. Our issues and systems sound very similar.
  9. Rick, I completely understand what you are saying and those are good ideas. But I have taken those other apps out of the equation. I have been testing with FSX weather engine, clear skies, and the fsx default ultralight. I can load up my flight with no issue in the center of the state and fly with great FPS. Then I try to start a flight @ KASE (CO) or KBCE (UT) and get the error when the loading screen is only at 30-40% loaded. I have also removed UTX - US and FS Global Ultimate - NAM for I thought there might be a conflict with those and the MSE UTAH scenery. My error and System Setup is here if needed. http://forum.avsim.net/topic/413174-megasceneryearth-20-ctd-issues/#entry2710679 I am just going to try to isolate a couple tiles at a time as suggested above. The question is how to fix those tiles and how much determination I have
  10. Thank heavens I have found someone with the same issue as me. For example, I am using Utah and can start my flight in KSCL, but as soon as I head south anywhere near BCE (Bryce Canyon) then crash. I have MI, FL, NY installed (no issues) but then in the last week I have installed CO, CT, UT and the all CTD somewhere. I have found that I will get several different modules as the culprit in the APPCRASH file. (util.dll, ntdll.dll, msvcr80.dll, fscopi~1.ocx) although util.dll seems to be the most common. If I remove the scenery, no issue. I have not started isolated it to a specific tile, but if it is likely just a corrupt tile at installation, I can start Isolating. I just found it interesting that the files purchased in the last 2 weeks are all having this issue and the ones purchased a month or so more, run great. I too had an issue in Nebraska, coming from LA 75 - 100 miles in from the CO border. Just curious if we are crashing with the same tile.
  11. Found an identical thread. http://forum.avsim.net/topic/413051-can-anyone-please-help-me/#entry2708875
  12. I have been consistently receiving CTD (fsx.exe APPCRASH) when running MegasceneryEarth 2.0 over the states of CO, UT, NE. I have not had issues previously with MI, FL, NY. For example: I am able to load up and take off from Denver without issue. But as soon as I pass west of Denver, then CTD. It will also CTD when I try to load a flight @ Aspen (KASE). For Utah, as soon as I approach Bryce Canyon, then CTD. In all cases, if I disable the scenery area from the library, all is fine. Any suggestions would be helpful. I am also running UTX USA and FS Global Ultimate - The Americas. PC Specs Windows 7 64-bit CPU= Intel Core i7-3770k RAM = 8GB GPU = GeForce GTX 660 Below is the AppCrash Data. I did notice the module was different each time it crashed. Version=1 EventType=APPCRASH EventTime=130177201423750249 ReportType=2 Consent=1 ReportIdentifier=d65b2e22-e76c-11e2-a2bd-ec460422f674 IntegratorReportIdentifier=d65b2e21-e76c-11e2-a2bd-ec460422f674 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=ntdll.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.17725 Sig[5].Name=Fault Module Timestamp Sig[5].Value=4ec49b8f Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00038dc9 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=7cf3 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=7cf314754711732647adaf012eb32201 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=62c0 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=62c0c4d0167c0e1f308a5b753985a147 UI[2]=F:\Microsoft Flight Simulator X\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]=F:\Microsoft Flight Simulator X\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\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\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.17514_none_ec83dffa859149af\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]=F:\Microsoft Flight Simulator X\language.dll LoadedModule[61]=F:\Microsoft Flight Simulator X\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=F:\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[64]=F:\Microsoft Flight Simulator X\flight.dll LoadedModule[65]=F:\Microsoft Flight Simulator X\ai_player.dll LoadedModule[66]=F:\Microsoft Flight Simulator X\acontain.dll LoadedModule[67]=F:\Microsoft Flight Simulator X\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=F:\Microsoft Flight Simulator X\fsui.dll LoadedModule[70]=F:\Microsoft Flight Simulator X\atc.dll LoadedModule[71]=F:\Microsoft Flight Simulator X\facilities.dll LoadedModule[72]=F:\Microsoft Flight Simulator X\demo.dll LoadedModule[73]=F:\Microsoft Flight Simulator X\main.dll LoadedModule[74]=F:\Microsoft Flight Simulator X\fe.dll LoadedModule[75]=F:\Microsoft Flight Simulator X\util.dll LoadedModule[76]=F:\Microsoft Flight Simulator X\simprop.dll LoadedModule[77]=F:\Microsoft Flight Simulator X\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]=F:\Microsoft Flight Simulator X\g3d.dll LoadedModule[83]=F:\Microsoft Flight Simulator X\panels.dll LoadedModule[84]=F:\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[85]=F:\Microsoft Flight Simulator X\ui.dll LoadedModule[86]=F:\Microsoft Flight Simulator X\sound.dll LoadedModule[87]=F:\Microsoft Flight Simulator X\sim1.dll LoadedModule[88]=F:\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[89]=F:\Microsoft Flight Simulator X\visualfx.dll LoadedModule[90]=F:\Microsoft Flight Simulator X\window.dll LoadedModule[91]=F:\Microsoft Flight Simulator X\terrain.dll LoadedModule[92]=F:\Microsoft Flight Simulator X\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=F:\Microsoft Flight Simulator X\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=F:\Microsoft Flight Simulator X\xuipc.dll LoadedModule[99]=F:\Microsoft Flight Simulator X\livingwater.dll LoadedModule[100]=F:\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[101]=F:\Microsoft Flight Simulator X\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Program Files (x86)\MMTaskbar\shellhook.dll LoadedModule[105]=C:\Windows\system32\RICHED20.DLL LoadedModule[106]=C:\Windows\system32\CRYPTSP.dll LoadedModule[107]=C:\Windows\system32\rsaenh.dll LoadedModule[108]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[109]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[110]=C:\Windows\syswow64\MSASN1.dll LoadedModule[111]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[112]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[113]=C:\Windows\system32\wbemcomn.dll LoadedModule[114]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[115]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[116]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[117]=C:\Windows\system32\NTDSAPI.dll LoadedModule[118]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[119]=C:\Windows\system32\dxgi.dll LoadedModule[120]=C:\Windows\system32\d3d11.dll LoadedModule[121]=C:\Windows\system32\nvd3dum.dll LoadedModule[122]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[123]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[124]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[125]=C:\Windows\system32\d3d10_1.dll LoadedModule[126]=C:\Windows\system32\d3d10_1core.dll LoadedModule[127]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[128]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[129]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[130]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[131]=C:\Windows\system32\winbrand.dll LoadedModule[132]=C:\Windows\system32\nvapi.dll LoadedModule[133]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[134]=C:\Windows\system32\WINSTA.dll LoadedModule[135]=C:\Windows\SysWOW64\gameux.dll LoadedModule[136]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[137]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[138]=C:\Windows\SysWOW64\wer.dll LoadedModule[139]=C:\Windows\System32\Wpc.dll LoadedModule[140]=C:\Windows\System32\wevtapi.dll LoadedModule[141]=C:\Windows\System32\msxml6.dll LoadedModule[142]=C:\Windows\system32\SAMLIB.dll LoadedModule[143]=C:\Windows\system32\netutils.dll LoadedModule[144]=F:\Microsoft Flight Simulator X\uiautomationcore.dll LoadedModule[145]=C:\Windows\system32\OLEACC.dll LoadedModule[146]=C:\Windows\System32\MMDevApi.dll LoadedModule[147]=C:\Windows\System32\PROPSYS.dll LoadedModule[148]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[149]=C:\Windows\system32\HID.DLL LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[151]=C:\Windows\system32\wdmaud.drv LoadedModule[152]=C:\Windows\system32\ksuser.dll LoadedModule[153]=C:\Windows\system32\AVRT.dll LoadedModule[154]=C:\Windows\system32\msacm32.drv LoadedModule[155]=C:\Windows\system32\midimap.dll LoadedModule[156]=C:\Windows\system32\dinput.DLL LoadedModule[157]=C:\Windows\System32\wship6.dll LoadedModule[158]=C:\Windows\System32\wshtcpip.dll LoadedModule[159]=F:\Microsoft Flight Simulator X\bglmanx.dll LoadedModule[160]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[161]=C:\Windows\system32\inetmib1.dll LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[163]=C:\Windows\system32\WINNSI.DLL LoadedModule[164]=C:\Windows\system32\snmpapi.dll LoadedModule[165]=F:\Microsoft Flight Simulator X\Modules\iFly737NG.dll LoadedModule[166]=F:\Microsoft Flight Simulator X\Flight One Software\Audio Environment\AEMODULE.dll LoadedModule[167]=F:\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll LoadedModule[168]=F:\Microsoft Flight Simulator X\Modules\Fsuipc4.dll LoadedModule[169]=F:\Microsoft Flight Simulator X\Captain_Sim\Captain_Sim.b757.menu.dll LoadedModule[170]=F:\Microsoft Flight Simulator X\Captain_Sim\757\cs.sound.dll LoadedModule[171]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll LoadedModule[172]=F:\Microsoft Flight Simulator X\PMDG_SimConnect_Ldr.dll LoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[174]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL LoadedModule[177]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll LoadedModule[178]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll LoadedModule[179]=F:\Microsoft Flight Simulator X\WaveLib.dll LoadedModule[180]=F:\Microsoft Flight Simulator X\Captain_Sim\Captain_Sim.b767.menu.dll LoadedModule[181]=F:\Microsoft Flight Simulator X\Captain_Sim\767\cs.sound.dll LoadedModule[182]=F:\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll LoadedModule[183]=F:\Microsoft Flight Simulator X\VistaMare\bin\VMCX_SP2.dll LoadedModule[184]=F:\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET.dll LoadedModule[185]=F:\Microsoft Flight Simulator X\Modules\FSCopilot.dll LoadedModule[186]=C:\Windows\system32\oledlg.dll LoadedModule[187]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[188]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SIMCONNECT.DLL LoadedModule[189]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[190]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[191]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[192]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[193]=C:\Windows\system32\Secur32.dll LoadedModule[194]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[195]=C:\Windows\system32\msimtf.dll LoadedModule[196]=C:\Windows\system32\msls31.dll LoadedModule[197]=C:\Windows\system32\d2d1.dll LoadedModule[198]=C:\Windows\system32\DWrite.dll LoadedModule[199]=C:\Windows\system32\D3D10Warp.dll LoadedModule[200]=C:\Windows\system32\MLANG.dll LoadedModule[201]=C:\Windows\system32\ntmarta.dll LoadedModule[202]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[203]=C:\Windows\SysWOW64\uiautomationcore.dll LoadedModule[204]=F:\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX.dll LoadedModule[205]=F:\FS Program Files\FSFDT\FSCopilot\FSCopGPWS.ocx LoadedModule[206]=C:\Windows\system32\MSVBVM60.DLL LoadedModule[207]=C:\Windows\system32\SXS.DLL LoadedModule[208]=F:\FSPROG~1\FSFDT\FSCOPI~1\FSCOPI~1.OCX LoadedModule[209]=F:\FS Program Files\FSFDT\FSCopilot\FSCopTimeSync.ocx LoadedModule[210]=F:\FS Program Files\FSFDT\FSCopilot\FSCopHeadEffects.ocx LoadedModule[211]=F:\FS Program Files\FSFDT\FSCopilot\FSCopTuner.ocx LoadedModule[212]=C:\Windows\system32\msiltcfg.dll LoadedModule[213]=C:\Windows\SysWOW64\MSCOMCTL.OCX LoadedModule[214]=C:\Windows\system32\wmp.dll LoadedModule[215]=C:\Windows\system32\wmploc.dll LoadedModule[216]=C:\Windows\system32\MFPlat.DLL LoadedModule[217]=c:\Windows\SysWOW64\jscript.dll LoadedModule[218]=F:\Microsoft Flight Simulator X\GAUGES\Captain_Sim.b767.sound.GAU LoadedModule[219]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.adi.GAU LoadedModule[220]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.fms.GAU LoadedModule[221]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.eicas1.GAU LoadedModule[222]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.eicas2.GAU LoadedModule[223]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.300.GAU LoadedModule[224]=C:\Windows\system32\msadp32.acm FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=F:\Microsoft Flight Simulator X\fsx.exe
  13. Thank you Ray. Using that convention, I can clealy see I am missing some M and N's. Now I just need to figure out which of the 31 files I need to re-download My guess somewhere around 15
  14. Just installed Michigan last night, and I have to say it was really cool to fly over my house and there it is in full detail Question: Is there logic to the naming convention of the files and the area. Reason I ask is, I appear to have missed the installation of a strip of land in the middle of the state. Of course I have no idea which zipped set of files I missed. I really don't want to have to go through and install them all again. (The missing area covers Mt.Pleasant easward through Saginaw and out to Lake Huron) I agree, the view is beautiful from above, but on the field it looks terrible not having trees, especially in northern Michigan where the airfields are bordered by dense woods. Question 2: I was going to see if I could use ADE and add woods to the perimeter of the airports? I am not sure that is even possible, but would like feedback before I even try.
×
×
  • Create New...