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.

rlashier

Members
  • Joined

  • Last visited

  1. While it may seem trivial, pleased that they finally have the city and town names displaying with their POI markers. Also, while I have not tested this yet, I hope it’s true that they fixed the issue of aircraft spawning at the wrong runway at many airports in Free Flight. Rich
  2. Yes, Bill, it was pressing the chrono that caused your sim rate to change. Turns out that if you turn the knob in the lower right of the chrono, it will adjust the sim rate. With one twist of the knob, the chrono turns yellow and rate accelerates to 2X. With another turn of the knob, the chrono will turn red and you are at 4X sim rate. Then, a simple press of the knob returns you to 1X rate. What’s odd is that PMDG altered this sim rate activation recently. In the 737-700 for MSFS 2020, the chrono’s upper left knob activated this functionality. But in the new 737-800, it moved to the lower right knob. Once you get the hang of it, it’s quite useful.. Rich
  3. That’s the way to handle it! When flying Airbus, I’ve found that the inclusion in the FMC of a MANUAL segment and a discontinuity prior to the start of your approach is quite customary. It’s funny that in so many tutorials about how to fly various airliners, the appearance of a discontinuity is viewed as an anomaly that must be dealt with by a deletion to tie waypoints together. But with the Airbus, this kind of discontinuity is more like a placeholder indicating some action (e.g., proceeding in Heading mode and following vectors until sufficient altitude is bled off) is required before starting the approach. Good luck! Rich
  4. Pardon me if I state the obvious, but you likely went wrong when you deleted the manual entry and then forced the deletion of the discontinuity. In my experience with the Fenix bus, the inclusion of the manual entry prior to the initial approach fix is quite purposeful. Often, you will want to proceed on the track associated with the manual entry, or follow other vectors, until you have bled off enough energy and altitude to commence the approach. Then would be the time to proceed direct to the IAF. Sometimes you can get away with deleting the manual entry and the related discontinuity, if there is sufficient distance to the IAF to lose the necessary altitude, but if not, you will almost certainly come in hot and heavy. Rich
  5. Prefer to start at gate, usually in turnaround state to save some time and drudgery.
  6. Until such time as the Nvidia App filters work in MSFS 2024, I will refrain from installing the app. I don’t find it helpful to change drivers frequently, and when a new driver provides any benefit for MSFS, it is a simple process to download and install them manually. Rich
  7. How refreshing to find a post in which simmers provide helpful information on how better to enjoy their simming, rather than slamming each other for their opinions or preferences for a particular flight sim, an aircraft, or a particular developer. Keep it up! Rich
  8. Navigraph’s integration with Simbrief and with several of the premier airliners’ EFBs make it fairly indispensable for significant flight planning, chart monitoring, etc. and add so much to the enjoyment of the hobby. But if the expense of a Navigraph subscription is a big con for you, I don’t think you would miss that much if you were to subscribe at 3 or 4 month intervals. Changes to content are actually quite minimal - a STAR name might change from BDEGA3 to BDEGA4 for example, but it’s still obvious which one to select. Rich
  9. I recommend you post this issue to the FSUIPC support forum. There is a new support forum there and John Dawson does a good job responding to issues from the program’s users. Attach a copy of the FSUIPC ini and log files to your topic and it should be sorted out quickly. Rich
  10. Performance improvement and lack of stutters on final approach to complex airports are most noticeable improvements for me. Flew the Black Square A36 from LVFR’s KBWI to DD’s KDCA, using the ILS01 approach. I lock my frames at 60 fps on my 60 Hz 4K monitor. Smooth all the way, never deviating from 60 fps. Previously in SU3, on final to DCA, frames would rapidly drop to the 40s, and the approach became stutter fest all the way to the gate. So I am very pleased with this update. There were occasional fraction of a second delays when switching between cockpit and external views, but this seemed trivial on the whole and hardly immersion killing. The performance improvements more than compensate for this. Rich 5800X3D, 4080 Super GPU, 64 Gb DDR4, 4, 1 TB SSDs, LG 4K monitor Win 11
  11. While I love how this aircraft flies in MSFS 2024, steering it on the ground is another matter. I currently control my aircraft with a CH Products yoke and throttle quadrant, and I also use a Thrustmaster Airbus flight stick that has rudder control on its twist axis. While I can steer the 737 Max on the ground with the flight stick rudder axis, I would much prefer to use nose wheel steering so that I can control this plane just with the yoke and throttle quadrant. Problem is that I cannot find a way to reliably assign nose wheel steering to an axis on the yoke or the throttle quadrant. Ideally, I would assign the nose wheel to the yoke’s “X” axis and use it for both aileron and nose wheel while on ground, but I also have an unused axis available on the quadrant. The 737 Max EFB has a checkbox for independent nose wheel steering under the Panel Style/General tab. The MSFS 2024 Controller setup menus include nose wheel steering as an assignable function. I have tried numerous times to assign nose wheel steering to my yoke axis or the quadrant axis with the MSFS 2024 controller setup menu, and both by checking and not checking the EFB independent steering check box. I’ve even tried assigning the steering to the aircraft with FSUIPC7 axis assignment, but this too has not worked. Regardless of the method used, the nose wheel steering is not working, or, it works temporarily but does not stick for subsequent flights. Any advice on how this should be done? Thanks much for any help. Rich System: 5800X3d, 4080 Super GPU, 64 Gb DDR4 ram, 4- 1TB SSD drives, LG 37 in. 4K display, Windows 11.
  12. I also love the KDCA approach with the 737, although I prefer the River approach to Rwy 19 to the Rwy 1 approach. Scenery is very impressive either way. Where did you find the Maryland livery? That’s fantastic! Rich
  13. On Flightsim.to there is a free KSLC by Desperoto that seems decent. Hey, the Jetways connect to the terminals! Rich
  14. If you prefer to fly tubeliners with glass cockpits and digital readouts, TAA is the way to go. I cannot tolerate the fuzzy digital displays with DLSS, and the lag in response when changing settings is not pleasant. Besides, TAA is fully compatible with Nvidia Frame Generation, if that is your preference, and you can ignore all the frenzy about DLSS swappers and such. Rich
  15. Noel, Whenever I have issues with the AP engaging after takeoff in the Fenix A320, it is because the runway heading is such that it deviates too much from the first leg of the flight path. The solution is to adjust your heading after takeoff to provide an intercept with the flight path. At that point, the AP should engage. I have found this to be the case at KBOS and other airports. If this is the source of your issue, know that this is part of the aircraft systems’ design, and not a bug. Rich

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.