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








Not quite sure what you mean; can you post a picture of the issue?
Hi, this is a glitch with Reassembly itself and not specific to the mod... there are ways I can fix it but they cause some undesirable side-effects (particularly, thrusters attaching upside down). I might end up doing it anyway though.
There is a pretty easy way to avoid this happening however - the bug occurs when the end of a thruster (where the flame comes out) is touching another block connection point. If you ensure that the ends of thrusters are not in contact with the connection points of other blocks, it should prevent this from happening.
Hey, sorry for the late reply.
This is most likely caused by a known glitch in the way the game handles thruster output ports - when you have blocks touching the output port of a thruster, there is a chance for the thruster to get stuck in a constant state of being only partially attached to the ship. This prevents regeneration and switching blueprints.
Try making sure that none of your thruster output ports touch any other block (except for another thruster connected to it) and see if this fixes the issue; if not let me know and I'll look into it more.
This is to do with the way Reassembly handles mods; it's not something which can really be fixed. However, if you want to import the default ships from the mod, use the command:
fleetpalette "Avalon Draconis Concord"
in the console to spawn all ships, and then just copy them via command mode as usual.
That's... really weird. The LCA-1 doesn't have this issue?
Not entirely sure what to suggest honestly; I've never heard of this problem before and can't reproduce it on my end. It's not a particularly unusual weapon functionally, so I can't really think of anything which would be producing such bizarre behaviour.
Appreciate the report nonetheless - don't have an answer for you at the moment but I'll keep an eye on this.