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
If you make sure your game performs well on the Deck then users will have no reason to touch that setting (and in practice people don't use that setting because it makes things look bad). You can also implement variable shading (should it be necessary) in your game, since you know what effect that will have on which parts in the way that the driver's automatic setting doesn't.
For most players, they don't need to change it. But I got some feedback players follow some "long battery life" video, just open it on global settings. They didn't really know about it. And some games are not affected by this option, like "hades", "monster hunter: rise".
If you feel it's a widespread issue, put in your documentation somewhere than half-rate shading makes the text look bad. Job done. Trying to fight the driver is a losing battle, and trying to undo something that the user has explicitly chosen is pretty obnoxious.