安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
Over-night steam reverted all my changes back to the defaults and it's working fine now..
However i did improve the Ballistic arc making it harder to intercept and making it more realistic.
flight phase 4: terminal approach (added 2 settings and changed the approach/dive dist.
TerminalApproachDist=22
TerminalDiveDistance=22
SupportsBanking=True
IgnoreHeightDifferenceForTargetDist=True
True, IR could technically lock a moving vehicle, but realistically nobody is going to be firing a Trident at a Bradley. The way players actually use it is either by manual point-targeting or big static installations, so there’s no real downside, and the new settings added are all set to 0 so it shouldn't be trying to track anything, it should follow the initial point set by the user
genuinely. yes. the same way as it was before, but changing the guidance type and making it so the target doesn't search for ever fixes it for me