AviationEnthusiast

Ideally, you want to make sure your system has enough available VRAM to handle every scenario in MSFS. Do you fly out of iniBuilds EGLL in the Fenix A320 and if so, do you use 8K textures? Do you use GSX and AI? If the answer is yes to all of the above, I'd consider 16 GB VRAM (RTX 4070 Ti Super) the bare minimum for 1440p and 24 GB VRAM (RTX 4090) for 4K. I have MSFS on two systems myself, and the 1440p build (RTX 4070 with 12 GB VRAM) is frequently put to the test with little to no memory left when flying into big third party airports.

I'm not sure. Could just be a disclaimer to streamline their support.

Look is subjective but yeah, I absolutely agree. It looks so much better.

I'm personally not impressed by the level of photogrammetry in MSFS and the issues it currently presents, namely melted buildings, spikes, worsened LOD ring in the distance and overall degraded picture quality up close compared to AG. Others might need the extra headroom that comes with using autogen instead. It reminds me of the recent discussion on DLSS (DLAA). I watched a guy on youtube demonstrate the latest DLSS release and he specifically pointed out how little ghosting there was and I'm like... there's freaking ghosting all over the place! So I believe it when people say they don't see it. Lucky bunch! In any case, until things improve at least, the rest of us poor souls are forced to disable photogrammetry and use TAA to reach the desired clarity.

It works just fine without PG enabled.

It's more pronounced in glass cockpits. I've been testing with the Fenix A320 and I'd honestly classify the result as horrendous when using Preset E. It's important to note that this is solely related to the smearing of text (e.g. PFD during takeoff or turning the dials). It does a much better job at eliminating shimmer, of course. Preset F has ever so slightly worse shimmer over Preset E but much less smear. It's very close to being the solution I've sought for so long. I wish it didn't bother me so much because DLAA looks so good!

Yeah, there's no perfect solution out there right now but most will probably find Preset F acceptable. To live with TAA, I went ahead and disabled the default post process sharpen setting (UserCfg.opt) and it's now controlled through a custom reshade instead. Much better than default.

Indeed. I've run extensive tests on two different MSFS setups with resolution being the only difference in terms of settings in use. 7800X3D and RTX 4090 was used for 4K whilst 5800X3D and RTX 4070 was used for 1440p. The result is clear. The higher your resolution, the less apparent the issue becomes. As you've already discovered yourself, Preset F offers the least amount of smearing of all available presets when using DLSS (DLAA). Preset E has horrendous smear but slightly less shimmer. That being said, it will come down to personal preference and/or tolerance. I personally can't tolerate the level of smear, even if greatly reduced using Preset F in 4K and a custom reshade profile with text sharpened and so I'm back to DX12 / FG with TAA, shimmering objects and all.

That screen flash is caused by having Bloom enabled. I've yet to try the new update so cannot verify but if it happens again and you wish to stay on DX12, simply turn off Bloom under the Graphics setting.

1. Press the Windows key + R and copy/paste %LocalAppData% and hit enter. 2. Locate and open the NVIDIA folder. 3. Open both DXCache and the GLCache folder and delete its contents. If you wish to remove the cache stored by Windows as well, perform the following steps: 1. Press the Windows key + R and type cleanmgr and hit enter. 2. Select the DirectX-shadercache and press OK and let it finish. Done.

They do indeed. They also enable legit resellers. It's a mixed bag like the internet as a whole, hench make of it what you will.

Make a backup of your Community folder and copy it over to your new install. You will no longer have access to any in-game marketplace purchases made on your old account though.

You could buy a key off another marketplace instead. https://www.eneba.com/xbox-microsoft-flight-simulator-40th-anniversary-premium-deluxe-edition-pc-xbox-series-x-s-xbox-live-key-global Apply discount code AKS8 during checkout and the total price comes in just shy of 60 EUR. Depending on where you live, that's a great discount (MS Store Premium Deluxe version is 133 EUR in my country). That being said, there are a couple of things to keep in mind here: 1. This is a code for the Microsoft Store version, not Steam. 2. It's a fresh code, meaning progress is not shared with your current account. You will have to create a fresh account, apply the code and start over in MSFS. 3. Eneba is a third-party marketplace that enables vendors to sell codes. You're not buying the code from Microsoft. I personally bought MSFS on Steam but I've purchased somewhere around 50+ codes off Eneba and never had any problems. Make of it what you will.

Just gave the beta another shot in its default state with no peripherals connected, empty Community folder and no third party applications loading through exe.xml. Also cleaned the nvidia shader cache for the sake of being thorough. No dice, but interestingly the macro stutter also occurs in the menu without actually loading a flight. I didn't notice at first until I spent a bit of time scrolling through the menus and rotating the globe. 100+ fps for 15 seconds | sim completely locks up for 1 second | repeats ad infinitum Needless to say, I'm quite worried this sim-breaking bug doesn't get fixed in time for the release (stable branch) leaving us with a sim that can no longer be used.

I am indeed but the choice of aircraft or location doesn't seem matter in my case (already tried default aircraft in the middle of nowhere). There's a consistent macro (not micro) stutter that forces the sim to completely lock up for a second, within a time frame of 15-20 seconds, despite the sim otherwise running at 100+ fps. Very odd behavior so I'm back on the stable branch until this bug gets sorted out. For reference, I'm on a 7800X3D and RTX 4090. DX12 and FG enabled. Photogrammetry is disabled. Nvidia driver version makes no difference.