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
check screenshots above then addon's description
Advanced metrostroi sets the platform indexes based on nearby traffic lights. But on non-russian maps, the signal system can be different, so the 'DefinePlatformPaths' function can set 2 or more platforms with same index. And this causes that UPO and Metrostroi Scoreboard not works well.
So please disable this section with server cvar as you said.
How can we tell russian maps and non-russian maps apart ?
I want to understand the problem and find a solution, it would be nice if you could help me :)
Then make this optional because it causes chaos on non-russian maps.
UPO is connected with config file pa_mapname in metrostroi_data folder
But Metrostroi Advanced may change paths (when it is necessary) without making any change to that config.
The config itself contents some info about paths, signals and stations used by UPO.
That's why UPO can go bad on some maps, unless you generate a new config with proper info inside.
thnx for ur feedback