Jump to content

Recommended Posts

Posted

what would cause tws to fail to lock a target head on at co alt? 600+ knots closure and not notching/beaming

7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr

Posted

You know that tws doesn’t really display a “lock” as such but just target priority numbers. Also, make sure elevation is correct as you may see datalink targets but not see them on own radar.

Virpil WarBRD | Thrustmaster Hornet Grip | Foxx Mount | Thrustmaster TWCS Throttle | Logitech G Throttle Quadrant | VKB T-Rudder IV | TrackIR 5

 

 

AMD Ryzen 5 3600 | Nvidia GTX 1060 6GB | 32GB DDR4 3200 | SSD

Posted
You know that tws doesn’t really display a “lock” as such but just target priority numbers. Also, make sure elevation is correct as you may see datalink targets but not see them on own radar.

 

yeh, it doesnt display the numbers. im posting this for a friend and ive told him to turn datalink off and see what appears

7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr

Posted (edited)

I've noticed this as well, since the last patch.

 

In fact, since the last patch there have so many gremlins in the whole system. TWS dropping lock. Missiles not tracking. TWS not picking up contacts. TWS picking up too many contact. etc. etc.

 

These have been reported in a number of places, as different issues. It's confusing, because there is a lot of overlap in the issues, while at the same time, many seem different.

 

https://forums.eagle.ru/showthread.php?t=281325

https://forums.eagle.ru/showthread.php?t=280902

https://forums.eagle.ru/showthread.php?t=281286

https://forums.eagle.ru/showthread.php?t=281319

https://forums.eagle.ru/showthread.php?t=281346

 

[EDIT: of course TWS does not lock targets! But you knew very well what the OP meant as much as I did: He meant it's not detecting them or picking them up. ]

Edited by Bearfoot
  • Recently Browsing   0 members

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