fpsVR News

The fpsVR BETA has been updated with the following changes:

• fpsVR now gets GPU memory usage directly from the GPU driver for AMD graphics cards. With this update, Windows performance counters are no longer used on PCs with AMD and Nvidia graphics cards.
  

The fpsVR BETA has been updated with the following changes:

• New algorithm for calculating CPU usage values. Broken performance counters in update 22H2 for Windows 10/11 are now irrelevant, as there are no plans to return to them. If you are already using Windows 10/11 22H2, you may want to switch to this beta version of fpsVR. The new algorithm uses the same data sources as in the latest beta versions of Afterburner and RivaTuner Statistics Server.
  

Hi,
Bad news: on some PCs starting from the operating system versions listed below you may have problems with the CPU counters. fpsVR takes data from Windows performance counters. Microsoft has broken these counters with updates but it seems that not all PCs have this problem. But probably on many. So you will probably see very strange CPU utilization and CPU core utilization readings.
If you can postpone installing the 22H2 updates for Win10/11, you should probably do so.

Windows 10 22H2 Build 19045
Windows 11 22H2 Build 22621

The fpsVR BETA has been updated with the following changes:

• Optimized fpsVR startup process (it should start faster on some systems).
  
• Fixed issue of randomly not displaying the battery charge of controllers with non-replaceable battery (such as Vive controllers, Index controllers). For some reason, when turn on a controller and detect it, SteamVR may accidentally tell fpsVR that a charge level check is not available for that controller. In this version, additional checks have been added - when you open or close the SteamVR dashboard, and when system events related to controller batteries occur.
  
• Made rollback to the older subsystem to determine the presence of special states of the running game, such as level loading, game hung, etc. As practice showed, the latest versions of fpsVR did not always work as intended, and as a result, fpsVR could go into a long pause for recording statistics.
  
• The system of version numbering of the application was changed.
  

The fpsVR has been updated with the following changes:

• fpsVR now detect whether VD or ALVR is currently being used. This information is displayed in the logs of the app for troubleshooting, and will also be used to fix future issues.
  
• The issue when fpsVR did not work correctly when using VD in certain specific configurations has been fixed. See more here.