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
Make sure you guys check out the Troubleshooting FAQ, 95% of all issues people have at startup are fixed by those solutions.
Click the steam-play button; a window opens (with latest news on the left and an automation-play button on the bottom-right.
When I click that play button, a new window opens and the big automation rotating wheel just rotates forever (and there's an automation tool-tip shown across the screen)
The little steam-play window pop-up never opens, so maybe it's waiting for that?
In task-manager automation is shown as running and memory-use just keeps rising.
I then click [alt-f4] which closes the automation window. After a moment steam shows the game as no longer running.
I then click the steam-play button again, and again the first automation window opens (with the news and the play button)
But this time, when I click the automation-play button, the game actually starts.
It gets to the same window (the big rotating wheel and the tool-tip) but only sits there for a few seconds (And this time the steam-play window does pop-up) before the actual game-window opens (with the sandbox option and settings and so on)
I don't know if it is related to the OP's issue, but thought I would just mention it.
My system is this:
Windows 10 Home 64-bit, i7-6700 CPU @ 3.40GHz, 16384MB RAM
NVIDIA GeForce GTX 980
I have .net 4.7.2, which was the only thing in the pinned trouble-faq that seemed to relate to the issue I have.
Anyway, I can get the game running by going through this 'double start-up' procedure, so it's not a big issue for me. But as said; maybe there's something in this post that helps the game-author along in the trouble-shooting :)
I can confirm you are correct :)
It did in fact start after what I thought was a 'hang'.