Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
1) The setting they have is "do you support 64-bit, yes/no?" and the default is "no". What they should have done is have a setting with 4 values: unknown, 32-bit only, 64-bit only, 32-bit and 64-bit, with the default being 'unknown'.
That way, the UI could have more cleanly shown which games are actually incompatible with your system, and which the developer just never entered data for.
2) Crowdsourcing the data. Steam knows if the overlay is injected into a 64-bit process, or if a 64-bit process is using the Steamworks API. They could have had the client report back the bitness of games, to fill in the data where the developers didn't.
3) They could have scanned over the game files they have on their own servers to detect what CPU architectures are supported by the executable files in the install of a game. This information is available in the headers of the Mach-O file format used by Mac executables. If every executable in a game's files has 64-bit support, you can go ahead and mark that game as having 64-bit support without any worry.
But they didn't, so here we are.