Foka Posted June 3, 2021 Posted June 3, 2021 When designating target form HARM PB mode, designating O/S from WPT does'nt move aimin cue line to O/S point, it stays with original WPT. It work correctly with JDAMs. Hornet HARM OS.trk 1
Binary Posted December 15, 2021 Posted December 15, 2021 I've noticed the same. It is also not just the aiming cue that is off, the HARM does also go to the original waypoint and not the offset designation when fired (I've made sure to designate the offset and not the original waypoint). Author of Scratchpad, DATIS, and maintainer of DCS-gRPC.
ED Team BIGNEWY Posted December 16, 2021 ED Team Posted December 16, 2021 I have a report open with the team to check offset 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, PIMAX Crystal
RedLion Posted April 27, 2022 Posted April 27, 2022 (edited) Dear Aviators, I'm not sure if this is wrong behavior or bug or correct as is, anyway I couldn't find anything in the manual 1. I designate the O/S waypoint as a target and can see the diamond showing on the HUD 2. Then I setup HARM in PB mode Here is the deal, HARM's azimuth steering line still point in to the original waypoint and ignores the offset target. Any help is welcome! Edited April 27, 2022 by RedLion
Foka Posted April 27, 2022 Author Posted April 27, 2022 1. Already reported. Bugs section is the place for such posts: 2. Now it even ignores WPT... sort of. Searching head of the missile is active much earlier then it was. It was activating ~10 nm before WPT, now it's much more... I don't know... 30 nm? 40?
Recommended Posts