WestAir

Shady 80 is the nickname we gave the MD-80 at the airline I was at. It was a real shady airplane that never really wanted to fly. I miss it. 😂

No need to reinvent the wheel. As long as the Fenix devs fix the issues with ProSim (fonts, some logic) so that it matches the actual bus, all this means is they saved years of redundant coding.

The Shady 80 is probably one of the best "modern" airliners for tubeliner sim pilots. It takes more babysitting than a 737 but also allows you moments of rest. I feel for the pilots nowadays. The A350 has taxi to landing automation, and even performs step climbs and tcas resolutions on its own. If they get 1 pilot approval by their 2025 deadline, like they want, it might become the most "realistic" flight sim tubeliner to simulate, but also the most boring.

My word. Look at how the labels are actually etched into the flesh of the panel; or how the serial numbers are etched on the top of certain modules. Look how the individual screws are 3d modeled, the switches have fastening holes modeled in, and we can even see the individual strands of covering inside the flap lever housing. Aamir, I dunno what you're paying your 3d Modeler or your texture guy, but it's not enough.

I don't think it's a mod. Ever since release, my AI Copilot has been hit or miss with the radios. Usually it will work at the start, but give up after an hour or so of cruise and not do any further radio changes. I can usually cycle it on/off to get it to work again, with varying success. Honestly I'm just waiting for a payware ATC program to appear and save us from ASOBO ATC. My co-pilot never stopped using radio calls on RC4 or those other programs that had copilot take-overs.

I finally got the FBW A32NX not to crash, and the autoflight to work, and then I got hit with +54C at 38000 feet. I figured "That's fine, I'll choose few clouds preset" but the WEATHER TAB IS GRAYED OUT. WHAT!? Why? Why would Asobo ever program the sim to be capable of locking the user out of the time/date/weather tab!? In what World does a programmer even consider this? I have never pressed the "shut down" button on my PC with so much anger before. What a waste of 4 hours. aershtdjfkgh

Completely understandable Andy. It's pretty infuriating to voice your issues and be met with indifference, or worse, doubt. ASOBO devs said they are aware of the countless CTD's and are working to fix them all. While I'm skeptical that they will, I guess we can only hope that they pull through somehow.

Looks like you purchased the 2075 post-apocalypse edition of the airport. Common mistake. 🤣

So I looked at their github, and it's actually a listed problem: Turns out it's a problem we all have, you just happened not to use the HDG knob during your initial flight and I did. At least I now know it won't happen again.

Anyone have the github patch logs for the FBW? I did a flight with it yesterday and the MCP was pretty useless; Couldn't activate HDG Select. When it entered approach phase it started to spin in circles. Coupled with some really bad SU5 scenery loading (Looked like the scenery from FL340 was a 240px youtube video) and Cessna's lining the airliner gates on arrival, it really wasn't an enjoyable flight at all. Hoping maybe they fixed the autoflight problems with this patch?

That's unfortunate. I hope ASOBO / Microsoft see this as a cautionary tale, and decide that the circumstances leading up to this can't ever happen again.

I'm curious about something. Do you mind going to the graphics settings, selecting "ultra" or "high" or some other remedial setting, saving, then trying to FLY with a default airplane? I had the same issue but once I refreshed the graphics settings by selecting a profile it worked.

Simmers in Australia are having a hard time with this theory.

Go into windows settings and turn on HDR, I'm told, and then there will be an option in MSFS to enable HDR as well. Source:

I've been watching this debate from the sidelines, and I just want to say that - and this is complete conjecture - but I'm willing to bet most MSFS players never made any leap at all; They're new simmers entirely, and most are on XBOX where the competition doesn't exist at all.

Hat switch on a CH yoke, PC version.

Yeah I did that, which stopped the blue glow and I also got rid of the big in your face UI text popups. The only issue left between SU4 and SU5 for me in this regard is that panning comes to a halt as the mouse passes over a switch or button.

Slightly off topic but does anyone know what setting removes the feature where the panning slows down if the mouse passes over a select-able switch or button? It makes panning around the cockpit jagged and unintuitive, but I dunno how to turn it off so the rate of panning stays constant no matter what my mouse is doing.

I assure you, sir, nobody hates on at AVSIM'ers more than AVSIM'ers. 🤣

Absolutely. The guys at ASOBO know about your problem. I bet they also know about 50 problems affecting the XBOX X/S and the CTD problem blowing up their forums. They also have other developments going concurrently (Weather, SU6, next Azure update, ATC, etc etc). It's a lot. It used to be we'd get service packs every year or so to fix these issues, and in the interim people in the community would piecemeal their own fixes. Remember filefront? Those were the days. In this new age we get to actually talk to the dev team and get fixes in weeks. Hopefully that's all it takes, and I hope you keep up the pressure to make sure your issues (our issues) stay near the top of their long list of things to work on.

A lot of us in AVSIM can see ASOBO is doing a fantastic job.* Obviously they have to show results to Microsoft on the XBOX platform - and they've actually made a game that works on both systems. For comparison, getting Minecraft or Call of Duty: Warzone to do the same took years. Asobo did it in one. It also runs with a lot fewer bugs than a lot of other recent games. (Looking at you: CyberPunk 2077). And they're very open and do bug fixes same day with third party developers. This is unheard of in the gaming industry and I kind of feel like some of us are overlooking how good a dev team we have here.

I figured it out after a while of troubleshooting. I think my user.cfg settings carried over to Update 5; Once i reset my graphical settings to ULTRA from CUSTOM, I stopped crashing with everything but the FBW A320. Once I downloaded the most recent patch for the FBW A320, it too stopped crashing. (They must have discovered a show-stopper after their initial SU5 build). The sim runs great! I have a few pet peeves with this version (The UI bar staying visible, the slow panning if the mouse passes over a clickable, the Traffic CTD bug), but otherwise it's a good update.

I can't make SU5 work yet. I've CTD'd 8 times all with different variables. (Traffic/MP off, tried the FBW x3, then the PMDG, then the default Beechcraft x3, then the 1st training flight | In FlyTampa Vegas, then KDCA, then the middle of nowhere in the South Atlantic a few times.) Sometimes it crashes the moment I select "fly now", others while initially loading in the cockpit. Should note prior to this patch I never encountered CTD's so it must be one of the new features or settings or something. I'll sit down and figure out what settings is doing it when I have more time.

Haha! No better therapy than the KDCA arrival in the NGXu with the Fenix A320 waiting at the gate for your turnaround! 😆 Here's to hoping it happens soon.

Sir you don't understand: If I didn't complain, I'd never say anything!