fpsVR News

[p]The fpsVR has been updated with the following changes: [/p][p][/p][p]This update was not planned for an early release, but circumstances force urgent changes. This is due to another wave of "hardwareprovider.sys" file blocking by antivirus programs.[/p][p][/p]

• [p]The CPU temperature poll is disabled for everyone by default. If you want fpsVR to display the CPU temperature, you will need to enable this functionality manually, go to the fpsVR settings (open the SteamVR dashboard and click on the blue fpsVR icon), on the "fpsVR" tab, go and click the "CPU Temperature Monitoring Status" button. But first read the following: Antivirus may blocks the driver launch (hardwareprovider.sys file / WingRing0 driver) with a warning that this driver is not safe. The fpsVR service uses the kernel-mode driver to poll the CPU to get information about the CPU temperature. fpsVR uses a fairly common and popular driver: "WinRing0". It is quite old and does have a vulnerability. fpsVR fixes the existing vulnerability in this driver by setting appropriate access rights to the driver immediately after launching the driver. But some antiviruses intercepts the call to start the driver, and this happens before the permissions are changed, and blocks it. The driver are installed on each launch and only active while the app is running. Recently, antiviruses have started blocking this driver and its file more often, so this change was made so that this functionality is disabled by default and only experienced users can decide for themselves whether they need it or not. In addition, if your antivirus blocks this file, you will need to add exceptions to your antivirus software (possibly even twice, once it can detect it as a trojan, and the second time as a vulnerable driver).[/p]
• [p]CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab[/p]
• [p]In the history viewer (in its VR version), a field has been added to display the VR driver (this will help you understand, for example, when using Quest 2/3, whether you used Steam Link, Quest Link, VD, etc. for a particular session) [/p]

• [p]The history viewer has been updated (VR version, there will also be changes for the desktop version later). Three new graphs have been added (which show what and how changed during the game session, second by second) and the size of the old two has been slightly increased:[/p][p][/p]

[p][/p][p][/p][p][/p]

• [p]Other minor fixes. [/p]

[p]The fpsVR BETA has been updated with the following changes: [/p][p][/p]

• [p]The CPU temperature poll is disabled for everyone by default. If you want fpsVR to display the CPU temperature, you will need to enable this functionality manually, go to the fpsVR settings (open the SteamVR dashboard and click on the blue fpsVR icon), on the "fpsVR" tab, go and click the "CPU Temperature Monitoring Status" button. But first read the following: Antivirus may blocks the driver launch (hardwareprovider.sys file / WingRing0 driver) with a warning that this driver is not safe. The fpsVR service uses the kernel-mode driver to poll the CPU to get information about the CPU temperature. fpsVR uses a fairly common and popular driver: "WinRing0". It is quite old and does have a vulnerability. fpsVR fixes the existing vulnerability in this driver by setting appropriate access rights to the driver immediately after launching the driver. But some antiviruses intercepts the call to start the driver, and this happens before the permissions are changed, and blocks it. The driver are installed on each launch and only active while the app is running. Recently, antiviruses have started blocking this driver and its file more often, so this change was made so that this functionality is disabled by default and only experienced users can decide for themselves whether they need it or not. In addition, if your antivirus blocks this file, you will need to add exceptions to your antivirus software (possibly even twice, once it can detect it as a trojan, and the second time as a vulnerable driver).[/p]
• [p]CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab[/p]
• [p]In the history viewer (in its VR version), a field has been added to display the VR driver (this will help you understand, for example, when using Quest 2/3, whether you used Steam Link, Quest Link, VD, etc. for a particular session)
  [/p]

[p]The fpsVR BETA has been updated with the following changes: [/p][p][/p]

• [p]The history viewer has been updated (VR version, there will also be changes for the desktop version later). Three new graphs have been added (which show what and how changed during the game session, second by second) and the size of the old two has been slightly increased:[/p][p][/p]

[p][/p][p][/p][p][/p]

• [p]Other minor fixes.
  [/p]

The fpsVR has been updated with the following changes:

Intel

• Added support for monitoring the temperature of Intel Arrow Lake and Meteor Lake processors. After installing this update, when you first start the application, Steam will ask for elevated rights to complete the update of the fpsVR service that polls the processor.

Reminder for users of other processors: if your CPU temperature monitoring does not work, it may be because your antivirus has blocked the use of this function in fpsVR, more details here: https://steamcommunity.com/app/908520/discussions/0/598520965488461543/



AMD

• There were several requests for support due to the fact that after updating the AMD video card driver, fpsVR stopped starting. The reason was that a failure occurs in the video card driver when initializing the API for monitoring the GPU (AMD ADL or AMD ADLX). So far, there is a suspicion that this happens with relatively new drivers (2024-2025). In this regard, fpsVR has been updated with functionality to detect such cases. fpsVR will now warn that there was a driver failure during the previous launch, if there was one, and that the driver needs to be reinstalled, or rolled back to an older version, and perhaps it is worth using the official driver cleaning utility (and this helps). Recommendation: Disable driver updates via Windows Update. When Windows itself updates the GPU driver, this usually does not lead to anything good....

Oculus

• A change has been made that will ignore negative frame compositor GPU frame time values ​​for data received from the Oculus API (when using a wired headset or Meta Link for wireless headsets) for some individual frames. This was due to a bug in the Oculus software. Therefore, it is likely that users of the Oculus Rift S and CV1 headsets (most likely not on Quest headsets) could see negative GPU frame time values ​​(at least in one case where this was observed on the Oculus Rift S). The frame time values ​​of the frame compositor are a very small part of the overall GPU frame time, so excluding this value for some frames will not make a big difference. If this bug will be fixed in the Oculus software, then no further changes will be required on the fpsVR side in the future.
  

Other

• The option to force the overlay position for seated games/applications is now saved in the app settings and is not reset after restart.
  
• In Windows logs, the fpsVR service for receiving data on the processor temperature is now mentioned not as Service1 but as fpsVRcpuService
  
• Fixed the issue of cutting off some of the information about the battery charge of trackers in the interface of the desktop window.
  
• Added an option for a sound warning about cable tangled. You can enable a single warning and a looped one (the sound will be played until the cable is untangled)
  
• Added an option to display the center marker (and, as a result, display cable tangled if enabled) provided that there are no active controllers with the right or left hand role. You can use this option, for example, if you play a game with a gamepad, but you still need to track cable tangled.
  
• Added an option that allows you to limit the display of the center marker only when the SteamVR dashboard is open.
  
• Added an option that allows you to disable the display of the final statistics of the game session at the end of the session (this does not affect the saving of the session history if the session history is enabled).
  
• Added a sound warning for the option that warns about low batteries (controllers, trackers and headsets). And now, in addition to the warning appearing at 15%, it will also appear at 25%.
  

The fpsVR BETA has been updated with the following changes:

[h3]Oculus[/h3]

• A change has been made that will ignore negative frame compositor GPU frame time values ​​for data received from the Oculus API (when using a wired headset or Meta Link for wireless headsets) for some individual frames. This was due to a bug in the Oculus software. Therefore, it is likely that users of the Oculus Rift S and CV1 headsets (most likely not on Quest headsets) could see negative GPU frame time values ​​(at least in one case where this was observed on the Oculus Rift S). The frame time values ​​of the frame compositor are a very small part of the overall GPU frame time, so excluding this value for some frames will not make a big difference. If this bug will be fixed in the Oculus software, then no further changes will be required on the fpsVR side in the future.