Yep - it's real taxiways. First pic is real taxiways on and 2nd pic is with it off. I've noticed this at a few other airports too - just kept forgetting to report it. Hopefully it's a code fix and not just one off fixes. It's always the sign that's wrong. [image: 93b6eb0d-5023-4f78-b50b-54601c0868ec.jpg] [image: a004a75d-9ee3-47e0-a88c-8dd65ea043c5.jpg]

Just a reminder that this was announced. I'm practicing my dual engine failure, tea pouring 1G barrel roll in the Barron. https://fselite.net/content/black-square-reveals-previously-unannounced-twin-in-development/

I think that behavior might actually be expected. The continuous-flow masks are only effective up to about FL250. As you approach that altitude the oxygen partial pressure becomes too low for the mask to maintain normal blood oxygen saturation, so the SPO2 reading starts to drop. The FL250 ceiling is basically the altitude where the system can still keep the pilot functional, not necessarily at 90% saturation. For extended flight, most guidance recommends keeping SPO2 around 90%, and increasing oxygen flow or descending if it starts dropping into the high-80s.

@alanfernandes Ok, I did some digging. The Starship was originally designed in the 1980s and produced between 1989 and 1995. The original Collins AMS-850 had no GPS capability; it relied primarily on dual IRS with DME/DME and VOR/DME updating. However, the avionics suite was designed so that GPS sensors could be integrated later. During the aircraft’s production run, many were equipped with dual Collins GPS-4000 LRUs feeding the FMS, likely in the early–mid 1990s. This allowed the system to fly basic LNAV GPS approaches, though the GPS was mainly used to improve long-term inertial navigation accuracy by providing position updates to the FMS. The newer GPS-4000S units are generally backward-compatible replacements with higher precision and WAAS/SBAS capability, and they’re easier to source today since the GPS-4000/4000A units are no longer produced. Some Starships may have been upgraded to the 4000S, but since the AMS-850 predates many of the 4000S capabilities, it cannot use vertical guidance from WAAS approaches and would only benefit from improved integrity and lateral accuracy.

Not sure you read the thread (particularly Nick's responses rather than my drivel), but those vars aren't (or weren't) being exposed, they're only internal. So AAO/SPAD/Mobiflight can't see them, at least not until you make the changes to expose them that Nick and I talk though up above. All sorted now though!

@hunterdouglas I think this is something that Just Flight support would be best placed to help with. See: https://community.justflight.com/topic/2/product-support

As long as it's an option - and not forced upon the user -, it's fine. I personally don't want anything turning red, blue, etc.

shouldn't even have that performance lightly loaded.

I think my issue was just related to X-Plane 12 and specifically the Dash8 as I have been flying in MSFS with PMDG 737 and I haven't had a corrupted flight yet (4 flights).

It's like this IRL with nav lights during the daylight. You can argue its a little bit to dark but its still perfectly within range. There are other areas where lights are to dark.

What makes you think that?

Solved....down loaded Axis and Ohs and configured the whole setup w/out using the MSFS2024 control panel.

@SadBucket you don’t necessarily need to rummage between different pages. Sky4Sim has already implemented a plugin that integrates its tablet into the MSFS tablet - for instance. If you want to use only Sky4Sim’s features, you can: just select the Sky4Sim icon and the S4S interface will appear and can navigate only the features provided by S4S — the only difference is that it shows up inside the MSFS tablet. It definitely improves immersion, especially in aircraft that already have the “3D MSFS tablet” available.

@django1489 Good try but nothing of the sort I'm afraid.

@SadBucket I do fly predominantly without the 430, however if I am flying a rnav departure or arrival, it comes in handy. Especially an intercept of a radial of a waypoint.

I'm mainly flying the Baron Pro, but have had the same problems, especially on short final and if the wind speed is 10kts+. I actually found the plane uncontrollable and nothing could stop it rolling over and crashing inverted. This happened with some other aircraft, but not all. I tried to use the MSFS2024 turbulence settings to fix it, but I found that setting it to Low or Medium resulted in no turbulence at all, so quite boring. Then I discovered and installed ActiveSky. I have set the Turbulence Effect Scale to 50% (the default) and then reduced overall wind turbulence from 100% to 50%. This results in there still being turbulence on the plane in the air, and some more turbulence on short final still, but now it's manageable. And what a great weather synthesis! Much more realistic looking skies, and more closely aligned to Windy.com's winds. Give it a go!