fpsVR News

The fpsVR BETA 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.
  

The fpsVR has been updated with the following changes:

• Fixed: Oculus battery counters were not displayed when the SteamVR experimental option to block the Oculus API was enabled (usually enabled by OculusKiller users).
  
• The history viewer (fpsVRviewer.exe) now automatically detects and recreates a corrupted configuration file (this rarely happens, probably due to a bug in the library used to work with json files).
  
• Other minor fixes
  

The fpsVR BETA has been updated with the following changes:

• Fixed: Oculus battery counters were not displayed when the SteamVR experimental option to block the Oculus API was enabled (usually enabled by OculusKiller users).
  
• The history viewer (fpsVRviewer.exe) now automatically detects and recreates a corrupted configuration file (this rarely happens, probably due to a bug in the library used to work with json files).
  
• Other minor fixes
  

The fpsVR has been updated with the following changes:

Common:

• Added support for displaying CPU temperatures: Intel 12XXX mobiles CPU with prefix H and HK.
  
• Added support for displaying CPU temperatures: Intel 13XXX desktop CPU (preliminary support based on available information).
  Steam may ask you for elevated rights to complete the installation of this update, when you launch fpsVR first time after this update (In order to update the processor temperature polling service)
  

Oculus/Meta:

• Added experimental support for displaying controller battery levels for Quest 1/2, Rift CV1/S, and headset battery levels for Quest 1/2. Tested on Quest 2 only. Please leave comments on how this feature works for you.
  Important notes:
  
  
  • Batteries charge information is not available when using VD or ALVR
    
  • Sometimes the Oculus service "forgets" to update battery data. This probably happens after the headset wakes up from sleep mode. And the display of charges may stop updating in the Oculus software for a while. fpsVR in this case, 5 minutes after the absence of new data, it will show the value of the headset charge equal to "--".
    
  
  In the image below, you can see the overlay variations that support displaying controllers and headset charges.
  
  
• OculusKIller: If you've been using OculusKIller you've probably noticed that fpsVR stopped working properly since update 1.24, specifically fpsVR was always in standby mode because it thought the Oculus dashboard was always open. Now fpsVR should detect that OculusDash.exe is not original and will not respond to a false dashboard state.
  
• The option to display extended data received from the Oculus API in the overlay was buggy. Now, in the case of using Link (by cable), the current bitrate will be displayed correctly and will not disappear.
  

The fpsVR BETA has been updated with the following changes:

• OculusKIller: If you've been using OculusKIller you've probably noticed that fpsVR stopped working properly since update 1.24, specifically fpsVR was always in standby mode because it thought the Oculus dashboard was always open. Now fpsVR should detect that OculusDash.exe is not original and will not respond to a false dashboard state.
  
• The option to display extended data received from the Oculus API in the overlay was buggy. Now, in the case of using Link (by cable), the current bitrate will be displayed correctly and will not disappear.