fpsVR News

The fpsVR has been updated with the following changes:

• Fixed an issue: when starting the game, there is a high GPU or CPU frametimes, sometimes even up to 100ms. The source of the problem was the OpenVR API function: WaitFrameSync. fpsVR has been using it for a long time to synchronize work, it is not clear why the problem appeared recently. There may have been some changes in SteamVR or the Nvidia driver that somehow caused the issue. This remains to be seen. A workaround has now been implemented without using this API function.
  
• Fixed minor visual bugs in the history viewer (in the built-in version).
  
• A button has been added on the “General” tab in the settings, that allows you to select an application for which you want to change the “Per-Application” setting, for applications that were launched earlier (since the last time SteamVR was launched). For example, this will allow you to change the rendering resolution for the application you just closed. The button appears after the first VR application is launched.
  

Currently, some users are experiencing the following bug:
When starting the game, high GPU or CPU frametimes are observed, up to 100ms. The problem is observed only if fpsVR is running in parallel (although it may be the same in other conditions, but such have not yet been identified).

[h3]Current workaround: Switch to another window and then return to the game window (Alt+Tab, using the mouse, or the SteamVR dashboard). There is no need to close fpsVR[/h3]

Since the problem occurs with any version of fpsVR, I am sure that the bug appeared with some version of the drivers (possibly Nvidia) or with some version of SteamVR. If you see the same thing on AMD cards, please let me know.
I will publish updates on this issue here in this news.

UPDATE: I found the source of the issue, it was the OpenVR SDK function: WaitFrameSync
fpsVR has been using it for a long time to synchronize work, it is not clear why the problem only appeared now. There may be some changes in SteamVR or in the Nvidia driver which led to the problem. I can do without using WaitFrameSync, I'm preparing a new update. Which I will release very soon.

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!