fpsVR News

The fpsVR BETA has been updated with the following changes:

• Added experimental 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.
  
• The timer function now announces the end of the timer once, without any advance warning. This is not the final version, most likely there will be changes in the next beta version.
  
• Changed the icon used in the SteamVR dashboard, more suitable due to changes in the SteamVR interface since version 2.0
  

Hi,
Due to possible incompatibility, branches(betas) Previous and Previous2 have been removed in order to force the transition to the latest version of fpsVR (because some people use SteamVR 2.0 and old versions of fpsVR). If you are still using an old version of SteamVR, then try new recreated branches(betas) of fpsVR:
previous_ (for SteamVR 1.16-1.22)
very_old (for SteamVR 1.12-1.15)
But do not switch to it if you have SteamVR version 2.0 or higher.
Use main branch (public) with SteamVR 2.0 or higher

PS There haven't been any fpsVR updates for a long time, but I promise there will be some soon :)

The fpsVR has been updated with the following changes:

• Avast users have encountered that this antivirus blocks the driver launch (hardwareprovider.sys file) 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: "WingRing0". 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 Avast intercepts the call to start the driver, and this happens before the permissions are changed, and blocks it. Now, in order not to bother Avast users with warnings, if there are two blockings in a row, fpsVR will stop trying to start this driver and the CPU polling service (CPU temperature will not be displayed in fpsVR in this case). You can try to start CPU polling again by resetting the blocking counter for example if you decide to add an exception (it would be unfair of me to recommend this action as Avast cannot add an exception for this driver only, so I do not recommend it) or if you change antivirus (which most likely check it after starting the driver or do not do it at all). You can reset the counter on a new page in the fpsVR settings under advanced settings.
  

The fpsVR BETA has been updated with the following changes:

• Avast users have encountered that this antivirus blocks the driver launch (hardwareprovider.sys file) 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: "WingRing0". 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 Avast intercepts the call to start the driver, and this happens before the permissions are changed, and blocks it. Now, in order not to bother Avast users with warnings, if there are two blockings in a row, fpsVR will stop trying to start this driver and the CPU polling service (CPU temperature will not be displayed in fpsVR in this case). You can try to start CPU polling again by resetting the blocking counter for example if you decide to add an exception (it would be unfair of me to recommend this action as Avast cannot add an exception for this driver only, so I do not recommend it) or if you change antivirus (which most likely check it after starting the driver or do not do it at all). You can reset the counter on a new page in the fpsVR settings under advanced settings.
  

The fpsVR has been updated with the following changes:

• Fixed bug where fpsVR crashed on headsets with screen refresh rate higher than 150Hz.