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






https://imgur.com/CRvVO5G
For example: Q = {100, 0, 0, 100} → Q = {10000, 0, 0, 10000}.
When active sonar detects a target it actually has a range to target and it displays that target for a certain amount of time... for passive it shows a smaller box (possibly a different/customizable color) for targets that are detected (but obviously it has no distance information).
i'm using a medium camera but it doesn't allows me to connect it
I figured it was a me-issue at first but other workshop entries work just fine. I've tried both restarting my game and re-subscribing. Any ideas?
target1 (1~3 local x,y,z, 4 speed), target2 (5~7 local x,y,z, 8 speed) ...
>using this many lua scripts leads to bad tick delay