34 minutes ago, mikeymike said:

Is  the ghosting of numbers etc apparent with a 4090 and Frame gen on?

if so ,I won’t be upgrading my 3080ti.

 

thanks

mike

 

If you wish to use DLSS (DLAA), the best solution is using a 4K resolution with Preset F enabled (not enabled by default). The reason for this is because Preset F is tuned to handle DLAA and while the amount of pixels rendered doesn't get rid of the underlying issue entirely, it does make it less noticeable. How much is going to vary depending on who you ask. I personally still have to leave it off and use FG with TAA instead but others are happy to use it and don't notice the ghosting/smear as much.

Hopefully later iterations of DLSS gets rid of it entirely.

I leave it off at all times. Sim looks much better without it. The idea is great, execution less so. I'm hopeful we'll all be able to use the technology sometime in the future when the results are satisfactory (visually).

59 minutes ago, wan2fly99 said:

Would this be okay to get for MSFS2020

GeForce RTX 4070 Ti GAMING OC V2 12G Graphics Card, 3x WINDFORCE Fans, 12GB 192-bit GDDR6X,

 

At the moment I have a 1080TI card

If any other suggestions  appreciate hearing from the Techie guys

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.

3 minutes ago, Christopher Low said:

Interesting. I wonder what exactly they mean by "incompatibility" then? I guess I will just have to buy the airport, and go on a drone tour

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

Just now, btacon said:

FWIW. I turned Photogrammetry off two years ago and have not looked back. I could not be happier. 
 

YMMV. TANSTAAFL

-B

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

1 hour ago, Tuskin38 said:

Why?

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.

3 hours ago, Christopher Low said:

Can someone who has the IniBuilds EGGW Luton airport addon installed please try it with PG disabled? The IniBuilds website information for the airport states that it is not compatible with PG switched off, but I am curious to know how incompatible it is. Are there serious elevation issues at the airport with PG disabled?

It works just fine without PG enabled.

1 hour ago, Cpt_Piett said:

Interesting. Been running preset E at 4K, and I might have noticed "smearing" on a few occasions. That was in the 146 though which is a steam gauge aircraft. Is the effect more pronounced on glass cockpits? Horrendous is a pretty strong word...

I haven't noticed any shimmer so far. Going to do a flight in the A300 now, still on Eager Donkey. 

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!

27 minutes ago, mmcmah said:

Preset E was awful for smearing, as you say. I find F to be at the very limit of what I will accept and so I have chosen it because the shimmering and overall image (to me) is more distracting when using TAA. As you have aptly put it, it will come down to personal preference and/or tolerance.

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.

2 hours ago, mmcmah said:

Interesting. Thanks for the response (still driving 😉). I'm honestly not seeing any improvement from Preset E over Preset C and for the DLAA that I'm now using (will test with DLSS to see if there's a difference), I prefer Preset F. Much much sharper and less ghosting.

I'm testing with the Kodiak and looking at the PFD display.

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.

17 minutes ago, jwhak said:

Don't wanna get to excited.  I Got I7-10700K 32Gb Ram 3600mhz & RTX 2070 Super try DX12 now with TAA option.  Gauges look good no blur and haven't noticed that darn flash yet.  Don't wanna get my hope's up. But if the flash is cured in TAA I think I will benefit a lot better of of DX12.

                                                           Happy Landings 2cents

 

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.

38 minutes ago, kfd said:

How do we clean these caches?

 

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.

23 minutes ago, DD_Arthur said:

Very, very good advice.

Eneba and sites like it enable credit card theft, fraud and organised crime.

How does this work: Mr. Criminal has come into possession of someone's stolen credit card or credit card details and wants to turn this theft into cash.

Mr. Criminal will use the stolen credit card to buy software - games...lots of them too. He won't download these games but he will have the codes to download them. He will then sell these codes through sites like Eneba and have his account credited with the proceeds. He will then be able to transfer these funds to a bank account and withdraw it as cash.

Using these sites enables crime.

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.

1 hour ago, Hyper14 said:

@AviationEnthusiast, your tip sounds the best for me, on question tho, if I get the eneba version, will I have all the planes that I downloaded and liveries already installed as before? Or do I have to re download everything over again?

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.

24 minutes ago, Hyper14 said:

So the In game offer is the only one? Isn’t there another option with a smaller price?

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.

22 hours ago, miguel370 said:

same here, are you using a 3d party airplane like fenix or pmdg?

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.

11 hours ago, miguel370 said:

same here, are you using a 3d party airplane like fenix or pmdg?

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.

Still a mess on my end with with a hard macro stutter every 15-20 seconds. I really hope this gets sorted out as the update in its current beta state is unusable.

7 minutes ago, chapstick said:

Can can someone remind me if/how you can get AIG Traffic Controller to always select MSFS at start instead of always having to select it?

Use -MSFS2020 as the command argument.

If you wish to launch AIG Traffic Controller alongside MSFS, simply add it to your exe.xml file (located inside %appdata%\Microsoft Flight Simulator).

Like so:

    <Launch.Addon>
        <Name>AIG Traffic Controller</Name>
        <Disabled>false</Disabled>
        <Path>PATH_TO_AIGTC\AIGTech - Traffic Controller.exe</Path>
        <CommandLine>-MSFS2020</CommandLine>
    </Launch.Addon>

Be sure to edit the path to your AIGTC folder.

48 minutes ago, cappy42 said:

Been studying this thread with interest.  I have a 4070 and a couple of questions:

1) Where is that nvngx_dlss.dll file?  I have marketplace version, and I cannot find that file anywhere.  I have hidden files turned on to view.

2) What is everyone doing about the screen flickering with Frame Generation.  I really can't use FG because it gives me a headache.

Turn off Bloom to eliminate the flickering. It's a bug.

59 minutes ago, Sethos said:

Thank you for posting a comparison, that's certainly a more stark contrast between them in comparison to what I'm seeing. We have an identical system, I'm also running DX12 + FG, so it's odd we're seeing such different results.

The only way I can get any kind of real noticeable blurring is by using the 'wrong' DLAA setting, that I've dubbed "DLAA", looks more akin to what you're seeing.

TAA

Nvidia DLAA

"DLAA"

 

I just tried on my other system (7800X3D and RTX 4070) and it's also ghosting on DLAA (Nvidia). Much prefer DLAA to TAA (ghosting aside) for the same reason you mentioned earlier. Unlucky!

Regular DLAA ("DLAA") is one big aliased mess on my end. Jaggies galore.

Very peculiar.

40 minutes ago, Sethos said:

I have to say, not sure if this is down to framerate (capped at 80FPS here), hardware (difference in 2000, 3000 and 4000-series GPU and their tensor cores doing the work), people conflating DLSS with DLAA or related to something else but I'm absolutely not seeing the blurring people are talking about, neither during a static scene nor movement. TAA and DLAA are identical on that front.

Here's a recording snapshot, of an 80FPS recording, panning back and forth between the screens. Doing a frame by frame on the video and capturing the same frame, any ghosting / trailing / blurring caused by the movement would show up here;

PMDG TAA / PMDG DLAA

Here's what TAA vs DLAA looks like on my end.

As you can tell, the results aren't pretty.

Screenshots were captured on a system running 7800X3D, RTX 4090 (DX12, Frame Generation) and latest version of nvngx_dlss.dll and nvngx_dlssg.dll (3.1.13). I use a modified version of Final Light (reshade) but it was deactivated during this test run. In any case, it made no difference to the ghosting.

Framerate cap set to 162.

19 minutes ago, F737MAX said:

 

 

 

There is a newer Nvidia DLSS dll file that significantly reduces the blurry gauges compared to the .dll that MSFS ships with.

If you're confident to do so, make a copy of the original file called nvngx_dlss.dll in your folder where MSFS.exe is located.

Download version 3.1.13 of the .dll file here:

https://www.techpowerup.com/download/nvidia-dlss-dll/

And place it into your MSFS folder. That's it.

Much improved and you gain the performance benefits of DLSS. YMMV, however, I like what it offers.

Thanks for posting.

For people using Frame Generation, you need to replace nvngx_dlssg.dll as well.

https://www.techpowerup.com/download/nvidia-dlss-3-frame-generation-dll/

Using DLSS by itself (Ultra Performance, Performance, Balanced, Quality) will lead to the aforementioned blurry glassy cockpits. On the other hand, using DLSS with DLAA retains similar sharpness to TAA but results in bad ghosting which is virtually non-existent with TAA.

Very unfortunate as I also prefer DLAA.

4 minutes ago, Sunlightnsk said:

Thank you for the advice. My monitor is 4k, but I would like to play in 2k. 

One more question: would 4070 be still good for using with VR?

I haven't tried it in VR, sorry. Maybe someone else can chime in?