drew03tx Posted November 23, 2019 Posted November 23, 2019 hey guys i need some help as im about to pull my hair out with this thing. It seems like EVERYTIME i see a RED indicated target on my attack radar screen, ill slew my TDC over the target, press Enter to enter STT and behold, this damn thing locks up a target thats either 99 miles away, when i was scanning around 40mi, OR itll lock up a friendly plane that was close in range to the enemy i was trying to lock....please help as im tired of firing on friendlys, and im sure they are tired of it too haha.
Harker Posted November 23, 2019 Posted November 23, 2019 That's a known bug. If there's another contact along the same azimuth, the radar might lock that instead. That shouldn't happen, the radar should respect both azimuth and range. Another thing, are you sure that the red diamond is a contact detected by your radar? It might be a datalink contact only, in which case, your radar doesn't see it and can't lock it (and chooses to lock something else instead). Does the diamond have a number inside (trackfile priority)? The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
drew03tx Posted November 24, 2019 Author Posted November 24, 2019 no it doesnt, after doing some reading i realized part of the problem is what you said, its just a datalink icon, however im still having a lot of trouble locating targets based on the BRA callouts from Awacs, i typically can only find targets within 15 miles using ACM modes if i get lucky enough not to get shot down first...
Harker Posted November 24, 2019 Posted November 24, 2019 You mean that they aren't getting picked up by your radar? It can be more difficult with low-flying targets. See if you can narrow your search pattern to something like 60 deg/6 bars around the expected azimuth of the target. I usually keep mine at 140/4, 140/2 or 80/4, but 60/6 might help locate a target that's out of your altitude coverage. Don't forget to change the antenna elevation as well. You can also go to the SA page, if the target in on your datalink, place the TDC over the target and get exact BRA and heading information, to make your search easier. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
GrEaSeLiTeNiN Posted November 24, 2019 Posted November 24, 2019 The solution I have found is to set PRF to High. I use to have the same problem. I had the right azimuth and scan elev but my ownship radar just wasn't picking up the contact. But once I switch PRF to High, my radar would pick up the contact quickly. AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4 TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | My HOTAS Profiles
raelias Posted November 25, 2019 Posted November 25, 2019 I hava the same issue of sometimes the target getting locked is another one further away on the same azimuth, it's really annoying Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf
VIKBELL Posted November 25, 2019 Posted November 25, 2019 I too am having this issue... There are 2 categories of fighter pilots: those who have performed, and those who someday will perform, a magnificent defensive break turn toward a bug on the canopy. Robert Shaw
Recommended Posts