安装 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(越南语)
Українська(乌克兰语)
报告翻译问题





在 Youtube 上 





Going back to how to make a route, if I'm understanding you correctly, would I put something like the below into a terminal block's custom data (let's say it's an LCD), that LCD block needs to be called something like "LCD", only one word.
Then I import it from that block using the IMPORT LCD command?
Breakpoint to Satreus Hub
Takeoff;Breakwater_Forward
GoToPoint;2175496.65419676,921419.718352143,86467.9611505841;1200;250
Landing;234;Satreus_Forward
Wait
This all look correct?
But for now, route management is not entirely obvious. In the waypoints block, you only GPS points. You need to describe the route itself manually in the custom data of any other block (it is very important that its name consists of one word and that there is no block with the same name or number after the name), then you can either generate the route and export it there to edit it, or write it yourself and import it from that specific block. At the time of creating the script, I had little knowledge of how to do this better, but the new navigation system will be able to store routes line by line directly in the waypoints block, and the configuration will be more flexible, and the points themselves will be connected by a graph.
Any guidance or examples would be greatly appreciated