Scott Miller

Thanks for all the replys, gu2 They all give me hope that 2024 will be worth getting (eventually). I probably won't go for the aviator version ($200 is a bit too pricey for me), however, the $130 Deluxe Premium is probably what I go for (that's about what I paid for MSFS2020. MSFS2020 was not preprogramed for my CH Eclipse yoke (at least I couldn't find it if it were. I'll have to take another look). I've hardly used MSFS2020 because of this. I have yet to complete a flight in MSFS2020 because of the difficulty I've had because all the FS2004/FSX keyboard commands were done away with (or I couldn't figure out how to use them with MSFS2020.

Ok, first question: What are the differences between the standard, deluxe, deluxe premium, and aviator versions (aside from cost)? Question 2: Is the learning curve as extremely high as MSFS2020? 2020 was such a radical departure from FS2004/FFSX that it is difficult in the extreme to learn how to use (at least it has been for me!). Question 3: Have they returned to the FS2004/FSX keyboard commands (the major problem with leaning to fly 2020 is the fact that they completely did away with the 2004/FSX keyboard commands!). Question 4: Are all my 2020 aircraft and scenery addons compatible with 2024 (or am I going to have to throw out all of my 2020 addons and spend hundreds of dollars to replace them with 2024 addons? Question 5:Does 2024 come preprogamed with the major known control yokes and joysticks or am I gong to have to program it to work with my CH Eclipse and CH pedals (I'm still trying to figure out how to program 2020 to work with them! As nice as the 2024 trailer is, if the answers to questions 2 through 5 is not YES! I may have to pass. Given the aggravation I've experienced with 2020 I don't think it'll be worth upgrading to 2024 (especially considering the cost (which is even more expensive that 2020 was)!

It worked! I installed everything but the Bush Trip - Scotland option and MSFS started up with no problem!

Thanks for the reply! I will try your fix out. I'll let you know if it works for me...

I installed this free update in the marketplace recently only to discover that it isn't comparable with MSFS (or at least not my copy of MSFS). After installing it MSFS would crash during startup everytime. It was only after I deleted this update that MSFS would startup normally again. Has anyone else had this problem? Is there a fix for it?

I had forgotten I had posted the request on how to employ the auto-coordination feature in MSFS! Hadn't touched MSFS in about a year. MSFS is difficult to get into. Hardest learning curve of any Flisim I've ever seen. Have yet to complete a single flight. My biggest gripe about about MSFS is that it didn't come preprogramed for my CH Yoke. Got the CH Eclipse Yoke and it's proving to be equally diffcult to program for use with MSFS. My second biggest gripe is that MSFS doesn't use the same keyboard\yoke commands that previous versions of FS used (FS2002. FS100 and FSX). BTW. where exactly is the auto rubber option in the assistance option? I haven't been able to find it!

I had forgotten I had posted the request on how to employ the auto-coordination feature in MSFS! Hadn't touched MSFS in about a year. MSFS is difficult to get into. Hardest learning curve of any Flisim I've ever seen. Have yet to complete a single flight. My biggest gripe about about MSFS is that it didn't come preprogramed for my CH Yoke. Got the CH Eclipse Yoke and it's proving to be equally diffcult to program for use with MSFS. My second biggest gripe is that MSFS doesn't use the same keyboard\yoke commands that previous versions of FS used (FS2002. FS2004 and FSX).

Thanks guys (sorry to take so long to reply)!

If you didn't have rudder pedals, you could, in past versions of FS use auto-coordination to operaed the yoke and rudders simultaneously. Does MSFS have this as well? I'm unable to use my rudder pedals, at least for the time being, after having my right foot amputated two months ago. I lost my left foot in 2018. I hope to be getting a prosthetic for the right foot in a month or two. In the meantime it'll be difficult to operate the rudders via the keyboard. With prosthetics I'll be able to operate the rudders (but not the toe breaks)..

Hey, edetroit, turns out you were right! The orphaned imaginesim TJSJ jetways were from AES. I had to turn imaginesims' TJSJ off in AES BEFORE deleting it from FS2004's scenery library. Leaving the scenery active in AES kept the AES jetways active. That was the good news. There's a bit of bad news (more mysterious than bad though) to go with the good. When exiting FS2004 with the LatinVFR TJSJ scenery loaded causes one of those error messages saying the software you were using , in this case FS2004, "encountered an unexpected problem and had to close, etc. etc." No be deal really as it comes after FS2004 is already in the process of shutting down anyway. Not sure what is causing it unless its because I still Imaginesim's TJSJ scenery on my hard drive. It's deleted from fS2004's scenery library though so this issue is a bit of a puzzle...

I don't think the installer allows you to change the destination folder (but it might be worth a try anywayz). Without knowing the names of the jetway bgls it'll be hard to track them down.

I don't think so. They are static jetways and they were part of the WA3 TJSJ terminal building before I got AES. Regardless, how do I remove them?

The WA3 airports ARE by Imaginesim. They include Atlanta, Charlotte, Cincinati, Nassau, and San Juan all bundled together in World Airports 3...They are installed in a Just Flight folder, not a Imaginesim folder.

I recently purchased LatinVFR's TJSJ scenery (forgetting that TJSJ is included in the World Airport 3 airport scenery I already had installed in FS2004). When I loaded it I could see some disconnected jetways that didn't seem to belong. I contacted LatinVFR thinking this was a case of sloppy programming on LatinVFR's part. It wasn't. Turns out the disconnected jetways belong to World Airport 3's TJSJ scenery. I tried deactiviting WA3's TJSJ which made all the WA3 TJSJ scenery disappear EXCEPT the jetways! I tried simply deleting the TJSJ scenery from the scenery library. Didn't work. Deleting the TJSJ folder from the FS2004/Just Flight/WA3 folder didn't work either. Finally I tried uninstalling WA3 entirely (the WA3 uninstaller doesn't give you the chance to install or uninstall specific airports, it an all or nothing thing). But STILL the WA3 TJSJ jetways are showing up in the LatinVFR TJSJ scenery! How the heck to I get get rid of these WA3 TJSJ jetways!? As much as I loved WA3's TJSJ scenery, LatinVFR's is better and these orphaned WA3 TJSJ jetways have got to go!!!

To Ronzie: Yes, I know their site is still up. That doesn't necessarily mean they are still in business though...According to their website my order has been "completed"! Chris, sorry to hear that he has been dealing with some personal issues. I can apprciate that. I've been dealing with a personal issue of my own (my wife's health) otherwise I would have posted my queston a lot sooner... Actually, PC Aviators has always been my favorite FS vendor. I've probably purchased more stuff from them than from all others combined. They have been very helpful to me in the past as well. The speed of the delivery of orders from PC Aviator can't be beat unless you download it (I prefer having the DVD in my possession). I'm glad to hear that PC Aviator hasn't gone out of business. I would have been very upset if they had (almost like losing a personal friend)! Well, hopefully, I'll get a reply to my second msg this week....

Has PC Avaitor gone belly up? Been trying to contact PC Avaitor about an order I placed Aug 30th (and have yet to receive) but they haven't responded to a message I posted on their website a week ago. i've tried calling yesterday but have up after being left on hold for over a half hour. When I called today the automated system didn't even pick up the phone. BTW, how do I keep the menu from collasping right after the AVSIM website pops up? I also don't seem to be able to do a topic search anymore...I know I haven't been on the website much (other than to do whats new searches on the library) lately. Apparently I've missed something (or didn't get the memo)....

Reverting to the 3/.4.22 driver did indeed correct the problem, Tom. But only in FS2002 and 2004. Still have to run FS98 either with hardware acceleration turned off in 640x480x8 low res full screen mode or windowed mode for 800x600x16 high res mode with the H.A. on...at least it runs now though. It didn't under Windows 7... Another problem with FS2002 is that some of the skyscrapers in the Chicago skyline have black bands on them that move as one's prespective moves. This may be a pre-existing condition with FS2002 though. I just never noticed it before (though you'd think I would have if this were the case)...The only reason I keep FS2002 around really is to fly Dreamfleet's 737-400 (my all time favorite FS aircraft addon). I'm too lazy to mess with the FS2004 merge! Anyway, I can live with the black bands issue if need be...

Ok, that sounds likely. I hadn't considered that the driver might be the cause of the problem. My current (for the moment) driver is 335.28. Just downloaded the 314.22 driver from the nVidia website. If it does indeed correct the problem (or even if it doesn't) I'll post the news here...Thanks, Tom! Scott Miller

Tom or Jeff: Please move this topic to the monitor, graphics card forum. Should have posted there in the first place! Thanks....

As some of you may recall I had problems I getting FS2004 to run on the 64 bit Windows 7 system I "upgraded" to last fall (including but not limited to having a previously selected menu option appear when going to select another or switching exterior/enterior views). Recently I discovered that there are motherboards still available (Z77 boards) that support Windows XP so I got one (MSI Z77A-G43 Gaming) and an Intel i3-3240 3.4 ghz cpu to go with it. Yeah, I know Microsoft stopped supporting Windows XP April 8th (I couldn't care less, aside from one single time, I never needed support from Microsoft anyway but I digress...) I've encountered a strange problem with Flight Simulator (FS98, FS2002 and FS2004. Haven't reinstalled FSX yet). With S98 I have to turn off hardware acceleration if I want to run it in full screen mode otherwise the exterior view goes nuts on me. I have to check the Transform and Lightening box on the Display/Hardware screen or I get the same thing with the exterior views (what is "Transform and Lightening). This problem doesn't arise in FS2004 whether the T & L box is checked or not. Another problem (this is where the "strange" aspect comes in) I've encountered in both FS2002 and FS2004 is that a half dozen aircraft have exterior parts showing up either much brighter than the rest of the plane's exterior. For example, the pilot's door on the default Cessna 172SP and Cessna 182S is brigther than the rest of the plane (on the pilot's side). Oj PMDG's B1900C/D its the cargo door. On the PMDG 737s with stairs in FS2004 its the small door that covers the ladder opening. The worst example is a freeware DH6 short nose where the engine access door, the pilot's door, the passenger door, the luggage/cargo door AND the rudder exhibit the same brightening (or alternatively, these are the a/c's correct appearance with the rest of the pilot's side of the plane being too dard. 3 or 4 other planes also exhibit this problem in degrees greater than the Cessnas but less than the DH6 short nose/sea otter/Vistaliner. The question is what is causing this problem and what is the best way to fix it. I'm pretty sure, too, that this problem existed with my Windows 7 system. I'm convinced that the problem is related to the graphics card I had on the Windows 7 system and am using in the "new" XP system (a EVGA GTX 650 w/1mb ram). Is there a way to eliminate the problem while continuing to use this graphics card or do I need to replace it (and, if so, with what)? Incidentally, none of my non-FS games are exhibiting this problem in any way. BTW, for those who might be interested, the frame rate was only slightly affected by "downgrading" back to a Windows XP system (from the mid-80s to the mid-60s, still a VAST improvement over the single digit frame rate I was getting on my old single core cpu XP system.. As always, any help resolving this problem would be greatly appreicated!

Happy (and relieved) that things are working again! All to easy to take the AVSIM folks for granted!!! Thanks for all the hard work!

This may be a dumb question but I was wondering if there is still a motherboard available that uses an Intel i5 CPU (or any 3+ ghz cpu), NVidia GTX650 (or better) video card, 1T SATA HDs, and 8mb or better ram that still supports Windows XP (I don't care that Microsoft no longer supports XP)? I'm still not entirely liking (much less loving) Windows 7 or the way FS2002/FS2004 runs on it (or maybe its just my ASRock motherboard that's to blame?).... Like I said, probably a dumb question, but I figure I've got nothing to lose by asking!

Hi, Jim. Sorry to take so long to respond. Yeah, I hear you, but NAV has saved my bacon on a couple of occasions. I see sort of like health insurance. It might seem like a complete waste of money as long as you're as healthy as a horse. If you have a heart attack or get in a car wreck or come down with cancer. Then you thank God you've got health insurance. I see NAV as a good investment even if renewing the subscription is a pain in the you know where. I had some other cases while reinstalling my FS stuff where NAV warned me that a particular file looked suspicious and gave me the option of installing it anyway but didn't actually remove and quarantine them like it did in this case. Scott

I tried the solution on the Flgiht1 QW support forum a few minutes ago and, low and behold, it fixed the problem! Had a bit of a problem with NAV, which mis-ID'd the new QW146.gau and QW146_2.gau files as infected files and deleted them. Took a couple of minutes to figure out how to restore and exempt them from NAV's quarantine list, but once done the new files work like a charm!

Ok Jim, here's the AppCrashView report: Version=1 EventType=APPCRASH EventTime=130309308892718552 ReportType=2 Consent=1 UploadTime=130309308894538656 ReportIdentifier=8121902f-5f93-11e3-9073-bc5ff4bc5b2c IntegratorReportIdentifier=8121902e-5f93-11e3-9073-bc5ff4bc5b2c WOW64=1 Response.BucketId=3888955581 Response.BucketTable=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fs9.exe Sig[1].Name=Application Version Sig[1].Value=9.1.0.40901 Sig[2].Name=Application Timestamp Sig[2].Value=4135a208 Sig[3].Name=Fault Module Name Sig[3].Value=QWBae146_2.GAU Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5255f00d Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=0006225f 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 UI[2]=F:\FS2004\fs9.exe UI[3]=Microsoft Flight Simulator 9.0 has stopped working UI[4]=Windows can check online for a solution to the problem and try to restart the program. UI[5]=Check online for a solution and restart the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=F:\FS2004\fs9.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\syswow64\USER32.dll LoadedModule[5]=C:\Windows\syswow64\GDI32.dll LoadedModule[6]=C:\Windows\syswow64\LPK.dll LoadedModule[7]=C:\Windows\syswow64\USP10.dll LoadedModule[8]=C:\Windows\syswow64\msvcrt.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\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[15]=F:\FS2004\SHFOLDER.dll LoadedModule[16]=C:\Windows\system32\WINMM.dll LoadedModule[17]=C:\Windows\syswow64\IMM32.dll LoadedModule[18]=C:\Windows\syswow64\MSCTF.dll LoadedModule[19]=C:\Windows\system32\MSACM32.dll LoadedModule[20]=C:\Windows\system32\VERSION.dll LoadedModule[21]=F:\FS2004\MSVCR70.dll LoadedModule[22]=F:\FS2004\MFC70.DLL LoadedModule[23]=C:\Windows\system32\OLEACC.dll LoadedModule[24]=C:\Windows\syswow64\ole32.dll LoadedModule[25]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[28]=F:\FS2004\MSVCP70.dll LoadedModule[29]=C:\Windows\system32\apphelp.dll LoadedModule[30]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[31]=C:\Windows\system32\UxTheme.dll LoadedModule[32]=C:\Windows\system32\samcli.dll LoadedModule[33]=C:\Windows\system32\sfc.dll LoadedModule[34]=C:\Windows\system32\sfc_os.DLL LoadedModule[35]=C:\Windows\system32\USERENV.dll LoadedModule[36]=C:\Windows\system32\profapi.dll LoadedModule[37]=C:\Windows\system32\dwmapi.dll LoadedModule[38]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[39]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[40]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[41]=C:\Windows\syswow64\urlmon.dll LoadedModule[42]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[43]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[44]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[45]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[46]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[47]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[48]=C:\Windows\syswow64\normaliz.DLL LoadedModule[49]=C:\Windows\syswow64\iertutil.dll LoadedModule[50]=C:\Windows\syswow64\WININET.dll LoadedModule[51]=C:\Windows\system32\MPR.dll LoadedModule[52]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[53]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[54]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[55]=C:\Windows\system32\mscms.dll LoadedModule[56]=C:\Windows\system32\DDRAW.dll LoadedModule[57]=C:\Windows\system32\DCIMAN32.dll LoadedModule[58]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[59]=C:\Windows\syswow64\WS2_32.dll LoadedModule[60]=C:\Windows\syswow64\NSI.dll LoadedModule[61]=C:\Windows\system32\msi.dll LoadedModule[62]=C:\Users\Steven\AppData\Local\Temp\~ef7bb6\~df394b.tmp LoadedModule[63]=C:\Windows\system32\D3D9.DLL LoadedModule[64]=C:\Windows\system32\d3d8thk.dll LoadedModule[65]=C:\Windows\system32\RICHED32.DLL LoadedModule[66]=F:\FS2004\RICHED20.dll LoadedModule[67]=F:\FS2004\language.dll LoadedModule[68]=C:\Windows\system32\nvd3dum.dll LoadedModule[69]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[70]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[71]=C:\Windows\SysWOW64\POWRPROF.dll LoadedModule[72]=C:\Windows\system32\CRYPTSP.dll LoadedModule[73]=C:\Windows\system32\rsaenh.dll LoadedModule[74]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[75]=C:\Windows\system32\winbrand.dll LoadedModule[76]=C:\Windows\system32\dsound.dll LoadedModule[77]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[78]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[79]=C:\Windows\syswow64\MSASN1.dll LoadedModule[80]=C:\Windows\system32\nvspcap.dll LoadedModule[81]=C:\Windows\system32\nvapi.dll LoadedModule[82]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[83]=C:\Windows\system32\WINSTA.dll LoadedModule[84]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[85]=F:\FS2004\MODULES\ABLSCPT.DLL LoadedModule[86]=F:\FS2004\MODULES\ACONTAIN.DLL LoadedModule[87]=F:\FS2004\MODULES\UTIL.DLL LoadedModule[88]=F:\FS2004\MODULES\ActiveRadar.dll LoadedModule[89]=F:\FS2004\MODULES\AI_PLAYR.DLL LoadedModule[90]=F:\FS2004\MODULES\ATC.DLL LoadedModule[91]=F:\FS2004\MODULES\AutoSave.dll LoadedModule[92]=F:\FS2004\MODULES\autower.dll LoadedModule[93]=F:\FS2004\MODULES\bglman.dll LoadedModule[94]=C:\Windows\system32\inetmib1.dll LoadedModule[95]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[96]=C:\Windows\system32\WINNSI.DLL LoadedModule[97]=C:\Windows\system32\snmpapi.dll LoadedModule[98]=F:\FS2004\MODULES\cfo_tfxinfo.dll LoadedModule[99]=F:\FS2004\MODULES\CONTROLS.DLL LoadedModule[100]=F:\FS2004\MODULES\FSUI.DLL LoadedModule[101]=F:\FS2004\MODULES\DEMO.DLL LoadedModule[102]=F:\FS2004\MODULES\DYNAMIC.DLL LoadedModule[103]=F:\FS2004\MODULES\EFB2004.dll LoadedModule[104]=C:\Windows\system32\olepro32.dll LoadedModule[105]=F:\FS2004\MODULES\ez-vfr.dll LoadedModule[106]=F:\FS2004\MODULES\F1_view.dll LoadedModule[107]=F:\FS2004\MODULES\FACILITIES.DLL LoadedModule[108]=F:\FS2004\MODULES\FE.DLL LoadedModule[109]=F:\FS2004\MODULES\FLIGHT.DLL LoadedModule[110]=F:\FS2004\MODULES\FLT1PIPERM.DLL LoadedModule[111]=F:\FS2004\MODULES\FSNav.dll LoadedModule[112]=F:\FS2004\MODULES\FSSound.dll LoadedModule[113]=F:\FS2004\MODULES\FSUIPC.dll LoadedModule[114]=F:\FS2004\MODULES\FSWidgets.dll LoadedModule[115]=F:\FS2004\MODULES\fswvars.dll LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[117]=F:\FS2004\MODULES\G2D.DLL LoadedModule[118]=F:\FS2004\pixomatic.dll LoadedModule[119]=F:\FS2004\MODULES\G3D.DLL LoadedModule[120]=F:\FS2004\MODULES\GLOBAL.DLL LoadedModule[121]=F:\FS2004\MODULES\gps.DLL LoadedModule[122]=F:\FS2004\MODULES\gps_export.dll LoadedModule[123]=F:\FS2004\MODULES\INSTRUCTOR.DLL LoadedModule[124]=F:\FS2004\MODULES\LegacyHUD.dll LoadedModule[125]=F:\FS2004\MODULES\MAIN.DLL LoadedModule[126]=F:\FS2004\MODULES\mpchat.DLL LoadedModule[127]=F:\FS2004\MODULES\MULTIPLAYER.DLL LoadedModule[128]=F:\FS2004\MODULES\PANELS.DLL LoadedModule[129]=F:\FS2004\MODULES\PMDGOptions.DLL LoadedModule[130]=C:\Windows\system32\MSVCP60.dll LoadedModule[131]=C:\Windows\system32\MFC42.DLL LoadedModule[132]=C:\Windows\system32\ODBC32.dll LoadedModule[133]=C:\Windows\system32\WSOCK32.dll LoadedModule[134]=C:\Windows\system32\odbcint.dll LoadedModule[135]=F:\FS2004\MODULES\REALITY.DLL LoadedModule[136]=F:\FS2004\MODULES\RXPFLS.DLL LoadedModule[137]=F:\FS2004\MODULES\RxpSrv.dll LoadedModule[138]=F:\FS2004\MODULES\SIM1.dll LoadedModule[139]=F:\FS2004\MODULES\SimScheduler.DLL LoadedModule[140]=F:\FS2004\MODULES\SOUND.DLL LoadedModule[141]=F:\FS2004\MODULES\SYMMAP.DLL LoadedModule[142]=F:\FS2004\MODULES\TERRAIN.DLL LoadedModule[143]=F:\FS2004\MODULES\Traffic.DLL LoadedModule[144]=F:\FS2004\MODULES\TrafficInfo.DLL LoadedModule[145]=F:\FS2004\MODULES\VISUALFX.DLL LoadedModule[146]=F:\FS2004\MODULES\Weather.DLL LoadedModule[147]=F:\FS2004\MODULES\WINDOW.DLL LoadedModule[148]=C:\Windows\System32\MMDevApi.dll LoadedModule[149]=C:\Windows\System32\PROPSYS.dll LoadedModule[150]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[151]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL LoadedModule[152]=C:\Windows\syswow64\imagehlp.dll LoadedModule[153]=C:\Windows\system32\ncrypt.dll LoadedModule[154]=C:\Windows\system32\bcrypt.dll LoadedModule[155]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[156]=C:\Windows\system32\GPAPI.dll LoadedModule[157]=C:\Windows\system32\cryptnet.dll LoadedModule[158]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[159]=C:\Windows\system32\SensApi.dll LoadedModule[160]=C:\Windows\system32\DINPUT.DLL LoadedModule[161]=C:\Windows\system32\HID.DLL LoadedModule[162]=C:\Windows\SysWOW64\msxml4.dll LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll LoadedModule[164]=C:\Windows\system32\wdmaud.drv LoadedModule[165]=C:\Windows\system32\ksuser.dll LoadedModule[166]=C:\Windows\system32\AVRT.dll LoadedModule[167]=C:\Windows\system32\msacm32.drv LoadedModule[168]=C:\Windows\system32\midimap.dll LoadedModule[169]=C:\Windows\system32\dpnet.dll LoadedModule[170]=C:\Windows\system32\msadp32.acm LoadedModule[171]=F:\FS2004\QualityWings\qwings.dll LoadedModule[172]=C:\Windows\system32\Secur32.dll LoadedModule[173]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[174]=C:\Windows\system32\mswsock.dll LoadedModule[175]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[176]=C:\Windows\System32\wship6.dll LoadedModule[177]=C:\Windows\system32\DNSAPI.dll LoadedModule[178]=C:\Windows\system32\dhcpcsvc6.DLL LoadedModule[179]=C:\Windows\System32\wshtcpip.dll LoadedModule[180]=C:\Windows\System32\netprofm.dll LoadedModule[181]=C:\Windows\System32\nlaapi.dll LoadedModule[182]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[183]=C:\Windows\system32\rasadhlp.dll LoadedModule[184]=C:\Windows\System32\npmproxy.dll LoadedModule[185]=C:\Windows\system32\msiltcfg.dll LoadedModule[186]=C:\Windows\System32\fwpuclnt.dll LoadedModule[187]=F:\FS2004\GAUGES\QWBae146_2.GAU State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator 9.0 AppPath=F:\FS2004\FS9.EXE My system uses an ASRock Z87 Extreme 4 MB w/DDR3-1600 8GB, an Intel i5-4670K cpu and EVGA GeForce GTX650 with 1GB Super Clock GDDR5 (with 331.82 driver). I took a look at the AVSIM CTD Guide but didn't see anything that looked like it would be of use since it didn't mention any CTD causes specific to QW's BAe146. Also, while it mentioned FS9, all of the info in the guide appears to be specific to FSX which is of no use to me as the CTD I'm experiencing is while attempting to load a QW BAe146 in FS2004. ---------------------------------------------------------- Hi, SirStigge! Thanks for the link to the Flight1 forum. I had reviewed it before posting my message here. The info in it didn't seem to fit my case. The CTD occurs immediately after I attemp to load a QW BAe aircraft from spot view, not only when I switch from spot view to 2D panel view or while I'm in mid-flight so the gauge problem discussed in the thread doesn't seem to apply here. Still I'll give the hotfix mentioned in the thread a try as I have little to lose at this point! Scott