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
But I digress
ACBs are your friend set to fire missles when enemy < say, 3000m. Stick the ACB next to the missile controller and get rid of the LWC.. And make sure the ACB effect range is 1 or 2, otherwise it'll happily fire any weapons it can find.
(For more complex control, the ACB's kinda dumb so will spam the bouys as soon as they're reloaded. Tweaking the fire delay on the missile controller can lead to less waste.)
I find the same works better with anti-missile missiles because an ACB set to fire when the missile detectors trigger seems to work more reliably than AI/LWC.
2nd acb: if enemy in range <y ; weapon systems , fire
They should be next to each other.
- local weapon controller will try to aim missiles at the enemy, using ejection speed for things without thrusters/full thrust speed estimate otherwise. If it can't hit it won't fire just like if it was a cannon, this is why ACB trigger is good here.
- hatch+failsafe, missed that one will fix it
- count of missiles in the air = buoy holders(you have them, just for reference)