Gattling

A trackfile/short video might be useful.

Many a times I thought of writing something on similar notes. I am glad I didn't do that. I would never have managed to explain it all the way you have done it. Hats off for that. In a contest between mildly skilled pilots, the most widely used BVR missile has literally come down to a visual engagement choice of weapon. The BVR engagement of AMRAAM instead of starting from MELD and gradually shrinking down to MAR starts of with jugglery and non-realistic ultra low-level maneuvers to sneak through the valleys, sometimes with the 100 accurately modeled RWR notches; disregarding every potential of the missile and every fundamental of the engagement, here you are at 100 feet AGL at less than 5 NM and now firing a ton load of steel at each other to have some high Pk shots. The current state needs to be looked into, I believe. Where defensive maneuvering definitely needs serious skill to be executed, but while disregarding every other fundamental principle of BVR engagement, it must not ensure 100% survivability in every given circumstances.

1. You can do that but the feature isn't very well optimized for the A-G attack profiles. The proximity and step up logic will cause steer points to change at occasion where you won't wish it to do that. Probably, suitable only for ML or HL navigation profiles only. 2. Yes, the initial positioning will be affected by that but then the slewing option is available for the same purpose. Acquire the point visually, slew the existing symbols to the exact location and TMS Fwd. All inherent errors of INS/GPS are now corrected for all points in concern. 1. Like I said in my previous post, they are PRIMARILY Non-Visual Bombing Modes and caters for any scenarios in which direct visual contact isn't assured n all cases and situation may develop into any other variation. Any other utilization would be extrapolation and further uses of the tool. 2. Yes, an ideal attack will always have a target as a steer point with exact co-ordinates and elevation data and a lovely weather/outside factors to execute the planned profile.

I believe I misunderstood you at the first instance. Have gone through the discussion and Track file once again for more deliberate understanding. The HMCS display must stabilize in the HUD FOV during Az/El and Roll alignment modes as soon as they are mode-selected. If they are behaving in any other way (as shown in your trackfile), it's likely because of some error.

This is a good example of the feature. What most tend to forget in the discussion of the VRP/VIP is the fact that they both are primarily NON-VISUAL bombing modes in lesser accurate co-ordinate scenarios when direct visual contact with one point (RP/TGT) can't be established either because of night, IMC conditions, camouflage etc. whereas the other point (TGT/IP) has better probability to be acquired because of distinct features or has more accurate co-ordinates available. If this is not the case and you are attacking in an ideal world of accurate co-ordinates and lovely weather, target steerpoint can also be used as a primary option. In this case the only benefit of VRP/VIP will offer is to avoid changing steer points in a time compressed environment and additional cues available in HUD/HMCS before starting the actual attack sequence for better SA. (As explained by TheBigTatanka above in his Para 3)

I just saw your track file and then tried HMCS alignment on ground, then in straight and level flight and later during turn. It works fine for me, the way I believe it's supposed to do. Try doing the alignment by actually putting in a turn instead of tilting your head too much while the aircraft is still straight. You are putting a error by yourself by that head tilt.

That would really be great as after all Locator is inherently a part of the PDLT for it's optimum utilization. Thanks for the update!

This will probably answer most of your questions. Broadly, i will try to cover all in the thread up till now 1. FCR going STT through PDLT - Yes, Take FCR cursor on t and do TMS Fwd. Remember a single target can't be a PDLT and FCR Target at the same time. So as soon as you command FCR lock, PDLT will be lost. 2. AMRAAM through PDLT - No, 120C needs FCR lock. 3. Wingman to engage PDLT - Only if he targets him with his FCR Remember, PDLT is a Link 16 function and can't be replaced with scenarios which needs FCR targeting. 4. PDLT lost case - Some extrapolation time i suppose will be there. But if situation gets prolonged (say around 10-15 seconds) PDLT will be lost. it will not ideally be reacquired once the contact come up again rather to be done manually again.

Pilot Roster - Last updated on 03-03-2022/1330Z Blue Force SEAD F-16 x 4 [NMS]MonoFteros [NMS]Kingsgate 2 x GTAG SWEEP F-15 x 2 [TaktLwG66]Brainiac [TaktLwG66]PeeJott SWEEP F-18 x 2 [PTF]Kula [PTF]Wake SWEEP F-16 x 4 [NMS]Vetis [NMS]Aeolus 2 x GTAG ESCORT F-18/F-16 x 4 2 x GTAG - F-16 1 x TopHatters - F-18 [PTF]Shaheen STRIKE F-18 x 4 4 x TopHatters STRIKE M2000C x 2 [PTF]Predator eeValDeeVal ATC + GCI x 2 2 x Free Slot Red Force JF-17 x 4 [PTF]Falcon [PTF]Zeus [PTF]Spark [PTF]Nitto Su-33 x 4 [100th]Breakshot [100th]Rich [100th]Frostie [100th]BlackPixxel SU-27 x 2 [51st]Roofies [51st]Stinger J-11 x 2 [PTF]Magnet 1 x Free Slot Mig-29S x 2 [51st]Teknetnium [51st]Yambo Mig-21 x 4 [PTF]Sheikh [PTF]Fascar 2 x Free Slot ATC + GCI x 2 [51st]Shamansky 1 x Free Slot

Great. Thanks..!

Thanks a lot for the deliberation. So, what i understand up till now; Early release Viper is limited to target/lock and subsequently do a valid BVR launch only one contact in SAM mode instead of 4 I guess in actual. Correct me if anything wrong in this statement. Goalposts; i think, the term for the blue Az bars.

Yes. Its pretty much same. But the cursor is unable to move and I cant target multiple contacts without that. I guess, single TMS Up should not narrow down the Az and lock the cursor. Is it early release limitation or some input problem at my end?

I have tried it under various own and target conditions and at multiple ranges but the result is always same. it directly goes into STT mode as if getting a twice TMS Up command. The FCR remains in STT and with no obviously no cursor and narrow Az. Similarly a single TMS Aft rejects the target altogether as if getting a twice TMS Aft command.

I am encountering this problem of Radar going to STT mode with single TMS UP command. I guess it should do that with twice TMS UP only. Anybody with similar problem or troubleshoot? Thanks.