fpsVR News

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.
  

The fpsVR BETA has been updated with the following changes:

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

The fpsVR has been updated with the following changes:

• An additional reserve GPU polling method has been added for AMD graphics cards - AMD ADLX. Several conditions are required for fpsVR to be able to use it:
  
  • Due to unstable operation of the video card driver, fpsVR could not initialize the main method. But there is no guarantee that the reserve method will help in this case. A sure sign of this: if the temperature and the amount of VRAM used were previously displayed, and at some point it stopped. In such cases, I recommend restarting the PC.
    
  • fpsVR failed for certain reasons (using Apple Boot Camp Software Graphics Drivers; using a laptop with mobile discrete graphics) to initialize the main method (AMD ADL).
    
  • In order for ADLX to work, amdadlx64.dll must be present in the system. Most likely it will be included in all AMD drivers released starting from 2023, the first such driver is AMD Software: Adrenalin Edition 23.1.1 for Radeon RX 7900 Series. The adladx64.dll library is temporarily included with fpsVR until most AMD video card users update the driver to a driver version that includes this library.
    
  
  
• The frequency of data updates using ADLX is limited to a period no more than 1 time per second (by default for ADL and NvAPI 2 times per second).
  
• Fixed SteamVR version check, now as originally intended, fpsVR will not run with unsupported older versions of SteamVR giving a warning about switching to a branch with an older version of fpsVR.
  
• In the "Advanced->Interpupillary distance" setting, the calculation of the final IPD was removed, as it worked differently for different VR headsets, for some correct and for some not (the reason for this is a strange behavior of one OpenVR API function).
  
• In settings on the "fpsVR" tab, the option to enable sending error reports now also enables sending beta reports. Previously a request to enable it was displayed only on the "beta" branch when you opened the settings. Error reports contain the same information as beta reports plus some information about the error. The beta report contains some values of key internal application variables and information about the application version, steam version, net framework version, CPU and GPU information. If you want to help fixing bugs please enable this option. Important note - starting from this version beta-reports will be sent not only on the beta branch but also on any other branch, once per each update. If you do not agree - you can disable this option on the "fpsVR" tab (It is turned off by default).