MrFuzzy

Also: "I apologize for calling you whiners, I had a bad day. Let me just call you impatient, cynical, arrogant, unreasonable and childish" LOL 😄

No issues with more content of course, provided that it doesn't break things (unlike it has happened until now) and the priority is given to fix the existing bugs and issues. Sorry if not everybody is jumping for joy at the release of another payware aircraft when the autopilot / approach bugs of the default ones are not fixed after more than one year.

I want a Forza Flight 2020, I wanna mow down trees with the propeller of my Cessna 🙂

No, that would not make sense. If you buy and download the game now you will have the latest build from the beginning, without the Japan content in the marketplace. All owned content must be downloadable at any time. Maybe you need a clean reinstall to fix it. Certainly another annoying bug...

Yeah... more likely they have a way to prevent it that works for a few seconds or is inapplicable to actual real time gaming.

Make sure to follow the "Clean install steps" down on this page: https://docs.flybywiresim.com/fbw-a32nx/installation/

Among those 3, the 11900. If you also have to change the MB to upgrade, Ryzen 5900X. DX12 may make a difference or not, I doubt the sim will ever be able to use more than 16 threads efficiently anyway.

Have you tried MAX_TEXTURE_REQUEST_DISTANCE=320000.000000? Credit to Rob Ainscough

4.8 should be its default frequency when all cores are used. I have no overclock and mine works at 4.8 GHz, boosting up to 5.2 when only one core is used. The voltage is OK too, probably the Noctua is not as good as the reviews say... I am always sceptic when I see those comparisons with liquid AIOs.

I bet they have no idea how to fix it. Also a previous ticket I opened for the hideous cloud reflections when the wind is low many months ago has been marked as "solved" but they did absolutely nothing about it. And the official forum thread has only 39 votes... https://forums.flightsimulator.com/t/cloud-reflections-on-water-look-absolute-aweful-like-some-128x128-pixel-texuture/389348/25

Please vote this thread: https://forums.flightsimulator.com/t/mountains-coastlines-constantly-morphing-since-the-usa-uk-nordics-world-updates/339453

Neither temp is normal... my 10850K is always between 60 and 62 °C in MSFS. I never tried Cinebench but 99 °C don't sound right at all. Probably the Noctua isn't enough for it, or the MB is applying a too high voltage to it to keep it stable. This is unnecessary most of the times, see here:

Even with 360 it should still be faster than SU4 because the glass cockpit are no longer on the main thread.

Not everything actually... for example are the LAN and volume control still on the same systray button?? Every time I had to change the sound device I needed one more click than Win 10. Also, drag and drop on apps on the taskbar didn't work and that was a PITA when I had to attach files to Outlook e-mails or simply move files. I rolled back after a few days and I won't migrate to 11 until these issues are resolved.

If you (like me) don't have a G-Sync certified / Ultimate monitor, the best thing to do is switch to 60 Hz refresh rate before launching the sim. If you use GSync at higher refresh rates, brightness will flicker when you have microstuttering. Do not limit fps from nVidia control panel or external tools, just set VSync on and 60 fps limit in MSFS settings. Also make sure that GSync is enabled in nVidia CP.

@bobcat999 The Eye starts rotating when I approach but the buildings look OK to me... try Objects LOD 9.0, it doesn't cost many fps.

I will try now and let you know.

What's really heavy on the CPU is terrain LOD. After many tests I think I found the sweet spot for my system: terrain LOD 3 and objects LOD 9. This limits the pop-in and morphing a lot, while keeping good framerates and preventing stuttering when I pan the view. I play with VSync and GSync on, limited at 60 fps. I removed the limits for performance measurement purposes only.

That's because instead of loading assets for the entire visible area of a circle, after SU5 the sim loads them only for your current FOV. If you notice, regardless of the LOD settings (= the radius of the circle), the RAM and VRAM usage doesn't go past 6 GB, while before SU5 it was common to see 16 GB of RAM used even with LOD 100 on PG areas! Therefore you can have very good performance even with insane LOD settings as long as you go ahead, but when you rotate the view the sim has to load many assets from the storage unit, or even worse from the Internet, hence the stutters. The 24 August fix should allow us to decide how much off-screen scenery will be loaded into RAM (or VRAM, it's not clear), and this should eliminate assets pop-in while still maintaining a better framerate than SU4 (because the glass cockpit gauges are not on the main thread anymore, and that alone was a big improvement). Let's wait and see.

Thanks a lot guys, I'm gonna buy it!

I am tempted to buy London City Pack, can anyone confirm if the pop-in is better than the default scenery?

And what is that supposed to mean? The masses are happy with the Maneskin but we used to have Deep Purple, Led Zeppelin and Queen. The masses are happy with McDonald. The masses were happy with Saddam Hussein and Gaddafi. I really don't care... in the development of the sim I see degradation of water, draw distance, illumination, objects popping in at less than one mile, and I would like to have separate branches of development for PC and console because FS has always been traditionally a PC game. Now it looks like a bad console port.

Yes, nobody is saying that MSFS svcks and honestly if it came out with graphics just better than an ORBXed P3D, nobody would complain. What's disappointing in MSFS is that we used to have certain standards at the beginning*, standards that are being lowered more and more after every patch, with SU5 that feels like a coupe de grace. The next-gen flight simulator, born on PC after 15 years of silence and defined by many "the new Crysis" takes now 4 to 6 GB of RAM - and it shows. People have invested in RTX 3000 cards and 64 GB of RAM just to find themselves, after one year, with a game tailored for XBox Series S. *By standards I mean: subtle objects pop-in in the distance, mountains not morphing, coastlines without water creeping up and morphing, stunning clouds and global illumination, realistic water... it was not perfect and maybe all the imperfections we are talking about have always been present, but not to this extent. We didn't deserve this, honestly... just because after one year virtually every PC gamer into flight simulation have bought it already and now they need to sell it to console gamers. Personally I am not even hardcore: I have spent about 800 hours in Fallout 76 and everybody knows how it is still (after 3 years) affected by bugs, glitches and old-gen graphics. But it's FUN and most importantly, it got better and less bugged after every patch.

OK but in this case it's not a fair performance comparison. Let's say that with SU5, in order to have the same graphical fidelity as before, you need to fiddle with Usercfg.opt, which is something that maybe only 10% of the people do... those who read the forums and have sufficient PC proficiency. Because if the new LOD 100 is 200, the new 200 is... 400? Moreover with the pop-in issue that cannot be removed because it's only marginally related to the LOD sliders. And when you get approximately to the same graphical fidelity as SU4 by modifying the config files, most probably you end up with the same performance and stuttering you had before. After all, reducing RAM usage by 50-60% and VRAM usage by 30-50% overnight CANNOT be without consequences. I know it's an endless argument and it's not worth spending more time and posts on it... just for Asobo: there must be something else to it, because the pop-in and morphing also depend on the specific location: compare London to Tokyo for example. The first is a pop-in and morphing mess at any LOD and settings, the latter a masterpiece of autogen and photogrammetry.

I don't think LOD has anything to do with that, and the two builds were compared with the same settings.