fpsVR news & patch notes

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

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 (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" instead of the required characters, this cannot be fixed.

  Reminder: if you're using fpsVR on Linux, don't forget to check the information in the first post in this thread: https://steamcommunity.com/app/908520/discussions/0/836124807123863711

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 dynamically adjustable for the next update, depending on the number of devices.

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" instead of the required characters, this cannot be fixed.

  Reminder: if you're using fpsVR on Linux, don't forget to check the information in the first post in this thread: https://steamcommunity.com/app/908520/discussions/0/836124807123863711/

The fpsVR has been updated with the following changes:

General

• VRAM 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).

Windows

• AMD

  • A 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)

• Nvidia

  • NVAPI 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/

The fpsVR BETA has been updated with the following changes:

Windows

• AMD

  • A 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 version change, which will likely fix the issue.

Linux (Proton)

• Nvidia

  • NVAPI 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/

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.

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.

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 a temporary fix, as the fonts used need to be changed. So, visual glitches are still possible. UTF-8 character support is still missing for Proton, this will be fixed in the next updates (stay on beta branch if you are using fpsVR on Linux).

• Other minor fixes

For more information on Linux requirements and a discussion, see the thread: https://steamcommunity.com/app/908520/discussions/0/836124807123863711/

Windows:

• Correct GPU detection on a PC with multiple Nvidia GPUs or multiple AMD GPUs. Testing required, feedback are 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 allows monitoring of your multiple GPUs via the ADL API (most often the case with AMD GPUs). However, ADL may not be available with certain drivers. In these cases, ADLX is used. If the GPUs are older, only the first GPU will be detected. If the GPUs are modern (not legacy), then there should be no problem detecting the correct GPU used for VR, but again it depends on the driver, the latest AMD drivers would be preferable here.

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 used

  • temperature 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 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 this news, post the following message:

- your CPU model

- the text of the file Program Files\\fpsVR\\log.txt (this is the folder where the monitoring service is installed, not fpsVR itself). If the file is very long and there isn't enough space to show it in its entirety in the comments, no problem. Post the first part that fits and trim the excess from the end.

- if something didn't work correctly for you, describe the problem in your own words.

Thanks in advance to everyone who participates. I'll update this post once testing is complete.

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. Unfortunately, the data available from SteamVR was created with wired headsets in mind, but Valve apparently has no plans to introduce any new features to these data structures. My attempts to request expanded functionality/fixes for the statistics were unsuccessful.

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 (load, temperature) doesn't work.

• fpsVR autostart doesn't work, start it manually.

• The Audio section in the settings doesn't work.

• The built-in VR history viewer doesn't work. This is likely a temporary issue, and it will be possible to adapt it to Proton in the future.

• The data set variant that is displayed by default in the overlay is disabled. If you select it, the next option on the list is automatically selected. This is due to incorrect rendering. Emulation under Proton distorts the overlay formatting. May need to redo everything.

• It's possible that something else isn't working.

The fpsVR BETA has been updated with the following changes:

fpsVR

• Optimization

• 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.

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 for very old Windows 10 builds) and switch the theme accordingly. You can also force either a dark or light (old) theme in the settings.

• Several minor interface fixes to make it easier and more intuitive to use.

• In the graph legend, "Max. CPU/Thread Usage" has been changed to "Busiest Core." This will make it clear that this metric on the graph shows the distribution of load on the busiest core. In the next updates, I plan to make the same fix in the VR version of the history viewer.

• New interface elements that do not yet work, as they are under development.

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 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).

• CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab

• 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)

• 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.

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 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).

• CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab

• 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)

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.

• 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.

• 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....

• 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.

• 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%.

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.

• Fixed a bug with a sound warning that occurred when starting fpsVR.

• 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 (don't worry, 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%.

• 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.

• 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).

• 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

• Added support for displaying the temperature for AMD Zen 5 processors. The application version has not changed, but one library has been updated. For the update, Steam may request elevated permissions (admin rights) to update the files of the service that polls the processor temperature. To complete the update process, you need to agree (unfortunately, this will happen for everyone, even those who do not have an AMD processor in their system).

• The app has been updated to use the latest version of the OpenVR API: OpenVR SDK 2.5.1. Therefore, this version of fpsVR requires SteamVR version 2.5 or higher.
• When the SteamVR keyboard appears, the fpsVR overlay will now disappear to avoid causing unwanted effects. A recent SteamVR update had a change that prevents applications from receiving controller position when the SteamVR keyboard is active. Because of this, fpsVR would switch the overlay position for games without controllers that was selected in the settings, which could interfere with the use of the SteamVR keyboard
• Fixed other minor bugs that did not affect the use of the application.

• The app has been updated to use the latest version of the OpenVR API: OpenVR SDK 2.5.1. Therefore, this version of fpsVR requires SteamVR version 2.5 or higher.
• When the SteamVR keyboard appears, the fpsVR overlay will now disappear to avoid causing unwanted effects. A recent SteamVR update had a change that prevents applications from receiving controller position when the SteamVR keyboard is active. Because of this, fpsVR would switch the overlay position for games without controllers that was selected in the settings, which could interfere with the use of the SteamVR keyboard
• Fixed other minor bugs that did not affect the use of the application.

• Added new grapths in the built-in history viewer. {STEAM_CLAN_IMAGE}/33339702/7b6fe60d995d2a984b39e9ac5d62b65e804e80b4.png
• Changes and fixes to the beta and error reporting system.

• Added new grapths in the built-in history viewer. {STEAM_CLAN_IMAGE}/33339702/7b6fe60d995d2a984b39e9ac5d62b65e804e80b4.png
• Changes and fixes to the beta and error reporting system.

• Fixed an issue: when starting the game, there is a high GPU or CPU frametimes, sometimes even up to 100ms. The source of the problem was the OpenVR API function: WaitFrameSync. fpsVR has been using it for a long time to synchronize work, it is not clear why the problem appeared recently. There may have been some changes in SteamVR or the Nvidia driver that somehow caused the issue. This remains to be seen. A workaround has now been implemented without using this API function.
• Fixed minor visual bugs in the history viewer (in the built-in version).
• A button has been added on the “General” tab in the settings, that allows you to select an application for which you want to change the “Per-Application” setting, for applications that were launched earlier (since the last time SteamVR was launched). For example, this will allow you to change the rendering resolution for the application you just closed. The button appears after the first VR application is launched.

• Fixed a bug where fpsVR could function incorrectly if the user enabled saving history for the desktop version of the history viewer, but his Documents folder was damaged or inaccessible for some reason (after incorrect removal or installation of OneDrive, incorrectly configured access, etc). In a future update, I plan to make it possible for such cases to select an alternative path for saving history, for example, to the AppData folder.