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










AI waypoints that have issues include, going entering Ballast C hatch, (ladder waypoint is too close to the hatch) fixing the drainage in the brig (AI tries accessing it from the floor below, easily solvable by deleting the waypoint on the top of the ladder), and going down from the hatch to the left of the upper airlock when autodoors aren't working (same issue as in ballast c) and lastly going in/out of shuttle/shuttle ballast, but despite these, this sub is amazing.
It's a bit tricky, and I had similar problems when developing it. The important detail is that the sequence in which you connect the railguns matters - if you have one periscope and two railguns, the one connected last (position, not trigger) in the editor will be displayed.
That's the initial setup, to make sure the right gun is selected when loading the sub - afterwards the connections can be swapped with relays (in my case, it uses some sort of timing mechanism to swap after 2.5 seconds after firing). The same principle applies when connecting the periscope via relays, the last one will show first (I think I also switched the initial state of the other relay off in the editor to make sure).
It's been a while since I worked on it, and I'd need to look into it again to give a full explanation. I might do a standalone version of the circuit, but I don't have much time for baro stuff at the moment.