PurdueKev

For anyone who has had stutter problems with SU3, I saw the same when I was using the latest (58X+) Nvidia drivers. Also terrible scenery loading. I had to roll back to earlier drivers and after that everything has been fine in terms of graphics rendering. Not saying that will fix it for everyone, but it is what I had to do. I first went all the way back to old reliable 566.36, which fixed the stuttering. I have carefully progressed to 572.42 (I think, maybe it is 572.24 LOL) so that I could get the more useful DLSS options. It boggles the mind that updating to latest Nvidia drivers consistently makes things worse, but there ya go.

While I agree the new interface has its quirks and confusion and is not necessarily intuitive, once you figure it out it is much more powerful than 2020. You don't have to manually change profiles each time you switch to different aircraft, for example, which was a pain. This concept is a bit more like DCS in that profiles will persist specific to each aircraft, though you have to take some time to understand the interface to make the most of it, I agree. It is also a pain that you have to set the profile for each peripheral separately - though I think that makes it easier to assign a profile that you already have for a new plane, rather than have to go through and set up every control assignment from scratch for each aircraft which is a drag with DCS (in MSFS you just select the profile and all the assignments come with it). Believe me, I hated it at first too and I don't dismiss the frustration at all. But for someone who has a lot of different controllers and likes to fly a variety of aircraft, it is a better approach once you learn it.

The selection is now "Apply to All Airplanes", which you can see in the choices in the video that YMMB shared. If you assign that to a profile, all your aircraft will load that profile by default, until you select a different profile in that aircraft specifically. And if you do then make a different profile for a specific aircraft, it will load it automatically every time you load that aircraft. You can also assign profiles to load for all variants of a specific aircraft type (like for all Bonanzas, or all Barons, or whatever).

Generally speaking, I am seeing very minor improvement in melted buildings, but the PG foliage still looks horrible. This is on a 1 Gbps connection (measured on my system with Ookla) on 6GHz wifi band. I won't say that SU3 did much of anything with this issue.

My experience is that "PG Off" completes in a matter of seconds, but when I try to turn "PG On" the system which will just sit and spin for minutes at a time. So for me, if I turn PG off and perhaps want to turn it on again, I have to restart the sim.

I don't disagree with you. Of course, that would require them to curate the 80,000 procedurally-generated helipads with autogen substitutes, which I am not holding my breath for. We don't need super-duper accurate duplicates of the buildings or anything (unless you are paying for a bespoke scenery package), just something better than buildings and trees that look like you stumbled into Minecraft by mistake.

To be fair, a lot of users do understand how to consider network speed in addition to the quoted service speed from your provider to your router. When you run a speed test from your computer, it typically includes everything in the pipeline including your wifi or LAN. People are still seeing issues even with hard-wired ethernet.

If you fly helicopters, turning PG off is not a fix, because most of the helipads that were added in MSFS 2024 are defined based on the underlying PG scenery. With PG off, you end up with helipads that are either buried under an autogen building, floating in the air 100 or 200 feet above the ground (because the PG building that the helipad is supposed to sit atop is gone), or completely non-existent. IMHO, Asobo needs to improve the prioritization of PG rendering based on distance, so that PG-generated scenery closest to you renders in higher fidelity than PG farther away. That does not appear to be the case right now. We don't need to be able to zoom in with virtual binoculars to see some building 20 miles away being perfectly rendered while flying at 20,000 feet - we just need the stuff closest to us while we are near the ground prioritized. TLOD seems to be a very blunt instrument at the moment. The foliage that happens to be PG (vs the autogen foliage) is particularly ugly and immersion-killing. I am eagerly awaiting SU3 to see if this addressed as some of the beta users are reporting.

I use Low setting, not because I think it is a spot-on replication of real-world turbulence but because I find Medium and High to be far too exaggerated in the sim. High might be technically "realistic," but when you don't have a way to physically feel the sensations of air moving the aircraft around then those higher settings are diffcult to fly through. I would kind of like something in between Low and Medium if I had my druthers. Granted I fly mainly GA and helicopters, so this might be different if you fly airliners. YMMV of course.

This is very good advice. I ultimately ended up buying a collective because I couldn't get the precise collective control with my standard throttle, and changing the springs on my stick to lower resistance ones, now I am hooked on flying helos. My favorite aircraft type to fly in both MSFS and DCS. The coordination you need is frustrating at first, but once it clicks it is really satisfying and a fun way to engage with the scenery. What can throw you is if you switch from an H125 to a Huey or a Bell on the next flight, and don't remember that the anti-torque is reversed and you need to apply rudder in the other direction when you lift off! 🤢😁 If flying a plane is like riding a bicycle, then flying a helicopter is like riding a unicycle during an earthquake LOL.

I am not a real life pilot and have not flown as a pilot in any plane, let alone the 172 (though I would love to get my PPL and do that!). But in all of the online aviation content from real pilots talks about being able to focus on the far end of the runway and gently pull back on the yoke at the flare to bleed off airspeed with power at idle, which allows the aircraft to settle. The tendency of some 2020 aircraft to float when you pull back on the yoke in the flare was not consistent with that at all - you almost had to force the aircraft with forward yoke to get the aircraft back down on the runway, rather than allow the loss of lift and the weight of the aircraft to bring it about. This was true even if you were just above stall speed. You couldn't follow basic flight instruction in the 172 in FS2020 and see the expected behavior. In FS2024 however, I think it is interesting how the flight instructor in the PPL learning missions gives you that same instruction, i.e. once over the threshold you are told to cut power to idle, focus on the far end of the runway, gently pull back on the yoke and allow the rear landing gear to settle onto the ground in a nose-high attitude - and lo and behold it works!

This latter point I agree with. The "floatiness" in the flare in 2020 just does not seem realistic with so many of the aircraft. 2024, at least with the 172, is the first time I feel like there is a sense of mass and inertia in that phase of flight.

I think it is certainly a potential cause, yes. At least there is some compelling circumstantial evidence. I think it was a bad choice for Asobo to port over all that 2020 content so quickly without first ensuring they have been debugged and compatible. I can't imagine that all of them work flawlessly at this early stage.

I think it is under Flight Interfaces in the settings - you can turn off the HUD separately in both cockpit and external views.

Good grief - no one is "deferring" to Sergio, he puts in a lot of time and effort to provide news and information useful to a lot of people. If you don't like what he is writing, you are free to ignore it.

I don't think including all of the folders is necessary; there may be incompatibilities with just one that would that would create the loading problem. But I wasn't going to try to spend the time isolating which one. If the addon is tested to be compatible, then it wouldn't be the cause. But many of them are not yet compatible so it does not surprise me that Asobo porting them over en masse would create a bug.

If you have experienced the infamous hang upon world loading at 97% (so common that it has become an internet meme since MSFS24 was launched), I came across a workaround that has solved the issue for me where I am now able to load and access the sim. Before this, I was getting these random stalls on startup where I would get the message "Loading unusually long: log saved to Report-loading.toml" with the world loading stuck at 97%. I say random, but it was happening probably 4 out of every 5 attempts. The solution that worked for me is posted here: Stuck at 97% The gist of it is this (reposted with h/t to RaginWombat839 on the official MSFS forums) What it seems you are basically doing is adding empty folders into the local "packages" Community folder on the C drive for all of your previously purchased MS2020 Marketplace content. It appears that on initialization the sim is looking for these - that's why they are logged in the "report-loading.toml" file - and if there is some issue with one or more of them (I don't know if that is an incompatibility, or just the absence of the folders, or what... I don't understand how they are handling this content in the cloud) the sim fails this startup check and never recovers. After placing those empty folders in that directory on the C drive, I have been able to start up the sim every time within 2-3 minutes. It is odd that it needs to see the empty folders, but that is indeed what fixed the problem. I suspected that there was something in the loading initializations with cloud-based content that was buggy, and sure enough that seems to be what afflicted me. It also seems like the sim performance is snappier and I haven't had the CTDs on loading a flight that I had before (though that could just be placebo effect or I haven't run the sim long enough yet). I don't know if this works for everyone having loading issues, but it solved my problems to where I can at least experience the sim now. I don't understand why all this MSFS2020 content needed to be rushed over to load from the cloud, since I really don't want anything installed from 2020 that is not proven 100% compatible (and some of the 2020 scenery I don't want anyway, as it may be lower quality), but Asobo in their infinite wisdom haven't given us that option. Hope this helps someone out there. Encourage you to follow the link and upvote the people who found the solution.

The problem is that even with an empty Community folder, per Asobo any FS2020 marketplace content you have purchased is still getting loaded at the server end - in the cloud. So you can have conflicts that you have no control over locally, unless they have fixed that in the last couple days.

The hamsters were getting tired running on those wheels. 😉

And many, many other game/sims (flying like DCS, racing, trains, truck driving, heck even farming) have this exact feature. "Missions" or "skirmish mode" or whatever in addition to career. It is not at all a novel concept, and something pretty much expected in the genre. By the way Sergio, I also mostly fly helis in FS2020 these days (almost exclusively, in fact, not because I dislike fixed-wing but because I love helicopters and it is a great way to engage with the world in the sim), enjoy it a ton (the HPG mission stuff is great) and was looking forward to seeing these mission features natively implemented in FS2024. It is disappointing this is the route they have gone. I agree with pretty much your entire article.

To be honest, that statement on the official forums sounds disingenuous to me. This is a cloud-based application by design - the server environment is inextricably linked to the simulator performance almost certainly. I am optimistic that the simulator will get better - they have no choice, honestly, and FS2020 did eventually become really good even after its launch issues - but continuing to wave away the issues here as "just overwhelming demand" is kind of tone deaf and just makes people more angry.

Made several attempts to start a flight this morning: - Able to avoid the dreaded "Loading unusually long: log saved to Report-loading.toml" as long as I am not recovering from a CTD. Anytime the sim hangs and I have to restart or the sim crashes, I have to restart my computer to not get stuck at that point the next time I try to start the sim. So even basic crash recovery is not implemented. which is a a major red flag. - When I did get the program started, get into flight setup and try to start a flight, the sim freezes 4 out of 5 times before it even loads the aircraft (this is on a default Cessna, nothing in my Community folder, just a plain vanilla install of the Premium Deluxe version). - Tobii is borked anyway, and I won't fly without head tracking (ironic that Asobo made a big deal about Tobii integration in the pre-launch marketng hype, and yet here they screwed up the native implementation even though it works absolutely flawlessly with MSFS 2020). I'm done for now and I will come back in a few weeks I guess. All of this indicates a software program that has barely reached alpha and hasn't gone through any sort of proper regression testing or debugging. I am not going to be an unpaid alpha tester for a AAA software title from a multi-billion-dollar tech conglomerate. Back to MSFS 2020, which works perfectly.

LOL yes - for awhile it was like winning the lottery when you finally connected to AOL after umpteen number of tries!

Inconsistent sound is almost certainly linked to server-side issues. Probably nothing you did, you are just at the mercy of what is going on in the cloud. I think that is true for nearly everyone's issues at the moment - it all depends on what is going on in the server at any given time.

My Community folder is empty, and I am still getting the "97% - Loading unusually long: log saved to Report-loading.toml" endless loop.