RNAVV19R

Yep, no publicly available approach. But I was wondering if an airline may have created their own approach, in which case the chart (and the approach itself) wouldn't be available to anyone other than that airline and anyone else that they sold it to. It's a long shot that anyone here would have this knowledge, but was just wondering.

Speaking of RNP approaches, anyone know if one exists for RWY 14R at RJOO? Or at least a RNAV Visual? None exist in Navigraph, but I wonder if one of the Japanese airlines might have designed one. Not sure how common that sort of thing is in Japan. Here is the approach:

Different companies handle this sort of thing differently. Some airlines develop their own RNAV Visuals or RNP approaches and make them available to other airlines, though I assume they do so for a fee. An example of this is the RNAV RNP 13L/R at KJFK. It was developed by JetBlue, but there are other airlines that have access to it.

Fair enough. Does no other airline have their own RNP approaches for those airports in Alaska? RNP approaches seem to be so ubiquitous now and many airlines have their own RNP approaches for other airports.

I saw Sam's video, too. There's an Alaska pilot who vlogs some of his trips as well. I remember him showing a brief glimpse of the approach chart of one of those Alaska RNP approaches in one of his videos. But I can't seem to find it anymore. Perhaps he was told to remove it from his channel. https://www.youtube.com/@ThePilotLife/videos

There are several airline specific approaches in Navigraph's NAV database, so this isn't surprising. Whoever their data supplier is has access to a bunch of these. Some examples: KLAS RNAV Visual 19R, KJFK RNAV RNP 13L/R, KSFO RNAV Visual 1R (although they are missing the RF leg). There may be more, but these are the ones that I know of. None of them have charts. You can even create the RNAV Visual for RWY 25 at KSBA as all of the waypoints are available in the database.

Haven’t experienced any of the issues discussed in this thread.

To be fair, the PMDG 737 flight dynamics have improved a lot in 2024. I hated the way it felt in 2020. iFly flew exceptionally well in 2020, but we will probably have to wait for the native 2024 version to get the best out of it.

That makes sense. Thanks for the explanation. Love your liveries!

I'm aware that the iFly comes with the 178 seat option. I'm just referring to the SWA liveries from Jviation. They were done only for the 189 seat layout.

According to Southwest's site, they use the 175 seat layout on the 737 MAX. Wonder why Jviation made the SWA liveries for the 189 seat layout.

I reinstalled and also used the correct Simbrief profile. I believe that was my issue since I was using the 178 seat profile but the livery I was using was for the 189 seat layout. Anyways, hand flying is perfect now. No more issues on that front.

Not sure if I will get to fly it this weekend, but will try reinstalling it first and then fly it again when I get the chance. If the issue persists, I will make a video.

Is it just me, or does this update kind of suck? I also noticed the weird VNAV behavior as well as GS hunting on approach. Also felt terrible when hand flying on approach. Turbulence set to Low and the wind was only 10 knots. I experienced weird flight dynamics last summer but that was in extreme conditions - 40C weather in Las Vegas with 30 knot winds. Never experienced this before in the iFly in normal conditions. This was after loading up the plane a second time after first loading in just to take a look at the plane without flying it. I even rebooted the PC in between.

Great news. We need a good KORD in the sim.

Maybe that’s why. Noticed that there were a bunch of AIG liveries not installed by default. Installing them now to see if it will make a difference.

Looks like there is still work to do to get this working correctly. Live traffic is not very accurate yet. When comparing to FR24, there have been several flights on approach that are entirely missing from BATC after connecting my Navigraph Ultimate subscription and enabling live traffic. This has happened at several airports. This happens when using FSLTL by itself and when using both AIG and FSLTL together. Sliders are all maxed out at 10.

Looking good.

Exactly what I've been looking for. This should finally add more traffic both on the ground and in the air. BATC traffic has been way too sparse, even with the sliders maxed out.

Are you using the Experimental version?

Pretty much everywhere. An airport like KATL will obviously have more traffic, but still not remotely close to what it is like in real life.

So this should greatly increase the traffic when using BATC. As it stands, even with the sliders maxed out, traffic is pretty sparse.

No, it's not a joke. I'm a hardware reviewer.

MSFS 2024 is an incredibly heavy sim to run. I have 5 GPUs with 4 of them being 16GB VRAM or lower, and I get the resource usage warning on all 4 unless I dramatically decrease resolution and/or settings. The 5th one is the 5090 which is my main GPU, and obviously no issues there. Whether that's warranted or whether it is poorly optimized by Asobo is a different discussion, but that's just the reality of the situation. Pointing being, if you have a mid range system that already struggles with the vanilla sim, then of course adding a bunch of highly detailed addons will further kill your performance. It's not surprising.

FSR 4 has been out for a while, and it's exclusive to the Radeon 9000 series. It uses the machine learning acceleration cores available on the 9000 series. You can mod the INT8 version of it on 6000 and 7000 series GPUs, although it's not as good as the the FP8 version. FSR 4.1, released recently, is a nice improvement over FSR 4.0. Official support for the INT8 version of FSR 4/4.1 is coming to the 7000 series this year, and in 2027 for 6000 series. And no, it's not better than DLSS 4.5. It's a big improvement over FSR 3, though.