Gneckes Posted February 19, 2021 Posted February 19, 2021 (edited) Only seems to happen in the A-10C and A-10C II, so i'm posting it here. See attached tracks - in the third track, the second missile does hit, so it may be related to the range at which the missile is fired. Edited February 19, 2021 by Gneckes
ED Team BIGNEWY Posted February 19, 2021 ED Team Posted February 19, 2021 Hi the track replays show the F-14 for me, are they the correct ones? 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
Gneckes Posted February 19, 2021 Author Posted February 19, 2021 Sorry, I messed up. This track should work: a10cforcecorrelate_miss.trk
ED Team BIGNEWY Posted February 20, 2021 ED Team Posted February 20, 2021 It looks like a range issue to me, you are correlating outside maximum range. 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
Gneckes Posted March 3, 2021 Author Posted March 3, 2021 Here's another trackfile showing the issue - in this case, force-correlating a point on the ground (the runway numbers) is a hit even when correlating and launching from beyond maximum range, but when correlating an elevated part of a building (the radar dome of the tower at the airbase), even when doing so well within range, is a miss. It seems to me the missile is actually aiming at the ground behind the target. a10cforcecorrelate_miss5.trk
Recommended Posts