CCIP release somtimes disabled by previous ANF mode actions

[Machalot]

When I carry high drag bombs for PLAN bombing, I like to use ANF to see the waypoint circle on the HUD to help me visually locate the target.  Once I have the target, I switch back to NAV and execute a CCIP run.

 

I found that if you are in ANF mode when you UNSAFE the trigger, it prevents any subsequent weapon release after switching back to NAV mode.  Steps to reproduce:

• Carry high drag bombs
• PLAN mode
• NAV mode with trigger SAFE
• Switch to ANF mode to locate target
• With target in sight, UNSAFE trigger (I realize this is probably nonstandard)
• Switch to NAV mode
• Place CCIP symbols over target
• Press Weapon Release trigger
• HUD symbology switches to "trigger down" display
• Bombs do not drop
• Trigger SAFE and then UNSAFE again
• Press Weapon Release Trigger
• HUD symbology switches to "trigger down" display
• Bombs do not drop

 

It's like the computer is locked into the wrong mode.  Once this happens, the only way I found to get unstuck is to:

• Switch to ANF
• Trigger SAFE (these first two steps can be reversed)
• Switch to NAV
• Trigger UNSAFE
• Press Weapon Release Trigger
• Bombs drop

 

Track attached.

AJS37_ANF_Unsafe_disables_NAV_CCIP.trk

[Machalot]

@IronMikeForgot to tag you. 

 

This "feature" caused me to fail a few missions lately on multiplayer. After flying 15 min through hostile territory, I flew over the target and failed to drop bombs on multiple passes, with no idea why it was failing, before finally getting shot down by SAMs. 

[Machalot]

It also bugs if you are in NAV with the safety open, then momentarily switch to ANF to spot the target, and back to NAV.  The CCIP symbols remain on the HUD, but weapon release does nothing.

[IronMike]

On 10/12/2021 at 5:23 PM, Machalot said:

@IronMikeForgot to tag you. 

 

This "feature" caused me to fail a few missions lately on multiplayer. After flying 15 min through hostile territory, I flew over the target and failed to drop bombs on multiple passes, with no idea why it was failing, before finally getting shot down by SAMs. 

Sorry for the very late reply, the previous patch and a subsequent trip kept me away from forums. It is tracked now and we will look into it. The team squashed a couple dozen (or more) of the one's you guys had reported previously, I am sure you will be happy to hear. Thanks again for your great input!