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)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Help us translate Steam
http://steamcommunity.com/app/25000/discussions/0/1699416432424801049/#c1692662484256265622
Someone asked us about this the other day, but I hadn't heard of a problem like this before then. They weren't seeing mods they had subscribed to from the Steam Workshop, too, so in their case I suspected it was a Steam specific problem (and probably nothing we can actually do anything about on our end).
You could try making sure your Steam downloads aren't paused, and that all downloads have finished. You could try rebooting, and setting Steam to "offline" mode as well.
Edit: running game exe directly works fine.
Time to kick in some bunny teeth.
EDIT: Running the game out of your steam folder as an admin is currently the only way to get this game to run. It's fine now that the game works but it's unnaceptable that a released game has a gamebreaking bug that not everyone necessarily knows how to fix.
EDIT: validating game files, all ok; disabling steam client overlay, no change.