fpsVR Patch Notes — May 26, 2026
Aggregated from Steam, cross-tracked with Battle.net coverage on GamePatchNote.
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 branch, and does not take into account that the old driver was blocked by antivirus software for many users, meaning the old driver was much worse).
The page for enabling or disabling CPU monitoring has been removed from the settings. It may return in a future releases after a redesign. In the meantime, you can control CPU monitoring by enabling or disabling the startup type of the Windows service "fpsVR Service - CPU Temperature Counter."
Correct GPU detection for monitoring on PCs with multiple Nvidia or AMD GPUs. Testing is required, your feedback is welcome.
Nvidia - Detecting the correct GPU will likely work with all GPU models and drivers.
AMD - Detecting the correct GPU will likely work with all GPU models if your current driver supports monitoring multiple GPUs via the ADL API (most often with AMD GPUs). If only ADLX is available, fpsVR will monitor the first GPU.
Linux (Proton 10.0-4+):
Added support for running fpsVR with Proton 10.0-4+ on Linux. Added automatic startup detection for Proton (use the -proton launch key if it doesn't work).
Added CPU and GPU monitoring on Linux. CPU data is read for the following modules: AMD: k10temp, zenpower; Intel: coretemp. GPU data for amdgpu and data from nvidia-smi (likely not working at the moment, testing required). All this functionality will work for a native Steam installation (fpsVR is a child process of Steam), for Flatpack installation: you need to open file system access (via the Z drive).
For more information on Linux requirements, known issues, and the discussion, see the thread: https://steamcommunity.com/app/908520/discussions/0/836124807123863711/
General:
fpsVR history viewer, desktop version (reminder: to launch it, use shortcut in the Documents\\fpsVR folder)
Dark theme added. By default, the history viewer will now detect the Windows 10/11 theme (this may not work for very old Windows 10 builds) and switch to the appropriate theme. You can also force either a dark or light (old) theme in the settings.
Several minor interface fixes have been made to make it easier and more intuitive to use.
In the graph legend, "Max. CPU/Thread" has been changed to "Top Loaded Core." This will make it clear that this metric on the graph shows the distribution of load on the top-loaded core.
The history viewer now reads and uses the main fpsVR program setting to display temperatures in Fahrenheit.
Detailed graphs (per-second data) have been added to the history viewer, which are the same graphs as in the built-in fpsVR history viewer, i.e., its VR version.
Added the ability to add custom comments for a session in the history viewer (desktop version).
When using SteamVR with wireless HMD, the "FPS:" field in the in-game overlay will now display as "FPS (PC):" (but not in all overlay variants, only where there is enough space). This is to better understand that fpsVR can only calculate FPS for PC-based gameplay. For example, in Steam Link, you might see a situation where you have a stable 90 fps at 90Hz but are experiencing a lot of dropped frames. This could be due to, for example, your router or the VR headset itself. The SteamVR statistics used by fpsVR will mark all frames as "used," even though the same statistics show some frames as dropped.
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 "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.