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.

DAD

Members
  • Joined

  • Last visited

  1. Updated to SU6 final and all good. actually better than the recent beta, very smooth and great (actually better) performance. had slight stutters and items popping in with the betas when flying especially into Ini EGLL but not today - and yes, I even saw landing gears on all other planes when coming into and just now when getting out of EGLL for my second leg to EDDL. nice work
  2. The anticipated update addressing the NOT IN DATABASE was released, works now again for me This is build 145. The build addresses: Continued navigation update logic improvements Added FACTORY RESET> option in PMDG SETUP> to purge the navdata from within the sim Fixes to the image file bloat that was causing high VRAM use
  3. Good to know. Hope I’ll see the same then in about an hour UPDATE: worked, all fine
  4. well, stuck at 0% authentification in progress...
  5. thanks. that DLSS 310.6 helped already a lot, could do another flight in the iFly. thanks to all who brought this up. happy camper again. fingers crossed. else I may go back to NVIDIA .47...
  6. Update. Could at least complete a full flight in the Fenix 319 though MSFS2024 then CTDed when standing at the Apron... anyway, will try a next one now in the iFly
  7. thanks, just saw that too. actually, 310.1 is the original one which comes with MSFS2024, will now change to 310.6 and see whether that helps
  8. After I updated to the latest beta the DLSS was Set back to .16 IIRC and then as usual I manually swapped it to DLSS latest .17. so yes, THAT could be a reason then. Will try the default DLSS and check it
  9. Nope. Will sit this out. Cannot be too long and have enough work to do anyway these days before leaving for vacation mid August. I am sure it will be fine again - some time
  10. this is the first build ever since I started to enter the public beta process which constantly crashes MSFS2024. Sometimes when the first inital loading screen comes up (when the seconds are counted bottom right), giving me a meaningless error message (funnily enough when I start via XBOX app that does not happen). but latest after flying about 30-60mins the sim locks or causes a hard crash/CTD. happens with any of my planes, 3rd party but also Asobo planes. Will skip flying now until the next beta comes....
  11. Welcome to the party, @Potester - and I mean Avsim ;-) Dummy question: do you use the latest iFly version? Did you try the default livery as well? Which NVIDIA driver are you using? Any third party apps running in the background? Your rig may not be the fastest but on my by today‘s means meager PC the iFly just behaves well.
  12. that's my point. Hence I answered "No" to the poll. But after some praised the Simbrief functionality (for good reason!) I felt that the poll may not show the right results if "subscription" is interpreted as either "have account" (which I do) or "have paid subscription" (which I don't).
  13. see, and yet another poll you can read this way or that way. Because "subscription" for me reads like "I pay money". Which I do not do as I hate subscription models. However, I am a Simbrief and hence free Navigraph user. So if usage is considered a "subscription" then my "no" count to the poll is wrong and would need to say yes. EDIT to avoid ambiguity the poll should (have) read like I use a free Navigraph subscription (Simbrief) I use a paid Navigraph subscription (AIRACs) I do not use any Navigraph service
  14. Through OC3 This is build 4.0.60. This build continues the effort to increase stability throughout the aircraft code files, with specifically: Auto-detect .fmc file issues and recover truncated .rte extensions Enhanced TO/GA functionality after baulked landing/touchdown Block PIP and Auto Ignition options on 900ER equipment pages Improved IF waypoint handling
  15. reinstalled the 777 and it loaded. though now does seemingly have no AIRAC data since the FMC does neither know KBOS nor EGLL... well...

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.