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.

ehakan

Members
  • Joined

  • Last visited

  1. Stan, Also to check "scenery.cfg" under "C:\ProgramData\Microsoft\FSX\" whether it has "Texture_ID=1" line in the area 01. Whenever I open FTX central, it deletes and make mess like you described. P.S: I didn't upgrade my libraries... [Area.001] Texture_ID=1 Title=Default Terrain Local=C:\Program Files (x86)\Steam\SteamApps\common\FSX\Scenery\World Layer=1 Active=TRUE Required=TRUE regards Hakan
  2. Thanks Kyle, I've already downloaded full installer. v.1.10.6436 Will be uninstalled as you described on message #1 soon. I won't touch 777 and OC. Anything else to do? Just Curious: I've bought NGX in 8/5/2011 and paid via PayPal. Is "log-in to your eCommerce account" means login with my Paypal username and password? Thank you.
  3. Same problem here. I've bought from you. When I logged in I can access base pack of NGX (and other orders) but not SP1D. Asks for loggin in ????? Thank you for your help. Regards.
  4. NGX 737-800 WL "Pegasus" livery gives an error in OC when trying to setup......
  5. Thanks for working on NGX:se. I've installed FSX:se & 777:se (in a few minutes), made couple of flights, memory stress tests and didn't encounter any freeze, error or something without touching fsx.cfg even its not contain HIGHMEMFIX=1. I think FSX:se is a great platform. So again looking forward NGX:se and of course 747v2:se.... Great job...
  6. Maybe this is ideal way to make request....
  7. Completely agree with you. Hakan.
  8. Let's confess, all we are still kids playing video games. What's wrong with that? :)
  9. Thanks all sir. I just forget to use VOR/LOC button and allowed "capture G/S before localizer" in options. Thank you all. Cheers. :)
  10. Thank you. I am going to check that. Thanks. As far as I understand, I should turn off the LNAV before glide sloping or pressing the APP button.
  11. During the flight on MCP: F/D:on (L/R), A/T: Arm, VNAV: on, LNAV: on and CMD A or B : on. I've never turn on both the CMD's. According to the aiport chart, 11nm before the runway (ILS signal) I'm pressing the APP. When the plane catch a ILS signal and start to glide sloping VNAV and LNAV lights goes off, just SPEED and APP stay on. So I can reduce the speed as referred by FMC. Is this procedure wrong? Could you please explain what the "RNP" is? Thanks.
  12. Sorry for delay, here is my video also. I recommend to watch in HD format :). While approaching LTBA 36R the localizer bug captured 100feet before touchdown. Airplane is PMDG 737NGX and same problem in PMDG 747-400X also. I didn't try MD-11X. My config is; Both nav radios tuned at 111.3, both course selectors at 355 (oops... they were automatically changed to 357 ????), I'm not sure that the APP activated, as you'll see on video I'm strugling to press APP for light go on, F/O APs ON. Landing config: flaps 40, Vref 149, speedbrake armed, gear down. Standard (windy) weather. Scenery - Default LTBA Thank you for your attention and effort. I'm going to watch your video.... Regards.
  13. Thank you, really appreciated. I removed the videoclip.
  14. My course was 355 heading 355. When I press APPR I was 158 knt, 2700ft, 40 degrees flaps, 1017hpa baro (adjusted at LTCA with TOPCAT), land gear on, speed brakes armed, G/S was ok and heading to runway at 355 and looks fine, lights ok, autobrakes set 2 at ERMAN. Thanks. How do you guess that?

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.