SharpeXB Posted August 19, 2021 Share Posted August 19, 2021 (edited) The radar consistently loses lock in TWS mode. Tracks attached. Stable version 2.7.5.10869 lostlock3.zip Edited August 19, 2021 by SharpeXB i9-13900K @ 6.2GHz oc | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | 24GB GeForce RTX 4090 | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted August 19, 2021 ED Team Share Posted August 19, 2021 Hi SharpeXB Have you seen this video yet? it may help 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
Hulkbust44 Posted August 19, 2021 Share Posted August 19, 2021 Make sure you have increased the brick timeout on the data sublevel. ED incorrectly modeled it to where the entire trackfile is deleted after the specified timeout. Only bricks should be affected.Mobius708 1 2 Link to comment Share on other sites More sharing options...
SharpeXB Posted August 20, 2021 Author Share Posted August 20, 2021 2 hours ago, BIGNEWY said: Have you seen this video yet? it may help I’ve seen that. And read the manual etc etc. I don’t see why when you’ve locked a target it continually gets unlocked unless it was notching or something. These aren’t. The only other A2A radar I use is the M-2000C and it never does this. You lock a target and lock means lock. i9-13900K @ 6.2GHz oc | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | 24GB GeForce RTX 4090 | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
Solution opps Posted August 20, 2021 Solution Share Posted August 20, 2021 (edited) 1. You are using TWS MAN. This means RADAR tries to track contact but won't adjust azimuth and elevation. You have to adjust those to maintain track in this mode. TWS AUTO automatically adjust azimuth and elevation to track L&S target. Use TWS AUTO. 2. Set TARGET AGING. This is clearly explained in above wags video and @Hulkbust44 's post. Default aging setting is by no means usable. I always set TARGET AGING to 16 and TWS AUTO track L&S target just fine in BVR regime. Edited August 20, 2021 by opps 1 2 Link to comment Share on other sites More sharing options...
SharpeXB Posted August 20, 2021 Author Share Posted August 20, 2021 2 hours ago, opps said: 1. You are using TWS MAN. This means RADAR tries to track contact but won't adjust azimuth and elevation. You have to adjust those to maintain track in this mode. TWS AUTO automatically adjust azimuth and elevation to track L&S target. Use TWS AUTO. 2. Set TARGET AGING. This is clearly explained in above wags video and @Hulkbust44 's post. Default aging setting is by no means usable. I always set TARGET AGING to 16 and TWS AUTO track L&S target just fine in BVR regime. Thanks, that solved it. 2 i9-13900K @ 6.2GHz oc | ASUS ROG MAXIMUS Z790 HERO | 64GB DDR5 5600MHz | iCUE H150i Liquid CPU Cooler | 24GB GeForce RTX 4090 | Windows 11 Home | 2TB Samsung 980 PRO NVMe | Corsair RM1000x | LG 48GQ900-B 4K OLED Monitor | CH Fighterstick | Ch Pro Throttle | CH Pro Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
Recommended Posts