FPS Monitor News

Changes in this new version:

• Fixed bug with "start with Windows" feature
  
• Fixed bug when some hotkey event is not fired if you press Shift, Ctrl or Alt with this hotkey.
  
• Better UWP games compatibility
  
• Better FiveM mod compatibility
  
• Better Vulkan games compatibility
  

Changes in this new version:

• Better compatibility with GTA V mod FiveM
  
• Fixed serious Vulkan API bug which can produce crashes on a game start up
  
• Updated hardware code to fix problems getting sensors from integrated GPU
  

Build #5303

• Fixed "lost" DIMM temperature sensors
  
• Fixed possible infinite hardware initialization
  

Hello everybody! The 5300 release is now available! Run to download 🧲

We have updated our hardware code and FPS Monitor now supports new NVIDIA RTX 3060!

📗 Other changes:

➤ Support for new cards NVIDIA RTX 3060, AMD Radeon RX 6800 and RX 6900 series
➤ Improved monitoring and fixed some sensors on various hardware (CPU, GPU, MB)
➤ Added monitoring of Effective GPU Clock and GPU HotSpot Temperature on NVIDIA GPU and Effective Clock for AMD Navi21
➤ Overlay visibility is saved on a scene change or software shutdown, so if you disabled an overlay and closed the program, it will be invisible on the next start
➤ Added temperature sensors switch Fahrenheit - Celsius (in Sysinfo extension settings)
➤ FpsMonitor will not show an error message when you start its second instance, now it just activates previously started instance
➤ A number of Invisible but very important fixes :)

Hello everybody!

Hardware access module is updated and now our system information overlay can get some Ryzen 5000 sensors ;)
Other changes:

• Added support for fractional min/max values in sysinfo graphs and bars
  
• Added support for fractional values in alerts settings
  
• Fixed Rainbow 6 crash when Vulkan API is used
  
• Fixed Mount & Blade || - Bannerlord detection
  
• Fixed Armored Warfare detection
  

Do you play R6? We have a good news for you. Unfortunately, R6 devs are blocking 3rd party Vulkan layers (we use our own layer to draw overlays in Vulkan-powered games). But there is a workaround to make our layer "eligible" :)
Open software installation folder and subfolder Tools (check a screenshot).



Then open fpsmonvk64.json in any text editor, find the "name" parameter and change its default value from "VK_LAYER_fpsmon" to "VK_LAYER_RENDERDOC_Capture", save the file, run the game.



What we have done? We have changed our layer name to white-listed layer name of RenderDoc software. This software is used by game developers and probably you will not have it and no conflict is expected.