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_CRJ700

Members
  • Joined

  • Last visited

  1. Looking for the OO/QX new Alaska liveries for the feelThere E175 for FSX. Everything I've found is P3D. I CAN'T be the only one on earth still using FSX and wanting this livery. There was a previous thread about this but the link goes to a page where the liveries are no longer available. -Brad...
  2. Update: 1) Ran the FSDT Live Update again despite GSX having been un-installed; No crashes. 2) Re-installed GSX, back to crashes. 3) Repeated item 1, no crashes. Also of note, what kicked all this off in the first place was my aircraft.cfg file for my Wilco Falcon 7X just up and vanished from the computer. Like full on David Copperfield, poof, gone. (And we don't need to get into the Falcon being garbage. I researched it before buying it, knew it was pretty hot garbage, but they did a sale, so it was CHEAP, hot garbage). That was the first crash, and then I've been mired in this ever since. Not sure if they're relatead, but at this point might as well not skip anything. I found out the cfg file was gone after I loaded a saved flight and it errored out and then opened up my hangar and found them gone.
  3. I've been researching this already and tried a few fixes, but nothing is taking. Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: g3d.dll, version: 10.0.61472.0, time stamp: 0x475e180c Exception code: 0x80000001 Fault offset: 0x000b50df Faulting process id: 0x69c Faulting application start time: 0x01da69e787740f9f Faulting application path: D:\Program Files (x86)\fsx.exe Faulting module path: D:\Program Files (x86)\g3d.dll Report Id: 59d802a9-2da5-40f5-8db1-170782208ea5 Faulting package full name: Faulting package-relative application ID: First thing I tried was changing "scenery.cfg" to "scenery.off" to let it rebuild. That worked for one cycle, but the next time I went to start up, back to crashes again. So I looked at the log again, and the error above was followed imediately by this: Faulting application name: couatl.exe, version: 3.2.0.5318, time stamp: 0x6553c66e Faulting module name: couatl.exe, version: 3.2.0.5318, time stamp: 0x6553c66e Exception code: 0xc0000005 Fault offset: 0x0005aa89 Faulting process id: 0x2ec4 Faulting application start time: 0x01da69e794417b61 Faulting application path: D:\Program Files (x86)\Addon Manager\couatl\couatl.exe Faulting module path: D:\Program Files (x86)\Addon Manager\couatl\couatl.exe Report Id: b6ffcd1d-d39b-4f88-a663-889bc480b771 Faulting package full name: Faulting package-relative application ID: So next I went to my FSDT updater and ran it. This would fix the problem again for only one cycle, and the next startup crashes again. So I repeated this step with the same result two or three more times. I figure something with GSX is corrupted so I uninstalled it with the intent to re-install. Again, this fixed the problem for one cycle, and now I'm back to the crashes again with these same two messages even though I haven't re-installed GSX. I'm not sure where to go from here. -Brad...
  4. Obviously the CRJ, but now there is a turboprop division how about the Embraer 120 Brasilia.-brad...
  5. I've successfully installed the Erick Cantu EMB 120 Brasilia into FSX but when I go to autostart the engines they won't turn over. Any thoughts? The starter comes on but that's it.

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.