Installed Version RC2 and tried tu use GPU-Z-Features the first time - unfortunately some problem with VRAM-Statusindication.

My System ist quite old and not very powerful, but it does the Job with Medium- and High-Settings in MSFS.

Win 10, MSFS 2020 (DX11), GTX 1060 with (only) 3 GB RAM (smile)

With GPU-Z started I get following Status-Indication in AutoFPS: PC DX11/FPS PRI/TLOD 20-150/GPU 98% - so VRAM-Indication missing.

AutoFPS.config includes

 <add key="VRAMOverflowHoldTLOD" value="95" />
 <add key="VRAMOverflowReduceTLOD" value="98" />

Interesting Log-File parts:

2025-01-02 14:03:14.886 [INF] [ LODController:gpuzRunning        ] GPU-Z companion app running
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Load sensor found
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Memory Used sensor found
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z Initial Memory Used: 2989 MB

 

2025-01-02 14:03:14.983 [INF] [ ServiceModel:ResetCloudsTLOD     ] Full reset of TLOD, clouds, graphics mode and Auto Target FPS states activated.
2025-01-02 14:03:35.193 [INF] [ LODController:UpdateVariables    ] FPS:36 Pri:TLOD Night:False TLOD:20 TLODRng:20 OLOD:100 AGL:9 FPM:0 Clouds:High GPU:98% VRAM:0% Lim:False
2025-01-02 14:04:15.660 [INF] [ LODController:UpdateVariables    ] FPS:31 Pri:TLOD Night:False TLOD:20 TLODRng:20 OLOD:100 AGL:10 FPM:17 Clouds:High GPU:98% VRAM:0% Lim:False
2025-01-02 14:04:25.790 [INF] [ LODController:UpdateVariables    ] FPS:30 Pri:TLOD Night:False TLOD:20 TLODRng:20 OLOD:100 AGL:358 FPM:3783 Clouds:High GPU:98% VRAM:0% Lim:False
2025-01-02 14:04:35.886 [INF] [ LODController:UpdateVariables    ] FPS:31 Pri:TLOD Night:False TLOD:22 TLODRng:20 OLOD:100 AGL:1100 FPM:4654 Clouds:High GPU:98% VRAM:0% Lim:False
2025-01-02 14:04:45.973 [INF] [ LODController:UpdateVariables    ] FPS:37 Pri:TLOD Night:False TLOD:82 TLODRng:20-120 OLOD:100 AGL:1948 FPM:5292 Clouds:High GPU:98% VRAM:0% Lim:False
2025-01-02 14:04:56.079 [INF] [ LODController:UpdateVariables    ] FPS:37 Pri:FPS Night:False TLOD:142 TLODRng:20-150 OLOD:94 AGL:2661 FPM:2790 Clouds:High GPU:98% VRAM:0% Lim:False

......

VRAM is always indicated to be 0%, although the GPU-Z-Sensor-Indicator says the actual value near 3 GB.

I could not find a solution in the readme, Therefore I appreciate your kind help!

Thanks

2 hours ago, Cpt_Piett said:

I very quickly got "VRAM LTD" in the status bar. And AutoFPS reduced TLOD accordingly. I think that feature is going to be very helpful. Even for 4090-owners with 24GB of VRAM like me. 

Man, if you are running into issues with that card, there is no hope for us mortals.

2 minutes ago, BrammyH said:

Man, if you are running into issues with that card, there is no hope for us mortals.

There is something weird happening for sure. Could be the VRAM overflow bug. I haven't checked what the status of this is - bug-logged perhaps?

I ran into some severe stutters overflying KLAX in the Fenix 319 at FL350 en route to KPSP. Things eventually settled down some 10nm before KPSP. I then did KPSP (also a PG area) to KLAX). 

About 40nm from KLAX (probably the start of the PG area), the stutterfest + VRAM overflow started. AutoFPS was not able to deal with it in time. Just before landing on rwy 25R, below 500ft or so, things settled down. 

I'm currently troubleshooting and trying to figure out what AutoFPS settings I could use to improve the situation. No luck so far. I'm about to do a flight KLAX-KPSP with PG disabled. 

2 minutes ago, Cpt_Piett said:

There is something weird happening for sure. Could be the VRAM overflow bug. I haven't checked what the status of this is - bug-logged perhaps?

I recall on the last Dev stream people were mentioning vram issues. Seb said something along the lines of "well, maybe it's time for a hardware upgrade." Then the look on their faces when somone said, "But yeah, I'm having the same issues on a 4090"

 

33 minutes ago, BrammyH said:

I recall on the last Dev stream people were mentioning vram issues. Seb said something along the lines of "well, maybe it's time for a hardware upgrade." Then the look on their faces when somone said, "But yeah, I'm having the same issues on a 4090"

Yeah, I think that caused some reactions 😅. It must be a bug though... It doesn't make sense that the sim would use more than 24GB of VRAM 🤷‍♂️

Well, I disabled PG and things were a bit better departing from KLAX. But there was a few seconds just after takeoff from 07R with terrible stutters and frame time spikes. This is not related to AutoFPS - should we could possible take the discussion elsewhere, e.g. my performance thread. 

I'll do one more KLAX takeoff attempt, with PG and Asobo's KLAX disabled. 

Edited January 2, 20251 yr by Cpt_Piett

https://forums.flightsimulator.com/t/fps-performance-vram-bug/668753

 

2 minutes ago, deepstar said:

https://forums.flightsimulator.com/t/fps-performance-vram-bug/668753

Ok, good. 484 votes and bug-logged. I guess that means that they acknowledge it's a bug? 

18 minutes ago, Cpt_Piett said:

I'll do one more KLAX takeoff attempt, with PG and Asobo's KLAX disabled.

Much better! Still a few stutters on approach to 25R, but it's a night and day difference. Conclusion: Asobo's KLAX is an un-optimized word not allowed. I think. 

Update: Takeoff to the east over the LA metro area, smooth, FPS 100+. VRAM did not exceed 19GB. I think PG+Asobo's KLAX was the culprit here. 

I'll leave PG off for now. It looks good (in some places), but it's too much of a performance hog. 

Edited January 2, 20251 yr by Cpt_Piett

Hello

May I ask what "PG" is?

 

I should have added that I’m on MFSF 2024, so DX12. When I lowered the textures from ultra to high, VRAM-usage decreased about 5%, so not really a big difference. Ground textures stay blurry, even with a TLOD of 600! Buildings and trees are very sharp (EDIT: but at a distance of some miles they get funny shapes). Runways are still blurry at a distance of 1 mile and a TLOD of 200.

 

Edited January 2, 20251 yr by JWvdH

3 minutes ago, Metall4You said:

Hello

May I ask what "PG" is?

Photogrammetry

1 minute ago, Cpt_Piett said:

Photogrammetry

Many thanks

5 hours ago, ohny said:

Installed Version RC2 and tried tu use GPU-Z-Features the first time - unfortunately some problem with VRAM-Statusindication.

My System ist quite old and not very powerful, but it does the Job with Medium- and High-Settings in MSFS.

Win 10, MSFS 2020 (DX11), GTX 1060 with (only) 3 GB RAM (smile)

With GPU-Z started I get following Status-Indication in AutoFPS: PC DX11/FPS PRI/TLOD 20-150/GPU 98% - so VRAM-Indication missing.

AutoFPS.config includes

 <add key="VRAMOverflowHoldTLOD" value="95" />
 <add key="VRAMOverflowReduceTLOD" value="98" />

Interesting Log-File parts:

2025-01-02 14:03:14.886 [INF] [ LODController:gpuzRunning        ] GPU-Z companion app running
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Load sensor found
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z GPU Memory Used sensor found
2025-01-02 14:03:14.887 [INF] [ LODController:gpuzRunning        ] GPU-Z Initial Memory Used: 2989 MB

 

When I detect GPU VRAM amount I had to set a minimum amount to avoid divide by zero when calculating GPU use %, so I chose the MSFS 2024 minimum spec of 4GB thinking that would be plenty. I being a 2020 and 2024 compatible app, I should have set it to 2GB or lower and will do so, as well as provide more meaningful log information, in an updated RC3 shortly. Thanks for pointing this out!

Edited January 2, 20251 yr by Reset XPDR

Autofps is an amazing program cant fly 2024 without it - game changer and I have an RTX 4080 S OC

5 hours ago, Cpt_Piett said:

About 40nm from KLAX (probably the start of the PG area), the stutterfest + VRAM overflow started. AutoFPS was not able to deal with it in time. Just before landing on rwy 25R, below 500ft or so, things settled down. 

As I am putting out an RC3 shortly anyway, I'm thinking of changing the VRAM overflow protection algorithm to reduce TLOD more aggressively at nearly full VRAM to try an avoid getting to an actual VRAM overflow situation. I was thinking that at 98% VRAM usage, the TLOD reduction step size could be up to 20, at 99% up to 50 and at 100% VRAM usage it's all hands on deck to stop the sinking ship and TLOD reduces by the greater of half or 50.

Edited January 2, 20251 yr by Reset XPDR