- fpsVR - 2.6.9695 - 19 July 2026
The fpsVR has been updated with the following changes: A bug in fpsVR when getting data via the Oculus API (Oculus Link on Quest or Rift) has been fixed. Previously, it hadn't showed up itself or gone unnoticed. The issue was: after switching the statistics session to "standby mode" after removing the headset and putting it back, fpsVR could get stuck waiting for a long time for data, even though the data was actually arriving.News! fpsVR has passed Valve Frame compatibility testing:Steam Frame Ready: Verified
- fpsVR Beta - 2.6.9695 - 18 July 2026
The fpsVR BETA has been updated with the following changes: A bug in fpsVR when getting data via the Oculus API (Oculus Link on Quest or Rift) has been fixed. Previously, it hadn't showed up itself or gone unnoticed. The issue was: after switching the statistics session to "standby mode" after removing the headset and putting it back, fpsVR could get stuck waiting for a long time for data, even though the data was actually arriving.News! fpsVR has passed Valve Frame compatibility testing (native use in headset):Steam Frame Ready: Verified
- fpsVR - 2.6 - 12 June 2026
The fpsVR has been updated with the following changes: General The font used has been changed from MS San Serif to "IBM Plex Sans". This will allow for further development of the app for Windows and Linux (Proton) with a (nearly) identical user interface for both operating systems.Motion Smoothing modes descriptions have been updated, removing the mention of half framerate, as it's irrelevant to how Motion Smoothing works now.Added the ability to use a keyboard shortcut to disable/enable Chaperone.fpsVR can now display frametimes graphs in the in-game overlay and in a desktop window of arbitrary width. All such graphs have been edited and aligned to the overlay width.Fixed a bug that could cause several frames to be included in session statistics at the very beginning of a session that shouldn't have been included.Linux (Proton) Almost all visual bugs have been fixed. The history viewer…
- fpsVR Beta - 2.6.9658 - 11 June 2026
The fpsVR BETA has been updated with the following changes: The font has been changed to IBM Plex San, it fits better than the one added in the previous update.Motion Smoothing modes descriptions have been updated, removing the mention of half framerate, as it's irrelevant to how Motion Smoothing works now.Added the ability to use a keyboard shortcut to disable/enable Chaperone.fpsVR can now display frametimes graphs in the in-game overlay and in a desktop window of arbitrary width. All such graphs have been edited and aligned to the overlay width.Fixed a bug that could cause several frames to be included in session statistics at the very beginning of a session that shouldn't have been included. Known issue:In the overlay, batteries information for trackers and other devices is currently displayed in a possibly too small font. Don't worry, the font size for this line is planned to be dy…
- fpsVR Beta - 2.6.9655 - 8 June 2026
The fpsVR BETA has been updated with the following changes: General The font used has been changed from MS San Serif to "M PLUS 1p." This will allow for further development of the app for Windows and Linux (Proton) with a (nearly) identical user interface for both operating systems. Let me know in the comments if the overlay interface breaks when displaying the game name in the overlay using non-Latin characters.Linux (Proton)Almost all visual bugs have been fixed. The history viewer (both built-in and its VR version) is now functional. The desktop version of the viewer also works, but you need to launch it through Protontricks or ProtonPlus, which is certainly not very convenient (there's no idea yet on how to improve this). An issue with UTF-8 strings (name of the running VR game, driver name, etc.) has been resolved. In the history viewer, old sessions may be displayed with "squares"…
- fpsVR - 2.5.9649 - 2 June 2026
The fpsVR has been updated with the following changes: GeneralVRAM information has been added to the overlay variant "Small".The "Full" and "Small" variants of overlay now explicitly display "GPU Monitoring: Off" and "GPU Monit. Off," respectively, when the user has disabled GPU monitoring via the fpsVR settings (via the monitoring refresh rate parameter).WindowsAMDA change has been made that will likely resolve the issue of determining which video card to monitor in cases where the AMD driver marks the GPU as "inactive" (presumably).Linux (Proton)NvidiaNVAPI is now used by default, just like on Windows, but under Proton, only VRAM data is available. GPU temperature and load are not monitored. If you want full monitoring, you will need to change the fpsVR launch parameter. More details on this topic are available: https://steamcommunity.com/app/908520/discussions/0/836124807123863711/
- fpsVR Beta - 2.5.9645 - 29 May 2026
The fpsVR BETA has been updated with the following changes: WindowsAMDA change introduced in the previous update allowed correct GPU selection for monitoring in cases where multiple GPUs on a PC. However, for some users, the AMD driver likely returning incorrect PCI Bus and PCI Device values. This caused GPU monitoring to break completely for some users (presumably less than 10% of AMD GPU users, based on testing in the beta branch). This update addresses this issue: if the Bus and Device check fails and a GPU is not found, the first GPU is selected for monitoring (essentially the same as before). This should restore GPU monitoring for those experiencing this issue.Fix was not necessary. The issue likely wasn't caused by changes made in the previous version, but rather by driver behavior on some PCs, most likely due to drivers from Windows Update. New update has been released, without a…
- fpsVR - 2.5 - 26 May 2026
The fpsVR has been updated with the following changes: On first launch after installing this update, Steam may request elevation of Steam privileges (request for admin rights) to update the processor temperature polling service.Windows: The PawnIO driver is now used for CPU monitoring. This driver is signed not only by its author but also by Microsoft. Advantages and disadvantages of using the new driver: This will likely almost completely resolve the issue with antivirus software. Antivirus software reacted to the old WinRing0 driver, but it is no longer used. Temperature display for older AMD FX/Bulldozer processors is no longer supported (possibly temporarily). The PawnIO driver has an issue with these processors. It is expected that over 98% of fpsVR users' PCs will monitor CPU temperature correctly, compared to 96% with the old driver (this estimate is based on testing in the beta…
- fpsVR Beta - 2.5.9641 - 25 May 2026
The fpsVR BETA has been updated with the following changes: Minor corrections and improvements. This update is a release candidate for version 2.5 to the public branch.
- fpsVR Beta - 2.5.9634 - 18 May 2026
The fpsVR BETA has been updated with the following changes: Linux (Proton 10.0-4+):Added automatic detection for Proton launches. There's no point in using the "-proton" launch key. CPU and GPU monitoring has been added. Testing required, feedback are welcome. CPU data is read for the following modules: AMD: k10temp, zenpower; Intel: coretemp. GPU data is read for amdgpu and data from nvidia-smi. All this functionality will work for a native Steam installation (fpsVR is a child process of Steam), for Flatpack installation: you need to open access to the file system.If fpsVR autostart didn't work for you when launching SteamVR, disable this setting and then re-enable it in the fpsVR settings, under "fpsVR," the first option. This issue shouldn't occur anymore.Some visual bugs have been fixed. The default overlay view can now be enabled in the settings, it was previously disabled. This is…
- fpsVR Beta - 2.5.9626 - 10 May 2026
The fpsVR BETA has been updated with the following changes: On first launch after installing this update, Steam may request elevation of Steam privileges (request for admin rights) to update the processor temperature polling service.The PawnIO driver is now used for CPU monitoring. This driver is signed not only by its author but also by Microsoft. Advantages and disadvantages of using the new driver:this will likely almost completely resolve the issue with antivirus software, antivirus software triggered by the old WinRing0 driver, but it is no longer usedtemperature display for older AMD FX/Bulldozer processors is no longer supported (possibly temporarily), the PawnIO driver has an issue with these processors.The history viewer (desktop version) now reads and uses the fpsVR app setting to display temperatures in Fahrenheit. Minor fixes
- Testing CPU monitoring with the new driver PawnIO - 7 May 2026
Testing in this format has been completed. Thank you to everyone who participated. Please return to the beta or public branch.I'm asking YOU for help testing the new PawnIO driver, which will replace WinRing0. The new driver (PawnIO) is signed not only by the driver's author but also by Microsoft, which fundamentally changes the situation and will likely almost completely resolve the issue of antivirus software triggering on unsafe driver (WinRing0).Why not just push the update to the beta branch? I decided to play it safe and do it in a more controlled manner.Instructions:1) Switch to the pawnio_cpu_monitoring branch (via the application properties in the Steam library), wait for the download to complete.2) Launch SteamVR and fpsVR. Steam will likely request elevated privileges (administrator privileges) to update the CPU monitoring service files.3) Quit fpsVR.4) In the comments to thi…
- fpsVR Beta - 2.5.9619 - 5 May 2026
The fpsVR BETA has been updated with the following changes: General: Detailed graphs (per-second data) have been added to the history viewer (desktop version), the same graphs as in the built-in fpsVR history viewer. As a reminder, you can find the history viewer shortcut in the "Documents/fpsVR" folder.When using SteamVR with Steam Link and VD, the "FPS:" field in the in-game overlay will now display as "FPS (PC):" (but not in all overlay options, only where there is enough space). This is to better understand that fpsVR can only calculate FPS for PC side. For example, in Steam Link, you can see a situation where you have a stable 90 fps at 90Hz but a lot of dropped frames. This could be caused by your router or the VR headset, for example. The SteamVR statistics used by fpsVR will mark all frames as "used", despite the fact that some of the frames were dropped according to statistics.…
- fpsVR Beta - 2.5.9560 - 5 March 2026
The fpsVR BETA has been updated with the following changes: General: Added an option to force Chaperone to be disabled. This will likely help with VR headsets for which the Chaperone disable option was not originally intended. More details can be found here:https://steamcommunity.com/app/908520/discussions/0/693124900336015089/ Fixed an issue where the overlay would not hide under specified conditions if the controller position was not linked to the headset or controllers. More details can be found in this thread: https://steamcommunity.com/app/908520/discussions/1/690873811210427123/ Added the ability to add custom comments for a session in the history viewer (desktop version)/ Proton (Linux): Experimental support. You can now run fpsVR under Proton. To do this, add the -proton launch key (and only this key) to the fpsVR properties in your Steam library. Limitations: CPU/GPU monitoring…
- fpsVR Beta - 2.5.9436 - 1 November 2025
The fpsVR BETA has been updated with the following changes: fpsVROptimizationAdded the "Try Use Oculus API for stats (Quest Link)" option to the "fpsVR" tab in the settings. When using Quest Link, statistics were collected via the Oculus API by default (unless the user had configured the Oculus API to be blocked using special software or in the SteamVR configuration). To address some possible issues, added this option, allowing you to switch to collecting statistics exclusively from SteamVR. There was at least one strange case where the statistics from Oculus API were broken. If you suspect something is wrong, you can also try this option.fpsVR History Viewer, Desktop Version (Reminder: To launch it, use the shortcut in the Documents\\fpsVR folder)A dark theme has been added. By default, the history viewer will now detect the current theme installed in Windows 10/11 (this may not work f…
- fpsVR - 2.4.9380 - 6 September 2025
The fpsVR has been updated with the following changes: 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.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…
- fpsVR Beta - 2.4.9380 - 6 September 2025
The fpsVR BETA has been updated with the following changes: 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 launchi…
- fpsVR Beta - 2.4.9346 - 7 August 2025
The fpsVR BETA has been updated with the following changes: 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:Other minor fixes.
- fpsVR - 2.3.9210 - 31 March 2025
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…
- fpsVR Beta - 2.3.9210 - 21 March 2025
The fpsVR BETA has been updated with the following changes: 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.
