Solved I hope this HARM related problem already fixed in 4.36 / 4.37 and so on
-
Before this, in all KTO with limited Mobile SAM TELAR, I rarely use Harm in a manner like “pretending” the SAM can’t being hit by HARM as long as they stationary, and in “objective with SAM CAPABLE Flag” Mostly SAM in KTO like that. I usually dismissed other AI, to do it by myself far beyond any SAM range with an EOM and TI set at SD (not glide - not flex) into precission steerpoint using “recon”. Kinda bored eh? Even, I use SDB and start from 37nm one viper wiped out 8 stationary single digit SAM. Then, later on, I need some to spice up a bit, so I act GOD by giving mercy into the red (even not realistic) that every SA-2/SA-3 SAM at day 3 I changed into SA-4/SA-6/SA-11 and SA-5 into SA-10. This made the proper employment of HARM needed, cause I do not put them into “SAM CAPABLE Objective”, set them unspot, and untick the “emit”. The result is fantastic, they can popped up at anytime at place even WDP don’t read the SAM location. Made me happy until I realize that :
-
SOI related integration in FCR (Slant range for A-A) messed up after the last harm delivered. This slant range at FCR SOI put in hud will be back into normal in ACM mode a.k.a DOGFIGHT mode. Unless I select dogfight mode, the whole slant range info at HUD, both AA/NAV/MRM will be refer to the steerpoint selected. I realize this in coincidence in my “I do as I like frag mission” named SWEEP but I carry HARM, so that I not only sweep red force jet, but also crush any SAM Radar that dare enough to illuminate me. After sent the last HARM, which is hit (you guys need to nerfed a lot the HARM seeker / logic, especially with Target Isolate describe in your manual), I do charge the SU-35. Bugged them, and I wait my number to execute came up at the HUD. This moment I realize that the slant range from the FCR do not slaved into the HUD info, but, it showed the range from my selected STPT.
-
If carry harm, and already delivered, goes strafing will need a lot of effort and step, caused by SOI integration failed in A/G mode. The TGP can’t be slewed, even I made FCR GROUND slew, the TGP will still locked into the last steerpoint. It happened with carry HTS, and without HTS. I have to go to the NAV, changed the FCR into A/G and TGP also, mark point, then, goes to AG, press long uncage to force into strafing mode. Why strafe? Y’all might ask that? I need that kind of adrenaline tho, cause you boys really made your AI ground troops really “Battle hardened veteran” nerve. Able to shoot back even I blast them with full burner above MACH 1, when strafing at night.
This in dogfight mode
and this in other mode
master arm on / sim / off does not fixed the anomaly, also I’ve tried to reset the FCR and deploy the test, do not resolve the problem. HARM page at SMS power on / off also do not made the problem resolve.
And now, I’ll give you boys a bit clue about HTS based on what I see in real HTS at F16. In BMS, HTS in HAD more or less is just enhanced HSD with a broken SOI integration. In Real, whatever you bugged at HAD, all SOI will pinpoint into that location. By that, carry HTS without HARM on station 3/7 is usefull. Imagine fly with the AI, Human execute the SAM FCR, and at the same time command “attack collateral target” using CBU / Mav.
That’s it. If dev already fixed this HARM at 4.37 then nice. If not, worth to check a bit.
Thank you as always for your attention
Live long and prosperPS: That’s screenshot taken from 4.35U3
-
-
@GP1508 still on 4.35?
there have definitely been some bug-fixes that involved messed up SPI after launching the final HARM… I don’t remember if that was fixed in 4.36 or 4.37. but I’m going to go ahead and mark this as ‘solved’.
-
-
@airtex2019 I hope already fixed sir. I just notice this through 3000 hours at 4.35. I just so comfort in 4.35.