安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
First the fact that the steam input settings doesn't reflect in your game makes me think you might not have steam input enabled by default (which doesn't prevent steam itself from detecting it, it just doesn't use it in games), check for each game by going to your library game page -> properties -> controller and see if it is enabled for your controller brand.
Wether or not it is enabled, you can try to test if turning it on (if it wasn't already enabled) or off (if you were actually using it) change anything.
If for some reason steam input actually doesn't work either you try to find in your game settings if you can change the mapping (for example Tunic does that and doesn't need to rely on steam input) or you try to change the mapping of your controller from your mac settings.
As for steam overlay not working for some games, it is most likely due to the game itself, when the game itself has a launcher (like the witness, I don't know for Gone Home), which can cause steam functionalities to stop working (like the overlay, and even steam input) simply because they are not included in the actual game.