VIXEN413 Posted July 22, 2022 Share Posted July 22, 2022 Noticed that WACQ does lock stuff up only around 6-7 Nm... was it not supposed to be able to do the job on a fighter sized pkane up to 10Nm? BR Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100, Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD 27" monitor with trk IR 5 and HP Reverb HMD. Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted July 22, 2022 ED Team Share Posted July 22, 2022 Yes 10nm and seems to be ok for me. Please attach a short track replay example if you are having issues. thanks 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...
VIXEN413 Posted July 22, 2022 Author Share Posted July 22, 2022 Hey there, I think the fact that I can get an ACM lock earlier or later depends on target track generation and it is linked with the bug discussed here as well about how the mission computer generates those tracks. first recorded game track I got WACQ lock at around 3Nm and on the second one just around 8Nm. Dunno, it seemed inconsistant today in general. I noticed that, usually when I recommit after a skate or abort, the hafus are dissappearing then reappearing on the ATK RDR and just as they reappear, I guess the mission computer regenerates the track and then I can get a WACQ or ACM lock. By the time, the 10NM mark is past for a while. Irony is that I have a tally way before it gets me an ACM lock... late WACQ.trk late WACQ2.trk Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100, Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD 27" monitor with trk IR 5 and HP Reverb HMD. Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map Link to comment Share on other sites More sharing options...
Kula66 Posted July 23, 2022 Share Posted July 23, 2022 (edited) I too find WACQ mode inconsistent, but I put it down to the length of time it takes to complete a full scan … too many bars and too big an angle to cover; vertical scan and boresight just focus on a much smaller areas of sky. It just depends on where in the scan pattern the target is. Edited July 23, 2022 by Kula66 1 Link to comment Share on other sites More sharing options...
VIXEN413 Posted July 23, 2022 Author Share Posted July 23, 2022 True that but even if it plays with bigger angle and more bars, it is still a reduced scan volume... should not take that much to complete a full swipe of the area, no? can any SME give their thaughts on this? BR Rig: MB Gigabite z390UD, CPU Intel I7 8700k, RAM 32G DDR4 3200 Gskill ripjaws, GPU MSI RTX2080SuperOC, HDD Crucial mx500 1tb M2 sata, PSU Corsair 850W, watercooling Corsair h100, Controlers TM f/a 18 stick on Virpil warbrd base, TM cougar f16 stick on cougar base, Cougar F16 throttle on TUSBA, ch pedals, TM cougar MFD 27" monitor with trk IR 5 and HP Reverb HMD. Modules F18, F16, F86, Mig15, FW 190D9, Nellis range map, Aggr campaign, Middle East map Link to comment Share on other sites More sharing options...
Recommended Posts