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!

51 minutes ago, ohny said:

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!

What do you mean by "hide" GPU-Z? If you are clicking on the close window button, I believe that it actually closes GPU-Z by default. Instead, either use the minimise button or set it to go to the system tray on close.

My suggestion is to go to GPU-Z settings and set it like this, which will start it with windows and minimise or close to the system tray:

Edit: This sounds familiar to the issue Cpt_Piett was having with an earlier test build here

Are you sure you are running the 0.4.4.2 release version, which includes the fix for this? Also, are you running the latest version of GPU-Z (2.61.0)? As long as GPU-Z is running, whether minimised, maximised, normal or in the system tray, the shared memory interface is active and it should be detected by this app.

If you still have this issue, message me your log file from a session where you minimise/maximise GPU-Z a few times and I'll see what the log tea leaves tell me.

Edited January 4, 20251 yr by Reset XPDR

43 minutes ago, Reset XPDR said:

What do you mean by "hide" GPU-Z? If you are clicking on the close window button, I believe that it actually closes GPU-Z by default. Instead, either use the minimise button or set it to go to the system tray on close.

My suggestion is to go to GPU-Z settings and set it like this, which will start it with windows and minimise or close to the system tray:

Edit: This sounds familiar to the issue Cpt_Piett was having with an earlier test build here

Are you sure you are running the 0.4.4.2 release version, which includes the fix for this? Also, are you running the latest version of GPU-Z (2.61.0)? As long as GPU-Z is running, whether minimised, maximised, normal or in the system tray, the shared memory interface is active and it should be detected by this app.

If you still have this issue, message me your log file from a session where you minimise/maximise GPU-Z a few times and I'll see what the log tea leaves tell me.

 

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 ...

 

8 minutes ago, ohny said:

But honestly I would prefer some hints from this community. Maybe someone has experienced the same issue and found a solution ...

Do you have the latest version? This is the one I use, and it works fine. 

Been flying with 0.4.4.2 for several hours in the Fenix A319 with AI traffic. Everything works great! I've decided to disable photogrammetry for airliner flights (for various reasons, see my MSFS2024 performance thread). 

Thanks again @Reset XPDR for your efforts in improving AutoFPS for 2024 - it's an invaluable addon 😄 

@ohny:   Do you have "refresh sensors while in background" enabled in GPU-Z settings and sensors? 

 

3 hours ago, Cpt_Piett said:

Do you have the latest version? This is the one I use, and it works fine. 

Yes, latest version installed.

45 minutes ago, Rumpelzuck said:

@ohny:   Do you have "refresh sensors while in background" enabled in GPU-Z settings and sensors? 

 

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.

6 hours ago, Rumpelzuck said:

@ohny:   Do you have "refresh sensors while in background" enabled in GPU-Z settings and sensors? 

 

Thanks for this. I've added the need to check that this option is enabled to the readme.

Occasionally AutoFPS does not read the sim FPS correctly. Example: currently flying at FL330 and FPS as reported by the dev mode FPS counter is around 50, but AutoFPS reports higher than 70. My target FPS is 70, so AutoFPS doesn't reduce TLOD - hence there are severe stutters. 

Hello

the same for me

 

7 hours ago, Cpt_Piett said:

Occasionally AutoFPS does not read the sim FPS correctly. Example: currently flying at FL330 and FPS as reported by the dev mode FPS counter is around 50, but AutoFPS reports higher than 70. My target FPS is 70, so AutoFPS doesn't reduce TLOD - hence there are severe stutters. 

You use FG though right? The dev mode FPS counter shows non-FG FPS, and always has, whereas AutoFPS shows you your actual FG FPS. Also AutoFPS takes 5-10 seconds to setting with FPS reading when going toggling between FG active and inactive. Isn't this what you are seeing?

If not, a screenshot of MSFS dev mode FPS counter, AutoFPS window and RTSS overlay stats in the one screenshot showing these discrepancies FPS would be helpful.

9 hours ago, Reset XPDR said:

You use FG though right? The dev mode FPS counter shows non-FG FPS, and always has, whereas AutoFPS shows you your actual FG FPS. Also AutoFPS takes 5-10 seconds to setting with FPS reading when going toggling between FG active and inactive. Isn't this what you are seeing?

If not, a screenshot of MSFS dev mode FPS counter, AutoFPS window and RTSS overlay stats in the one screenshot showing these discrepancies FPS would be helpful.

I use FG. In the situations where the issue occurs, AutoFPS reports FG active. I'm aware that dev mode shows non-FG FPS so I took that into account. I'm also using the RTSS overlay, which shows FG-FPS. 

It could be that 5-10 secs of FPS settlings that I'm seeing. I'll keep an eye on it an report back with some screenshots if it occurs again. 

1 minute ago, Cpt_Piett said:

I use FG. In the situations where the issue occurs, AutoFPS reports FG active. I'm aware that dev mode shows non-FG FPS so I took that into account. I'm also using the RTSS overlay, which shows FG-FPS. 

It could be that 5-10 secs of FPS settlings that I'm seeing. I'll keep an eye on it an report back with some screenshots if it occurs again. 

I'm pretty sure that's what it will be. I put in the settling period upon returning to FG active because the FPS is not stable for a while after the transition due to the new values being double what the previous FG inactive values were, so it takes a good few seconds for it to settle again.

Anyway, if that's not how it is working, I'm sure you'll let me know, with screenshots to boot! 😂

Hi:
Long user of your app. As others have mentioned before: it's a real game changer. Thank you so much for your dedication.

I have a 'little' request that I think could be useful: I ask you to consider including text boxes, as well as controls, in the excluded elements of the double click tool to hide certain parts of the interface.

When I want to enter a new value in a text box, I usually double-click the previous value and type in the new one. I've done this so often that every time I try to modify a parameter, I end up hiding the expert options, which means I have to double-click twice more to bring them back.

I hope this change won't be very difficult to implement.

Best regards