Exactly what I am experiencing.
I just completed a flight from EDDF to LIMC and I was astonished by the blurred and washed out look of the ground textures, and by the roundness and lack of details of mountain peaks.
6 Likes
It makes low alt flights pretty sad and breaks immersion.
I also feel this has gotten even worse in the game lately.
And..
Flew over San Diego yesterday and there was 4 container ships piled up in the harbour like a handful of Legoās.
Flat spots where there was supposed to be buildings etc.
A lot more. But everyone with eyes has seen it.
I guess flying around for the scenery aint what this game is about.
ĀÆ_(ć)_/ĀÆ
4 Likes
Iām still not seeing great FPS (CPU limited) with the Fenix (A321) at EGLL (either Ini Premium{dialled down} or Gaya) with AI traffic (BATC). I only see 13-16FPS which I then have to multiply up with lossless scaling to be something more usable. I have tried tweaking lots of graphics settings/options to no avail. It wonāt even hold 20FPS locked. (VSYNC or no VSYNC). I donāt remember it being this bad after SU1. Sadly itās currently unusable for the Fenix for me. At least the landing FPS drop bug has gone, but I need more than 14FPS to land with! FS2020 was never this bad.
With SU3, FS2024 is generally looking better and works fine for me for GA (which sadly I donāt do that much of), although the sluggish responses of most of the UI/menu system is really very annoying, constant latency when navigating menus, especially with say navigating to the marketplace/user library. Why? This should be the smoothest slickest part of the sim.
Not sure what to make of FS2024 right now. Itās definitely looking better, LODS look better with many bugs fixed, but it still has a very sluggish UI & itās impossible to get performance out of the sim to run Fenix at say EGLL with AI traffic (BATC). I will need to go check some other airliners, but itās very time consuming to do this though!
5950/3090/64GB/4K/DLSS Performance
3 Likes
This is just crazy. My PC just rebooted after 3.5 hours on approach for landing 
.
1 Like
Are you sure this was not MS installing some update for Windows? It happens to me sometimes as well, in the midst of work. Should not happen, but it does.
Dont think so. The whole system just crashed in a moment.
PC rebooting is not common for any version of MSFS. That strikes me as lurking hardware or driver issues rearing their head under stress. Check the Windows Event Viewer for any fault reports or errors logged in the moments leading up to the crash, and of course it should go without saying to be sure all your low-level BIOS, hardware drivers and GPU drivers are up to date.
4 Likes
I had the same problem a month ago with the whole pc rebooting after about 10 minutes or less of flying. Tried all the suggested remedies and nothing worked. Finally out of desparation, I ordered and installed a new 1200W power supply to replace the 700W I had been using for a couple years with no problems, and I havenāt had any crashed rebooting since. I still get a ctd from time to time but not the major reboot of the pc. I realize there are a thousand potential reasons for the issues we have, Iām just glad it worked out for me like it did. Somebody else might not be as luckey.
2 Likes
Iāve deleted the rolling cache and scenery indexes so that they get rebuilt and will try another flight in SU3 today.
Latest build is much improved. Still having PG loading issues on approach. FS2020 was a lot more reliable in this regard. Does DL regions help? Still having stutters on landing / takes a bit for smoothness to return once on the ground at arriving airport. BATC (not Asobo problem?) def makes this worse by a lot. Still an issue with no traffic flying airliners. TLOD is still not on par with FS2020
2 Likes
Iāve been observing a behavior that I donāt know if itās related to SU3 or MSFS 2024 in general. For example, I started at KJFK, Fenix āāA319, with no traffic, nothing. FPS around 80-85. I injected traffic with PSXT, at 30% which took me to 58-62 (100 aircraft). Forcing a little more at 100% with a radius of 100NM, it took me to 38-42 FPS (400 aircraft). So far, nothing new. The new thing came when I closed PSXT in the same initial condition and to my surprise I didnāt get anywhere near the initial 80-85 FPS. The conclusion I come to is that, after overloading, it canāt return to the previous status, a kind of āpermanentā degradation until restarting. Has anyone observed this behavior?
1 Like
Isnāt this a memory leak in the add-on? Could it be an idea to post in their support forum?
1 Like
I have amazing performance in VR in beta now except for handcrafted airports. Other aircraft is more visible ir the air thanks to the new lod curve but still they lack detail until you get very close. No landing gear issue still persists. Itās so ugly to see most all aircraft landing without landing gear.
2 Likes
Yes, itās a good idea but before posting I wanted to check if anyone else had this same type of issue
1 Like
Thereās a noticeable issue with LOD handling - specifically, when switching between cockpit and external views, parts of the airport scenery and/or cockpit suddenly pop in or disappear. Itās something I find extremely distracting and honestly unacceptable. Iāve noticed this behavior both with the PMDG 777 and the default Asobo 737 MAX.
4 Likes
I have seen that with the PMDG 777. Interestingly, it does not happen with the iFLY 737 Max or IniBuilds A350.
Wonder if some developers need to make tweaks to accommodate the new LOD curve. Might not be for Asobo to fix. Also, annoying but not sure āmajorā.
2 Likes
I would open task manager and check if PSXT, or any parts of it, are still running in the background after you close it.
100% pure juice. .13 has grown on me and Iāve been able to find the right settings for my hardware with the new curve. Still issues with VRAM in JFK and LAX but those airports will need to be redone to reflect the new curve. Been flawless maybe a stutter here or two, but so much better once itās been tweaked.
9 Likes
I didnāt find anything tangible in Event Viewer (The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffc901acae33d8, 0x0000000000000000, 0xfffff80681e6a56a, 0x0000000000000000).
All drivers are up to date and I have never had reboot issue before. I forgot to mention that I play in VR. My spec: 13900K, 4090, 64GB RAM, PSU is 1200W. What is strange for me is that it happened after 3,5 hours of flight.
Could be something as simple like overheating. Using the components to the max for an extended time. Or an underpowered power supply.
1 Like