JankoWeber: I chose the title of this thread because 64 bit operating systems
almost always use newer versions of glibc than 2.19.
I think glibc 2.19 is from 2014, 2.17 from 2012. On the
shop page it says that GearCity was released
on January 14, 2022. That's why I thought
this was a mistake.
I started GearCity in 2010. It was released in Steam Early Access in 2014. And I kept it in Early Access while the game was in active development. When I started working on a different game, GearCity left Early Access. That was in 2022.
The 32-bit Linux build is built in Slackware 14.1. That uses glibc 2.17.
The 64-bit Linux build is built on Valve's Ubuntu 14 runtime. That uses glibc 2.19.
GOG, who maintains the store page copied the system requirements from my Steam page. However, GOG does not distribute 32-bit Linux builds. GOG's internal distribution systems are 64-bit Linux only. So I had to get the 32-bit build uploaded to the "Extras" system, as recommended by other users.
That is done now.
So the 64-bit Linux requirement is glibc 2.19+. The 32-bit Linux requirements are glibc 2.17 to glibc 2.33. Newer versions of glibc have removed functions which the 32-bit build is built against. There are no plans to update the 32-bit Engine or build environments for the base game. There is a community funded Free DLC in the works. It will take several years to complete, but it will likely have a 32-bit Linux build built against more modern glibc.
JankoWeber: While searching for newer demo versions I came across the
OpenBeta 1.23 for MS-Windows and this one works worse
Well, using WINE to play the Windows version should be moot now. The 32-bit Linux build is uploaded to GOG. It is built on the same platform and uses the same libraries as the 1.16 Linux Demo you tried before.
JankoWeber: The translation into German is
incomplete.
Translations are community-made, and version 1.23 is 6 years old. There has been a lot of progress since then, but it won't be perfect. I don't speak German. There are over 600 pages of text in GearCity, and I can't afford to have it professionally translated. So it's only as good as the fans of the game can do in their spare time.
JankoWeber: Some windows contain no text. In the menu it is
often not clear which button should press next. After I opened
the safe door in the office the mouse control no longer worked.
How should I know if this is better with newer versions. *?
These all sound like issues with WINE on your system more so than anything.
JankoWeber: "Our complex AI requires a lot of computing power."
I use Pentium Dual Core E2180, GeForce GT710 and 2GB RAM
Is the processor fast enough?
How much computing power did comparable games need
30 years ago?
The game is single-threaded. For full 300 AI, with a player managing 100+ different vehicle models, even a
Intel Core i9-14900K will have 30-second turn times later in the game.
But if you're playing 300 AI, and keep yourself at a modest 10-20 models, you should be able to do 30-60s late-game turn times with your Dual Core.
And if that's too much, you use fewer AI. So, it's all about expectations.
The game was mostly written on a Phenom 9550, which is only about 10% faster than your Dual Core. I played the game for years on that machine using full AI with no problems.
JankoWeber: I read about this game on the Internet:
"I am now in the year 1960 and the game is getting slower
and slower. One round (1 month) now takes about 1-2 minutes."
Then I'll probably have to wait at least 5 minutes.
"The fields/windows for the texts are much too small."
I remember that I also had this problem.
It is particularly shocking for me when it is written:
"You don't really recognize the correlation between
cars produced, cars sold and the profit or loss."
If that is the case...
...then it makes no sense for me to play GearCity. *!
Please remember that many of these reviews were written years ago. The game was in constant development for 12 years. A commercially released for 8 of those in-development years. So a lot of it will be out of date. If turn-times are too slow for you, use fewer AI. If the text is too small, increase the font size or resolution scaling in the game. There are also many people who don't take the time to learn the UI/System, watch the videos, follow the tutorials, read the manual, etc. So, they find the game confusing or lacking feedback.
Ultimately, it's your choice if you want to buy the game or not. Your original posts were about the availability of the 32-bit Linux build. I went through the process to get it and the 32-bit OSX ports up on GOG via the Extras system. I don't maintain the 32-bit Demos on my website, but the engine is the same as the 1.16 Demo you played. So if the v1.16 32-bit Linux build worked, the v2.0.0.10 32-bit Linux build should work. As for trying out newer versions of the game, if you don't have access to a 64-bit machine, perhaps watch a few playthrough videos on Youtube. While I do plan on maintaining 32-bit builds for the base game, there are no plans to update the demos for 32-bit builds.