安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
As for the loop, open the vanilla small airport asset in the asset editor (you might have to create a new one using the airport asset as a base). If you go to add a road, the road arrows will appear above the airport roads, showing you their path. The taxiway makes a loop from the runway, which allows for planes to enter on the long side, and exit on the long side (they look for a runway node which is not attached to any other nodes - i.e. the end of the runway). Then look at the airplane stops, you can see that the node that connects to the taxiway has 3 segments, 1) a taxiway that enters the node, 2) a taxiway that leaves the node, and 3) the plane stop itself.
Segments are, as long as they are connected correctly.
It doesn’t always work, because the plane AI is very finicky. Each situation is different.
Also note that the planestands can be drive through, where the in and out are on different ends of the planestand.
As for the planes despawning, this happens when the plane becomes empty and there is no return path to the runway.
Finally, if you drag a taxiway or runway node with moveit, you can end up breaking the segment, so you will have to delete and replace it (dragging the mid-segment control for arcs should have no effect on that).