Emmy Posted March 16, 2018 Posted March 16, 2018 Can't recall seeing this prior to the latest patch + hotfix in 2.5OB. Launch a Maverick and the next seeker is caged at boresight and not already slaved to SPI. Is this new or have I never noticed this before? [sIGPIC][/sIGPIC] http://www.476vfightergroup.com/content.php High Quality Aviation Photography For Personal Enjoyment And Editorial Use. www.crosswindimages.com
Polo Posted March 16, 2018 Posted March 16, 2018 Pretty sure it's always been like this, only the selected Maverick's seekerhead moves at any one time. Ryzen 5800X3D | 64GB DDR4 @ 3600MHz | Gigabyte X570-Aorus Ultra | Gigabyte GeForce 4090 | Samsung C34F791 | Varjo Aero | Windows 11 Pro x64 | Auzentech X-Fi Forte | too many flight controllers...
Emmy Posted March 16, 2018 Author Posted March 16, 2018 It might just be 65Hs. Shot some 65Ds as well, and the crosshairs stayed put on the locked target. [sIGPIC][/sIGPIC] http://www.476vfightergroup.com/content.php High Quality Aviation Photography For Personal Enjoyment And Editorial Use. www.crosswindimages.com
Maverick806 Posted April 14, 2018 Posted April 14, 2018 I've been seeing this myself lately so I did a little testing with AGM-65Ds. What I noticed was: -When you're carrying 2+ per station on an LUA-88 the next rounds are already slaved to the previous target like I was used to. -When you're carrying 1 per station on an LUA-117 the second Maverick is bore-sighted instead of pointing where your first round was fired. Is this expected behavior or a bug? 9800X3D, 64GB DDR5, RTX 3080 Valve Index, RS FSSB R3 Ultra, TM Viper TQS, TM TPR Pedals
Recommended Posts