FPS Monitor

FPS Monitor

FPS Monitor Not Detecting GPU
Has anyone encountered the same issue? FPS Monitor is unable to detect the graphics card.

Initially, the GPU section only displayed "AMD Radeon" and I thought it might be a priority issue.

Later, I disabled the integrated graphics in the BIOS, and now it only shows ${GPU0/s}
However, MSI Afterburner displays the GPU correctly
and it also appears normally in the Nvidia App .

I checked related discussions in the Steam forums and tried toggling the GPU Wake Up setting on and off, but it didn't help.

If anyone with experience has any ideas, I would really appreciate your help!
Originally posted by eXePert:
Hello!

Some standard scenes use macros like ${GPU0/s} or similar for CPU where the name of the processor or video card is substituted in short form. If you remove /s it will be full, if you change 0 to 1 it will be the second card. BUT, 0 by default is usually a discrete card, but new AMD cards for some reason have naming starting with 0 and therefore in such scenes with this macro ${GPU0/s} shows the name from AMD built-in cards. You can just erase the macro and write any text manually and replace all sensors in the current scene with discrete. Or, just delete this scene after disabling dGPU in BIOS and load it again in Scenes - Scene Manager with Show scene presets checked at the bottom, select it and click New from preset. By default, when loading this scene, the ${GPU0/s} macro should now have a discrete card in it. If you have a 5080, 5090 discrete card, the 5503 release version does not yet support them, go to the FPS Monitor properties in your Steam library and select the branch in the list labeled “Beta-beta”. The program will be updated to version 5504 where there will be all almost all sensors from the new cards.
< >
Showing 1-4 of 4 comments
A moderator of this forum has indicated that this post answers the original topic.
eXePert Feb 13 @ 9:40am 
Hello!

Some standard scenes use macros like ${GPU0/s} or similar for CPU where the name of the processor or video card is substituted in short form. If you remove /s it will be full, if you change 0 to 1 it will be the second card. BUT, 0 by default is usually a discrete card, but new AMD cards for some reason have naming starting with 0 and therefore in such scenes with this macro ${GPU0/s} shows the name from AMD built-in cards. You can just erase the macro and write any text manually and replace all sensors in the current scene with discrete. Or, just delete this scene after disabling dGPU in BIOS and load it again in Scenes - Scene Manager with Show scene presets checked at the bottom, select it and click New from preset. By default, when loading this scene, the ${GPU0/s} macro should now have a discrete card in it. If you have a 5080, 5090 discrete card, the 5503 release version does not yet support them, go to the FPS Monitor properties in your Steam library and select the branch in the list labeled “Beta-beta”. The program will be updated to version 5504 where there will be all almost all sensors from the new cards.
Alvin Feb 14 @ 2:24am 
My current graphics card is a 5080, so this is the cause of the issue.
It seems that the next update will resolve the problem.

Thank you for your reply!
kulka1981 Feb 16 @ 12:47am 
Originally posted by Alvin:
My current graphics card is a 5080, so this is the cause of the issue.
It seems that the next update will resolve the problem.

Thank you for your reply!

Hi have the same problem on my 5080
eXePert Feb 16 @ 6:16am 
Originally posted by kulka1981:
Originally posted by Alvin:
My current graphics card is a 5080, so this is the cause of the issue.
It seems that the next update will resolve the problem.

Thank you for your reply!

Hi have the same problem on my 5080
Read my last post, upgrade to version 5504, select the beta-beta branch.

Next week will probably see a new beta and release with support for new hardware in recent times.
Last edited by eXePert; Feb 16 @ 6:18am
< >
Showing 1-4 of 4 comments
Per page: 1530 50