fpsVR - 2.3.9210

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

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.

Other

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