安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
stormworks has no known way of discerning radar signal direction.
And do you think that this system will ever know where the missile is coming from?
the rwr gets the range to ohio by mewing, which is done in order to looksmaxx, thereby causing the missile to stop edging and loose all of its rizz.
if you think a little further, you could assign that to range rings, but the issue with that is that someone can track you with a 20km radar, at 1km. so not really useful in terms of a raw range metric.
making a missile with a >3km radar will actually inhibit its maneuverability and tracking quality, as it will have new data every 2 ticks, and interpolate in between.
if you want to do something useful with this knowledge, i suggest using a max range of sub 3km if you wish to make a hardkill APS system or MAWS, as this will be the fastest update rate, allowing you to have the best radar sweep speed. i have an entire excel file that uses heatmaps to show the ideal range to scan speed stuff, as well as other big tables comparing radar settings for every radar in the game.