Mike T

Okay, so as an "aviation professional," which ATC addon is okay then? Because - Let me remind you. IT'S. A. GAME. A game! For sale in the game section in stores and on gaming sites. You're the equivalent of a SEAL Team 6 operator complaining that Call of Duty is not realistic enough. So by your standards, MSFS 2024 and MSFS 2020 are not okay. PMDG is not okay. BATC is not okay. SI is not okay. FENIX is not okay. Nothing is okay because they're all flawed. Jeeze, I'm admittedly a glass-is-half-empty kind of guy - but you people make me look like a grinning optimist by comparison.

Personally, I blame BATC for the extinction of the dinosaurs, the fall of Rome, and the invention of the term "influencer."

??? GSX doesn't require a profile to work. The only thing a profile does is allows the author to add realistic push procedures and better placement of the pushback truck. Without a profile it works just fine. Not to mention that if the default, "non profile behavior" doesn't suit your needs then you can simply make one yourself and not depend on someone else to do it for you, since all the tools to make one are included for free in GSX.

Use AIG traffic and not FSLTL traffic because the difference in performance is significant. I'm using BATC with 10/10/10 and see little difference in performance vs no traffic at all.

When I'm not stepping on Lego in my bare feet, stubbing my little toe on the bedpost, slamming my fingers in my car door, or losing all of my money gambling in Las Vegas, I use Discord. However, I generally enjoy the aforementioned more than Discord.

Being an airline pilot ceased to have fame and glory in the 1960s. There is little fame and glory in a 4 day trip with 5 legs a day, with a 5:30 am check in each morning. None. Second, yes, you bid your line to maximize income, or to maximize days off. I don't know anyone who says - ooooh, I'll fly KLGA turns all month, so I can challenge myself by flying Stadium Visual approaches or into KDCA to fly River Visual approaches all month. I think the point was, if you look at all the posts, there is little about how much FUN anyone is having, or what a miracle of technology FS 20/24 truely is, warts and all. This is especially true for those of us who started this hobby with just a buch of 8 bit pixelated lines at 2 fps on an 8086 machine. Now I can't believe what I see in front of me, every time I fly. I'm in awe. But it's if no one sees that, it's never good enough, there is no fun in the posts here (anymore - what a place Avsim used to be). I saw a post complaining that there are too many female voices in ATC and everyone knows that's a wrong ratio for female voices in real life! I mean...wow, if Disney World is claimed to be the Happiest Place on Earth, Avsim has to be the most miserable place on earth. So, nothing wrong with wanting the highest fidelity possible in Flight Simulator, but jeeze...stop, look around, look at what we have, and have some FUN!

Moderators - PIN THIS POST. It would make 99% of the posts here absolutely pointless and make your jobs a lot easier (albeit boring!) A game. It's just a game.

Turn off ReBar. I haven't seen a VRAM error since.

I love the scenery. It's an excellent up-to-date rendition and as someone whose company keeps insisting on doing our offsite leadership meetings in Vegas, I know this airport very well. Glideslope captures the look and feel. KLAS is an aging airport that looks the part and Glideslope's rendition is spot on. Performance is also excellent. Best 5 bucks I've spent in a LONG time. Keep em coming...

Ironically, there are no ships in that screenshot either. so...

One other thing that Fenix doesn't do is the Rudder Disc button on my tiller works natively - No configuration required.

Yes WinWing MCDU and FMS work natively.

The issue is not just with SI traffic. BATC traffic crashes it also.

Actually, major airports often require aircraft to take off with a tailwind when the TAF shows the wind shift is only temporary and the tailwind is well within safety margins (below 10 kts). Major airports are unlikely to redirect inbound traffic, and the line of aircraft waiting for takeoff because the wind has changed direction. Doing so causes delays for dozens of flights for no reason. Of course if the wind shift will be for the next few hours or above 10kts they will change runways. With Regional and small airports, it's a different story. With light traffic and no disruptions caused by changing runways there is no reason to take off with a tailwind. So, BATC was probably right to require you take off with a 7kt tailwind. It happens all the time.

After two months of flying in 2024, the biggest issue I've encountered is the VRAM issue, and until the VRAM issue is addressed, 2024 will not be a viable simulator. I just had to scrap a DTW to RSKI run because the VRAM issue brought the sim to a crawl and the IniBuilds A340 instruments stopped responding (other issue?) after wasting an hour of planning and prep. The problem with the VRAM exhaustion issue can rear its head at any time. You go from the never-before-encountered bliss of 100fps at JFK to 1 fps or less (yess LESS than 1 fps) while doing nothing but sitting at the gate. Likewise, you have the best flight of your life with great performance on takeoff and en route, but just as you make your final approach to a complex airport at 80 fps, all of a sudden, you're at 2 fps and attempting to land your stuttering mess. So you've wasted 40 minutes loading and preflighting your aircraft or spent 8 hours flying only to end up not being able to take off or land. Now. If you're a GA pilot you may wonder what Mike T is on about - because I doubt you'll encounter this issue. But tube liner pilots flying into complex airports in complex aircraft, with AI Traffic (you can turn off the AI Traffic and still encounter the issue) see the VRAM warning as soon as they load up the scenery in many cases. Frustratingly, I'm not running everything pegged at Ultra, and I can keep turning down settings per the VRAM warning until I'm running on mid and low, at which point you might as well go back to MSFS 2020 or P3D v6. And yes, I've tried the "auto-config" setting and it can look pretty horrible. I'm running a high-end system with a 4080, and when 2024 is good, it is breathtaking, but when the VRAM issue hits, it ruins everything. The problem then becomes that I'm seeing 5090/4090 users encountering the VRAM issue too, so I'm loath to spend $ 3,000 on a 5090 for nothing. And because I know that my 4080 can run at very high frame rates, at high settings, until the VRAM issue hits there's no way I can justify it. Are any of the beta testers seeing anything better? I DON'T want to go back to 2020, but I never have so much as a peep with it and I know that when I start a flight, I can complete it, which makes it compelling when the new shiny toy has a glaring issue like this one does. Mike T.

You can report that controllers are being overworked here: https://www.natca.org/

The parks around Chernobyl glow at night. So if you're flying over it then it's pretty realistic.

It's running at 5.5Ghz constantly. I'm staring at it in Gigabyte Control Center while the PC is idle (5% usage) - Temp 46c. Max Temp running FS 54c. '24 doesn't demand high CPU usage so its only around 45% most of the time. UNLESS you turn on gaming mode where you'll get 100% usage for less frame rates.

Without knowing your specs, simply having 500 Mbps doesn't mean much because it could well be like driving a Toyota Prius on the Indianapolis 500 track and complaining that your car is not achieving 200 Mph 🚙 I have highly crisp textures out to the distance: 1. Ensure you have Dynamic Settings off - Makes the terrain look terrible to achieve more performance. 2. TLOD / OLOD = 200. Even dropping it down to 150 blurs the terrain noticeably. Droping the settings seem much more drastic than '20 3. Ansiotropic Filtering to 16 if your card can handle it, no lower than 8 3. Nvida - Texture Filtering = Clamp

Officially 1 month of using MSFS with SU2, and it has become the Flight Simulator I've waited my whole life for. It has surpassed MSFS 2020 on every level in terms of performance and scenery (now - it was horrible prior) but I've learned a few lessons along the way that I'll share - and remember YMMV. 1) AMD 9900X3D CPU / MOBO setting. If you have poor performance in MSFS 2024, go into your BIOS and clear out all of your overclocks and tweaks and do a "Load Optimized Defaults. I'm running the GigaByte Aorus (870E chipset). This setting puts in a generic overclock to 5.5 GHz. You want to do manual over / underclocking, then you do so at your own risk. The more I experimented, the worse the performance got. FS 24 is a unicorn, it seems, and a very fragile one at that. So your setting that makes CyberPunk scream, makes FS 24 a stuttering pile of frustration. 2) I'm running 64GB of EXPO1 memory (or XMP 1 - depending on your memory). The only other setting in the BIOS besides Optimized Defaults is selecting this. Memory is running at 6Ghz. Be careful with Memory tweaks! MSFS is very fragile. EXPO1 and XMP1 give no issues. You start messing with it after that and it will crash. Trust me. 3) DO NOT use AMD Gaming Optimization! Gaming mode reduces the cores from 12 (24 vCores) to 6 optimized cores by turning off SMT. This may very well work well for other titles but I've tested MSFS 2024 with Gaming mode (SMT off) vs non Gaming Mode optimizations and by far non-Gaming Mode is better. You also see core usage at 100% with Gaming Mode on vs barely 40% with Gaming Mode off. 4) If you're getting CTD blaming anything 3D or NTDLL, take out the overclock in your video card. I am running a Asus 4080 and had a stable overclock in either Nvidia App or MSI After Burner which works fine in everything else but MSFS 2024. As I said above, MFS 2024 is very fragile. I was having random CTDs and took out the overclock. I've flown pretty much every day for this month and no issues. 5) Verify that your video card firmware (not Nvidia driver) is up to date. There was a bunch of firmware updates required by my card (Asus Crate updates my card) but I didn't know and I was getting bad sound crackling and pausing every 5 - 10 seconds in both '20 and '24. Did a firmware upgrade and they went away. I actually built a whole new computer and still had the issue so I narrowed it down to the video card which was the only part that I kept between rigs. 5) You've probably already figured out that FS 24 is hugely reliant on VRAM. Most times FS 24 recovers once you see the warning, but every now and then it doesn't and the sim becomes a stuttering mess (cough FSLabs A321...cough). If it doesn't recover to normal framerate after 30 secs max, you're gonna have to restart - and a full reboot of your rig to be safe. Which sucks after you sat at the gate for 45 minutes loading pax and setting up your flight deck. 6) I'm running all settings on Ultra or High. 200/200. Raymarched shadows off. Rocks and fauna off (I'm flying heavy iron. If I see rocks or fauna then I'm having a really bad day). I'm sharing this because FOR ME (again YMMV) FS24 has gone from a nightmare to a dream. And some of that nightmare was self inflicted by me. So now I know the rules of FS 24 if you're having issues the above is a good starting point. My only fear is that FS 24 is performing so well and it is indeed so fragile that I'm afraid a driver or update will break it! Either way, I hope this helps anyone who is still having issues with MSFS 24. I've officially deleted 20 this week. Oh MSFS 20 - I hardly knew ye!

It's worse. Much worse. I have the Fenix and it screams in FS 24. The FSL (both CEO and NEO) struggles greatly with VRAM consumption, stuttering, low frames in 24. So if you are struggling already with the Fenix in 24, you'll most likely do worse. YMMV of course.

I suspect it's your BIOs config. Go into your BIOS and reset everything back to "Optimized Defaults" with the only tweak your RAM set to EXPO1 (if your RAM supports it), and try again. I had the same issue after applying all of the AMD Gaming optimizations thinking those would benefit FS but it had the opposite effect. It seems those may work well with other games but MSFS 2024 in its current state hates them. I have the 9900X3D and in NYC with Samscene NY + detailed JFK, LGA, and EWR + BACT set to 10 I'm getting never before levels of FPS / smoothness.

For me it is Asus Crate Utility. For some reason my Video Card wasn't set up correctly in there so it gave me no updates until I fixed it and then I saw updates going back to 11/24. Otherwise go to your card MFG website and search for your card and then firmware / software. This is an often overlooked step because one assumes that all you need is the NVIDA drivers but that is often not true since many cards have other components that need regular updates. At the very least it won't hurt anything and if you're having these stutters / sound pops it is worth a try.

Your issue is not with the drivers, or Asobo, it's with the Video Card specific firmware. I had this exact same problem which made both '20 and '24 unflyable and it happened all of a sudden a few months back and I could not fly MSFS at all. I even built a new system with Windows 11 from scratch and just installed MSFS keeping the same video card (Asus 5080), but had the exact same issue, leading me to believe it must be the video card. I then discovered that there were a bunch of firmware and Asus specific video card updates. After updating, all the stutters went away and performance in '24 is monumentally better than '20. Then with the next NVIDIA driver update the stutters started coming back again. A few days later ASUS released another card update and it went away, performance is stunning. So at least for me this what the fix after months of frustration.

It's back up