Charts Sales Upcoming Patches Events Calculator

New on SteamEvery app, DLC and depot the minute Steam creates it AppsEvery app on Steam, newest change first PackagesSubs and bundles, and what each contains DepotsDepots, manifests and install sizes TagsSteam's user tags and the games under them Developers & publishersCompanies and their catalogues TechnologiesEngines, SDKs and anti-cheat found in the files Change historyEvery PICS changelist as it lands

SignalsNineteen readings of the whole catalogue CompareAny games side by side RecordsAll-time peaks and the days they were set ReportsWeekly and monthly write-ups Alerts & newsroomWatch a game, get told when it moves Steam statusIs Steam up, right now Web API explorerTry the endpoints in the browser

EventsSteam's own events and the sales calendar CalculatorWhat a Steam account is worth, and its pile of shame

/

Sign in

/

SteamPeaks

The ultimate resource for Steam data.

ExploreCharts Sales Sales and fests Upcoming Patches Events Records Trending Signals

DatabaseApps Packages Depots Tags Developers Technologies Change history

ToolsCalculator Compare Search Alerts Steam status API

SiteMethodology FAQ Discord Support Sign in via Steam

Not affiliated with Valve or Steam. Game names and artwork belong to their owners. All times UTC.

Privacy Cookies Fair use Status

fpsVR Beta - 2.3.9210 · fpsVR · SteamPeaks

fpsVR›Events›fpsVR Beta - 2.3.9210

Game update

fpsVR Beta - 2.3.9210

fpsVR · published 18 months ago · build 17795853

All events Players around this date Read on Steam

The fpsVR BETA has been updated with the following changes:

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.

More from fpsVR

Other announcements

Game update19 Jul 2026fpsVR - 2.6.9695The fpsVR 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 th…Game update18 Jul 2026fpsVR Beta - 2.6.9695The 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, ev…In-game event12 Jun 2026fpsVR - 2.6The 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 irrelev…