20 minutes ago, Zimmerbz said:

Are there recommended settings or a guide that describes how to set up Auto FPS?  I have mine working but it always sets the TLOD to 30 in the sim and It makes it look awful 

What type of flying do you do?

What are your PC Specs?

29 minutes ago, Zimmerbz said:

Are there recommended settings or a guide that describes how to set up Auto FPS?  I have mine working but it always sets the TLOD to 30 in the sim and It makes it look awful 

Set FPS to 30.

Use expert mode.

Use the drop down menu to choose Auto TLOD.

Try the default settings. Let me know how that works for you.

21 minutes ago, abennett said:

What type of flying do you do?

What are your PC Specs?

Specs are and I only do jetliner flying

Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU   64GB G.Skill Performance DDR4 SDRAM 3600MHz       Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System   2TB Western Digital, NVMe M.2 Solid State Drive

11 minutes ago, CFIJose said:

Set FPS to 30.

Use expert mode.

Use the drop down menu to choose Auto TLOD.

Try the default settings. Let me know how that works for you.

 

What are the defaults?  I don't see a way to go back to default and I am pretty sure I changed a few things. 

1 minute ago, Zimmerbz said:

Specs are and I only do jetliner flying

Intel Core i7 12700K (5.0GHz Max Boost Clock) 12-Core CPU   64GB G.Skill Performance DDR4 SDRAM 3600MHz       Graphics Processor:12GB Nvidia GeForce RTX 3080 Ti, GDDR6x System   2TB Western Digital, NVMe M.2 Solid State Drive

 

What are the defaults?  I don't see a way to go back to default and I am pretty sure I changed a few things. 

Run the installer and uninstall.

Then re-install AutoFPS.

Then try the above.

4 hours ago, CFIJose said:

Run the installer and uninstall.

Then re-install AutoFPS.

Then try the above.

@ZimmerbzThat'll work but it is easier to run the installer once and and select the clean install option.

5 hours ago, Zimmerbz said:

Are there recommended settings or a guide that describes how to set up Auto FPS?  I have mine working but it always sets the TLOD to 30 in the sim and It makes it look awful 

Per the readme FAQ:

• Start the app before you load your flight,
• Leave Use Expert Settings unchecked,
• Pick what type of flight you are doing via the radio buttons ie. either VFR (GA aircraft) or IFR (airliners),
• If using an FPS cap, enter that as your target FPS otherwise enter a target FPS your system can usually easily achieve or click on auto target FPS for the app to pick it for you,
• Click back on MSFS and wait until any FPS settle or TLOD seek events have finished (60 seconds max), then
• Go fly!

Have your relevant MSFS settings (TLOD, OLOD and Clouds) set as you normally would without this app then try the above with auto target FPS set and tell me if your experience improves, noting that TLOD is intentionally meant to be low on the ground compared to your MSFS default TLOD setting.

Message me your log file, located in %appdata%\MSFS_AutoFPS\log, if you are still getting a poor experience and I'll interpret it for you.

 

7 hours ago, Maddormo said:

Like I promised, I was testing those two values (92 and 95%) last night, and for a highly detailed scenario, I found that with my 8GB of VRAM, the results were way better. At no point did I see the app trigger the alarm by dropping the TLOD to 20 due to VRAM overload. I noticed it was fighting with the TLOD values while trying to maintain the frames, but I didn’t see a massive drop in detail like I did with the previous settings. But, to be fair, we’re talking about a pretty specific situation, and maybe most people won’t need these kinds of tweaks.

But I encourage anyone visiting very complex airports, using study-level planes, or flying in highly detailed scenarios (like photogrammetry or digitized national parks) to check if the app often drops to TLOD20. If that’s the case, they should try these other thresholds. This way, everything will be more controlled without having to take drastic measures by dropping all the way down to 20.

If you want to give it a shot, I recommend Packwood (55s). Head north, climb to 5000', and do a few 360s. You'll see the VRAM go up like a rocket.

Thanks for the feedback on this. If you didn't see the reduce action take place then I'd say that it was the 92% hold setting specifically that did the trick. The reason I kept this value so high at 96% is based on my experience testing it on my own system, which to be fair is relatively swimming in VRAM compared to yours, and those of other testers who mostly had 16GB+ GPUs. I did have one tester with just 4GB VRAM running 20204 and didn't get a reported issue from them, which is interesting.

Nonetheless, it turns out I do have a gaming laptop that I don't actually use much for gaming, but it has MSFS 2024 on it and it has a 3060 with 6GB of VRAM so I will have a play with it and see if I can get VRAM to overflow, noting I will be somewhat limited as I don't have any MSFS 2024 payware scenery to try it with, unless you meant try Packwood (55S) with default scenery?

The boss has spoken.

I just noticed that the thread was merged. Cool.

5 minutes ago, CFIJose said:

The boss has spoken.

I just noticed that the thread was merged. Cool.

It's all good. You were on the right track with your help, which I appreciate you doing.

Edited January 21, 20251 yr by Reset XPDR

47 minutes ago, Reset XPDR said:

unless you meant try Packwood (55S) with default scenery?

If you want test it, affirm, default scenery is more than enough. From Packwood, flying north, following the valley, and especially reaching 5000ft, VRAM will fill up due to the ultra-detailed mesh (VEXCEL) of Mount Rainier (at least using 1440p, like in my case).

Edited January 21, 20251 yr by Maddormo

30 minutes ago, Maddormo said:

If you want test it, affirm, default scenery is more than enough. From Packwood, flying north, following the valley, and especially reaching 5000ft, VRAM will fill up due to the ultra-detailed mesh (VEXCEL) of Mount Rainier (at least using 1440p, like in my case).

Will try it right now. Any aircraft in particular?

2 hours ago, Maddormo said:

If you want test it, affirm, default scenery is more than enough. From Packwood, flying north, following the valley, and especially reaching 5000ft, VRAM will fill up due to the ultra-detailed mesh (VEXCEL) of Mount Rainier (at least using 1440p, like in my case).

I just tried your suggested flight twice and I found it difficult to get the settings high enough to get VRAM use up high without killing FPS specifically because of the high settings.

Here are the two flight tracks I made:

On the first run VRAM use started at 81% and never got above 85%. On the second run, the one that curves south at Mt Rainier and shown below, it started at a more promising 84% but never got above 90%.

Quote

2025-01-22 09:14:55.682 [INF] [ LODController:UpdateVariables    ] FPS:28 Pri:TLOD+ 75 Night:False TLOD:100 TLODRng:100 OLOD:50 AGL:111 FPM:7317 Clouds:Medium GPU:93% VRAM:84% Lim:False
2025-01-22 09:15:05.845 [INF] [ LODController:UpdateVariables    ] FPS:21 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:2851 FPM:8346 Clouds:Medium GPU:96% VRAM:87% Lim:False
2025-01-22 09:15:16.006 [INF] [ LODController:UpdateVariables    ] FPS:21 Pri:FPS Night:False TLOD:71 TLODRng:58-100 OLOD:45 AGL:3369 FPM:774 Clouds:Medium GPU:98% VRAM:87% Lim:False
2025-01-22 09:15:26.182 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:45 AGL:3587 FPM:1576 Clouds:Medium GPU:99% VRAM:85% Lim:False
2025-01-22 09:15:36.377 [INF] [ LODController:UpdateVariables    ] FPS:21 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:45 AGL:3179 FPM:-2213 Clouds:Medium GPU:96% VRAM:86% Lim:False
2025-01-22 09:15:46.569 [INF] [ LODController:UpdateVariables    ] FPS:19 Pri:FPS+ 10 Night:False TLOD:92 TLODRng:35-100 OLOD:45 AGL:2557 FPM:-1074 Clouds:Medium GPU:98% VRAM:88% Lim:False
2025-01-22 09:15:56.750 [INF] [ LODController:UpdateVariables    ] FPS:20 Pri:FPS Night:False TLOD:76 TLODRng:25-100 OLOD:45 AGL:2412 FPM:-95 Clouds:Medium GPU:97% VRAM:87% Lim:False
2025-01-22 09:16:06.932 [INF] [ LODController:UpdateVariables    ] FPS:21 Pri:FPS+ 56 Night:False TLOD:94 TLODRng:81-100 OLOD:45 AGL:2175 FPM:-87 Clouds:Medium GPU:98% VRAM:87% Lim:False
2025-01-22 09:16:17.106 [INF] [ LODController:UpdateVariables    ] FPS:20 Pri:FPS+ 60 Night:False TLOD:100 TLODRng:85-100 OLOD:45 AGL:1973 FPM:-152 Clouds:Medium GPU:95% VRAM:87% Lim:False
2025-01-22 09:16:27.275 [INF] [ LODController:UpdateVariables    ] FPS:25 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1794 FPM:312 Clouds:Medium GPU:99% VRAM:87% Lim:False
2025-01-22 09:16:37.461 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1259 FPM:511 Clouds:Medium GPU:98% VRAM:89% Lim:False
2025-01-22 09:16:44.591 [INF] [ LODController:RunTick            ] TLOD Min + auto-reduced to 50
2025-01-22 09:17:13.082 [INF] [ LODController:UpdateVariables    ] FPS:20 Pri:FPS+ 40 Night:False TLOD:78 TLODRng:65-100 OLOD:50 AGL:2064 FPM:234 Clouds:Medium GPU:99% VRAM:87% Lim:False
2025-01-22 09:17:23.268 [INF] [ LODController:UpdateVariables    ] FPS:19 Pri:FPS Night:False TLOD:66 TLODRng:25-100 OLOD:50 AGL:2321 FPM:2094 Clouds:Medium GPU:98% VRAM:85% Lim:False
2025-01-22 09:17:33.450 [INF] [ LODController:UpdateVariables    ] FPS:21 Pri:FPS Night:False TLOD:46 TLODRng:25-100 OLOD:50 AGL:1514 FPM:2241 Clouds:Medium GPU:97% VRAM:84% Lim:False
2025-01-22 09:17:43.616 [INF] [ LODController:UpdateVariables    ] FPS:22 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1529 FPM:3218 Clouds:Medium GPU:95% VRAM:86% Lim:False
2025-01-22 09:17:53.789 [INF] [ LODController:UpdateVariables    ] FPS:24 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1463 FPM:2041 Clouds:Medium GPU:98% VRAM:87% Lim:False
2025-01-22 09:18:03.986 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:2814 FPM:1228 Clouds:Medium GPU:97% VRAM:85% Lim:False
2025-01-22 09:18:14.230 [INF] [ LODController:UpdateVariables    ] FPS:25 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:2819 FPM:-6719 Clouds:Medium GPU:98% VRAM:85% Lim:False
2025-01-22 09:18:24.405 [INF] [ LODController:UpdateVariables    ] FPS:20 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1897 FPM:308 Clouds:Medium GPU:99% VRAM:90% Lim:False
2025-01-22 09:18:34.584 [INF] [ LODController:UpdateVariables    ] FPS:20 Pri:FPS+ 10 Night:False TLOD:80 TLODRng:35-100 OLOD:50 AGL:1616 FPM:718 Clouds:Medium GPU:97% VRAM:90% Lim:False
2025-01-22 09:18:44.767 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:TLOD+ 10 Night:False TLOD:35 TLODRng:35 OLOD:50 AGL:1165 FPM:3955 Clouds:Medium GPU:98% VRAM:89% Lim:False
2025-01-22 09:18:54.953 [INF] [ LODController:UpdateVariables    ] FPS:22 Pri:TLOD+ 10 Night:False TLOD:35 TLODRng:35 OLOD:50 AGL:172 FPM:447 Clouds:Medium GPU:98% VRAM:87% Lim:False
2025-01-22 09:19:05.139 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:TLOD+ 10 Night:False TLOD:35 TLODRng:35 OLOD:50 AGL:674 FPM:2459 Clouds:Medium GPU:97% VRAM:86% Lim:False
2025-01-22 09:19:15.311 [INF] [ LODController:UpdateVariables    ] FPS:22 Pri:TLOD+ 10 Night:False TLOD:35 TLODRng:35 OLOD:50 AGL:428 FPM:-5223 Clouds:Medium GPU:98% VRAM:86% Lim:False
2025-01-22 09:19:25.497 [INF] [ LODController:UpdateVariables    ] FPS:22 Pri:TLOD+ 10 Night:False TLOD:53 TLODRng:35-90 OLOD:50 AGL:1714 FPM:315 Clouds:Medium GPU:97% VRAM:85% Lim:False
2025-01-22 09:19:35.679 [INF] [ LODController:UpdateVariables    ] FPS:22 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:2853 FPM:2622 Clouds:Medium GPU:95% VRAM:86% Lim:False
2025-01-22 09:19:45.845 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:2363 FPM:1925 Clouds:Medium GPU:98% VRAM:87% Lim:False
2025-01-22 09:19:56.018 [INF] [ LODController:UpdateVariables    ] FPS:23 Pri:FPS+ 65 Night:False TLOD:100 TLODRng:90-100 OLOD:50 AGL:1590 FPM:967 Clouds:Medium GPU:97% VRAM:87% Lim:False

In reality, I wouldn't run MSFS 2024 at these high settings because 20 FPS is a pretty poor result, which means with lower settings VRAM use would be even lower. ie. Unfortunately, I am not able to replicate your rapid VRAM usage increase on a low VRAM GPU around 55S and north of it, even with more aggressive settings than I would normally use.

 

 

Edited January 22, 20251 yr by Reset XPDR

10 hours ago, Maddormo said:

If you want test it, affirm, default scenery is more than enough. From Packwood, flying north, following the valley, and especially reaching 5000ft, VRAM will fill up due to the ultra-detailed mesh (VEXCEL) of Mount Rainier (at least using 1440p, like in my case).

I just had another thought as to why my VRAM didn't fill up with the Mount Rainier test and that is that maybe it needs one of the settings (like texture resolution?) to be set at a certain level for it to activate. I do have photogrammetry turned on but I was using global medium for the test which may have been too low.

Do you know if this is the case and if so what setting should I try?

First off, thanks for taking the time to test my specific case. After checking your log, I can guarantee that the significant difference isn't the texture size (in fact, I've set it to low) the main differences are TLOD and TLODRng.

yours: TLOD:100 TLODRng:90-100

mine: TLOD:400 TLODRng:100-400

Thats is the reason because your VRAM is more stable.

My values work great for non mountain areas and far away from complex airports, photogrametry or these new Vexcel areas. However, after more test during last night, I have realized that the best solution if I want to fly over those sceneries while keeping VRAM under control, is to reduce the TLOD Top to below 300 (ideally between 250 and 275) and let the app make its smooth magic 🙂. Since I usually fly in very different areas, I don't mind changing that value depending on the area I plan to visit

Another important difference is you have selected medium level for the clouds and for me Ultra is an absolute red line. I can't live without them.

One question: i have selected FPS Cap as Auto method (in my log appears as ATLOD), but I saw in your log that you have selected "Pri:FPS+ 65" Sorry, but I don't remember all the modes by heart. Which one is that?

Again, thanks for your time!

Edited January 22, 20251 yr by Maddormo

4 hours ago, Maddormo said:

First off, thanks for taking the time to test my specific case. After checking your log, I can guarantee that the significant difference isn't the texture size (in fact, I've set it to low) the main differences are TLOD and TLODRng.

yours: TLOD:100 TLODRng:90-100

mine: TLOD:400 TLODRng:100-400

Thats is the reason because your VRAM is more stable.

My values work great for non mountain areas and far away from complex airports, photogrametry or these new Vexcel areas. However, after more test during last night, I have realized that the best solution if I want to fly over those sceneries while keeping VRAM under control, is to reduce the TLOD Top to below 300 (ideally between 250 and 275) and let the app make its smooth magic 🙂. Since I usually fly in very different areas, I don't mind changing that value depending on the area I plan to visit

Another important difference is you have selected medium level for the clouds and for me Ultra is an absolute red line. I can't live without them.

One question: i have selected FPS Cap as Auto method (in my log appears as ATLOD), but I saw in your log that you have selected "Pri:FPS+ 65" Sorry, but I don't remember all the modes by heart. Which one is that?

Again, thanks for your time!

Ah yes, TLOD was my other thought too. Unfortunately, if I had set higher TLOD my FPS would have been in the teens on my poor old gaming laptop, which is why I didn't test it higher.

Re auto method, I chose FPS sensitivity because I didn't know what mode you were using and that is the default auto mode. The results would have been similar had I used FPS Cap or AutoTLOD as I would have been forced to lower my TLOD Top to keep reasonable FPS in any case.

Now that you mention FPS Cap showing up as ATLOD with logging, I will update the logging to show this mode correctly for the next maintenance release. As FPS Cap is just a special configuration of ATLOD it is not a big deal, but I am glad you mentioned it for me to fix.

The upshot of all of this is that I believe what I have written in the readme regarding the use of VRAM+ still stands for your situation, particularly the last line as that is what you ended up doing ie.

• If you are continually experiencing auto TLOD limiting activating, consider reducing your app TLOD settings and/or reducing other MSFS graphics settings.

Also, based on our discussion on this, I have made it clearer in the readme which config file to change and what specific config key values can be changed for VRAM+, namely:

• Uses two thresholds for VRAM usage, both changeable in the app root directory config file (not the one in the bin subdirectory) after running the app once after updating:
  • VRAMOverflowHoldTLOD threshold, defaults to > 96% VRAM in use and will cap TLOD to its current value, even if favourable performance conditions exist.
  • VRAMOverflowReduceTLOD threshold, defaults to > 98% VRAM in use and will progressively reduce TLOD down until the Hold threshold is achieved, but no lower than the default low-end setting in MSFS of 25.

Thanks for all your feedback on this.

Latest beta broke Autofps 😞

Ill try suggestion in startup screen to start Autofps first now