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



The Steam.app you download and put in your /Applications folder is a stub that just contains a copy of the Steam bootstrapper. When you run it, it basically just immediately hands off control to another copy of the Steam bootstrapper in "~/Library/Application Support/Steam", downloading that copy first it doesn't already exist. That second bootstrapper installs the rest of the client.
I imagine there's probably a good reason for this slightly convoluted structure, probably something to do with permissions, but anyway, the upshot is that the copy of the bootstrapper installed into /Applications isn't autoupdated, it's the same one you got when you first installed Steam. It's also what the System Report, er, reports on. Because it's old and it doesn't get updated, it's still 32-bit
The actual Steam client which is installed into "~/Library/Application Support/Steam" is actually 64-bit. You can confirm this by looking at the actual running process in Activity Monitor.
Now, the old bootstrapper in /Applications and the new one in "~/Library/Application Support/Steam" is still the same component that does the same job, so the fix if you really want the thing in System Report to say 64-bit is to just copy the new bootstrapper executable (it's called "steam_osx") over the top of the old one.
I've done this myself on my own install, and voilà:
https://steamuserimages-a.akamaihd.net/ugc/949598805522084109/36B37ED24C8918C33FC1939C2EFD9273BFFD9E07/
So no, Valve aren't going to drop support for Mac in 10.15, because all the work, apart from the moral equivalent of running a one-line bash script to copy one file, has been done already.
Can anyone here make a standalone non-tutorial solution/version to this problem and upload the file type to Google Drive, Mega.nz, or MediaFire so that it's easier for user to make Steam 64-Bit on macOS?
-------------------------------------
The one-line bash script is:
Copy and paste into the terminal. And because you should never c&p a command into your terminal before understanding what it does:
cp: copy a file from source to destination
-ipv: Prompt before overwriting (i), preserve all file metadata (p), be verbose and show what files are being copied (v)
~/Library/Application\ Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steam_osx: the location of the new 64-bit steam_osx
/Applications/Steam.app/Contents/MacOS/steam_osx: the location of the old 32-bit steam_osx we're going to overwrite.
If it is really just as simple as (essentially) a one-line bash script, WHY IS THIS STILL HAPPENING at all?? It really does cast aspersions on the capabilities of the Valve developer team that they couldn't have one developer spend one afternoon crafting an auto-update solution that *does* execute the actual—not moral—equivalent of a one-line bash script to copy one file, to actually fix the problem.
If it's simple enough for almost anyone to do it, yet no-one at Valve yet has, that is a serious, and damning, statement about their developers.
I wonder if this is possible on Valve's developed and published games on macOS versions made from Snow Leopard up to Mojave, not Catalina and later releases, by using CS:GO's 64-bit macOS executable as a source/replacement. Only time will tell.