ohny

Thank you for clarification. Now it is clear even for an almost 80 years old user like me!

Thanks for the clarification. For me as non-native-english-speaker obviously using "FPS cap" and "FPS Cap" for two different issues was a little bit confusing 🙃.

Even after studying the readme carefully, there is still one question open for me: When using the Non-Expert-Mode: Which Auto-Method will the program use? Or do I have to first switch to Expert-Mode, select the corresponding Auto-Method e.g. FPS Cap and then swich back to Non-Expert-Mode?

Without studying all available information 😃 I have a simple question: Does the Program running in Non-Expert-Mode anyhow uses the settings defined in the corresponding Expert-Mode und make some number-crunching with those values?

Oh Boy!!! That's what I missed! After installation of GPU-Z the default for this function is unticked. So after activating everything is working as it should. Thanks Rumpelzuck and all the others who tried to help.

Yes, latest version installed.

Thanks providing your ideas. I think I used your recommended GPU-Z-Settings also without success, but tried them again. But again AutoFPS freezes the indicated values as soon as I minimize or put GPU-Z into system-tray. Strange point is, that hovering the mouse in sytem-tray over the GPU-Z-icon, also those values are frozen and do not change during flight. So for me it is obvious, that GPU-Z is causing the stable values within AutoFPS, because the source of the data (GPU-Z) is not updating them. Only getting GPU-Z back to the top the logging starts again and consequently the statusline in AutoFPS is updated. Maybe I have to search within the GPU-Z-Forum (if any ...) to find a solution. But honestly I would prefer some hints from this community. Maybe someone has experienced the same issue and found a solution ...

Need some support how to get AutoFPS and GPU-Z working correctly. When GPU-Z is open the status-line in AutoFPS correctly indicates the current GPU-/VRAM-values and everything works correctly. As soon as I hide GPU-Z the values are frozen to the latest status und are no more updated. Additionally when hovering with the mouse over the GPU-Z-Icon in the tray, it also has frozen the latest values identical to the ones showing in the AutoFPS-Statusline. Only opening GPU-Z again gets the App to work again updating the sensor-values. I tried several different settings in GPU-Z, but without success. Although it seems to be a GPU-Z-issue and not AutoFPS-related: Could someone inform me about the "Magic Button" within GPU-Z I have to activate getting it to log the sensor-values permanently also if hidden in the background to feed AutoFPS. Thanks!

Updated to RC3 and problem solved: VRAM appears in the status line and thus GPU usage information is working. Thanks a lot for changing your excellent program to work also with few poor-guys-systems like mine with only 3 GB VRAM. About 10 years ago this was a far sufficient value ...

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

Hello Reset, I'm using the MSFS2020-App with MSFS 2020 since quite some time with no issues - thanks. As I want to stick to MSFS 2020 also for the near future I'm wondering, whether it is anyhow recommended to switch over to your new general MSFS2020/2024-version. Does this actual version provide some improvements also for MSFS 2020-users, or is the 2020-part identical with the latest MSFS 2020-App-version 0.4.3.1? Thanks!

Is it a bug or a feature, that Alt OLOD Base cannot be set lower than 1000 ft?

Thanks for all your comments. So it seems to be an issue with my system and not a general one due to the update. The slow-motion-loading appears also after several loading cycles, But meanwhile surprisingly the loading-time for "Fly" sometimes recovered again to normal values, but next time unfortunately again long loading - so it is not a stable issue. Maybe my system hopefully will recover by time by itself, which obviously seems to happen from time ti time ...

Thanks Cpt_Piett for your reply. I did not install a new addon or made a severe change in the system. My feeling though is this issue started after the last update a few days ago.

Since a few days loading of a flight (Fly Now) is extremely slow compared to time before (now approx. 5 min, before 1,5 min). Does anybody observe the same problem? Any idea how to solve this issue? Thanks for help!

The way I load the simbrief-FP into default 320Neo/MCDU is as follows: - Create FP in simbrief. Under "Flight Plan Downloads" select "FS2020". Filename is shown as .pln-file and "Download". Store file wherever you want. - In MSFS - Worldmap select "(Space)More" and then "(Space)Load/Save" (or just press double-Space). Under "Load from this PC" select your stored FP pln-file and the FP is in your MCDU. Only Arrival-Data have to be manually added. That's it.

Thanks a lot! Good to know.where this information is documented.

Still have a basic question: If not using the expert option: Are some of the settings of this option also valid if expert is not ticked? If not, which settings does the app use in non-expert? Maybe the answer is hidden in the description, but so much information ... Thanks!

Right, this is how it shows. Your explanation is logically, but the "b" only appears after flying for some time, not from the beginning. I will further check if or when it appears again.

I am using the latest AutoFPS-Version with DX11 and without Expert-Options. Target FPS is set to 30. All works well, but after some time the Target FPS-Field shows an additional "b", in my case "30b". What does the "b" mean? Thanks

@ JordanChin Thanks for creating your hybrid-shader-solution. Will download and try. Do you recommend to use it with original Microsoft WaterConstants.xml or the Bojote-Version? Thanks. ohny