fpsVR News

The fpsVR BETA has been updated with the following changes:

• Adladx64.dll library is temporarily included in fpsVR until most AMD graphics card users update driver to the version that includes this library (i.e. now this file is not only in amd_adlx_test branch as it was in previous update, amd_adlx_test branch will be removed soon)
  
• The frequency of ADLX updates is limited to at least once per second (default for ADL and NvAPI is 2x per second).
  

The fpsVR BETA has been updated with the following changes:

• An additional fallback GPU polling method has been added for AMD graphics cards - AMD ADLX. Several conditions are required for fpsVR to be able to use it:
  
  
  
  • fpsVR failed for some reason (using Apple Boot Camp Software Graphics Drivers; using a laptop with mobile discrete graphics) to initialize the main method currently in use (AMD ADL). This can be seen if you do not see the GPU temperature.
    
  • You have installed the AMD WHQL driver which includes the amdadlx64.dll library. Most likely, it will be included into all drivers released starting from 2023, the first such driver is AMD Software: Adrenalin Edition 23.1.1 for Radeon RX 7900 Series.
    
  
  If you don't want to wait for the driver mentioned above that includes this library for ADLX and you really need it, you can switch to "amd_adlx_test" branch, where this library is already included to fpsVR.
  
• Fixed SteamVR version check, now as originally intended, fpsVR will not run with unsupported older versions of SteamVR giving a warning about switching to a branch with an older version of fpsVR.
  
• In the "Advanced->Interpupillary distance" setting, the calculation of the final IPD was removed, as it worked differently for different VR headsets, for some correct and for some not (the reason for this is a strange behavior of one OpenVR API function).
  
• In settings on the "fpsVR" tab, the option to enable sending error reports now also enables sending beta reports. Previously a request to enable it was displayed only on the "beta" branch when you opened the settings. Error reports contain the same information as beta reports plus some information about the error. The beta report contains some values of key internal application variables and information about the application version, steam version, net framework version, CPU and GPU information. If you want to help fixing bugs please enable this option. Important note - starting from this version beta-reports will be sent not only on the beta branch but also on any other branch, once per each update. If you do not agree - you can disable this option on the "fpsVR" tab (It is turned off by default).
  

The fpsVR has been updated with the following changes:

• Starting with this version, fpsVR works with SteamVR version 1.23.7 or higher; if you are using an older version of SteamVR, switch to previous2 or previous branches.
  
• Pico 4:
  
  
  
  • Fixed an minor issue for Pico 4 (when connected via VD) which caused sometimes pauses in fpsVR statistics recording(FPS indicators were grayed out at that moment) due to inaccurate data being received. The issue is that in the frame data received from SteamVR, the m_flSystemTimeInSeconds field is not aligned to vsync, how it should be.
    
  
  
• Oculus Link/Airlink
  
  
  
  • Starting with this update, if you remove your headset or if you disconnect the headset from SteamVR, the stats are temporarily paused (FPS indicators turn gray) until you resume playing in your headset. Previously, this did not happen correctly, although the time and FPS display froze, but in fact there was no pause. The pause is necessary because in these states fpsVR can not in principle receive statistics from the Oculus API. So probably session stats could have been distorted earlier.
    
  
  
• Nvidia
  
  
  
  • The maximum available video memory size now displays not the total physical memory size of the video card, but actually how much is available for the applications in the system. For example, for RTX4090 total memory size will not be 24GB, but e.g. 23.6GB. Unfortunately, this is not yet available for AMD.
    
  
  
• Added coloring for the video adapter memory usage indicator:
  Orange color - more than 85%.
  Violet color - more than 90% and at the same time reached the maximum value for this game session or about this value.
  
• Added coloring for indicator of RAM usage:
  Orange color - more than 90%.
  Violet color - more than 95%
  
• Added a fallback method to calculate GPU usage and GPU memory usage in case Nvidia and AMD APIs are not initialized successfully (for example, in case of AMD drivers for Boot Camp). This is an old fallback method that was disabled for these GPU vendors in version "2.0", but for this implementation it will initialize only if Nvidia and AMD APIs failed to initialize.
  

The fpsVR BETA has been updated with the following changes:

• Added a fallback method to calculate GPU usage and GPU memory usage in case Nvidia and AMD APIs are not initialized successfully (for example, in case of AMD drivers for Boot Camp). This is an old fallback method that was disabled for these GPU vendors in version "2.0", but for this implementation it will initialize only if Nvidia and AMD APIs failed to initialize. So for the vast majority, this update will not change anything.
  

This build is a release candidate for the main public branch.

The fpsVR BETA has been updated with the following changes:

• Minor changes in logging and error reporting system.
  

This build is a release candidate for the main public branch.