Already a MSFS legend in my opinion !

1 hour ago, RALF9636 said:

So you have the sim limited at 30 FPS by rivatuner and the tool make the FPS fluctuate around 27?

Would you share your VSync settings (sim / NVCP)? Or do you have a GSync monitor?

I get stutters with such a setup.

Rivatuner will set the sim FPS to 30. I set the Mod to 27 so if it drops towards 27 FPS, the mod will start reducing TLOD etc.

 

For NVIDIA CP: Anistropic Filtering is 16X (turned off in the Sim), Low Latency=Ultra, Monitor=Gsync (my second monitor is only 1080p so it doesn't apply) OpenGL Rendering GPU=2080ti, Power=Maximum, Texturing Filtering-anistropic sample=OFF, Texture Filtering-Neg LOD Bias=CLAMP, Threaded Opt=On, Vertical Sync=Fast.

Vsync is turned off in the sim.

I will send you my in-sim settings and LOD settings here in a few minutes

1 hour ago, Reset XPDR said:

It should have worked. Just run the installer again and chose "start with MSFS" again and see if that fixes it. It should put an entry in your MSFS EXE.xml file like so:

    <Launch.Addon>

        <Disabled>False</Disabled>

        <ManualLoad>False</ManualLoad>

        <Name>MSFS2020_AutoFPS</Name>

        <Path>C:\Users\<username>\AppData\Roaming\MSFS2020_AutoFPS\bin\MSFS2020_AutoFPS.exe</Path>

    </Launch.Addon>

 

That's strange, the entry is in there: 

Quote

<Launch.Addon>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Name>MSFS2020_AutoFPS</Name>
    <Path>C:\Users\<username>\AppData\Roaming\MSFS2020_AutoFPS\bin\MSFS2020_AutoFPS.exe</Path>

EDIT: It worked now 🥴

Edited February 21, 20242 yr by Cpt_Piett

2 hours ago, RALF9636 said:

So you have the sim limited at 30 FPS by rivatuner and the tool make the FPS fluctuate around 27?

Would you share your VSync settings (sim / NVCP)? Or do you have a GSync monitor?

I get stutters with such a setup.

In-Sim Settings= 4K Gsync Monitor TAA to 65% (for now), Frame Generation is On (with that dlss mod), Vsync Off, Off screen caching Ultra, Terrain Vector Ultra, Buildings/trees/grass are High.

LOD Mod is set to Min of 70 TLOD. Clouds are Ultra. Texture Res High. AF is off (as stated from previous post). Texture SS is 4x4, the rest are medium range except for contact shadows are Ultra.

14 minutes ago, Sonosusto said:

In-Sim Settings= 4K Gsync Monitor TAA to 65% (for now), Frame Generation is On (with that dlss mod), Vsync Off, Off screen caching Ultra, Terrain Vector Ultra, Buildings/trees/grass are High.

LOD Mod is set to Min of 70 TLOD. Clouds are Ultra. Texture Res High. AF is off (as stated from previous post). Texture SS is 4x4, the rest are medium range except for contact shadows are Ultra.

Thanks. Having a GSync monitor of course explains why you don't see stutters with this setup. Without the GSync function I need a fixed framerate for a stutterfree experience.

Hopefully @Reset XPDR finds a way to work something out with CPU/GPU load detection for these scenarios.

 

@Reset XPDR, here is an idea how you don't need to maintain two separate apps but can merge both apps into one, combining the best of both concepts:

You just need to allow individual TLOD intervalls for several AGL steps. So the app could be customized to work just like the DynamicLOD app, or just like the AutoFPS app, or as a combination of the two.

 

Examples:

 

This would work like the DynamicLOD app (Target FPS would be irrelevant in this setup):

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     100                          100                          30                                  5

1500               150                          150                          30                                  5

5000               200                          200                          30                                  5

 

This would work like the AutoFPS app (AGL steps would be irrelevant in this setup):

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          300                          30                                  5

1500               50                          300                          30                                  5

5000               50                          300                          30                                  5

 

This would work like the AutoFPS app with the TLOD Min on ground option:

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          50                          30                                  5

1500               50                          300                        30                                  5

5000               50                          300                        30                                  5

 

This would be an example of a combination of the best of both concepts:

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          80                          25                                  5

1500               80                          200                        30                                  10

5000               100                        300                        30                                  10

 

Does that make sense to you?

 

1 hour ago, RALF9636 said:

@Reset XPDR, here is an idea how you don't need to maintain two separate apps but can merge both apps into one, combining the best of both concepts:

You just need to allow individual TLOD intervalls for several AGL steps. So the app could be customized to work just like the DynamicLOD app, or just like the AutoFPS app, or as a combination of the two.

 

Examples:

 

This would work like the DynamicLOD app (Target FPS would be irrelevant in this setup):

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     100                          100                          30                                  5

1500               150                          150                          30                                  5

5000               200                          200                          30                                  5

 

This would work like the AutoFPS app (AGL steps would be irrelevant in this setup):

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          300                          30                                  5

1500               50                          300                          30                                  5

5000               50                          300                          30                                  5

 

This would work like the AutoFPS app with the TLOD Min on ground option:

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          50                          30                                  5

1500               50                          300                        30                                  5

5000               50                          300                        30                                  5

 

This would be an example of a combination of the best of both concepts:

AGL              MinLOD                MaxLOD           Target FPS                  FPS Tolerance

0                     50                          80                          25                                  5

1500               80                          200                        30                                  10

5000               100                        300                        30                                  10

 

Does that make sense to you?

 

It sort of makes sense but the issue I have is that it takes an already complex DynamicLOD_ResetEdition to another level and goes against my founding principle for AutoLOD FPS of simplicity, so combining the two takes them somewhere I really don't think they should go. Thanks for the suggestion. I will think about it some more in any case.

Edited February 21, 20242 yr by Reset XPDR

On 2/20/2024 at 8:35 PM, Reset XPDR said:

You set it to your actual FG FPS target. Do note that in order for the automation to work, you have to set a lower FPS target than any FPS lock you have in place, otherwise it will never work TLOD up as won't exceed the FPS tolerance you have set. ie. if you have FPS target of 60 and an FPS tolerance of 5%, with is 3 FPS, TLOD will not increase unless FPS goes above 63 FPS, so if you have an RTSS lock of 60 it will never get there. You should set an FPS target at least the target FPS minus the calculated tolerance lower minus a few more FPS so it can actually get above that tolerace, eg. 55 FPS would be good in this case.

Thanks a lot! I tried today's version for a LIMC (default)-KIAH (FSDT), and I was amazed I could keep 60 FPS during approach and landing while having almost 100 AI planes there.

Since I use Noel's method for locking FPS (and the FG mod), sometimes I need to reduce the frame lock in RTSS to anything between 50 and 60 FPS. Do I lose anything by setting a lower FPS target in AutoFPS, instead of the 55 FPS you suggested?

PS: nice profile picture😉

Edited February 22, 20242 yr by Luis Hernandez

3 minutes ago, Luis Hernandez said:

Since I use Noel's method for locking FPS (and the FG mod), sometimes I need to reduce the frame lock in RTSS to anything between 50 and 60 FPS. Do I lose anything by setting a lower FPS target in AutoFPS, instead of the 55 FPS you suggested?

No, you can set it as low as you want, same principle ie. 50 FPS RTSS means you need to be setting your target FPS by at least the FPS tolerance + a margin for auto TLOD to work within. As a rough rule of thumb, I suggest multiplying your RTSS cap by the FPS tolerance value, doubling it and taking that much off your RTSS cap. eg. 50 RTSS and 5% FPS tolerance gives 2.5 FPS, doubled is 5 FPS so take that of 50 RTSS to give an FPS target of 45 FPS.

7 hours ago, Reset XPDR said:

It sort of makes sense but the issue I have is that it takes an already complex DynamicLOD_ResetEdition to another level and goes against my founding principle for AutoLOD FPS of simplicity, so combining the two takes them somewhere I really don't think they should go. Thanks for the suggestion. I will think about it some more in any case.

The last pages of this thread showed that the sheer existence of two seperate apps can cause confusion, so having it all in one app could eventually simplify things for both you and the users. You could provide some  simple presets for different use cases upfront and hide the rest in the expert options.

Anyway thanks again for your contribution. I hope you can make progress regarding CPU / GPU load detection for FPS cap / VSync scenarios.

 

5 minutes ago, RALF9636 said:

The last pages of this thread showed that the sheer existence of two seperate apps can cause confusion, so having it all in one app could eventually simplify things for both you and the users. You could provide some  simple presets for different use cases upfront and hide the rest in the expert options.

Anyway thanks again for your contribution. I hope you can make progress regarding CPU / GPU load detection for FPS cap / VSync scenarios.

 

I get your point and I will continue to think about all of what you have proposed, even if my initial reaction was less than enthusiastic. 😊

After having tried both apps, I have to admit I am confused which one I should choose to use permanently. Can you please give me  a little guidance here?

50 minutes ago, JWvdH said:

After having tried both apps, I have to admit I am confused which one I should choose to use permanently. Can you please give me  a little guidance here?

I've tested both extensively, and have to say that I prefer the autoLOD version. I find it more intuitive to use, and I think it has enough functionality to give me great FPS in most situations. 

1 minute ago, Cpt_Piett said:

I've tested both extensively, and have to say that I prefer the autoLOD version. I find it more intuitive to use, and I think it has enough functionality to give me great FPS in most situations. 

I agree.

Curious to know what kind of flying you do?

For me, having the flexibility to manage “high/lows” seems to be the better solution to tube liner flight (e.g., 3rd party airports, lots of injected traffic, 3rd party demanding aircraft).

High/lows to me is setting a sliding scale that keeps TLOD to a minimum on the ground and OLOD to a maximum, and the opposite as I climb out. Hence the non-auto app.

Maybe a placebo but I feel like I get a better visual experience on climb and descent, and less shutter on the ground and gate.

Anyone else have a similar experience?