Jump to content
Sign in to follow this  
mbunjes

three weeks of FSX crashes

Recommended Posts

Ever since finishing the build of my new flightsim computer three weeks ago I have been trying to get FSX to work with my 737NGX, unsuccessfully up till now.

 

When trying to load a previously saved flight with the NGX FSX crashes after 3% loading.

The fault module is the PMDG737NGX.dll.

 

It is possible to load the default ultralight at an airport and then change to the PMDG. I can then go and fly. Problem is, after every crash FSX reverts to default and I lose all my hardware settings  so I spend an hour getting all my hardware to work again.

 

I disconnected all my hardware (Saitek yoke and rudder, Opencockpits FMC, MCP, COMM, 2 X NAV, ADF, XPNDR, g throttle, Arduino button box,  a Bodnar card and a TH2GO) and I had no more problems.

 

I connected the hardware items one at the time, tried loading a saved flight, restarted the computer and loaded the flight again : perfect. So there I was with everything except the TH2GO connected and everything working. Great.

 

 I left it two days, started up FSX, loaded a saved flight : crash at 3%

 

I then disabled the modules as per the CTD guide : everything worked. I enabled the FSUIPC module : crash. Deleted the FSUIPC.ini : no crash. I inserted just the button mappings from the saved FSUIPC.ini : crash

 

So now I’m at a point were I’m suspecting my flying hardware to be faulty but I have no idea how to proceed further.

 

BTW. The hardware worked flawlessly on my former flightsim pc.

 

Latest AppCrashView report :

 

Version=1

EventType=APPCRASH

EventTime=130521505229044886

ReportType=2

Consent=1

ReportIdentifier=50622a3f-2091-11e4-82ce-74d435e52476

IntegratorReportIdentifier=50622a3e-2091-11e4-82ce-74d435e52476

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.61637.0

Sig[2].Name=Application Timestamp

Sig[2].Value=46fadb14

Sig[3].Name=Fault Module Name

Sig[3].Value=PMDG_737NGX.DLL

Sig[4].Name=Fault Module Version

Sig[4].Value=1.0.0.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=4f5162a3

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=00016c30

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.1

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1043

UI[2]=D:\FSX\fsx.exe

UI[3]=A fatal error occurred.

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]=D:\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.3079_none_cbf38852470c569f\MFC80.DLL

LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\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.3079_none_03cbcb30205b7fe3\MFC80ENU.DLL

LoadedModule[60]=D:\FSX\language.dll

LoadedModule[61]=D:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll

LoadedModule[63]=D:\FSX\ablscpt.dll

LoadedModule[64]=D:\FSX\flight.dll

LoadedModule[65]=D:\FSX\ai_player.dll

LoadedModule[66]=D:\FSX\acontain.dll

LoadedModule[67]=D:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=D:\FSX\fsui.dll

LoadedModule[70]=D:\FSX\atc.dll

LoadedModule[71]=D:\FSX\facilities.dll

LoadedModule[72]=D:\FSX\demo.dll

LoadedModule[73]=D:\FSX\main.dll

LoadedModule[74]=D:\FSX\fe.dll

LoadedModule[75]=D:\FSX\util.dll

LoadedModule[76]=D:\FSX\simprop.dll

LoadedModule[77]=D:\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]=D:\FSX\g3d.dll

LoadedModule[83]=D:\FSX\panels.dll

LoadedModule[84]=D:\FSX\multiplayer.dll

LoadedModule[85]=D:\FSX\ui.dll

LoadedModule[86]=D:\FSX\sound.dll

LoadedModule[87]=D:\FSX\sim1.dll

LoadedModule[88]=D:\FSX\simscheduler.dll

LoadedModule[89]=D:\FSX\visualfx.dll

LoadedModule[90]=D:\FSX\window.dll

LoadedModule[91]=D:\FSX\terrain.dll

LoadedModule[92]=D:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=D:\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]=D:\FSX\xuipc.dll

LoadedModule[99]=D:\FSX\livingwater.dll

LoadedModule[100]=D:\FSX\fs-traffic.dll

LoadedModule[101]=D:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[105]=C:\Windows\system32\rsaenh.dll

LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[111]=C:\Windows\system32\wbemcomn.dll

LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL

LoadedModule[117]=C:\Windows\system32\dxgi.dll

LoadedModule[118]=C:\Windows\system32\d3d11.dll

LoadedModule[119]=C:\Windows\system32\nvd3dum.dll

LoadedModule[120]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[121]=C:\Windows\system32\bcrypt.dll

LoadedModule[122]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[123]=C:\Windows\SysWOW64\bcryptprimitives.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:\Windows\SysWOW64\dxdiagn.dll

LoadedModule[128]=C:\Windows\SysWOW64\d3d10.dll

LoadedModule[129]=C:\Windows\SysWOW64\d3d10core.dll

LoadedModule[130]=C:\Windows\system32\winbrand.dll

LoadedModule[131]=C:\Windows\system32\WTSAPI32.DLL

LoadedModule[132]=C:\Windows\system32\WINSTA.dll

LoadedModule[133]=C:\Windows\SysWOW64\gameux.dll

LoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll

LoadedModule[135]=C:\Windows\SysWOW64\XmlLite.dll

LoadedModule[136]=C:\Windows\SysWOW64\wer.dll

LoadedModule[137]=C:\Windows\System32\Wpc.dll

LoadedModule[138]=C:\Windows\System32\wevtapi.dll

LoadedModule[139]=C:\Windows\System32\msxml6.dll

LoadedModule[140]=C:\Windows\system32\SAMLIB.dll

LoadedModule[141]=C:\Windows\system32\netutils.dll

LoadedModule[142]=C:\Windows\system32\uiautomationcore.dll

LoadedModule[143]=C:\Windows\system32\OLEACC.dll

LoadedModule[144]=C:\Windows\System32\MMDevApi.dll

LoadedModule[145]=C:\Windows\System32\PROPSYS.dll

LoadedModule[146]=C:\Windows\system32\AUDIOSES.DLL

LoadedModule[147]=C:\Windows\system32\RICHED20.DLL

LoadedModule[148]=C:\Windows\system32\HID.DLL

LoadedModule[149]=C:\Windows\system32\XInput9_1_0.dll

LoadedModule[150]=C:\Windows\system32\wdmaud.drv

LoadedModule[151]=C:\Windows\system32\ksuser.dll

LoadedModule[152]=C:\Windows\system32\AVRT.dll

LoadedModule[153]=C:\Windows\system32\msacm32.drv

LoadedModule[154]=C:\Windows\system32\midimap.dll

LoadedModule[155]=C:\Windows\system32\dinput.DLL

LoadedModule[156]=C:\Windows\System32\wship6.dll

LoadedModule[157]=C:\Windows\System32\wshtcpip.dll

LoadedModule[158]=D:\FSX\Modules\FSUIPC4.dll

LoadedModule[159]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[160]=C:\Windows\system32\WINNSI.DLL

LoadedModule[161]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll

LoadedModule[162]=C:\Windows\SysWOW64\ieframe.dll

LoadedModule[163]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll

LoadedModule[164]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll

LoadedModule[165]=C:\Windows\system32\Secur32.dll

LoadedModule[166]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll

LoadedModule[167]=C:\Windows\SysWOW64\mshtml.dll

LoadedModule[168]=C:\Windows\system32\msimtf.dll

LoadedModule[169]=C:\Windows\system32\msls31.dll

LoadedModule[170]=C:\Windows\system32\d2d1.dll

LoadedModule[171]=C:\Windows\system32\DWrite.dll

LoadedModule[172]=C:\Windows\system32\D3D10Warp.dll

LoadedModule[173]=C:\Windows\system32\MLANG.dll

LoadedModule[174]=C:\Windows\system32\ntmarta.dll

LoadedModule[175]=C:\Windows\syswow64\WLDAP32.dll

LoadedModule[176]=D:\FSX\GAUGES\PMDG_737NGX.DLL

LoadedModule[177]=C:\Windows\system32\NETAPI32.dll

LoadedModule[178]=C:\Windows\system32\srvcli.dll

LoadedModule[179]=C:\Windows\system32\wkscli.dll

LoadedModule[180]=C:\Windows\system32\WSOCK32.dll

LoadedModule[181]=C:\Windows\system32\MSVCP100.dll

LoadedModule[182]=C:\Windows\system32\MSVCR100.dll

LoadedModule[183]=C:\Windows\SysWow64\XAudio2_7.dll

LoadedModule[184]=D:\FSX\GAUGES\PMDG_737NGX_3.DLL

LoadedModule[185]=D:\FSX\Gauges\PMDG_737NGX_2.dll

LoadedModule[186]=C:\Windows\system32\snmpapi.dll

LoadedModule[187]=C:\Windows\system32\NLAapi.dll

LoadedModule[188]=C:\Windows\system32\napinsp.dll

LoadedModule[189]=C:\Windows\system32\pnrpnsp.dll

LoadedModule[190]=C:\Windows\system32\DNSAPI.dll

LoadedModule[191]=C:\Windows\System32\winrnr.dll

LoadedModule[192]=C:\Windows\System32\fwpuclnt.dll

LoadedModule[193]=C:\Windows\system32\rasadhlp.dll

LoadedModule[194]=C:\Windows\system32\icmp.Dll

Sec[0].Key=LCID

Sec[0].Value=1043

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=Microsoft® Flight Simulator X

AppPath=D:\FSX\fsx.exe

Share this post


Link to post
Share on other sites

Your Microsoft Visual C++2005 is out of date.  FSX needs the 2005 w/SP1 version.  I see Microsoft Visual C++ 2010 loaded successfully (used by PMDG) but I do not see version 2008 installed (or at least it did not load).  Many addons require Microsoft Visual 2008.  See page 5 of the CTD Guide for links to the correct versions.

 

The faulting module - PMDG_737NGX.DLL - has been known to crash if the uiautomationcore.dll is in the main FSX folder. I do not see where it was loaded so that cannot be the problem. I have read that this problem is caused if you select another aircraft and then the PMDG737NGX. PMDG has specifically identified this will cause problems if you select another aircraft and then the PMDG aircraft during the same flight session.

 

I'm not sure why a previously saved flight is not working. Loading previously saved flights has always been a headache in FSX and I have totally avoided it. Many are successful. Most likely the panel state is not the same as it was in the previous flight. You might submit a ticket to PMDG support to see if they have a solution for this problem.

 

If the fsuipc module is causing crashes when you enable it in the dll.xml, then you might have the wrong version required by one of your installed products. Installing the latest version is always the best solution. It could also be a corrupted dll.xml but that's less likely as FSX is not loading the fsuipc when you disable it.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Jim, sorry for the late reply and thanks for the suggestions. Unfortunately none of them resolved my issues.

I have submitted a ticket to PMDG and it seems that you're not supposed to map an axis using FSUIPC. So I configured all my axis using FSX and while it solved the issue of FSX crashing while loading it's not possible to use the throttles together with a switch mapping for reverse thrust. The flaps and speedbrake don't work in this way but luckily they can be assigned using FSUIPC. Also the fuel cut-off switches don't work. At this point I'm seriously considering switching over the competition and try the IFly 737.

Share this post


Link to post
Share on other sites

I have submitted a ticket to PMDG

Sorry to hear you are still having problems. If they come up with solutions, especially the PMDG_737NGX.dll error, please post it here so other members can try the fix too.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I managed to track down a fault in my set up. After reinstalling FSX and the NGX and plugging in my hardware one by one, testing every time, I noticed the PMDG crashing FSX on loading when I had my Bodnar card connected. It had some circuitry connected to it but no buttons were assigned in FSUIPC.

But when I removed the wires from the card my problems were over. There's probably a short somewhere in the button wiring but I find it very strange that only the NGX was affected by this. The default FSX planes were all working correctly.

Anyway, I'm happy.

Share this post


Link to post
Share on other sites

I have this crash if i have my throttle levers or any levers on my saitek, away from the up position!


Vernon Howells

Share this post


Link to post
Share on other sites

I managed to track down a fault in my set up. After reinstalling FSX and the NGX and plugging in my hardware one by one, testing every time, I noticed the PMDG crashing FSX on loading when I had my Bodnar card connected. It had some circuitry connected to it but no buttons were assigned in FSUIPC

Thanks for the valuable information. I have subsequently read where many get this crash because of a bad configuration of a controller used for FSX, especially if programmed through the fsuipc. If they programmed through the controller's software, no problems. So your solution definitely makes sense. These controllers are getting more and more sophisticated but at least we have an idea now as to what might be causing the dreaded PMDG_737NGX.dll to show up as the faulting module.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I've narrowed it down even further. There are several switches connected to the bodnar card which give no problems whatsoever.

However there's also a parking brake switch connected. When I leave this switch on when loading the NGX, it will crash. When I switch it off, no problems.

It's not assigned in FSUIPC so as far as I can tell it's not doing anything in FSX nor in the NGX.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...