Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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