31 minutes ago, AnkH said:

You see, people are different. For me, Fidelity FX at 200 results in an image that is waaaaay oversharpened. And I swear I have nothing like strobing tarmac when using FG. My issue is now, that since I used FG in MSFS, I can hardly get along any FPS below 40-50 anymore, while some years ago, 30FPS were perfectly fine for me. Things change...

Sure we are all different.  Not only do I use FFX at 200 I also use GFE's Detail Filter which for me is far superior to HDR10 which my monitor supports.   For my 3440x display I aim for sharpness on a par with actual vision in the RW, and that's where it is right now everything is crystal sharp w/o any kind of image aberration just like the RW is to my eyes.  If these sharpening algorithms resulted in some kind of shimmer or edge issue I wouldn't use it be alas it just looks absolutely perfect to me.  It was RS at 150 that did the most for this issue and that became the major benefit of the 4090 for me.

I believe you when you say you don't have these and I also am certain if you saw what I see you would react exactly the same way it's way too obvious to simply ignore.  My rate is locked at 45 FPS almost everywhere in the most complex scenario on rate occasion need to set the lock to 40.  In lesser scenarios will set at 50 but could go to 70fps but no point when 45 is good enough.  When I got the 4090 I searched far and wide for explanation as to why the strobing on tarmac and never found an answer and after so many attempts at using FG finally gave up.  

The other big issue is I use a 2nd display and am constantly changing mouse focus to each screen and with each change back to the main screen a substantial screen judder happens, and that also does not happen without FG.  If I couldn't maintain 40-50fps everywhere I'd reconsider enabling FG but fortunately this hardware can.  Just now out of uber performance hungry EHAM I had a grand total of one stutter from a long taxi thru takeoff and nary another.

 

Edited October 25, 20241 yr by Noel

On 10/24/2024 at 5:17 PM, pmplayer said:

Right now doeing that, ( with DX12 ) i am on a 4h ride about 25mins done and to say looking good so far, knock on wood..

cheers 😉

Just to report back, i didn't notice any serious errors during the flight, nor any obvious stutters, so it looks good to use the FBW A320 with DX12 and FG !

These are just my observations, and yes to say, the build was the latest on the day of the flight.

cheers 😉

On 10/25/2024 at 3:17 PM, Noel said:

Sure we are all different.

Absolutely, as is everybody's hardware!

Your settings on my system is an absolute train wreck.  Way over sharpened (for my eyes, glasses, monitor etc), and that detail filter is awful.  But this is the thing - we can take hints and try out other peoples settings, but at some point we have to finish up with what works for us and our hardware.  Your detailed explanation of smoothness in MSFS was an absolute game changer for me.  Since that thread I have had complete smoothness all the time.

If anybody tries other people settings or ideas, but they don't work, it isn't automatically your system at fault.  Keep trying and experimenting  and you will have a eureka moment where it all clicks for you and your hardware.

26 minutes ago, MrBitstFlyer said:

Way over sharpened (for my eyes, glasses, monitor etc), and that detail filter is awful. 

What is "over sharpened" anyway?  With your eyewear do you have at least 20/20 visual acuity?  If so, then everything should be pretty much razor sharp in the RW for you, yes?  

I'm pretty certain if YOU looked at MY screen you would absolutely agree how 'perfect' image quality is!  I think it's more down to the specific hardware & software than subjectivity TBH.  When I look at my display it pretty much looks the same as when I look out my own eyes at the RW.  I've had others look at it and they agree they cannot believe how real/good it looks!  

Cheers, fly on!

2 hours ago, Noel said:

I'm pretty certain if YOU looked at MY screen you would absolutely agree how 'perfect' image quality is!

I have no doubt that would be the case 🙂. On my screen you would probably agree your settings look awful 😁

There are so many variables at play that makes a 'perfect' image right for that individual on that hardware.  No doubt we both see the real world in the same way, but it is what we use to generate the view that can be so different. 🙂

On 10/25/2024 at 4:17 PM, Noel said:

Not only do I use FFX at 200 I also use GFE's Detail Filter 

Can you elaborate this? Is this one of the Alt + F3 filters? Do you use a specific setting there? 

I just switched back to TAA from DLSS, as the image clarity is just way ahead. GFE Detail Filter might allow me to use DLSS again. As I do not have a 4090, but a 4080, VRAM is actually an issue on my end at 4K...

5 hours ago, AnkH said:

I just switched back to TAA from DLSS, as the image clarity is just way ahead.

Have you updated the two dlss DLL files?  I ask because on my 4K display dlss is perfect - super sharp textures out to the horizon (when conditions allow).  I see no difference when using TAA.

 

8 hours ago, AnkH said:

Can you elaborate this? Is this one of the Alt + F3 filters? Do you use a specific setting there? 

Yes it is one of the Alt + F3 filters.  I make minor adjustments to it but its default settings look the best of anything on my LG Ultragear 34" 3440x display including making the VC light enough and everything else as perfect as I can imagine it.  And I use TAA.   For this display it's critical to then use NCP's desktop color controls to set contrast as high as 75, then play with gamma which is dropped down to around 93 and brightness fine tuned to perfect.

Edited October 27, 20241 yr by Noel

6 hours ago, MrBitstFlyer said:

Have you updated the two dlss DLL files?  I ask because on my 4K display dlss is perfect - super sharp textures out to the horizon (when conditions allow).  I see no difference when using TAA.

Yes, both DLSS files updated and configured for ultra quality. Still the difference to TAA is instantly visible. Back in my 1440p days I used DLAA with DLSS, this was fine but I fear for my VRAM doing this with 4K. 

1 hour ago, AnkH said:

Yes, both DLSS files updated and configured for ultra quality. Still the difference to TAA is instantly visible. Back in my 1440p days I used DLAA with DLSS, this was fine but I fear for my VRAM doing this with 4K. 

Just goes to show how different each system can be.  At 4K, DLSS Ultra Quality and FG, the difference is so small it may as well be invisible.  Sharp textures as far as the visibility allows - TAA without FG doesn't give me any sharper textures.

11 hours ago, MrBitstFlyer said:

Just goes to show how different each system can be.  At 4K, DLSS Ultra Quality and FG, the difference is so small it may as well be invisible.  Sharp textures as far as the visibility allows - TAA without FG doesn't give me any sharper textures.

It is not about textures, but the overall clarity of the image. Which is imho just clearer, sharper using native 4K. Not only for MSFS, I personally never agreed to those saying that DLSS image looks even better than native. It might be that some details are better with DLSS, it might be that the image is overall more calm with DLSS, but the clarity stays better with native resolution. In any game I used so far. 

The point is also: thanks to FG and LS, FPS is no issue anymore. But VRAM sadly is... so in my case, I would use DLSS anyway only as an VRAM reducing option. Which doesnt work the higher the quality is 🤣 Even worse, adding LS on top needs another amount of VRAM... why I did not go for the 4090 back then remains a mistery to me.

4 minutes ago, AnkH said:

It is not about textures, but the overall clarity of the image. Which is imho just clearer, sharper using native 4K. Not only for MSFS, I personally never agreed to those saying that DLSS image looks even better than native. It might be that some details are better with DLSS, it might be that the image is overall more calm with DLSS, but the clarity stays better with native resolution. In any game I used so far. 

The point is also: thanks to FG and LS, FPS is no issue anymore. But VRAM sadly is... so in my case, I would use DLSS anyway only as an VRAM reducing option. Which doesnt work the higher the quality is 🤣 Even worse, adding LS on top needs another amount of VRAM... why I did not go for the 4090 back then remains a mistery to me.

I'm curious: what are the symptoms of running low on VRAM when you try using LS plus TAA? Do you start getting stutters or CTDs or something? Or does MSFS dynamically manage the VRAM so that everything works within the available resources and problems are avoided? I would have expected the latter!

58 minutes ago, tfm said:

what are the symptoms of running low on VRAM when you try using LS plus TAA? Do you start getting stutters or CTDs or something? 

The symptoms are pretty "interesting": when I do not use LS, the VRAM is managed pretty well even if scratching on the 16GB limit. Some stutters occur, but nothing critical. However, when using LS and VRAM gets full, the tool reacts strange in a way that it does not maintain the x2 or x3 scaling but something else, resulting in really, really bad stuttering. Even the FPS overlay reflects this: with enough VRAM, it tells me 48/144 (as I set it up) and everything is smooth. The moment the VRAM is full, it changes to something like 15/50 and it stutters like hell. Reason unknown, it only happens if VRAM is full. 

2 hours ago, AnkH said:

It is not about textures, but the overall clarity of the image. Which is imho just clearer, sharper using native 4K. Not only for MSFS, I personally never agreed to those saying that DLSS image looks even better than native. It might be that some details are better with DLSS, it might be that the image is overall more calm with DLSS, but the clarity stays better with native resolution. In any game I used so far. 

The point is also: thanks to FG and LS, FPS is no issue anymore. But VRAM sadly is... so in my case, I would use DLSS anyway only as an VRAM reducing option. Which doesnt work the higher the quality is 🤣 Even worse, adding LS on top needs another amount of VRAM... why I did not go for the 4090 back then remains a mystery to me.

Possibly the extortionate price? 😉

54 minutes ago, AnkH said:

The symptoms are pretty "interesting": when I do not use LS, the VRAM is managed pretty well even if scratching on the 16GB limit. Some stutters occur, but nothing critical. However, when using LS and VRAM gets full, the tool reacts strange in a way that it does not maintain the x2 or x3 scaling but something else, resulting in really, really bad stuttering. Even the FPS overlay reflects this: with enough VRAM, it tells me 48/144 (as I set it up) and everything is smooth. The moment the VRAM is full, it changes to something like 15/50 and it stutters like hell. Reason unknown, it only happens if VRAM is full. 

Thanks! It's frustrating that even in 2024 the different bits of a PC don't seem to know how to play nicely together. I've always wanted MSFS to use 100% of everything on my PC, but it never does ... so maybe I should be careful what I wish for!