4 hours ago, AnkH said:

How did you manage to cap FPS BEFORE nVIDIA frame generation is applied? I never managed to do this, caps always work on frame generated FPS in my case...

Not sure if that's what you're asking but RTSS FPS limiter works on native and FG and besides providing the best frame time variance can be enabled/disabled with a key press, and as well one can change the cap during runtime with key presses.  Front Edge Sync is the option that gets the best FTV in our experience having tested all options available at the time which was in late 2022 when I did testing.

1 hour ago, Noel said:

Not sure if that's what you're asking but RTSS FPS limiter works on native and FG and besides providing the best frame time variance can be enabled/disabled with a key press, and as well one can change the cap during runtime with key presses.  Front Edge Sync is the option that gets the best FTV in our experience having tested all options available at the time which was in late 2022 when I did testing.

+100 for RTSS

On 1/23/2025 at 1:23 PM, Ianrivaldosmith said:

Yeah that a strobing effect, rather than flickering. I've noticed that too at X3, but not so much at X2. 

Yes I suspect strobing is probably a better term - but it's quite subtle, whereas I consider strobing to be completely off then completely on, which it is not.

Do you experience this strobing in both ver. 3.0 and 2.3. I ONLY see it when using ver. 3.0 at any X-factor.

52 minutes ago, somiller said:

Yes I suspect strobing is probably a better term - but it's quite subtle, whereas I consider strobing to be completely off then completely on, which it is not.

Do you experience this strobing in both ver. 3.0 and 2.3. I ONLY see it when using ver. 3.0 at any X-factor.

Only v3.0

What I've referred to as 'strobing' has been the primary deterrent for using NV DLSS FG for me--I simply can't stand it it's way too distracting.  That being said some of my preferred settings make it worse than it needs to be, primarily around sharpening algorithms like TAA.  Having recently added BATC on top of Self Loading Cargo has thrown me over the edge of being able to stay in native mode everywhere in any plane.   Native rendering always offers the best image quality at least w/ my settings which include TAA, PrimaryScaling at 150, SecondaryScaling at 1.5 which helps reduce ghosting in glass cockpit characters, AMD FidelityFX at 200 and even NV's Details filter's sharpening slider.  So now that I am unable to sustain a minimum native rate of 45fps I've had to make peace with FG.  To help cope with strobing while on the ground (tarmac/runway depending on lighting and specific textures used) I have changed to NVSR + DLAA which helps some, and also run wide open while on the ground only when strobing/flickering is happening.  That reduces the aberration by maybe 60% or so.  If it's still too much I will make the 2nd screen the focus and so gets rid of FG on the main display as we know.  I would far rather taxi at 35fps or whatever is sustainable w/o any graphic aberration.   In any case IQ is really very good and I just have to be mindful to use what I can to lose the graphic aberrations and it's already becoming habitual. 

I hope DLSS4 helps that would be fabulous!

On 1/24/2025 at 4:10 PM, Ianrivaldosmith said:

I would say if you have a 4090, and a good CPU, just use the built in frame generation within MSFS. I do.

Ian,

That's the way I'm leaning right now, we'll see what the coming days bring with DLSS4 officially being launched.

I did buy LLS and used it as described in your fine tutorial on a 13-hour flight form EGLL to WSSS, worked exactly as you described (38/114). Of note was the fact that I saw reduced power draw and reduction in ghosting behind AI aircraft. There were some strange thing happening with green taxi lights, both at EGLL and WSSS, though. I'll do some more testing when I have time.

3 hours ago, Noel said:

Not sure if that's what you're asking but RTSS FPS limiter works on native and FG 

Well, if you put 60 as a limit into RTSS and you have FG active, it limits to 60 INCLUDING FG, means the native FPS are at 30. What I am asking is if it is possible to limit the FPS before FG, means if you put a limit of 60 with FG on, the output will be 120. 

This is how it works for LS: I limit the FPS to 47 via RTSS and only then the frame generation by LS is applied resulting in 141 FPS when using 3x...

28 minutes ago, AnkH said:

This is how it works for LS: I limit the FPS to 47 via RTSS and only then the frame generation by LS is applied resulting in 141 FPS when using 3x...

Why does one use LS over stock NV FG?  Is it that 3x improves FG associated graphic aberration?   This was my sense about multi frame gen in RTX50 that you would get so many frames that artifacts would essentially be brute force disguised.

Edited January 25, 20251 yr by Noel

10 minutes ago, Noel said:

Why does one use LS over stock NV FG?

Because I dont want to fiddle around with another setting? Interistingly, using frame generation by nVIDIA and on top 3x LS frame gen results in visually less artefacts compared to 4x LS frame gen alone, eVen if it is technically 6x. And of course, 141 FPS look smoother than 70...

It will be interesting to see RTX50's MFG and see if it obliterates all artifacts.  I might be willing to go there because quite frankly I'm sick of 'fiddling' as it were.  I spent a few months off and on trying to figure out how to fix the audio-video cutouts post 24H2 update!

2 minutes ago, Noel said:

It will be interesting to see RTX50's MFG and see if it obliterates all artifacts.  I might be willing to go there because quite frankly I'm sick of 'fiddling' as it were.  I spent a few months off and on trying to figure out how to fix the audio-video cutouts post 24H2 update!

Unless it's multi frame implementation obliterates them the rest of the DLSS4 results should be similar...  I don't think we are going to be able to get our hands on a 5090 for under $2800-3000 in the "real world"  which is a hefty price not to fiddle if fiddling produces the same results LOL... 

 

11 minutes ago, psolk said:

Unless it's multi frame implementation obliterates them the rest of the DLSS4 results should be similar...  I don't think we are going to be able to get our hands on a 5090 for under $2800-3000 in the "real world"  which is a hefty price not to fiddle if fiddling produces the same results LOL... 

It's all such a moving target and right now even with stock NVSR + DLAA w/ my other settings as they are things are quite good already.  I just have over 4y of none of these issues including the 2nd screen related judder, and it's been hard to part with.  I do enjoy the higher base frame rate and when the remaining artifacts are solved should hopefully be in for another 4y of fabulous graphics and no more fiddling!

If it indeed turns out RTX5090 solves all of this I'll possibly sell the 4090 and get the OOP cash back in tolerable territory.  

When recovered from too much fiddling sounds like I must check out LS!

Edited January 25, 20251 yr by Noel

Agree with everything you said @Noel and if the real world 5090 feedback is that good despite the price I will probably be right there with you putting the 4090 on the market 😂 

I was in part trying to talk myself out of one 😭

LS is really an amazing tool.  Understandably it's not for everyone but for the price it is hands down one of the greatest tools out there.  Not just for FS either.  Works with any sim or game really.  

Frame generation options:

• LSFG

Scaling options:

• LS1
• AMD FidelityFX Super Resolution
• NVIDIA Image Scaling
• Integer Scaling
• Nearest Neighbor
• xBR
• Anime4K
• Sharp Bilinear
• Bicubic CAS

The latest feature allows you to use Lossless Scaling to generate additional frames in games that do not have such support, including emulators.

Lossless Scaling is also useful for upscaling modern games if you cannot run them at native screen resolution (GPU limited) and want to get rid of blur due to bilinear scaling of the GPU driver, as well as for upscaling older and pixel-art games which do not support modern screen resolutions or full screen mode.

For modern games it is best to use LS1 or AMD FSR. For scaling pixel-art games, use Integer Scaling or xBR. Anime4K is best suited for cartoons or anime.

$6.99 seems like I'm stealing something with this tool LOL  

 

Edited January 25, 20251 yr by psolk

1 hour ago, psolk said:

I was in part trying to talk myself out of one 😭

Yep!  Well, again, trouble-free artifact-free could be worth it for me unless LS can match or beat that by for example solving the 2nd screen related judder and eliminating all artifact.  I read NV MFG does 8x frames which *should* solve artifacts I would think, with frame rate of 240fps for example, and with therefore no need for DSLL4 as one can perhaps stick with TAA in MSFS.  I don't have a need for NV FG to work in anything beyond MSFS 2020/24.

13 hours ago, Noel said:

I read NV MFG does 8x frames which *should* solve artifacts I would think,

I was under the assumption the more frames generated, the higher the artefacts. Seems to check out that way in LLS too. 

Edited January 26, 20251 yr by Ianrivaldosmith