安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题




Alternatively you can copy the standard demand curve and change the copy to something simple like this: origin 50% from e.g. 8:00 to 19:00, 0% from e.g. 2:00 to 6:00, gradual increase/decrease between those hours. As destination, 100% from 7:00 to 18:00, 0% from 0:00 to 3:00, gradual increase/decrease between those hours. Distance demand needs to be predominantly local, sharply reducing past the distance to the furthest points in the city and probably 0% at 50-100 km distance. See how it works and then you can tweak as needed.
(sorry messed up the version)
Did you set up enough population? If you operate at 100% global demand setting (default), this is intended to translate to number of pax equal to 25% of population over 24 hours in a typical large city and typical demand curve. If you want to see 10,000 actual pax going out of the airport by train, I would set up POI at 40,000. If you operate at higher or lower global demand setting, you would want to adjust these numbers further.
Also, airport as destination competes with other destinations. So in general you would expect to see fewer people go to the airport than originate from the airport if the airport demand POIs are the same for origin and destination. This is why I set up in the example above origin demand at 50% max and destination demand at 100%. So in the above paragraph, if you get 10,000 pax spawned in airport, you may only see 5,000 go to the airport. To address this, further increase POI e.g. to 80,000 and reduce the origin demand to 50% or less.