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.

FSX CTD when attemping to fly over KSEA

Featured Replies

  • Author

I nailed it...I am now able to fly anywhere in around KSEA including even landing at 2S1 Vashon Island...and no CTD's or freezes. It is the double files for the airshow.bgl that was causing FSX to crash when it tried to load up Vashon.I thank a certain poster who asked me to check out Vashon by unticking it in the Scenery Lib and then doing a test fly. Having done that...and been successful for an overflight....I then enabled it...and had another CTD. I then went into the 2S1 Scenery folder, and found that doubling up on the Airshow.bgl file. I removed one....went to the 2S1 Control Module...ticked the Airshow on...and then the Airshow off. No problems. Ran the KFHR-KSEA overly test flight in the F1 Citation Mustang...and no problems whatsoever. Case closed! If you have CTD issues around KSEA running ORBX PNW....check out the above on your system. It was an easy fix..once I found what was what.... Again...thanks to the PM message poster that pointed me out to Vashon Island as a suspect cause to investigate. My gratitude!Happy flying all.....Mitch

Mitch,Congrats! Just keep us informed if you get another CTD. :( I'm afraid that the problem is a system overload of some kind caused by the different sceneries installed in PNW or AUS.I'm only sharing this input because I've read in some posts that users had to lower their settings in order to stop the CTDs.

MSFS

  • Author
Mitch,Congrats! Just keep us informed if you get another CTD. :( I'm afraid that the problem is a system overload of some kind caused by the different sceneries installed in PNW or AUS.I'm only sharing this input because I've read in some posts that users had to lower their settings in order to stop the CTDs.
-----------------------------------------------------------------Thanks DJ! I pretty well spent the whole of Sunday ferreting this out, and tuning up FSX while I was doing it....such things as going to the latest My Traffic (it is now from 5.3a to 5.3b) Did that...and am now having a blast flying my face off all around the topography near KSEA...which until today, was CTD-City. I know that I did not add or modify 2S1 in any way...so it was the latest installer that placed two Airshow BGL's which crashed out FSX, when they both attempted to load. Removing one...and then unticking the Airshow from the control module was all it needed to end the misery. I probably could now run the Airshow scenery if I wanted to...and there now is only one to load, as is proper. I'll certainly notify if another problem arises, DJ...but I have to tell you...in grooming out FSX today...it is just a fantastic and smooth pleasure to run. It always is...WHEN it DOES run without giving you 'gas'...... LOL!I'm about to end Sunday evening by taking an iFly flight out from KCVG to KMIA. I hear there is nice weather and good cloud structure on the route... :)Have a good evening....Mitch

Turning off 2x supesampling fixed this for me I am not sure why. I was always getting CTDs when around heavy load areas regardless of what fsx.cfg settings I usedI have almost all sliders maxed and it brings my computer to its knees in heavy weather and scenery, 10-20fps but still smooth enough. Used to crash when in those high load areas, but not now. Too bad I don't get as sharp graphics but still very nice.

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.