fpsVR News

The fpsVR BETA has been updated with the following changes:

• The app has been updated to use the latest version of the OpenVR API: OpenVR SDK 2.5.1. Therefore, this version of fpsVR requires SteamVR version 2.5 or higher.
  
• When the SteamVR keyboard appears, the fpsVR overlay will now disappear to avoid causing unwanted effects. A recent SteamVR update had a change that prevents applications from receiving controller position when the SteamVR keyboard is active. Because of this, fpsVR would switch the overlay position for games without controllers that was selected in the settings, which could interfere with the use of the SteamVR keyboard
• Fixed other minor bugs that did not affect the use of the application.
  

The fpsVR has been updated with the following changes:

• Added new grapths in the built-in history viewer.
  
• Changes and fixes to the beta and error reporting system.
  

The fpsVR BETA has been updated with the following changes:

• Added new grapths in the built-in history viewer.
  
• Changes and fixes to the beta and error reporting system.
  

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.