fpsVR News

[p]The fpsVR BETA has been updated with the following changes: [/p][p]General: [/p]

• [p]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:[/p][p]https://steamcommunity.com/app/908520/discussions/0/693124900336015089/ [/p]
• [p]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: [/p][p]https://steamcommunity.com/app/908520/discussions/1/690873811210427123/ [/p]
• [p]Added the ability to add custom comments for a session in the history viewer (desktop version)/ [/p]

[p]Proton (Linux): [/p][p]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. [/p][p]Limitations: [/p]

• [p]CPU/GPU monitoring (load, temperature) doesn't work. [/p]
• [p]fpsVR autostart doesn't work, start it manually.[/p]
• [p]The Audio section in the settings doesn't work. [/p]
• [p]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. [/p]
• [p]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. [/p]
• [p]It's possible that something else isn't working.[/p]

[p]The fpsVR BETA has been updated with the following changes: [/p][p][/p][p]fpsVR[/p]

• [p]Optimization[/p]
• [p]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.[/p]

[p]fpsVR History Viewer, Desktop Version (Reminder: To launch it, use the shortcut in the Documents\\fpsVR folder)[/p]

• [p]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.[/p]
• [p]Several minor interface fixes to make it easier and more intuitive to use.[/p]
• [p]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.[/p]
• [p]New interface elements that do not yet work, as they are under development.[/p][p][/p]

[p]
[/p]

[p]The fpsVR has been updated with the following changes: [/p][p][/p][p]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.[/p][p][/p]

• [p]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).[/p]
• [p]CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab[/p]
• [p]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) [/p]

• [p]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:[/p][p][/p]

[p][/p][p][/p][p][/p]

• [p]Other minor fixes. [/p]

[p]The fpsVR BETA has been updated with the following changes: [/p][p][/p]

• [p]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).[/p]
• [p]CPU temperature polling state settings have been moved from Advanced settings to the "fspVR" tab[/p]
• [p]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)
  [/p]

[p]The fpsVR BETA has been updated with the following changes: [/p][p][/p]

• [p]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:[/p][p][/p]

[p][/p][p][/p][p][/p]

• [p]Other minor fixes.
  [/p]