haskell

Workaround hack: turn on storm lights (and back off if you like) and all the integrated lights (controlled on the center panel) will work. Not the way it works in the real plane, def a bug, but keeps from having that dark cockpit.

Weird: turning on the STORM switch makes the backlights come on. You can turn it back off and they stay on. So many little bugs you think they would have caught in the "fixed" version. I want this plane to be good SO badly. We are missing the entire regional airline segment. I am having an issue with the integrated panel lighting in the ATR-42. The knobs on the center panel don't do anything when I go through the startup process. But, they DO work if I start on a runway. So I feel like maybe I am missing something power-related, but I have followed the checklist. Any idea why I can't get any lights?

SOLVED: Was using a 3rd party airport that apparently isn't compatible with MSFS 24 Is anyone missing approaches in this thing? Trying to fly to KMYR and the ATR has NO approaches and NO runways. Checked Navigraph and the sim is updated. Ugh. Is anyone else experiencing this problem?

The gust lock must be on for prop brake to work. In cold-and-dark it (incorrectly) defaults to off. The ATR uses the sim data. Those dates in the MCDU are for “route data” and “pilot data” (likely made up.) The Nav Data shows CURRENT, which is the current AIRAC that is used in the sim.

OK

Not sure I was trying to keep you.

HARD PASS! Owned it for 3 years and it’s arguably worse than when I bought it. Impossible to map controls to external hardware, RNAV occasionally just skips waypoints, VNAV non existent. And just a couple of weeks ago they announced they are STARTING OVER on the autopilot to build it from the ground up. They are way over their heads and won’t admit they just don’t know how to finish it. From a google AI conversation I had about it: It is incredibly offensive when a developer launches a product as a "paid early access alpha", collects your money, leaves it broken for years, and then pivots by claiming they are "rewriting it from scratch" to dodge accountability for poor initial coding. FlightSim Studio’s May 2026 Roadmap explicitly admitted they are abandoning their current default-patched autopilot layer to do a complete rewrite from scratch. It is a massive blow to everyone who bought the module expecting a functional, high-fidelity plane within a reasonable timeframe. To make matters worse, their community management history includes shutting down their own Discord and banning paying customers who dared to call out the poor state of the aircraft.

Whoa! And they want 60 bucks for THAT??

Yeah I’ve had that issue since I went AMD. Something in Adrenaline stays busy and keeps the cursor (and sometimes the circle icon) flashing for hours. Must be isolated because not everyone has it but Reddit has a lot of posts about it. So I figured I don’t need all the Adrenaline tweaks, I just use the settings in MSFS so I just did a driver-only install. Worth a try.

Hey Doc, I just updated to the latest. But it worked on the older driver. The change came when I went from XBOX Game Pass version to Steam. No crashes since. I did delete Adrenaline and do a driver-only install as that “busy cursor” was driving me nuts. Not sure if everyone experiences that but it was unbearable. I’ve had that issue on every version of Adrenaline since I got the card.

THIS is a problem I have with BATC. I was flying into KYKM and the weather was marginal VFR. I had filed for the ILS 27, but vectored for the visual to 22 (which has no approach.) They cleared me for the visual while I was still in cloud (would never happen IRL.) I requested the ILS 27 and got a terse “runway 22 is the active!” That would never happen as 22 is too short for airliners. With no visual on the runway, I had to rage-quit BATC and vector myself to the ILS for 27. That was frustrating enough to put BATC on the shelf. Now when I do use it, I ask for the appropriate runway, it tells me no, I ignore it and complete the flight with no ATC.

Interesting update: I have a 30 day XBOX Ultimate trial and was using that version. Steam is having a sale and I have 2020 on Steam so prefer it for 2024. I figured why not and bought it. No crashes on the Steam version popping in and out of VR. WOOT! So it must be something unique to XBOX. At any rate, I am a very happy 2024 camper!

If you google there are a LOT of people experiencing it. It happens 100% of the time for me. CTRL-TAB = bye bye MSFS. I tried disabling OpenXR and it made no difference. https://forums.flightsimulator.com/t/ctd-every-time-when-leaving-vr/757679

I think it’s an FS issue. I’ve tried several mice, Bluetooth and wired, and get the “sticky mouse” issue toward the end of flights. Exiting VR and restarting it clears it up (not possible in 2024 since exiting VR crashes the sim)