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.

Midnight Music

Members
  1. Finally working, the latest firmware update put the throttles back to single stroke, double shaft mode. Of course, Win Ctrl never mentioned that in their update. Now the Fenix reads correctly.
  2. I think I figured something out. The throttles were not sliding, they were jumping. I went back to Windows configuration and ran through a calibration. Windows put the throttles back into sliding rather than jumping mode, now the throttles move correctly. This is probably why Fenix couldn't read correctly. I will test it later today. I think it got messed up when I did the firmware update.
  3. It's the other way around. It would not work in single stroke, so Win Ctrl support told me to use double stroke. It started working after that. Something odd is going on if single stroke is working for you.
  4. All of the above and still no go. Weird, because it worked just fine with the previous version. Now everything tests perfectly in SimAppPro, it's when I get to the Fenix that it goes awry.
  5. I spent hours trying to configure the Win Ctrl Airbus throttle, trying to get it work with the Fenix Airbus. It finally did after a lot of trial and error and a lot of customer support, and it worked really well. Recently Win Ctrl did a firmware update and now the throttle doesn't work anymore with the Fenix Airbus. I went back through all the steps I did before, but now it just won't configure correctly at all to work with the Fenix. Has anyone else experienced this? I have been back and forth with customer support, but the same things get said, so there's no help. If anyone knows a solution, please let me know!!! Lee
  6. I like it a lot too. It's working fairly well; however, I've had a lot of problems with the Simbrief login in GSX. I hope they can fix that. Lee
  7. I find the new version works really well with SU5. I put Auto FPS in my virus exclusions. I think it helps. Windows is very aggressive these days. Lee
  8. Could someone maybe explain how the default traffic switches from using its own Asobo models to using FSLTL models, I don't quite see how that would happen. Lee
  9. It's a great program, but it still misses some of the default Asobo handcrafted airports like EHAM, EHRD and EGFF for instance. I'm trying to figure out what setting might be off because it does read some default handcrafted airports like LXGB. EDIT: I just discovered that by "installing" those airports in the MSFS 2024 Library, they appear.
  10. Chaseplane really liberates you because you can have so many different views available whereas the default system is very limited in how many views you can have. It's definitely worth it. Lee
  11. I never installed Latin VFR, I'll go check again, I have nothing installed in that area, it's all default. Don't get me wrong, I really like the scenery, I just want to make sure it all works!
  12. I had ai landing on the grass and misdirection's on taxiing, I'm wondering if it is the underlying navdata then. I was landing on Rwy 10. Lee
  13. It looks very nice and it is much more up to date. Performance is very good. There's a glitch with the alignment of the runways and taxiways, that they need to fix right away! Lee
  14. Turns out it is a WinWing problem. It doesn't affect the operation of the Fenix airbus, but WW software loads background control settings that have nothing to do with your flight operation but are registered by Fenix as not being calibrated. Just ignore them. Hopefully WW will come out with a fix. Lee

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.