Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Selecting MD-11 Crashes FSX

Featured Replies

Hello, I have been flying the MD-11 for a couple of months now. Yesterday, I tried to load up the MD-11 and upon selecting it in the Free Flight window, FSX crashes with one of those "fatal error" windows. This was after flying successfully earlier in the day and for months. I sometimes get an error about {smartassembly} needing to be on the computer. I have searched the forum and the web for possible fixes. So far I have spent three hours over the past day doing:- Uninstalling MD-11 and re-installing- Repairing FSX- Removing all Visual .NET frameworks (I can't get 3.5 to reinstall due to Windows 7 giving me an error saying "You must use Control Panel's Turn on and off Windows Components to install this" which I have tried turning on and off but to no affect- Removing and reinstalling Visual C++ runtimes- Doing all the above in various orders So far still no luck. All my other planes work including the PMDG JS4100. I am running Windows 7x64. The only thing I can think of that I did between working and not was installing FS Passengers demo which I have since removed. I am thinking it could have overwritten something but I'd think a re-install of the MD-11 would have that fixed. Any help would be appreciated. Thank you!- Richard

  • Author

It looks like I may have fixed it. After some more searching, I came across this in the support folder: http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx In dll.xml there was a line at the end of the addon lists that had an open <Launch.Addon> with nothing inside and no matching closing element. I deleted that and it seems to work now. I'll keep my fingers crossed and keep this in case it helps others!

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.