The fpsVR has been updated with the following changes:

• "Windows 11" tab removed in settings. Old fixes for Windows 11 issue (continuous frame drops) removed.
  
• New fix for Windows 11 implemented. It is fixing Windows 11 multimedia timer resolution (See explanation below).

Valve has already made the same fix, but so far only for the beta version of SteamVR (SteamVR beta 1.22.5+). fpsVR runs this fix on startup and fixes the issue for the non-beta SteamVR too, as well as the Oculus service. You no longer need to activate the Oculus console window. You no longer need to control the position and state of windows (but it's better to keep the game window on top of all the others, manually)

Explanation of issue:
Windows 11 multimedia timer resolution for any process depends on the state of its window. Higher resolution can improve the accuracy of time-out intervals in wait functions, which is very important for the VR frame generation pipeline. Starting with Windows 11, by default if a window-owning process becomes fully occluded, minimized, or otherwise invisible or inaudible to the end user, Windows may automatically ignore the timer resolution request and thus does not guarantee a higher resolution than the default system resolution.

How does fpsVR solve this issue in 1.23 update?
On startup, fpsVR launches the w11fix.exe file (added in this update). This file changes the properties of the SteamVR and Oculus processes, it explicitly disabling the PROCESS_POWER_THROTTLING_IGNORE_TIMER_RESOLUTION property.

This fix is separated into a separate file for the following reasons:
1) This fix uses a new Windows API for Windows 11
2) If you are using Oculus headsets, you can run this file before starting a game session, even for games from the Oculus store, so as no need to start SteamVR and fpsVR. The file is located in the fpsVR root folder.
3) You can freely share this file with anyone who does not use fpsVR.

Warning: w11fix.exe is small, only 15 kilobytes, it is possible that some antiviruses will falsely detect something, if this happens, just add it to your antivirus exclusions.

The fpsVR has been updated with the following changes:

• fpsVR should now better detect and fix the fact that the fpsVR window on the desktop is outside the desktop's working area.

The fpsVR has been updated with the following changes:

Windows 11:

• Features to minimize the appearance of issue with Windows 11 (continuous frame drops). See tab "Windows 11" in settings.
  Important note for Oculus headset users: check settings, you need to enable the Oculus service window for this functionality to work properly.
  If you don't want to use this functionality, you can disable it in the settings (one option is enabled by default). But please pay attention to this guide, which describes recommendations for bypassing this issue manually. The guide also describes the issue itself.
  
• The fpsVR desktop window will no longer open at startup if fpsVR is running under Windows 11. You can still open a window using the tray icon. (Windows 10: Window is also disabled now by default, but the next time you start fpsVR, it will be restored to its previous state).

Note: fpsVR settings available in VR: open the SteamVR dashboard (SteamVR user interface in VR), there will be a small fpsVR button.
fpsVR settings are also available on the desktop: there is a blue icon in the Windows tray, through this icon you can open the fpsVR settings.

Other:

• Complete reworking of the keyboard shortcuts emulation functionality for the desktop utilities overlay (can be enabled in settings, tab "Overlays") and the Utilities tab in fpsVR settings. Visible changes are: the ability to edit keyboard shortcuts, the ability to use the Win key. The ability to emulate keyboard shortcuts when opening and closing the dashboard (for example, to pause video recording of your gameplay while you have the dashboard open). See Utilities tab in the fpsVR settings.
  
• Overlay (full version) now shows more information about current resolution settings
  
• Adjustment range changed: Twist Rate Setting (settings -> Cable Untangling tab -> More settings)
  
• Default value for "Fadeout Angle" changed from 50 to 80 (settings -> Overlays tab -> Other Settings) (Due to the fact that beginners simply do not notice the overlay at the initial settings and do not understand where to look for it.)
  
• Other minor fixes and tweaks

Update: https://store.steampowered.com/news/app/908520/view/3108050393088045025

The fpsVR has been updated with the following changes:

• Added: a notification is displayed in the application window on the desktop that the current VR game/application is using the Oculus API and not OpenVR (SteamVR), in such cases
  
• Added experimental support for Intel 12XXX CPUs (if CPU temperature is not displayed - run "Verify Integrity of Game Files" for fpsVR to update CPU polling service https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335)
  
• Added a new option in the settings (Overlays -> Other Settings) - "Show full VR session time instead of time in specific VR game/app"
  
• Fixed issue when fpsVR got stuck in "standby" mode (fps is displayed in gray color and statistics session did not start). This happens when users of the Index headset quickly switch the screens frequency mode.
  
• For sessions that are over an hour long, the time output format is now displayed as "h:mm"

Known issue: the option to display the full session time is not saving the next time fpsVR is started, will be fixed soon in the next beta.

The fpsVR has been updated with the following changes:

• Fix: removes displaying of reprojection ratio for Vive Pro 2 (since HTC driver probably marks all frames as reprojected, as soon as HTC fixes this and their driver starts sending correct data to SteamVR, fpsVR will show it)

The fpsVR has been updated with the following changes:

• Added: average and maximum CPU/GPU temperatures in history viewer reports
  
• Fixed: the problem described here

The fpsVR has been updated with the following changes:

• fpsVR now allows disabling the center marker without disabling the cable tangle tracking.
  
• By user request the position "Follow to the Bottom Position" added to list of positions for roomscale games/apps (when the controller is turned on). Was removed in 1.20
  
• Fixed: "Follow to the Bottom Position" position for seated games / applications (when the controller is off) did not work correctly under certain conditions.
  
• Changed some text labels on the "Overlays" tab in settings to make it easier to understand the purpose of settings related to the position of the overlay.

The fpsVR has been updated with the following changes:

• Added: Ability to customize any positions when the overlay attached to device (for roomscale games with controllers). Ability to save changes to one of three slots.
  (tab "Overlays" in settings)
  
• Added: Ability to customize positions oriented to SteamVR seated position (for seated games without controllers). Ability to save changes to one of three slots.
  (tab "Overlays" in settings)
  
• Added: Button to temporarily force use of the seated positions (while controllers is on).
  (tab "Overlays" in settings)
  
• Added: Fadeout effect and settings for overlay fadeout (Check "Overlays" tab in settings)
  
• Optimization and minor bug fixes

If you are using an old version of SteamVR (1.12+) then switch to the "previous" beta branch to use fpsVR 1.18.2, current version of fpsVR requires SteamVR version 1.16.8 or higher

The fpsVR has been updated with the following changes:

• Fixed a bug due to which the minimum (0.1) value of the size of the in-game overlay was not saved on restart.
  
• Added workaround: There is a bug in the SteamVR Beta (since version 1.17.1) that causes the fpsVR autorun setting state to always be displayed as disabled, although it might be set to the opposite. Also, this bug does not allow changing this value. The issue is not always observed and depends on the number of installed overlay applications (probably). Valve hasn't responded yet on the report about this issue, so was decided to add a workaround for this issue.