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








I think the least intrusive fix for this is to force the projector to remove blueprint before adding the ship to it, all other projectors on the ship wouldn't be affected...
(Edit: actually I am already removing the vanilla stored projection but not this mods' stored projection, that's certainly something that I'll be fixing)
Still, someone could still abuse it by using 2 projectors and ping-pong stack stored projections? xD
Not sure how to deal with that part.
Hmm does the game itself have a limit?
Because one could do the same issue with 2 vanilla projectors, only difference is you have to blueprint the ship manually which means client has to store and stream the blueprint to the server, unlike here where it's done server side.
https://support.keenswh.com/spaceengineers/general/topic/projector-use-causing-huge-increase-in-sandbox-sbc-size-and-blueprint-block-count-errors
https://support.keenswh.com/spaceengineers/general/topic/projector-storing-nested-projector-data
Reloading the blueprint for a medium sized station now also doesn't lag the server anymore at all.
Thank you very much!