The fpsVR BETA has been updated with the following changes:
Linux (Proton 10.0-4+):
Added automatic detection for Proton launches. There's no point in using the "-proton" launch key.
CPU and GPU monitoring has been added. Testing required, feedback are welcome. CPU data is read for the following modules: AMD: k10temp, zenpower; Intel: coretemp. GPU data is read for amdgpu and data from nvidia-smi. All this functionality will work for a native Steam installation (fpsVR is a child process of Steam), for Flatpack installation: you need to open access to the file system.
If fpsVR autostart didn't work for you when launching SteamVR, disable this setting and then re-enable it in the fpsVR settings, under "fpsVR," the first option. This issue shouldn't occur anymore.
Some visual bugs have been fixed. The default overlay view can now be enabled in the settings, it was previously disabled. This is a temporary fix, as the fonts used need to be changed. So, visual glitches are still possible. UTF-8 character support is still missing for Proton, this will be fixed in the next updates (stay on beta branch if you are using fpsVR on Linux).
Other minor fixes
For more information on Linux requirements and a discussion, see the thread: https://steamcommunity.com/app/908520/discussions/0/836124807123863711/
Windows:
Correct GPU detection on a PC with multiple Nvidia GPUs or multiple AMD GPUs. Testing required, feedback are welcome.
Nvidia - Detecting the correct GPU will likely work with all GPU models and drivers.
AMD - Detecting the correct GPU will likely work with all GPU models if your current driver allows monitoring of your multiple GPUs via the ADL API (most often the case with AMD GPUs). However, ADL may not be available with certain drivers. In these cases, ADLX is used. If the GPUs are older, only the first GPU will be detected. If the GPUs are modern (not legacy), then there should be no problem detecting the correct GPU used for VR, but again it depends on the driver, the latest AMD drivers would be preferable here.