Jump to content

Recommended Posts

Posted

F16_BORE_ISSUE.trk

I have discovered that the F16 using the BORE ACM mode is unable to lock targets outside of 10NM, despite range being set to 40 and the HSD confirming the scan zone of 40NM. This issue has persisted among several tests under different conditions.

Posted

I think that is correct by design as BORE is a WVR function for a quick lock and snapshot.
Cheers!


Sent from my SM-G998B using Tapatalk

W10 Home 64Bit, Intel Skylake I5 6600K 3.50GHz, ASUS ROG Stryx Z270F MoBo, 64GB G.Skill RipJaws V DDR4 3200 RAM, Samsung 960 Pro 512GB M.2 SSD (OS), Samsung 850 Pro 512GB SSD, 2TB Seagate SDHD, 2TB WD Green HDD, Gigabyte 3060 12GB VRAM

  • ED Team
Posted

Deleted my last comment, apparently it can lock outside the 10nm and the team are looking at it internally. 

thank you 

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...