41 minutes ago, Cpt_Piett said:

You don't need to use GPU-Z, AutoFPS works 100% fine without it. 

Thank you.  It was not obvious. This continues to evolve at a very rapid pace over how many months?  Not all of us can keep up hourly, or even perhaps daily.
 

Still, after the Addons LInker, this effort is unquestionably the most important I have used for both 2020 and 2024.  Hands Down!

 

2 minutes ago, fppilot said:

This continues to evolve at a very rapid pace over how many months?  Not all of us can keep up hourly, or even perhaps daily.

Yes there's been a lot of updates lately. I think things will settle down with the next release version though. Unless Reset has something else planned 😉

20 minutes ago, Cpt_Piett said:

Yes there's been a lot of updates lately. I think things will settle down with the next release version though. Unless Reset has something else planned 😉

Nah, I'm pretty much done. Even though there are a lot of changes I have incorporated lately, they are all pretty much under the hood to make the app more Asobo bulletproof. 0.4.4.2 is essentially functionally equivalent to the old 0.4.3.1 from back in Oct last year.

43 minutes ago, Reset XPDR said:

Well first of all, try not to quit the app in the middle of the flight as you are asking for trouble 😄

If you do restart the app while in a flight and experience this, you can just quit the app, go in to the MSFS settings menu, toggle a setting like vsync, save setttings and go back to your flight then run the app again and it should pass. This process resets your UserCfg.opt file to the current sim setting state, which the app needs find a match with when it runs the compatibility test.

Edit: I realise that you probably restarted the app mid flight because I came out with yet another version while you were mid-flight, so I'm probably to blame for you doing that.

Nonetheless I will make it clear in the readme that the preferred starting sequence is this app then MSFS or at the very least MSFS then this app via autostart or manually before MSFS gets to the main menu, then leave the app running until you have finished with MSFS.

Thanks, this is very useful to know! 

I wanted to double-check that the log file is still in use in RC1, that's why I restarted the app 🙂 At least I've stopped updating the app within a sim session 😉

3 minutes ago, Reset XPDR said:

Nah, I'm pretty much done. Even though there are a lot of changes I have incorporated lately, they are all pretty much under the hood to make the app more Asobo bulletproof. 0.4.4.2 is essentially functionally equivalent to the old 0.4.3.1 from back in Oct last year.

Somehow that does not seem surprising.  It is just as beneficial today as its was back then. It is truly evident there is a law of diminishing returns.  Once it gets so good, it is difficult to provide an additional increment of change that is truly perceptible, or significant.  

You have provided an improvement so effective that it is literally now a core element.

 

12 minutes ago, Reset XPDR said:

Nah, I'm pretty much done.

I believe I have heard that before! 🙃

Strange issue: AutoFPS doesn't detect the values from GPU-Z unless GPU-Z is in focus. Even stranger: when I hover the mouse over GPU-Z in systray, AutoFPS detects the values. 

EDIT:

The values are logged in the log file. But don't appear in the app status line. 

Quote

2025-01-01 04:11:51.301 [INF] [ LODController:UpdateVariables    ] FPS:112 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3706 FPM:-1 Clouds:Ultra GPU:98% VRAM:81% Lim:False 
2025-01-01 04:12:01.417 [INF] [ LODController:UpdateVariables    ] FPS:115 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3768 FPM:6 Clouds:Ultra GPU:99% VRAM:81% Lim:False 
2025-01-01 04:12:11.531 [INF] [ LODController:UpdateVariables    ] FPS:111 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3735 FPM:-2 Clouds:Ultra GPU:98% VRAM:81% Lim:False 
2025-01-01 04:12:21.643 [INF] [ LODController:UpdateVariables    ] FPS:112 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3738 FPM:1 Clouds:Ultra GPU:99% VRAM:81% Lim:False 
2025-01-01 04:12:31.753 [INF] [ LODController:UpdateVariables    ] FPS:112 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3751 FPM:-0 Clouds:Ultra GPU:99% VRAM:81% Lim:False 
2025-01-01 04:12:41.863 [INF] [ LODController:UpdateVariables    ] FPS:111 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3798 FPM:6 Clouds:Ultra GPU:99% VRAM:80% Lim:False 
2025-01-01 04:12:51.976 [INF] [ LODController:UpdateVariables    ] FPS:110 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:4394 FPM:64 Clouds:Ultra GPU:98% VRAM:80% Lim:False 
2025-01-01 04:13:02.088 [INF] [ LODController:UpdateVariables    ] FPS:108 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:4819 FPM:36 Clouds:Ultra GPU:97% VRAM:81% Lim:False 
2025-01-01 04:13:12.206 [INF] [ LODController:UpdateVariables    ] FPS:111 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:5079 FPM:14 Clouds:Ultra GPU:96% VRAM:81% Lim:False 
2025-01-01 04:13:22.332 [INF] [ LODController:UpdateVariables    ] FPS:110 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:4798 FPM:21 Clouds:Ultra GPU:98% VRAM:81% Lim:False 
2025-01-01 04:13:32.951 [INF] [ MainWindow:LoadSettings          ] Expert:True Mode:FG ATgtFPS:False FltType:IFR TgtFPS:65 TLODMethod:Sens Tol:5 TMin:200 TMin+:false TMax:400 TMax+:True MtnAltMin:1000 TLODMaxExtra:200 TMax-:True TLODBAlt:1000 MaxDesRate 2000 CustomOLOD:False CloudQ:False Pause:False Vh:95% Vr:98% 
2025-01-01 04:13:48.639 [INF] [ LODController:UpdateVariables    ] FPS:112 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:4174 FPM:1 Clouds:Ultra GPU:98% VRAM:81% Lim:False 
2025-01-01 04:13:58.756 [INF] [ LODController:UpdateVariables    ] FPS:111 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:4103 FPM:8 Clouds:Ultra GPU:97% VRAM:80% Lim:False 
2025-01-01 04:14:08.869 [INF] [ LODController:UpdateVariables    ] FPS:111 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3879 FPM:-13 Clouds:Ultra GPU:98% VRAM:80% Lim:False 
2025-01-01 04:14:26.058 [INF] [ LODController:UpdateVariables    ] FPS:109 FGAct:False Pri:FPS Night:False TLOD:600 TLODRng:200-600 Mtns+:200 OLOD:200 AGL:3658 FPM:-26 Clouds:Ultra GPU:96% VRAM:81% Lim:False 

Update: the GPU-Z values re-appear if the AutoFPS window is in the foreground. 

Edited January 1, 20251 yr by Cpt_Piett

27 minutes ago, Cpt_Piett said:

Strange issue: AutoFPS doesn't detect the values from GPU-Z unless GPU-Z is in focus. Even stranger: when I hover the mouse over GPU-Z in systray, AutoFPS detects the values. 

EDIT:

The values are logged in the log file. But don't appear in the app status line. 

Update: the GPU-Z values re-appear if the AutoFPS window is in the foreground. 

As a wealthy retired executive this is all well above my pay grade.  😗

39 minutes ago, Cpt_Piett said:

Strange issue: AutoFPS doesn't detect the values from GPU-Z unless GPU-Z is in focus. Even stranger: when I hover the mouse over GPU-Z in systray, AutoFPS detects the values. 

EDIT:

The values are logged in the log file. But don't appear in the app status line. 

Update: the GPU-Z values re-appear if the AutoFPS window is in the foreground. 

As long as gpu-z is running, the app should be getting the data it needs the shared memory interface, regardless of whether gpu-z is minimised, maximised or hiding in the system tray. The only thing I have changed in RC1 is that, in order to reduced the chance of the status line running beyond the window border, no gpu-z values show at any time while FPS is settling or TLOD Min+ is seeking. Is that what you are experiencing?

11 minutes ago, Reset XPDR said:

The only thing I have changed in RC1 is that, in order to reduced the chance of the status line running beyond the window border, no gpu-z values show at any time while FPS is settling or TLOD Min+ is seeking. Is that what you are experiencing?

That seems to be the case, yes. When FPS has settled, the values are back. 

7 minutes ago, Cpt_Piett said:

That seems to be the case, yes. When FPS has settled, the values are back. 

Would you prefer I put it back to show them at all times? It's an easy change and might be better to do if it causes confusion like you experienced.

16 minutes ago, Reset XPDR said:

Would you prefer I put it back to show them at all times? It's an easy change and might be better to do if it causes confusion like you experienced.

Nah, now that I understand why it occasionally disappears it’s fine. I guess it could be confusing for others though, hard to tell. 

50 minutes ago, Cpt_Piett said:

Nah, now that I understand why it occasionally disappears it’s fine. I guess it could be confusing for others though, hard to tell. 

I'll see if it fits with a worst case remaining status line and will put it back in if it does. I might have gone a bit overboard with my decluttering! 😄

Edit: With the gpu-z items shown always, it is possible to get the status line to overrun its containing boundary, but I have to go out of my way to push it that far, requiring FG being inactive AND a settle timer > 10 seconds AND very high TLOD settings AND 100% VRAM use AND thus VRAM Limited which is not very realistic. eg.

As such, I think I can safely put the gpu-z items back to always show. It'll be back in RC2 or the release version, ideally the latter if nothing else comes up.

Edited January 1, 20251 yr by Reset XPDR

I have to say that the VRAM-detection is a game changer for me! I have a RTX 4070 Ti Super-card and while flying over London in my A2A Comanche, VRAM usage is constantly over 95%. So TLOD is constantly being reduced or locked. Without this it would probably be unflyable. Thank you very much!

2 hours ago, JWvdH said:

I have to say that the VRAM-detection is a game changer for me! I have a RTX 4070 Ti Super-card and while flying over London in my A2A Comanche, VRAM usage is constantly over 95%. So TLOD is constantly being reduced or locked. Without this it would probably be unflyable. Thank you very much!

That makes 2 in our small test group that have triggered it for real, and they are both GPUs packing 16GB of VRAM, which should be a very healthy amount of VRAM. It will be interesting to see how many take it up and benefit from it when the formal release goes live, probably tomorrow my time, especially those with lower amounts of VRAM. Having to run GPU-Z will put some off, but it's not that difficult to install it and have it be started by Windows and run in the background and they may come around if more success stories like yours are reported. Thanks for the feedback!

Just made a VFR flight in SOCAL from Big Bear to OceanSide, with the RC1 (and GPU-Z loaded). It was so enjoyable that I forgot to monitor the V-RAM load on my 3080 with 10Gb. I just remembered high TLOD and OLOD  (~300) all along the highly delightful flight. Thanks to MSFS_AutoFPS.