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.

737 NGX just quits when programming FMC

Featured Replies

  • Author

Removing SweetFx causes my FSX not to launch at all - interesting

  • Commercial Member

Honestly sounds like you have much bigger system-level problems here. I know for an absolute fact we don't use the default 747's GPWS gauge in the NGX - you can verify that yourself looking at our panel.cfg to see which gauges are loaded.

Ryan Maziarz
devteam.jpg

For fastest support, please submit a ticket at http://support.precisionmanuals.com

  • Author

Ahh Hello Ryan, good to know PMDG staff are reading this.

 

Yes, it is quite possible I have bigger issues with system level problems. (Your comment "bigger system-level problems" is vague - tell me what you are really thinking here),,but it appears to be the 737 NGX that is currently is the only plane I regularly fly which causes FSX to quit to desktop when ALT Entering or ALT Tabbing. And the annoying thing is it is not always consistent immediately- sometimes it happens well into the flight. (an early poster (ZowenII) mentioned UIAutomationCore DLL so I have put that back in and am testing that now.)

 

As for the 747 GPWS gauge - I put that out there because it it seemed strange to me you would use this sound file - and now you have confirmed you do not. This was a red herring that must have caused an unrelated crash to desktop.

 

.And the only other real solution that I have avoided is reinstalling FSX from scratch. I have too many add-ons and too many un-installs to do before even attempting the un-install of FSX - then the pain staking process of rebuilding what seems to be a working simulation apart from this one issue - is, well, shiver, too hard a decision to make.

 

Anyway, I am prepared to un-install the 737 NGX and re-install - I am just putting it off for the moment while I test UIAutomationCore

 

Thank you for those who have offered suggestions.

The funny thing is, is that this "GPWS_Sound.gau" that supposedly lives in the stock 747-400 panel folder doesn't even exist on my installation. Is the file actually there on your installation in the directory you have posted? I haven't a clue why it would be loaded if you are using the NG, unless it is in your dll.xml or exe.xml and authorized in your FSX.cfg, but what would happen if you just deleted it, renamed it, or de authorized it, supposing it exists?

 

If GPWS_Sound.gau doesn't belong to the default FSX 747, then who does it belong to, and what is it doing in your stock 747 path?

 

 

Isn't this file from FS2004?

  • Author

The FSX GPWS_Sound gauge is a modification for the 747 Cockpit for both FSX and FS2004 bundled with 3rd party freeware contributions that use this gauge to enhance the usability of the 747 for both the default and Opensky variations. At some stage I probably installed a 747 modified panel - that is my guess

So did you solve it?

 

And if your FSX won't start without SweetFX than something is seriously wrong, you may have accidentally removed a file from your Main FSX directory .

  • Author

Sorry, slow to follow up. I haven't been around lately - too busy and have not been flying at all. I have had one flight with the NGX since this situation arose, and it was not a serious heavily FMC programmed flight - but I didn't get any quits to desktop - (which is good), but not a complete test.

 

With regards to Sweetfx - I think I didn't remove it completely - just removed all files with Sweetfx in the name - and the DLL was expecting to see the modified file - and when it didn't, it didn't start. (I created a cardinal sin and forgot to backup first)

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.