Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.
It seems that the next update will resolve the problem.
Thank you for your reply!
Hi have the same problem on my 5080
Next week will probably see a new beta and release with support for new hardware in recent times.