8 minutes ago, Cpt_Piett said:

I did indeed have both FG and LSFG enabled. With native FG enabled, LS FG FPS is correctly showing in x2, x3 and x4 modes. 

Do you mean with native FG disabled ie.. using LSFG only?

For giggles, I tried both FGs enabled yesterday just to see what happened and it was actually pretty good, even if the FPS were all over the place, in MSFS and AutoFPS, because of the conflicting FG implementation but it actually worked. If I get time, I might see if I can try and tame the FPS readings in such cases, but IMO it is not essential as using the LSFG target FPS still worked and you just got extra fake FPS when MSFS was the active window.

31 minutes ago, Reset XPDR said:

You can use FPS locked with FPS sensitivity and tolerance methods but it needs to be set 5% or so higher than your target FPS so that the logic has the headroom above target FPS to do its thing. This is how you were using AutoFPS before I asked to to raise/remove your FPS lock to test the new TLOD Min Extra functionality ie. you had an FPS lock of 63 and a target of 60 FPS and it all worked good.

Auto TLOD differs from the other two automation methods in that it was initially designed to ignore any target FPS and just work TLOD to an altitude schedule, very similar to how OLOD currently functions. This works well for those that would otherwise need to have a locked FPS that needed to be maintained at all times for either vsync (2D) or motion reprojection (VR) reasons, otherwise screen tearing (2D) or image wobbling (VR) occur. I am in the latter camp with my Quest 3 headset needing a constant 40 FPS to maintain motion reprojection at 80 Hz (MR is effectively FG for VR, but is predictive not reactive like FG).

Thanks a lot for the detailed explanation. 

I did two flights in the Fenix with test10. 

1. Geneva to Torino, Auto TLOD, FPS unlocked

• good performance overall, few stutters
• TLOD on the ground 300 with TLOD Min Extra active
• TLOD increased gradually to TLOD Max Extra (in my case 400+400) once above the terrain threshold
• On descent, TLOD decreased gradually from 800 at AGL 7500ft to 230 on the ground

2. Torino to Geneva, Auto TLOD, FPS locked at 65 with RTSS (target FPS 60)

• good performance overall, few stutters
• TLOD on the ground 300 with TLOD Min Extra active
• TLOD increased gradually to TLOD Max Extra (in my case 400+400) once above the terrain threshold
• On descent, TLOD decreased gradually from 800 at AGL 4900ft to 300 on the ground

I looked through the log file and couldn't see anything strange. Let me know if you want to look through it. 

Settings (lossless scaling was open but not active):

I did a CapFrameX test for the approach into Geneva. Excellent result!

 

Edited September 9, 20241 yr by Cpt_Piett

32 minutes ago, Reset XPDR said:

Do you mean with native FG disabled ie.. using LSFG only?

Yes, sorry for the typo.

Edited September 9, 20241 yr by Cpt_Piett

Can we see some discussion of progress with only use of AutoFPS with RTX 4+ FG without use of LS?  Until perhaps MSFS 2024 I have little to no interest in bringing Steam onto my new system.  Just staying clean of aspects of installations that provide only a single dimension for me.  I have no other use for Steam at this time.

Edited September 10, 20241 yr by fppilot

10 minutes ago, fppilot said:

Can we see some discussion of progress with only use of AutoFPS with RTX 4+ FG without use of LS?  Until perhaps MSFS 2024 I have little to no interest in bringing Steam onto my new system.  Just staying clean of aspects of installations that provide only a single dimension for me.  I have no other use for Steam at this time.

AutoFPS has supported the correct display and use of native FG with RTX 4+ for a long time now, as far back as v0.4.1, so I am not really sure what discussion you are after since it already works. Please advise.

21 minutes ago, Reset XPDR said:

AutoFPS has supported the correct display and use of native FG with RTX 4+ for a long time now, as far back as v0.4.1, so I am not really sure what discussion you are after since it already works. Please advise.

A discussion on how latest advancement of AutoFPS creates improvements in MSFS with Nvidia FG without any use or influence from the separate Lossless Scaling utility. Am a loyal AutoFPS  user for months but have no interest in the Steam-LS performance.  Just NV FG and AutoFPS.

Edited September 10, 20241 yr by fppilot

29 minutes ago, fppilot said:

A discussion on how latest advancement of AutoFPS creates improvements in MSFS with Nvidia FG without any use or influence from the separate Lossless Scaling utility. Am a loyal AutoFPS  user for months but have no interest in the Steam-LS performance.  Just NV FG and AutoFPS.

Auto FPS already works correctly with just NV FP and no LS, like it did before LS showed up.  It still works that way with these latest test versions, even with me adding LS support to AutoFPS. If you choose not to use LS, NV FP will work just like it always has.

eg. Here's a screenshot of the latest AutoFPS test version running right now with MSFS in NV FG and no LS in sight and it still works fine.

24 minutes ago, Reset XPDR said:

Auto FPS already works correctly with just NV FP and no LS, like it did before LS showed up.  It still works that way with these latest test versions, even with me adding LS support to AutoFPS. If you choose not to use LS, NV FP will work just like it always has.

eg. Here's a screenshot of the latest AutoFPS test version running right now with MSFS in NV FG and no LS in sight and it still works fine.

Thank you.  Just seem to see only discussions involving LS.  Want to see both perspectives.

Now I have to ask a stupid question.
What is lfsg? Do you have to buy it and can I use it with my 4080S with FG? What's the point? I fly with locked 60 FPS because my Samsung 43 inch TV supports 60 Hz.

 

34 minutes ago, f.skywalker said:

Now I have to ask a stupid question.
What is lfsg? Do you have to buy it and can I use it with my 4080S with FG? What's the point? I fly with locked 60 FPS because my Samsung 43 inch TV supports 60 Hz.

 

LSFG is an alternative frame generation app to nVidia's own frame generation implementation but it works with all video cards and any DX version. If you are already using native FG with your 4080 and are able to maintain your locked 60 FPS, then no you don't need it.

thank you very much.
in most cases I can maintain the locked frames.
I usually use Auto TLOD with target 56 frames. Works very well. I would recommend another alternative function of Auto FPS

6 hours ago, fppilot said:

Just seem to see only discussions involving LS

Well, to be fair, LS support was only implemented in the latest test version, so only a tiny fraction of the total discussion in this thread is related to LS. 

19 hours ago, Reset XPDR said:

My dream is to be able to get into the workings of MSFS performance metrics and find out what the CPU frame time is, because with this I could work out CPU headroom in all modes which, in concert with GPU headroom I can already work out, would allow the app to change TLOD in a predictive rather than reactive mode and that would improve the app experience significantly. I still haven't worked out how to do this, well not without a significant performance impact on the app in doing so, but I am sure it can be done so I will continue to research it. If anyone knows of a low performance impact way to do this in C# please let me know!

 

 

Have you tried reaching out to @MattNischan ? He might have some insight or point you in the right direction...

Edited September 10, 20241 yr by Flyfaster_MTN002

1 hour ago, Flyfaster_MTN002 said:

Have you tried reaching out to @MattNischan ? He might have some insight or point you in the right direction...

That would be cool, reset.

Maybe we could all help contribute for this and the 2024 sim by providing you with "coffee" funds.

4 hours ago, Flyfaster_MTN002 said:

Have you tried reaching out to @MattNischan ? He might have some insight or point you in the right direction...

No, but if he sees you've tagged him and wants to help me out I'll be very receptive.

3 hours ago, Sonosusto said:

That would be cool, reset.

Maybe we could all help contribute for this and the 2024 sim by providing you with "coffee" funds.

I am happy to do this without contributions as I enjoy the challenge, but thanks for the gesture.