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
I should know better than to ask a closed end question.
64bits... yeah, I second that. Even more than 2 years later, nothing has happened 😒
I have a 32GB machine and I expect any less than trivial game to be 64 bits nowadays. When programmed properly, such a 32 to 64 migration can't be that difficult (I know reality has a lot of pitfalls, such as libraries used only supporting 32 bits, etc. Yes, I have developed software for a living.)
I imagine there are those that won't even consider buying 32b products these days which equals lost sales.
I also wonder if the real issue with Command the commercial version not being released as 64b is that the professional and military customers are actually the pub/devs bread and butter and gamers are just the icing on the cake (i.e. we're not the main source of revenue for them). Getting the military to buy in to switching over to 64b and the cost and hassle of supplying it to their users may be the real reason for the devs reluctance to even consider the switch let alone discuss it with the gaming customers.
We can hope 🤞 that some day the switch is made though I don't recommend holding one's breath waiting for it. 😒
Exactly like you say.