fpsVR News

The fpsVR has been updated with the following changes:

• Fixed a bug where fpsVR could function incorrectly if the user enabled saving history for the desktop version of the history viewer, but his Documents folder was damaged or inaccessible for some reason (after incorrect removal or installation of OneDrive, incorrectly configured access, etc). In a future update, I plan to make it possible for such cases to select an alternative path for saving history, for example, to the AppData folder.
  

The fpsVR has been updated with the following changes:

• Fixed a bug due to which trackers batteries charges were not displayed in the corresponding section of the in-game overlay.
  

The fpsVR has been updated with the following changes:

• At the end of a gaming session, the in-game overlay will display summary statistics for sessions that lasted more than 2 minutes. (In the current implementation, when SteamVR Home is enabled, the time for which this information will be displayed will depend on how quickly SteamVR Home starts, in the future I will probably fix this)
  
• Added build-in History Viewer. It allows you to view information about the last 10 sessions that lasted more than 2 minutes. See fpsVR overlay in SteamVR dashboard : "General" -> "History Viewer"
  
• Added new section "Devices". The information displayed on it will be useful for those who use a large number of devices, such as trackers for full body tracking.
  
• Added an option to "Devices" to enable notifications about battery levels in multiples of 10 (90%, 80%, 70%, etc.)
  
• Added a warning on the page for resolution detection (See button "Detect Resolution" on section "General") stating that at high resolutions with the "Advanced Supersampling Filtering" SteamVR option enabled the detection of resolution will not work correctly.
  
• Some options have been moved between settings sections, taking into account changes.
  

Also look at the previous “small” update, which you might have missed given the way Steam displays this information for updates marked as a “small update”: https://steamcommunity.com/games/908520/announcements/detail/3902994707213070437

Happy New Year!

The fpsVR BETA has been updated with the following changes:

• Added build-in History Viewer. It allows you to view information about the last 10 sessions that lasted more than 2 minutes. See fpsVR overlay in SteamVR dashboard : "General" -> "History Viewer"
  
• Added new section "Devices". The information displayed on it will be useful for those who use a large number of devices, such as trackers for full body tracking.
  
• Added an option to "Devices" to enable notifications about battery levels in multiples of 10 (90%, 80%, 70%, etc.)
  
• Added a warning on the page for resolution detection (See button "Detect Resolution" on section "General") stating that at high resolutions with the "Advanced Supersampling Filtering" SteamVR option enabled the detection of resolution will not work correctly.
  
• Some options have been moved between settings sections, taking into account changes.
  

The fpsVR has been updated with the following changes:

Steam Link

• Fixed: headset battery was displayed as "Other batteries".
  
• A workaround has been applied to a SteamVR issue (with Steam Link) where the VREvent_PropertyChanged event from SteamVR is missing when a headset user changes the headset frequency in the SteamVR interface. This caused the fpsVR logic to not work correctly.
  

Intel

• Added support for temperature monitoring for Intel processors with Ext. Model 0xBA (13500H/13900H) and with Ext. Model 0xBF (13400F/13500/13700HX). The next time you run fpsVR after this update, Steam may request administrator rights to update the CPU monitoring service.
  

Timer

• Fixed a bug that caused "-01" seconds to be displayed when the timer ends.
  
• Fixed a bug that resulted in the absence of a sound notification when reusing the timer function.
  
• The timer function now announces the end of the timer once, without any advance warning.
  

AMD GPU

• The time between updates for GPU monitoring using ADLX has been increased to 2000ms (if the user setting is set to less than 2000ms).
  

ADLX is used in approximately 5% of cases for users with AMD GPUs, in cases of using mobile GPU chips, drivers for Bootcamp, and in cases where the driver does not work correctly and does not initialize the standard API: ADL. Unfortunately, AMD does not fix problems with their APIs: ADL works generally well, but for some unknown reason it does not work for some users (possibly on certain driver versions), while ADLX has been about a year since its release and still has not fixed issues with performance. I was able to get some advice on using ADLX from an AMD rep, there may be some improvements in future versions of fpsVR and this increase in time between updates will be reduced in the future. Also see: https://steamcommunity.com/games/908520/announcements/detail/5943124160454215874