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
In some phases i just disable auto-assign temporarily to avoid the issue.
Same thing sometimes happens with the Demolition Office aswell.
Now when batch starting constructions in one city that should be out of range of the other offices, some offices from the other cities assign themselves. They do not share a construction office group.
It seems the distance is calculated wrongly or the distance filter is not applied in the auto search logic.
of course this could be micro managed away, but would be great when the autosearch wasn't broken aswell
Not a great result.
Also groups should not matter anyway, as CO assignment tool was closed all the time and not used (seware substation was assigned to group 5 BEFORE allowing autosearch for group 3).
Yes, after ca 20 tasks in mind, CO stops searching alltogether usually. Which then can lead to further slowdowns, because sometimes each CO finds different tasks and thus in larger building sites are not always all offices assigned together to some buildings. So CO assignment tool is still needed anyways.
At that point I am turning of autosearch because I need to manage sites anyway and turning off autosearch actually speeds up things alltogether